Hi!
Successful update. No need for call ver. Just needed to add vmadd386.sys to the config. However, it doesn't work in option 2. I had to add this line: 4?Device=C:\Dosadd\vmadd386.sys
Nice, but which drivers are loaded in option 4 and which in option 2? What does the documentation say about VMADD386.SYS and FSHARE, which are their requirements? Do they need HIMEM or EMM386? Or are they usable only WITHOUT any EMM386, for example? I could imagine that option 2 involves EMM386 style drivers which can have compatibility issues with some things. Note that in OTHER cases, you actually NEED an EMM386 style driver to do some magic: https://www.bttr-software.de/forum/board_entry.php?id=23369&page=0&order=time&category=0 https://www.vogons.org/viewtopic.php?p=1418209#p1418209 But of course that is not related to vmadd386 at all ;-)
I am also tryin out win 3.xx and also curious about 95 to see how they might work. So far Win3.11 just locks up the live system (usb 2605 testing).
You probably mean Windows for Workgroups 3.11, not the year 2000 update for standard Windows 3.1: In both cases, you are probably trying to use the 386enh (-anced) mode, which has high compatibility requirements. In WfW 3.11, the non-386enh mode is similar to the safe mode in Win95 and Win98, so people prefer not to use it. In Win 3.1, 386enh mode just gives you extra features, but you can easily use Win 3.1 in standard mode :-) Either way, you will have to carefully select drivers, kernel version and configuration options to make WfW 3.11 work. For example it may need a specific version of HIMEM, SHARE, EMM386 or fail to run if you have too much RAM installed. Which you could fake with the FreeDOS drivers, but Windows might rely on using the MS drivers bundled with Windows. It could also have problems with EMM386 or caches. You could try a FAT16 partition and use command line options for Windows to tell it to not try funny things with the harddisk controller. Instead, it should use the more compatible but slower BIOS. Regards, Eric PS: The thread Tomas mentioned talks about alternative VirtualBOX, not VirtualPC drivers, for shared folders and mouse drivers for DOS and Windows 3. Sounds useful, but not Virtual PC compatible, I believe? :-) _______________________________________________ Freedos-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-user
