nice, thanks

As I recall, Windows 3.x can be installed in DOS 7.1 (Windows 98 original), but not run without a patch. I also don't recall getting that dir error. I believe I used w3xstart to get Windows 3.x running on DOS 7.1, and yes, it's on a FAT32 partition.

yes you are right about the w3start patch, it's used to run win3x not install it... anyways the FAT32 problem is there and is known for a long time... maybe AdamP your 3.x partition was a small one (~2-8GB?) and that's why you did not get it....?

Sorry for the Necro. But does this mean you can get Windows 3.11 working alongside Windows 98 as well?

Should be possible.

I have win95 and 3.11 under Dos 7.1

I have a config.sys with Selection which Windows to boot.Each windows has its own drive Letter and Folder-name.

But there a some Problems. Some Drivers for example install in the wrong windows.

So i learned, before make changes to the system, make backup first.

But ehen configured well, it works great.

MS-DOS 7.x supports long filenames, correct? Is it possible to get those to show up in Win 3.x?

i never tryed.

I use 2 partitions , one with win95 , the othe one with win 3.11

It's because i hope i can stop win 3.11 to corrupt any long Filenames from win95.

Anonymous Coward wrote:

MS-DOS 7.x supports long filenames, correct? Is it possible to get those to show up in Win 3.x?

Way back in the day, I had a utility that somehow patched the Win3.x File Manager to support long filenames. I guess that counts.

Win3.x is sufficiently unstable that I wouldn't want to do anything more in it than I absolutely have to.

Be careful with utilities that don't support LFN and running them on filesystems that do.

I remember running pc tools defrag on my newly installed Windows 95 back in 1995.....not good.

Riva128 TNT?
does that apply to the m64 card aswell? re: win3.11 driver being buggy?

I am currently working in that solution and found this thread. Perhaps I can figure it out.

40GB Harddrive:
02GB FAT16 Boot
06GB FAT32 Dosdata (mostly dosgames)
32GB FAT32 Windata (mostly wingames)

I install Win95b into the Boot-Partition and change the startupfiles so that win95b is always starting to the Dosprompt.
I install Win95b into "Win9x-Folder" and Win311 into "Win3x-Folder".

I create some Batchfiles in order to start either Win95 or Win311. Currently Win311 does not boot at all, Win31 does indeed boot but only with "/s"= Standard-Mode. I must have 386-mode otherwise my sound and graphic-drivers do not work correctly.

Doc

The patches do fix the 386mode issue. Thx!

I found one bug or is this normal behavior?
- Booting into Win95b command-line and executing win3x after installing the patches.
- When I quit Win31 I get back to C:, but I have to do a reboot because I always get the message "file-system corrupted on C:" if I do anything (like "dir") after quitting Win31.

With the patch on win3.1 running dos 7.x I’ve found many programs break

Encarta 95 blows up for example with a strange version error

If I remember correctly there is some option for 3.x win.ini that directs it to use DOS for filesystem operations.
That was not the default behavior because of the performance penalty to enter real mode for every filesystem call.
Right now I do not remember the details, so I am not sure whether I am confusing that with the VirtualHDIrq thing.

Rhuwyn wrote:

Sorry for the Necro. But does this mean you can get Windows 3.11 working alongside Windows 98 as well?

Yes, it's possible, afaik in the same partition as well.
You have to make a bootmenu inside the config.sys to load the drivers needed for each OS.
Then inside the autoexec.bat you have to use the %config% variable to jump to the right section inside the autoexec.bat to make some preparations BEFORE starting Windows:
For example you choose to start Win98. Then in the autoexec you jump to the Win98-Section.
There are some commands to rename some folders.
For example rename the Windows Folder:

1:MENU
2IF %CONFIG%==WIN311 GOTO WIN311
3IF %CONFIG%==WIN98 GOTO WIN98
4GOTO EXIT
5
6:WIN311
7IF NOT EXIST C:\WIN311 REN C:\WINDOWS C:\WIN311
8IF EXIST C:\WIN98 REN C:\WIN98 C:\WINDOWS
9WIN
10
11:WIN98
12IF NOT EXIST C:\WIN98 REN C:\WINDOWS C:\WIN98
13IF EXIST C:\WIN311 REN C:\WIN311 C:\WINDOWS
14WIN
15GOTO EXIT
16
17:EXIT

Make sure to check, if the Folder was already renamed (for that reason I used the IF EXIST and IF NOT EXIST commands) to avoid renaming twice and therefore scramble both folders.
The programs folder doesn't need to be renamed.
Windows 3.11 uses C:\PROGRAMS, Windows 98 uses C:\Program Files (under Windows 3.11 shown as C:\Progra~1. DON'T CHANGE ANYTHING IN THIS FOLDER!!!).

Of course you have to adapt this commands to your needing, especially the names of the sections I used (WIN98 and WIN311).
They MUST match the section names used inside the config.sys for the bootmenu.

Is this a problem with running Windows 3.1 on DOS 7.1 or FAT32?

It's a little bit of both.
Windows 3.11 has sporadically little issues regarding the memory management,
especially if you use FILESHIGH, STACKSHIGH, FCBSHIGH and BUFFERSHIGH.
You can get some problems of using 32 Bit Disk/File Access, too.
Usually you won't run into major problems, but still be careful, especially with system tools.
NEVER EVER use the DEFRAG or SCANDISK from earlier DOS Versions.
They usually shouldn't work at all, but for security reasons don't even try it, they CAN destroy the FAT.
Use the Defrag from Windows 9x instead.
If you really want to defrag from pure DOS, search for the norton utilities.

Delphis1982 wrote on 2023-06-24, 18:10:

It's a little bit of both.
Windows 3.11 has sporadically little issues regarding the memory management,
especially if you use FILESHIGH, STACKSHIGH, FCBSHIGH and BUFFERSHIGH.

Sorry if I'm off topic, but I have to thank you for pointing this out.
I was struggling with a 486 build that would crash with memory errors after exiting Win 3.11. I knew it was related to my network card (Netgear EA201) and I assumed I needed to get a different one. I didn't have FILESHIGH, STACKSHIGH, FCBSHIGH, or BUFFERSHIGH, but your comment pointed me in a new direction. It turns out, I fixed it by adding the 'NOTR' parameter to the emm386 line in config.sys. (NOTR tells emm386 to not search for token ring network adapters.)