I think i've posted about this before but never mind. I've been trying to get Windows 3.11 FWG running on all sorts of emulators for some time, such as Bochs, Virtual PC, and QEMU. I've never had any luck though when it comes to using Win32s - applications seem to cause an error and then quickly crash out to the DOS prompt. I found out today using Qemu that this only happens when I load net.exe in the autoexec.bat, needed for the Windows network. If i Rem out the line, Win32s apps such as Freecell and others work perfectly. So, I was wondering, why should the network cause this, and is there a fix? Thanks

I only have experiences with Virtual PC (I downloaded bochs but VirtualPC seemed faster, better sound and emulates a better graphics card), and never managed to use the last version of Win32s in it. Everytime I opened a program (even freecell) virtual pc it crashed. I didn't realize network could have anything with this but, as I DO use VPC network, I can't stay without net start... I've found out that an older win32s version does work. The version I use is 1.25 and no crashes... But it is not very useful... Most Win32s applications i use in the REAL Win3.11 (XNVIEW, for example) won't work with this older version :-(

I've got it sorted! Within minutes of posting this I thought about trying to replace the files with those from the powerload windows 3.x resource site - it's the NT 3.51 version of net.exe - and it works perfectly! I'm not sure if it fixes Virtual PC but don't see why not. Give it a try: http://www.oldfiles.org.uk/powerload/download/wfwadd.exe Worked for me :)

Forgot to mention that it's not JUST the net.exe file you replace, but all of the ones mentioned in the readme file supplied.

Great! Now you can forget everything you just did and comment out 'netstart.exe' in your autoexec.bat altogether. It's not needed for anything in the real world...- unless your on a local corporate network (c'mon, companies (other than public libraries) using win31 on a network anymore...?!) %00

If you comment out net start then you get an error after Windows starts saying the network has not been started! :P I do anyway.

Scrap all that actually, it's broken again for me now. My fault for messing around. Was working all fine until I enabled 32-Bit disk access, and even disabling it again has not fixed the problem. Oh well, back to the drawing board.