Main page I Packages I Help I Forum

SvarDOS community forum

a place to talk about SvarDOS and other DOS-related things

jump to end reply list of threads

Windows for Workgroups 3.11 Enhanced Mode

7579bf5302c9f7e5 e01667abcfdfcae5 deea55d01cbcf1dc 93e54228710235d9 405464b4a28db99e 6ac9038f4159e779 3494dfd64660154a 652a23c843ae25f9
Hello there, Has anyone managed to run the enhanced mode for WfW 3.11 under SvarDOS? If yes, can you share your config.sys and autoexec.bat please? Thanks! :)
914488c23c724b71 831bc56dbfabe5b2 8b75df193fc83a0f 3ce33036bdcce42b d8efa38b45466a88 4a8d6c2fb127932f 66d18f6fe5ce0ce3 e95ecaaac41fb734
If I recall correctly, the Windows VSHARE driver has to be disabled, as this is incompatible with the EDR kernel. You may resort to the SvarDOS DRSHARE package (SHARE.EXE), if you use a Windows program which requires SHARE to be installed.
0d025f180080f858 5ea12b18f9c25f41 172d267f387ea872 840f85b9eac41aa2 0b5990ca086c8a74 ceb4a412e71f6cb3 95e39fce5b50cdb1 4ed5aad44941b0c2
I just tried it: The line containing "device=vshare.386" in windows\system.ini has to be removed or commented out. Then Windows 3.11 WfW runs on my SvarDOS without any further changes to the config files.
7579bf5302c9f7e5 e01667abcfdfcae5 deea55d01cbcf1dc 93e54228710235d9 405464b4a28db99e 6ac9038f4159e779 3494dfd64660154a 652a23c843ae25f9
Thanks Bernd! :) I suppose WfW 3.11 won't run in enhanced mode from a FAT32 partition. Is that correct?
914488c23c724b71 831bc56dbfabe5b2 8b75df193fc83a0f 3ce33036bdcce42b d8efa38b45466a88 4a8d6c2fb127932f 66d18f6fe5ce0ce3 e95ecaaac41fb734
> I suppose WfW 3.11 won't run in enhanced mode from a FAT32 partition. Is that correct?
Honestly, I do not know for sure (I am not that familiar with Windows 3.1+). I just copied a Win installation over to a FAT32 drive and launched it from there. The five minutes I tested it, I noticed no obvious malfunction. However, for maximum compatibility you should better use FAT-16, as Win3.1 has no knowledge about FAT32 at all. Most likely there will be some compatibility problems.
7579bf5302c9f7e5 e01667abcfdfcae5 deea55d01cbcf1dc 93e54228710235d9 405464b4a28db99e 6ac9038f4159e779 3494dfd64660154a 652a23c843ae25f9
I did exactly what you did, but unfortunately, it won't start in enhanced mode. Also, the Windows setup won't work correctly with himemx, so I had to either use MS-DOS 7.1's himem.sys or install the DRHIMEM package to use its himem.sys. Maybe I am missing something else?
7579bf5302c9f7e5 e01667abcfdfcae5 deea55d01cbcf1dc 93e54228710235d9 405464b4a28db99e 6ac9038f4159e779 3494dfd64660154a 652a23c843ae25f9
Okay, I reinstalled SvarDOS but this time into a FAT16 2GB volume, then installed WfW3.11 using the steps mentioned above, and it now runs fine in enhanced mode after following your advice to remove the share drivers from system.ini Interestingly, I can still access large FAT32 volumes using its File Manager, I tried a 7GB partition and a 100 GB partition! More testing has to be done, of course! :)
0d025f180080f858 5ea12b18f9c25f41 172d267f387ea872 840f85b9eac41aa2 0b5990ca086c8a74 ceb4a412e71f6cb3 95e39fce5b50cdb1 4ed5aad44941b0c2
> Interestingly, I can still access large FAT32 volumes using its File Manager, I tried a 7GB partition and a 100 GB partition!
File access is probably handled by DOS, at least as long as you do not enable 32-bit file access under Windows, I guess. What most likely will not work is FAT32 formatting these drives with the file manager. If you test this, please report the results :)
7579bf5302c9f7e5 e01667abcfdfcae5 deea55d01cbcf1dc 93e54228710235d9 405464b4a28db99e 6ac9038f4159e779 3494dfd64660154a 652a23c843ae25f9
Unfortunately, I ran into a lot of trouble, I could not get the WfW NDIS driver working (I may try using the DOS packet driver + trumpet winsock) Also, I could not get the VBESVGA driver or any SVGA driver to work. And I could not get the sound drivers installed. I suspect that WfW is very picky, I'll try the "regular" Windows 3.11 tonight :)
914488c23c724b71 831bc56dbfabe5b2 8b75df193fc83a0f 3ce33036bdcce42b d8efa38b45466a88 4a8d6c2fb127932f 66d18f6fe5ce0ce3 e95ecaaac41fb734
Hmm, can you give some details about your hardware configuration? Is it real hardware or some virtualization?
914488c23c724b71 831bc56dbfabe5b2 8b75df193fc83a0f 3ce33036bdcce42b d8efa38b45466a88 4a8d6c2fb127932f 66d18f6fe5ce0ce3 e95ecaaac41fb734
I tested the AWE64 sound card driver under Win 3.11 WfW. This works. Graphics driver for ET4000 also works. This is on an emulated 486 DX2 80MHz system, emulated via 86box.
7579bf5302c9f7e5 e01667abcfdfcae5 deea55d01cbcf1dc 93e54228710235d9 405464b4a28db99e 6ac9038f4159e779 3494dfd64660154a 652a23c843ae25f9
Not virtualisation nor emulation. I am using a motherboard called "ITX Llama" and at its heart a SOM called Vortex86-EX, it's clocked at 300MHz with 128MB of RAM. The sound card is Crystal Sound CS4237B , I am using a driver that was reported it installed fine on the same board, but using MS-DOS 6.22
Suggestion: Replace your SHARE.EXE file from one that comes straight out of MS-DOS 6.22, not from other DOSes. And retry.
You should absolutely not use MS-DOS share.exe, any version, with an EDR-DOS kernel.
ecm is right. But please, pay attention, we are both right: You said you were using MS-DOS 6.22 on your ITX Llama board, then use a fresh SHARE.EXE from MS-DOS 6.22 as I said. If you are using an EDR-DOS kernel, instead, only use the SHARE.EXE that matches their kernel, as ecm said.

your name or nick

password (optional)


check the LAST box: