#MS DOS 6.22 DISK WINDOWS#
(Canbe extracted under Windows 3.1x if Win32sv1.30 32bit support is installed first)Įach Boot Disk contains the following ~ IO.SYS, MSDOS.SYS, COMMAND.COM, FDISK.EXE, FORMAT.COM and SYS.COM EXE File (Needs to be extracted underWindows 95 or higher)
#MS DOS 6.22 DISK ARCHIVE#
IMG file (Needs Disk ImagePro for DOS or WinImage for Windows to extract to Floppy)īasicIMG Bootdisks are further compressed into ZIP format archive files(Download basic UnZip Utility oruse PKZIP or WinZip to open)ĭisk Imagesaved as Disk eXpress Self-Extracting Diskette Image for DOSĭisk Imagesaved as a Compressed WinImage IMZ File (Can only be opened byWinImage for Windows)
#MS DOS 6.22 DISK PRO#
WinImage v8.0 32bit version for Windows 9x, NT (x86), 2000 & XP(Link to WinImage Download page)Īll Bootdisk Images are now categorised as follows:ĭisk Imagesaved by Disk Image Pro for DOS as. Microsoft Win32s v1.30 ~ 32bit support for Windows 3.x WinImage v3.0 16bit versionfor Windows 3.1x (Complete with Helpfiles and Notes) and re-create all the following DOS images in1.44MB 3½" HD Format Only. (Program Only - No Help File)ĭisk Copy Fast v5.3 Diskette Creation Utility for DOS ~ SharewareEditionĭisk Conversion is disabled in this shareware copy, But it isable to read and write 1.68MB DMF Format. Note ~ This version of Disk Image Pro does not supportNon-Standard diskette sizes such as Microsoft 1.68MB DMF, But itis ideally suited for Bootdisk creation with its diskette sizeconversion capability. Please Note ~ You need to Download DCP or WinImage Separately:ĭisk Image Pro v2.6 DisketteImage Creation and Extraction Utility for DOS
#MS DOS 6.22 DISK PC#
Read Convert.Txt in each Zip Package which contains Boot Image & Instructionsīootdisks for versions of MS PC & DR DOS and DOS based Bootdisks for Windows up to and including ME are listed here. Each image is saved in 3 1/2" 1.44MB HD Format, But can be easily be converted into 360Kb 5 1/4" LD, 1.2Mb 5 1/4" HD and 3 1/2" 720Kb LD Formats by both DCP and WinImage. You can probably use one of those to boot and then insert disk 1 from the set that Flack linked to and run SETUP.got it installed, thanks everyone.These images have been archived using Disk Copy Pro 2.6 (DCP) IMG format, which is a DOS based utility which can also be extracted by WinImage. seems to have a bunch of suitable ones - they're distributed as EXE files that will presumably write to the floppy directly. Without a pre-existing copy of DOS 6.22, if you want a DOS 6.22 bootable floppy disk (which is presumably what you need to run SETUP on the first DOS 6.22 disk), you have to have an IMG, or something that will write an IMG. In the DOS 6.22 days, this was done by formatting a disk using "format /s" (I think), or by using the "sys a:" command. Not only do certain files have to be in specific locations on the disk, but you need to write to the boot sector. The point is that there is no way of simply copying files to a floppy disk that will make it bootable. It's bootable as well, so if that workaround is better suited to your needs, than seek that out. As far as I know, it's handmade (I can't imagine Microsoft ever releasing MS-DOS 6.22 on CD), but it works just dandy. iso floating around that has all of MS-DOS 6.22 on a single (albeit tiny) disc. IMG files I have are bootable, as well.Īlternately, there's an. IMG file over to an empty floppy, it's painless. If you use a problem like WinImage to copy over to unpack/copy the. IMG files which will ensure that you have a 1:1 copy of the original MS-DOS disks. But Jorpho is also correct in the fact that it is better to use. IIRC, The FILE_ID.DIZ is usually lists the release's groups information.similiar to how cracking groups today use. I certainly didn't have anything else to boot off that would have helped.Correct on all counts. because when I set up my old Pentium, I would have used those disks to set the machine up from scratch. I have a set of original MS-DOS 6.22 disks sitting around somewhere (can't seem to find them at the moment), and I'm almost positive the first disk was bootable.