Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!think.com!linus!linus!mwunix.mitre.org!jcmorris From: jcmorris@mwunix.mitre.org (Joe Morris) Newsgroups: comp.sys.ibm.pc.misc Subject: Re: DOS 5.0 reseller protection? Message-ID: Date: 18 Jun 91 20:52:52 GMT References: <23618@shlump.lkg.dec.com> Sender: news@linus.mitre.org (News Service) Organization: The MITRE Corporation, Bedford MA Lines: 28 Nntp-Posting-Host: mwunix.mitre.org reisert@mast.enet.dec.com (Jim Reisert) writes: >In article , > elund@graphics.rent.com (Eric W. Lund - Subop) writes... >> >>The author stated the install disks are not "bootable", and intimated that >>creating bootable disks are a major hassle. Is there any copy protection >>(logical, or through "hassle") in DOS 5.0? >I found this to be the case. At one point, after I had upgraded from DOS >3.3 to DOS 5.0, I screwed up my CONFIG.SYS file and couldn't boot off the >hard drive anymore. I booted off the old 3.3 floppy ('cause I forgot to >make a bootable 5.0 disk) but then couldn't access the hard drive anymore! >The only way to get out of the loop was to re-install 5.0 on the hard drive. >There was no way for me to make a 5.0 boot disk with the 5.0 upgrade disks I >had. I got into this situation in exactly the same manner; the trick was to bang on the BREAK key while booting the uninstall diskette. Then edit the bug out of CONFIG.SYS, reboot the fixed disk, and MAKE A BOOTABLE FLOPPY...dammit. Your problem is probably the same one that bit me: the DOS5 installation rebuilt the FAT to BIGDOS format, which is unknown to DOS 3.3 and prevents it from recognizing the DOS partition. Joe