Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
can windows 3.11 run on dos 7.00 and up. if it cant, why not? what is the difference between dos 6.22 and 7.00? thanks everybody

There is a program that supposedly will allow Win3.x to run under DOs 7 and higher, I've never tried it and I'm not sure if it will work and I can't remember the name of it right now. HOpefully someone will post the name. I do have it in a computer that needs fixing, if I can get to it I'll e-mail it to you.
MS-DOS 6.22 was the the last 16 bit version of DOS. It can only use FAT16 partitions and Win3.x is designed to run using it's limitations. msdos.sys, which is a bootup file, is a binary file under DOS 6.22 and earlier versions.
MS-DOS 7 can use FAT32 partitions and has a text msdos.sys bootup file.

a follow up to the previous answer is how does one make a bootable floppy from dos 6.22 files? i was told to copy first io.sys, then msdos.sys, then command.com, in that order. this did not work.
i have copied the dos 6.22 files from a download site, and can copy the files to floppies, but cannot make a bootable floppy.
many thanx.
kathy

Windows 3.x should run under MS-DOS 7.10 w/o any major work, all that you might have to do is run setver in the config.sys.
As far as how to make a bootable DOS disk, do format a: /u /s (U for unconditional, don't sayve, and S for system), or you can run Sys c: a: (sorce, dest)
DrScriptt...

copying does not create bootable diskettes. Two of the boot files, io.sys and msdos.sys must be placed in the "boot strap" portion of the diskette/hard drive. The copy command does not do this. To make a disk or hard drive bootable one of these will work:
use the DOS command sys.com. There's a few rules, like you have to have sys.com from a bootable disk or drive. The format looks like this:
sys.com a:
Format will also do it:
format a: /s
The /s tells format to add the system files to the diskette which will make it bootable.
WinImage copies of a bootable diskette can also be used to recreate a new bootable disk. That's why you see a lot of files ending in *.imz

Dos 7.00 WAS Windows 95. You could enable 32bit operation in Windows 3.1.
How to make a bootable floppy from the files IO.SYS, MSDOS.SYS and COMMAND.COM.
There is only one catch. You have to SYS A: with an OS that is the same version.
I would do this instead: SYS A: on a different floppy with whatever operating system I was using. This puts the files in the MBR section of the floppy. Then, I would attrib them -s -h -r so they can be overwritten. Then, I would overwrite them with version 6.22 files which I would ATTRIB +S +H +R (except Command.Com is just +R). Then, the floppy should boot.

Windows 3.1 & MS-DOS 7x
Windows 3.1 will run with no problems under MS-DOS 7.0 (Windows 95 or 95A (OSR1)) But NOT with MS-DOS 7.10 (Windows 95B (OSR2) or Windows 98/98se) Due to changes made by Microsoft themselves. (The problem has nothing to do with FAT32)The patch you need for running Windows 3.1 under MS-DOS 7.10 is 3XSTART.exe which can be found on the Win3x page at my PowerLoad Resource Pages which has full notes on the subject. Well worth a read!
MS-DOS 6.22
The problem "kathy" cannot be solved by use of FORMAT or SYS if she does not have a working copy of MS-DOs 6.22 in the first place! Yes someone with the knowledge could create a Bootdisk from the downloaded IO.SYS, MSDOS.SYS & COMMAND.COM but it would be far more simple if downloads were provided as self-extracting bootdisks in the first place! One other problem is the lack of a internal disk label which needs to be DISK 1Thats six (6) spaces
on disk 1, and Disk 2 & 3 in the same format on the other 2 disks.Have a look on my Bootdisk Project Page for more help!

![]() |
![]() |
![]() |

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |