ramdisk /q nohigh size=4096 R:
Well, the first thing that you did wrong, was to tell it to create a 4 GB RAMDISK BELOW the 4 GB mark. You really don't want to do that. Then, "size" is not a valid parameter, and even if it was, you don't have 4 GB free below the 4 GB mark. The command that you want is: "ramdisk R:" (without the quotes). That will create a FAT32 drive (but I never tried more than about 1.5 GB, since I only have 5 GB on my biggest system).
I think the previous post takes you to the wrong place. There is some discussion, but that is not the thread where i described how to do it. The thread where I described how to do it is a bit confusing because it was created as I worked my way through the project.
A simple (I hope) summary:
1) Get the package. The latest should always be;
ftp://212.12.30.18/public/QS/QS_LDR.ZIP.
2) UnZip it someplace.
3) Use ATTRIB -H -R -S to make OS2LDR visible, and not protected (you can put that back later, if you like, but it is not necessary). COPY your original OS2LDR file to OS2LDR.IBM
4) Put OS2LDR and QSINIT.LDI in the root of your boot drive (replacing the original OS2LDR file).
5) Put \ramdisk\hd4disk.add into \OS2\BOOT.
6) Create a file os2ldr.ini in the root of the boot drive. It should contain something like:
[config]
default=2
timeout=4
[kernel]
OS2LDR.IBM=Original boot, RESTART
os2krnl=Default boot
os2krnl=Show driver names, ALTF2
This creates your QSINIT boot menu, and it will default to make QSINIT boot the os2krnl (unless you hit a key), after 4 seconds. READ the docs for the details.
7) Create a file QSSETUP.CMD. This is effectively the STARTUP.CMD for the QSINIT loader. It resides in the root of your boot drive. You want a RAMDISK, above the 4 GB mark, using all available memory. QSETUP.CMD should contain one line:
RAMDISK R:
7a) (I almost forgot) Put the line:
BASEDEV=hd4disk.add
in CONFIG.SYS. I put it immediately after AHCI, or Danis (depending on what I use).
8 ) Okay, now you should be able to boot, and a drive R: should be a FAT32 drive on your system (you do need the FAT32 driver installed, but I suggest that you do NOT use the FAT32 cache program (no point, and it only causes trouble).
9) I find that using FAT32 is probably not the most desirable solution, so I take a few extra steps to convert it to JFS. The trick here is that you need to format the drive, before the WPS starts up, then, you need to unmount, and mount, it again after the WPS starts up, but before you attempt to use it.
10) Make a file called makeR.cmd in the root of the boot drive. It should contain:
format R: /FS:JFS /V:RAMDISK < RAMFMTRESP.TXT
11) RAMFMTRESP.TXT contains the "Y" response to the format command. It should contain one character, a "Y", without the quotes.
12) Put the line:
CALL=C:\OS2\CMD.EXE /Q /C C:\makeR.cmd
near the end of CONFIG.SYS. i suggest before you define %TEMP% (which can point to the RAMDISK, just don't try to use that until it finishes doing step 13), and before you run DMT.EXE (if you use it).
13. Now, add the lines:
lvm /hide:[ Vol.00 ]
sleep 2
lvm /driveletter:[ Vol.00 ],R:
to the top of STARTUP.CMD (create the file if it doesn't already exist).
Now, a boot should cause the drive to be formatted as JFS, and the WPS should be educated to use it as a JFS drive. On really SLOW machines, you may need more than a 2 second sleep. It seems that all of my systems need at least 2 seconds. (SLEEP is a command that exists on newer versions of eCS - you may need to use REXX to do that on older versions of OS/2 and eCS).
Note, that is is possible to use HPFS, BUT, it seems that there is some sort of problem, that JFS does not have, so I suggest avoiding that option.