|Announcement date:||October 1983|
|FRS date:||late 1984|
|OS support (VMS):||MicroVMS V1.0 to VMS V5.0-2|
|OS support (ULTRIX):||ULTRIX/VAX V1.0 to ULTRIX/VAX V2.4?|
|Number of processors:||1|
|Translation-buffer:||512 entries |
|Q-bus:||1 @ 3.3MB/s|
The MicroVAX I was the first of a number of MicroVAX models from DEC. It used the QBUS as its primary bus between the CPU (the KD32 CPU) and main memory, the only VAX to do so. It was said to be the slowest VAX ever (about 0.25 VUPS), even slower than the VAX-11/730 resp. VAX-11/725.
Boot ROM Restrictions
See the instructions from: AA-KM46A-TN MicroVMS 4.6 Installation and Operations, Chapter C.1 Creating a Console Diskette:
The console diskette will contain files used to bootstrap from a disk attached to the second MSCP controller. Use the following steps to create a console diskette. This example assumes that the first RC25 disk attached to the second MSCP controller (DABO) will be the new system disk:
- Log in to the system manager's account, SYSTEM.
- Check the first diskette drive to ensure that it is empty and inactive; the red diskette activity light should not be glowing. If there is a diskette in the drive, remove it following the instructions in Section 3.1.11.
- Label a scratch diskette CONSOLE DISKETTE. A scratch diskette is a new diskette or a diskette containing no information that you want to save.
- Enter the following command to invoke the command procedure that creates a console diskette for a MicroVAX I system:
- What system disk do you want to be able to boot from? DABO
- Ignore the informational messages displayed on your terminal screen. The procedure prompts you for the name of the diskette drive on which the intermediate media (console diskette) will be mounted. In this example, the media is mounted in diskette drive 1 (DUA1).
Where will the intermediate RX50 media be mounted? DUA1
- Insert the diskette labeled CONSOLE DISKETTE into drive 1 and enter YES in response to the following prompt:
Are you ready? YES
- When it has finished building the console diskette, the system displays the following message:
The media on DUA1 may now be used to boot device DABO
After you create the console diskette, write-protect it to prevent anyone from accidentally overwriting the contents. To write-protect a diskette, cover the square notch in the upper-right comer of the diskette with a silver tab. Note that in order to bootstrap the system, the console diskette must be in diskette drive 1.
You may want to add the following command to the end of SYS$MANAGER:SYSTARTUP.COM to mount the console diskette automatically every time you bootstrap the system. This prevents other users from removing the diskette thinking that the drive is not in use.
$ MOUNT/SYSTEM/FOREIGN $FLOPPY1 INTERMEDIATE
The command procedure SYS$UPDATE:VMBUVAX1.COM and other files needed might not be on the system disk depending on the option used when the system was installed.
You can install the missing components using:
$ @SYS$UPDATE:VMSINSTAL UTIL $TAPE1:
The tape (resp. tape image) AQ-FP13D-BN_MICROVMS_4.6_87 must be loaded (resp. attached to) the TK50 tape drive beforehand.
Answer all questions with N:
* Do you want to install the entire kit: N * Do you want to install the MAIL utility: N * Do you want to install the SEARCH utility: N * Do you want to install the DIFF utility: N * Do you want to install the DUMP utility: N * Do you want to install the RUNOFF utility: N * Do you want to install the PHONE utility: N * Do you want to install the MicroVMS HELP library: N * Do you want to install the Remote terminal support via SET HOST/DTE: N * Do you want to install the Foreign Terminal Support: N * Do you want to install the LAT-11 terminal server support (via Ethernet): N * Do you want to install the Stand-alone backup on system disk support: N
* Do you want to install the MicroVAX-I bootstrap that works for any MSCP system device: Y
You should now be able to set up the special boot diskette for booting from a disk attached to the second MSCP controller.
Supported Boot Devices
Boot ROM Characteristics
- Microverify is the name given to the diagnostics executed by the MicroVAX I boot ROM. There are three LEDs on the DAP module and a seven segment display on the patch panel which will isolate the problem (if any) to one of the two CPU modules.
- Floating Point Instructions in Microcode
- No TOY Clock
There are a lot of MicroVAX I Options; some of them are not "officially supported", but work nevertheless.
The MicroVAX I uses standard Q-bus memories which are not as fast but are also less expensive and usable by both the MicroVAX I and other 16-bit processors (such as the MicroPDP-11). There are 22 address lines on the Q-bus, limiting maximum memory to 4 MB.
- MSV11-P Parity Memory
- MSV11-Q Parity Memory
- MSV11-M Parity Memory: not supported and not yet tested, but supposed to work
- MSV11-J PMI ECC Memory: not supported, but working! (-JD and -JE variants only; the -JB and -JC will not work)
- MSV11-R PMI Parity Memory: not supported and not yet tested, but supposed to work
Mass Storage Options
- RQC25 RC25 Disk System with Qbus Controller, made of:
It is currently unknown/untested whether the 'real' MicroVAX I supports the RLV12 controller as well.
Anyway, booting from an RL01/RL02 is not supported by the MicroVAX I boot ROM.
- VCB01 Monochrome Video Subsystem
MicroVAX I is the only MicroVAX model with "old-style" VDS (Vax Diagnostic Supervisor) diagnostics.
Sample MicroVAX I Boot Messages (MicroVMS V4.6)
These messages are taken from my 'real' MicroVAX I:
MICROVERIFY STARTED MICROVERIFY PASSED 00000000 03 >>>B DUA0 ATTEMPTING BOOTSTRAP MicroVMS Version V4.6 6-Jul-1987 17:00 PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM) 28-MAR-2022 8:28 The MicroVMS system is now executing the system startup procedure. The MicroVMS system is now executing the site-specific startup commands. %RUN-S-PROC_ID, identification of created process is 00000015 %RUN-S-PROC_ID, identification of created process is 00000017 %SET-I-INTSET, login interactive limit = 64, current interactive value = 0 SYSTEM job terminated at 28-MAR-2022 08:30:57.94 MicroVMS V4.6 Username: SYSTEM Welcome to MicroVMS V4.6 Last interactive login on Saturday, 3-DEC-2022 17:59 Last non-interactive login on Monday, 3-JUN-2013 15:41 Main Menu 1 - Exit to DCL 2 - Log out of the SYSTEM account 3 - Invoke the MAIL utility 4 - Invoke the PHONE utility 5 - Add a user account to the system 6 - Install optional software 7 - Add or Delete a MicroVMS component 8 - Create or Modify an Autologin Terminal 9 - Back up or Restore the user files on a disk 10 - Build a Standalone BACKUP kit 11 - Set the maximum number of interactive logins 12 - Configure the network 13 - Shut down or start up the network 14 - SHUT DOWN the system Enter a number (? or ?# for HELP): 1 If you wish to use the menus again, type the following: $ @SYS$MANAGER:MGRMENU $
- MicroVAX I - documentation at Bitsavers
- VAXstation I Technical Reference Manual (EK-VS200-TM-PRE)
- MicroVAX I Owner's Manual Release Notes (EK-KD32A-OM-CN1)
- Supermicrosystems Handbook - the MicroVAX I is covered on pp. 2-4–2-5 (pp. 19-20 of the PDF) and elsewhere
- Differences between the MicroVAX I and the MicroVAX II CPUs (MicroNote #022)
- The MicroVAX I Data-path Chip
|v • d • e VAX Computers and Operating Systems|
|VAX-11/7xx (including VAX 86x0) - VAX-11/780 • VAX-11/785 • VAX-11/750 • VAX-11/730 • VAX 8600 • VAX 8650|