These neat, small and very quiet pizza-boxes are fun to use, especially with a VAX driving them from behind the scenes (a VAX is not required to boot and use them, though). Getting them was easy enough, but getting them up and running was quite a lengthy process. Mainly because they insist on being feed with some operating system prior to be willing to serve.
Unless you're prepared to dig deep into the darkest holes of the internet, you might prefer to contact us via mail about the issue of getting an image of this OS.
Instead of listing some rather not helpful technical specifications, we'll discuss the topic of getting them up and running. How about that ?
Warning: The procedures explained below might permanently damage your VXT, wreck any electronic device around, unearth some daemon, explode your TV or otherwise disrupt what you might call your normal way of life. We're not responsible for any results of following our advice. No way. You've been warned.
3.1 When you might skip this section
There's a good possibility, that your VXT is already set up to boot via MOP. If you happen to see something like the following on your screen a moment after turning on your VXT, then you might skip to section 4 (unless you need to find out about your VXTs MAC adress. See section 3.2 for that, if the adress is not displayed long enough during the memory check). If things don't work out, come back and follow the procedure.
VXTBOOT 2.. -EZA0 1.. MOP V3.. MOP V4..
If you get something else, then we possibly need to change the configuration of the box.
3.2 Getting the MAC address of your VXT
Having said that, powercycle your VXT, and press <CTRL>-<C> until a chevron (">>>") appears on the screen. It's more a question of picking the right point in time, than hammering the keyboard.Now that you're there, you might want to play a bit (enter "help"), for example. Afterwards use the "sh dev" (short for "show device") command for getting the MAC adress of the build-in ethernet NIC. The list should roughly look like this:
>>> sho dev VMS/VMS ADDR SOME OTHER MUMBO JUMBO ------- ---- ---------------------- ESA0 08-00-2B-3F-40-32The example above carries the MAC adress of one of our own VXTs.
3.3 Reset to factory defaults
As a starter, we'll now reset our VXT to factory defaults. If you don't like the idea of doing this, you might skip this step.
>>> TEST/UTIL 1The screen will flicker, and the VXT will startup.
3.4 Selecting the boot methodAfter the box is back up, powercycle and get a chevron, again. First, we need to clear the currently selected boot method, having the VXT try all methods it knows:
>>>B/10000The VXT will try to boot, again. Let it search, and move over to your VAX.
4. Preparing your VAX mop server
That's really easy. Here's a log of how to do that:
mkdir -p /tftpboot/mop cp VXTOSIMAGE.SYS /tftpboot/mop cd /tftpboot/mop ln -s VXTOSIMAGE.SYS 08002b3f4032.SYS /usr/sbin/mopd -aNote, that you should use the MAC adress of your VXT as the target filename for the link instead of ours, of course.
5. Customize your VXTPowercycle your VXT, and see it booting of your VAX. After the Terminal Manager is up (you might have to press F3 to get it on screen), select Customize->Communications->TCP/IP to set up some basic TCP/IP configuration values for the box.
After you've configured all the setttings to your likings, you're ready to go. On your Vax (or any other machine) try xterm -display MyVXT:0, for example. Try Customize->Security->Connections Allowed in case you get some refusals (set the radio button to "All").
6. Hints, helpful resourcesGoogle is your friend, as always. Try searching for "VXT manual", for example. A short list of commands useable at the chevron is provided below:
Reset the terminal password:
To be continued ...
All trademarks are the property of their respective owners.