|
|
|
DOS 6.22 Bootable Installation DIsk
|
Original Message
|
Name: Aske
Date: February 10, 2005 at 02:50:58 Pacific
Subject: DOS 6.22 Bootable Installation DIskOS: Windows XPCPU/Ram: AMD Duron 1300, 512 MB PC |
Comment: Hey there, i'm quite new to dos, and i only succeeded installing DOS 7.1, with it's automatic boot disk creation. i wanted to install 6.22 because the "Killer" from 7.1 is VERY annoying, and keeps screwing up my windwos 3.11 installations. So i loaded all the files from disk 1 to a disk, and disk 2 and so on, and when i insert the first disk and boot up the system, it just tells me to remove the non-system disk from the drive and reboot. so i tried with a dos 6.22 bootdisk, and i managed to get the machine booted, and when i insert dos disk 1 again and write setup it just tells me to insert dos disk 1, and reboot the machine, wich results in non-system disk error... what is the right precedure? SRY, if i cant spell, i'm not that good ad english. This is my life, This is my time, show me the light, and i go there
Report Offensive Message For Removal
|
|
Response Number 1
|
Name: Mechanix2Go
Date: February 10, 2005 at 03:19:39 Pacific
|
Reply: (edit)If you just want your w3.1 to run on the hard drive with DOS 6.22, you MIGHT be able to do it by booting on a 6.22 floppy and doing this: sys c: [enter] But even if that works, and it may not, you will need to replace DOS 7 external commands with their 6.22 version. Some of the critical files are: himem.sys format.com chkdsk.exe The easy way is to format the HD with 6.22 and then install win 3.1 You don't need a "full install" of 6.22 ; over half of it you will never use. M2
Report Offensive Follow Up For Removal
|
|
Response Number 2
|
Name: Radio Randy
Date: February 16, 2005 at 22:25:02 Pacific
|
Reply: (edit)Now, here is what you REALLY wanted to know... It sounds like you already have a bootable DOS 6.22 disk. You will need to copy all of the "install disk 1" files to that disk. If you are asked if you want to replace files on the disk, say "no". Now, your disks are probably labeled "disk_1" or "disk 1" or, maybe not at all. You need to re-label the disks using all 11 characters in the label. In other words, use the word "disk", followed by six spaces, then "1, 2, or 3" depending on which install disk you are making. I tried this fix on my install disks and it worked perfectly. Good luck.
Report Offensive Follow Up For Removal
|
Use following form to reply to current message:
|
|

|