Every system has been shipped with a preprogrammed NVsRAM for the type of system expected, that is, with or without an MFM hard drive system installed. The NVsRAM is bootable and is designed to be the primary boot device. However, should you desire to change the NVsRAM's programming or if the NVsRAM should lose it's programming for some reason, it can be easily reprogrammed.

The NVsRAM chosen for distribution was the Texas Instruments BQ4850YMA, a 512Kb NVsRAM (non-volatile static RAM) model with real time clock. The Dallas DS1647Y model has similar capabilities and is a direct replacement, if necessary. While these models use only 32 pins, the 36-pin socket was installed to allow using the larger 1024Kb models from both companies. However, if these models include real time clocks, additional hardware and software is required to process this capability. Some clock models include alarms and wakeup capability!

CAUTION: When installing the 32-pin NVsRAMs, ALWAYS leave the four empty pins of the socket to the LEFT! A jumper, located just above the NVsRAM socket, is also required to be modified and jumpered to accommodate the 36-pin units.

Note: Another 2-pin jumper is located just above the NVsRAM that can be cut to ensure write protection to the NVsRAM. When the trace between the pins is cut on the back of the board and a jumper is NOT installed, the NVsRAM will be WRITE-PROTECTED.

The easiest means of reprogramming the NVsRAM is to reload the original programming, using the utility EPWRFILE and a disk image file, EPTEST.DAT. For those individuals who ordered IDE devices with their IDE controller boards, the EPTEST.DAT file was already created by me and saved in two directories on the IDE device: \EPROMPGM (Eprom Programming) and \ORGEPROM (Original Eprom). For those installing their own IDE devices, I recommended in the installation procedures that you do the same using the procedures provided in the next section.

Drive LED Indicator: Located to the left of the IDE connectors is a row of Light Emitting Diodes (LEDs) on the top edge of the board. From left to right, these indicate:

-- NVsRAM Read Operation. This green LED lights whenever the NVsRAM is being Read.
-- NVsRAM Write Operation. This red LED indicates NVsRAM Write processes and
    should only illuminate when the NVsRAM is being written to.
-- IDE1 Master Read/Write. These work like typical hard drive LEDs.
-- IDE1 Slave Read Write.
-- IDE2 Master Read/Write.
-- IDE2 Slave Read/Write.

This indicator is a plugin device that may be replaced with leads to a front plate indicator, if desired. The two right-most pins are left unused and may be connected to a remote Breakout Switch, if desired.

Creating an NVsRAM (Eprom) Image File - EPTEST.DAT

1. Create two subdirectories on your IDE or MFM drives: \ORGEPROM and \EPROMPGM.

2. Copy all the NVsRAM files to BOTH of these directories.

3. Finally, change the default drive to one of these partitions and run the EPRDFILE utility.
    This utility will create the file EPTEST.DAT containing an image of the NVsRAM's programming in the file.

4. Copy the EPTEST.DAT file to the other subdirectory as a backup.

NOTE: The EPWRFILE uses the image file created by EPRDFILE to reprogram the NVsRAM on the IDE Controller Board. However, it presently appears that we cannot run EPWRFILE with the data file, EPTEST.DAT, located on an IDE device. If the data file is stored on an IDE device, EPWRFILE will appear to work properly, with the IDE LED flashing and it will report that the file was successfully written to the EPROM (NVsRAM), however, if you look carefully you will see that the red NVsRAM LED is NOT flashing, and the file was NOT written to the NVsRAM. Be sure to copy all the programming files, including the EPTEST.DAT file, to an MFM hard drive or create a 3.5" floppy disk and store them there.

Reprogramming the NVsRAM (Eprom) from the EPTEST.DAT file:

1. If able, boot to the NVsRAM (Eprom) as usual and change the default drive to the MFM hard drive
    or 3.5" floppy drive containing the reprogramming files.
2. Run EPWRFILE and watch the red Eprom programming LED to ensure the operation is working.
3. Reboot to the NVsRAM (Eprom) as usual using the command {B}oot {F4}s. If the programming was successful, the system should boot to the NVsRAM.
4. If that was not successful, proceed with the following procedures:

Reprogramming the NVsRAM (Eprom) using the Programming Configuration Procedures:

1. Boot to the MFM drives or the Z-DOS v4.06 floppy disk.
2. Interrupt the boot operation when the computer asks to load an alternate Configuration File (you have 3 seconds to press any key).
3. Press {P} to set the Programming Eprom procedures.
4. A new line will be added to the Boot screen:
    F: EEPROM /CLOCK(Programming)

5. Note the new drive letter listed for programming the Eprom, as you will need this later.
6. Change to the MFM \EPROMPGM directory or to the 3.5" reprogramming Floppy created earlier.
7. Run EPROMPGM X:, where the X: is the drive letter for programming the Eprom.
8. Once completed, the NVsRAM will be completely programmed and hopefully bootable.
9. Reboot to the NVsRAM using the command: {B}oot {F4}s 10. If successful, return to the programming directory or 3.5" reprogramming Floppy and run EPRDFILE to update the EPTEST.DAT file. Hint: You can change the name to another file name to protect the original EPTEST.DAT file, in case you need to return to the original programming for some reason. Might I suggest EPTEST.01, etc.
11. If not successful, please repeat the procedures, or call me.

Changing the programming of the NVsRAM (Eprom):

To change the programming of the NVsRAM on the fly, be sure to reboot in the programming mode, copy or delete any files to the NVsRAM as necessary, and finally run CHKSUMEP to create a new checksum on the NVsRAM. However, there is the possibility of really messing things up. I highly recommend just editing EPROMPGM.BAT with EDLIN or another line editor and simply following the above procedures. It does everything automatically.

Closing:

I hope you found this document useful. I have found this new booting capability to be extremely fast and reliable and hope you do also. If you have any questions or need help, don't hesitate to e-mail me at the link below.