Get HPFS386 files from LANserver 3.0 FixPack, 1994.
Installation is a breeze, but as always: backup before getting into a panic.
Get the five required files and put them into C:\IBM386FS. The files are: HFS.MSG (not strictly necessary), HFSH.MSG (not strictly necessary), HPFS200.386, HPFS386.IFS and CACHE386.EXE.
Add these two lines to your CONFIG.SYS BEFORE the existing HPFS.IFS line.
REM -- start of HPFS386 -- IFS=C:\IBM386FS\HPFS386.IFS C:\IBM386FS\HPFS200.386 /cache=4096 /heap=4096 /autocheck:C RUN=C:\IBM386FS\CACHE386.EXE /lazy:on REM -- end of HPFS386 --
Do not REM the existing HPFS line yet, as it is your safety net: should HPFS386 fail to install, HPFS will start as before and allow you to access your disk those boot floppies you keep close by at all times. Right?
Reboot, check and enjoy :-)
From the .MSG files and the .INF files shipped with Warp, you can deduce some of the parameters you can play with.
Once satisfied with the setup, you can REM that HPFS line.
I would like to get some feedback on a couple of things:
How do I check whether any driver is ring 0 or ring 3?
How do I measure the real world differences between one driver or the other? I have been using DiskIO, version 1.9 by Kai Uwe Rommel, and this leads me to believe that the newer versions of HPFS386 have less CPU overhead than the older version.
Does anybody know the last thing on the access rights issue?
From the Warp 5 FAQ, I picked up something about a long due overhaul of HPFS. It will possibly go the way of a Journaling File System. Will it?
Remember, I give no guarantees, the risks and rewards are all your own.
Cheers/2 you all.
Yes, the small print. HPFS386 is part of LanServer/WarpServer. It is illegal to use HPFS386 without a license for either one of the two. But I cannot imagine IBM objecting to its use by Warp users. IBM should just be flattered with our end-user interest in Warp.
Please let me know your success or horror stories, other comments, suggestions, additions or answers concerning HPFS386.