| > Is there a foolproof method of installing the RAMDISK and editting the
> PROFILE so that it works and even a software unsophisticate like myself
> can make work?
No computer program is foolproof, because fools are so ingenious.
The MWC RAM disk trips up a lot of people, because it is so poorly documented.
In your case, since you autoboot your HARD DISK, you want to create a RAM
DISK that is NOT a boot disk. Because it is easier to document command
line things in a NOTES file, I will give you command line instructions. I
assume you want the RAM disk to be a 200K disk as drive letter F:
1. Put RDY.PRG and RDY.RSC in the top level C:\.
2. Run MSH.PRG.
3. To MSH, say the following, and observe the use of upper/lower case:
cd c:\
rdy BOOT=0 CMD=MAKE DISK=F SIZE=200 FILE="TEMP.PRG"
temp
The system will now reboot.
4. (This whole step is optional, but is a good idea.) Use the desktop
"install drive" feature to create an icon for drive F:. Do this by
selecting any other disk drive (it turns color), and select the
"install..." item from the ,"options" menu. When the form comes up,
change the drive letter to F and the title to "RAM DISK", and be sure to
click on INSTALL (the default is CANCEL). Save this new desktop.
5. Run MSH.PRG, and say:
cd c:\
mkdir F:\TMP
rdy CMD=SAVE FILE="C:\AUTO\DISKF.PRG"
6. Using your favorite editor (Microemacs 3.10_J?), edit PROFILE, and find
the definition of TMPDIR. Delete all the junk that tries to figure out if
you have a RAM disk or not, and just say:
setenv TMPDIR=f:\tmp
You should be all set now. Next time you power on your system, the ram
disk will automatically load. Note that when the RAM disk loads, the
system will reboot, so your system may appear to boot twice.
|
| I've noticed that when I reboot from a RAMDISK (MWC), drive A gets
accessed for a brief moment (reading boot block?) then the light
goes off, and everything comes up fine.
BUT, the drive A floppy motor keeps spinning! The light is off
though... Has anyone else seen this?
_John_
|