Return to BSD News archive
Xref: sserve comp.os.386bsd.bugs:410 comp.os.386bsd.questions:1200 Newsgroups: comp.os.386bsd.bugs,comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!saimiri.primate.wisc.edu!sdd.hp.com!ncr-sd!SanDiego.NCR.COM!mdp From: mdp@rhine.sandiego.ncr.com (M. D. Parker) Subject: Problem in getting DIST disk to boot Message-ID: <1993Mar30.205022.7080@donner.SanDiego.NCR.COM> Sender: news@donner.SanDiego.NCR.COM (News Owner) Reply-To: mdpc@cup.portal.com Organization: NCR Corp, E&M San Diego Date: Tue, 30 Mar 1993 20:50:22 GMT Lines: 34 I recently downloaded the entire 0.1 386BSD distribution and the 0.2.2 patchkit. I created the FIXIT and the DIST disks in the manner indicated. I tried the DIST boot disk on another 386 PC I have access to just to make sure the disk was created correctly. On the real platform, the disk will not boot at all. The floppy light just seems to stay on but nothing happens. Upon power up reset, I get the initial message but again the system hangs. I do wait for about 10-15 minutes before making this determination. Again, this disk works in another 386 system so the disk is not the problem. Hardware Configuration of real platform: 486-DX50 w/ 256K Cache 16 MBytes Memory 2-IDE Western Digital Drives aprox 200 Mbytes each 1 Parallel Port 3 Serial Ports (COM1/COM2 normal, COM3@IRQ 2 w proper IO Address) 1-5-1/4" floppy disk 1-3-1/2" floppy disk Orchid Farenheit 1280 VGA card w/ 1 MByte memory Colorado Memory System Jumbo 250 tape drive off floppy controller Logitech Bus Mouse @ IRQ 5 This configuration works successfully under DOS 5.0 and Windows 3.1 with NO problems. As I utilize this configuration for DOS work that I have to perform I do not want to modify the hardware very much. Is there some DIST disk that I should be using instead of this one or is there some method of making a disk that would work in this environment. BTW, the 0.2 DIST disk failed as well. Thanks for your help and guidance. Mike Parker