FreeDOS the Open Source DOS is still actuve and many improvements are under development. It supports FAT32 partitions and work is in progress for a 32 bit version. Take a look at
Not sure of the status of Windows 3.1 on FreeDOS (granted, this is a DOS forum), but should that be an issue, the newest "commercial" version of DOS would be PC-DOS 2000 (from IBM). Though there's no support, it still should be available from some sites, and I'm sure there was a link here somewhere to a legitimate download of it from IBM. A search past postings should turn it up...
DOS 8 exists in Windows ME. A hacked version is produced by Windows XP "format as a DOS diskette" as 8.03. Most of the utilities are straight copies of 7.10, with the version number changed from 7.10 to 8,00.
In either case, DOS 7 and 8 from Microsoft are about phasing out DOS support, while still supplying some DOS functionality. It's pretty much a compromise, but if you need to support advanced modern hardware and old DOS programs in a native boot, then either try MS-DOS 7.10,2222 (from win98se), or some non-microsoft DOS.
The dream you dream alone is only a dream, The dream we dream together is reality.
I dont have a floppy drive so can you make a floppy of MS-DOS 8.0.3 if you have Windows XP and copy it to a ZIP file and email it to me at spongecell@inbox.com
Maybe I can do what you ask even if my keyboard has an italian layout (obviously), but here the key points are
- What do you want to achieve with that bootable DOS diskette?
- Are you enough skilled to master DOS environment (commands, drivers, configuration files)?
DOS 8.0 from Windows ME is the worst choice to build a DOS environment as the raw floppy by XP lacks all the external commands that make the system useful.
Better to use DOS 7.1 from Windowws 9X or FreeDOS. To go that route however (and DOS 8.0 lane too) you ned to have a strong and good knowledge of DOS fundamentals as to trust in someone's tips doesn't suffice at all.
The information on Computing.Net is the opinions of its users. Such
opinions may not be accurate and they are to be used at your own risk.
Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE