Fix the file allocation table on drive C.

I used to use Norton Disk Doctor back then. I am sure there are other alternatives. IIRC, the built-in CHKDSK of DOS6 still does not do it.

I have MS-DOS 7.10 in there.

Then perhaps you have Scandisk. Try that.

Ok, I'm letting Scandisk checking the sectors, let's hope it doesn't find any bad sector...

Damn, it's really slow...

EDIT:

Ah well...

😢

Look how Scandisk trolls me:

This partition is not formatted FAT32 by accident, is it? (not even sure how Win3.x would behave if you tried launching it from such a partition...)

The odd thing is that Windows 3.1 always works if I first launch Doom 2 (even just launch it and then close it).
As long as I launch Doom 2, I can boot Windows 3.1 with the command, it's nonsense.

Maybe some fault with Protectmode Switching ?

can you try starting with win /s

Which DOS Version is running ?

TRY this: (If you run 7.10 98/95)
http://www.conradshome.com/win31/files/3xstart.exe

I only have MS-DOS 7.10 and Windows 3.1 in it, where should I place the extracted files from this archive ?

ok then this will fix the issue, just read the readme included.

I have the same error, but only when win3.11 was running , exit, and try to run again.
I think, it has something to do with the network too.

Ah, i remember......
Do you have smartdrv in config.sys or autoexec.bat?
Then remove it, or REM it out.

What version of himem.sys and emm386 are you using? From Windows3.11/Dos 6.22. or from Dos7.10 ?

I think w3xstart is already used, because win3.x is starting (or trying).
When io.sys is not Patched, there is another error.

Hmmm... actually after I manage to get into Windows 3.x and try to enter again, it does that error aswell...

I dunno what version of himem and emm386 I'm using, probably it's dos 7.10's one.

Anyway, I got this error while trying to patch io.sys with that software:

Did you try chkdsk c: /f from a bootable floppy (DOS 5/6) ?
Despite beeing an older utiliy, this one can sometimes fix errors Scandisk can't.
Should work with a pure FAT16 drive, at least. Don't know how it behaves on VFAT.

I also remember there was an unlock/lock command in DOS 7.0.
I've no idea what it was for, but I think I needed it for defrag a long time ago..
Can't find any information on the web, though.

I believe lock and unlock set the permissions on that drive so you can write or read only.

Elia1995 wrote:

I believe lock and unlock set the permissions on that drive so you can write or read only.

Ah, okay then. Was a long time ago I used this command the last time (ca. 1996-97). 😊

Sammy wrote:

I have the same error, but only when win3.11 was running , exit, and try to run again. I think, it has something to do with the […]
Show full quote

I have the same error, but only when win3.11 was running , exit, and try to run again.
I think, it has something to do with the network too.

Ah, i remember......
Do you have smartdrv in config.sys or autoexec.bat?
Then remove it, or REM it out.

What version of himem.sys and emm386 are you using? From Windows3.11/Dos 6.22. or from Dos7.10 ?

I think w3xstart is already used, because win3.x is starting (or trying).
When io.sys is not Patched, there is another error.

the only smartdrv I found was in autoexec.bat and it was already REM'd.

Uhm, by the way, are you people running Windows 3.10, Windows 3.11, Windows for Workgroups 3.10 or Windows for Workgroups 3.11 ?
For original Windows 3.1 was an update available for free.

For me it's just "Windows 3.1"