Call me silly, because I have seen this so many times in the past and now when I want to do something about it, I can find nothing on the subject! Basically, I'm having lots of fun messing around with various "Virtual machine" PC emulators, and installing WFW 3.11, setting it all up with apps etc, modernising it with new fonts and graphics etc. (mainly because this was the first GUI I ever used in my younger days) One thing is bugging me - how do you get Windows to report/use all the RAM in the "machine"? I've tried using Windows 98's HIMEM.SYS, but the "help/about" screen always shows a number around the 65000kb mark (my virtual machine has 128MB RAM) I'm sure I remember some time back seeing someone's screen dump of the Help/About screen, accurately showing the right amount of RAM, but I cannot remember the procedure? Any ideas? Cheers

There's a popular RAMDRIVE program, XMSDSK which also contains a utility (SETXMSTO.EXE) which can allow DOS to see and use more than 64Mb - check the documentation You are, once again, Microsoft's bitch

Cheers Jboy, SETXMSTO.exe seems to have done the trick.

That's great, it seems to work for most systems, despite the disclaimer in the readme - damn good ramdrive too You are, once again, Microsoft's bitch

Also try a program called "umbpci" at http://www.uwe-sieber.de/umbpci_e.html . What this does is allow access to DOS UMBs without loading EMM386. Works well. On the main, Windows 3.x should not be given too much memory, otherwise the poor blighter will choke. Remember in the Days when windows 3.1 walked the world, memory was very expensive, and machines typically had something like 16 MB or (much) less. Giving it in the order of 32 MB should clear out most probs. On the other hand, one could hunt down something like 1MBFORT (which stops it from running out of the critical DOS memory too quickly). Between 1mbfort and umbpci, you should overcome most of Windows memory probs. The dream you dream alone is only a dream, The dream we dream together is reality.

Is 1MBFORT the same sort of application as FIX1MB and the SYSHOOK driver? I've been trying all sorts of these, but I don't know what's best, or if indeed they are all the same. I know it's not a real system, but still I'd love to get it all set up how I want it! I'll have to check out that UMBPCI too, sounds interesting. Now if only someone could discover why Win32s 1.3 doesn't want to work on a virual machine of any sort, then I'd be very happy! Thanks for the information, people.

"Giving it in the order of 32 MB should clear out most probs." I'm not sure what that means (and may not be alone) 32 Mb is not a magic number - obviously more than that will work ('problem' free) Win31 Memory Limits You are, once again, Microsoft's bitch