Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!uunet!pdn!myrddin!tct!jim From: jim@tct.com (Jim Kunzman) Newsgroups: comp.os.os2.misc Subject: Re: os2 installation blues Message-ID: <286D9D57.1C54@tct.com> Date: 30 Jun 91 08:59:03 GMT References: <91179.160056HORST@SLACVM.SLAC.STANFORD.EDU> <43802@cup.portal.com> Distribution: na Organization: TC Telemanagement, Clearwater, FL Lines: 30 According to buggs@cup.portal.com (William Edward JuneJr): >Submodel = 01 > >I too am havin' a bummer time installing OS/2 1.3 EE. >I have a 20MHz '386, AMI BIOS, Ultrastore 12F ESDI controller, Maxtor > XT-8760 ESDI HD with DOS 5.0 >I did as appendix D says for Dual Boot, I then boot up the installation > disk, I notice it comes up in HPFS mode with C: as a virtual? drive? > then go through a couple of info screens to the HPFS info screen, then > a RED warningscreen comes up telling me FDISK unsuccessfull >The error.log shows: >Model = FC For now you might just want to not install HPFS. For me FAT works fine (although I'd like the long file names) with my Adaptec controller. I guess some of the controller mfgrs are having problems writing HPFS compatible drivers. Using FAT only is a small price to pay. Nevertheless, register your disatisfaction with your controller manufacturer. Don't waste your breath trying to talk to IBM (unless you have an "in" in Boca). IBM will not support non-IBM peripherals (nor should they have to). If peripheral manufacturers want to sell equipment, then they should produce the drivers. Not to say that this is right, but it's standard practice in (most) of the UNIX world... It's also becoming more common in the DOS and OS/2 world. If OS/2 starts to catch on, we will see a lot more vendors building OS/2 drivers of all sorts. Let's hope that is the case... -- Jim Kunzman at Teltronics/TCT , !(This space intentionally left blank.)