jaffe@jaffe.mc.ab.com (Bruce Jaffe (ext 3581)) (03/13/91)
I'm attempting to try out 4dos, but having some trouble getting configured properly. At first I allowed the swapping media to be chosen by 4dos. It decided to use extended memory, managed by himem.sys. It appears that once 4dos takes over extended memory for swapping, other applications (like Windows or Smalltalk) cannot run. This is apparently a limitation imposed by himem.sys. Next, I decided to force swapping to disk with the /sd option. This didn't work out well either, since the Norton Disk Monitor promptly complains that writes are being attempted to the system area. I couldn't even get past autoexec.bat in this mode. I tried making a 4start.bat with a "swapping off" command. This got past the boot up sequence. Windows and Smalltalk both fire up OK. But, if swapping mode is turned back on, there are problems. At the command line level there are still occasional warnings from Disk Monitor, for example in trying to do something as innocuous as piping something through "more". Also, somehow engaging disk swapping seems to tie up extended memory as before. I'm hobbling along for the moment in non-swapping mode (/sn). I suppose I could just turn off Disk Monitor, but I hate to do this, especially since I have no idea what is causing the write violations. Has anyone had similar problems? I welcome suggestions. Thanks, Bruce Jaffe