home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.os2.misc
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!cs.utexas.edu!uwm.edu!linac!uchinews!ellis!sip1
- From: sip1@ellis.uchicago.edu (Timothy F. Sipples)
- Subject: Re: ...3? months, and I still can't install 2.0...
- Message-ID: <1992Nov21.014642.21244@midway.uchicago.edu>
- Sender: news@uchinews.uchicago.edu (News System)
- Reply-To: sip1@midway.uchicago.edu
- Organization: Dept. of Econ., Univ. of Chicago
- References: <laird.721789380@stable.ecn.purdue.edu>
- Date: Sat, 21 Nov 1992 01:46:42 GMT
- Lines: 38
-
- In article <laird.721789380@stable.ecn.purdue.edu> laird@stable.ecn.purdue.edu (Kyler Laird) writes:
- >Well, I thought enough time had passed, so I took another hack at
- >installing OS/2 2.0. This time I didn't do it on the network
- >server, though. (I'm pessimistic.)
- >I didn't get any further, but I do have more data points to look at.
- >For those interested in a challenge (Timothy?), my situation:
- >Northgate machines - 386DX/33 16MB RAM, 2*386SX/20 8MB RAM, 486DX/33 16MB RAM
- >IDE drives
- >all are running OS/2 1.3 with flakey floppy drive accessiblity (OS/2 thinks
- > it's a 360K drive no matter what I set the CMOS to. It can read
- > 720K disks, but formats to 360K.)
- >When I reboot after the initial part of the 2.0 install, I am unable to
- >access the floppy (3.5" 1.44MB) drive. I can boot from the 2.0 (or 1.3)
- >install disk and access the drive without problems. Even with the HD
- >configured to boot SYSINST1.EXE (like the install disk), the floppy
- >remains inaccessible.
- >I tried a patched IBM1FLPY.ADD long ago with no change observed. My latest
- >call to IBM came up with a pointer to IBM1SFLPY.ADD (9.3 file name???!!!),
- >but the date was older than the one that I had gotten originally (I think).
- >So...something different happens when booting from the fixed disk than does
- >when booting from floppy. But what? My config.sys looks almost identical
- >to the one on Install Disk 1.
-
- My hunch (and it is only that) is that there's something wrong with
- the hard disk/floppy disk adapter (which is probably one of those
- IDE/floppy combos). If you have one handy, try a substitute card
- (preferably of a different brand). I would also check any jumpers on
- the card itself (to, for example, make sure that the floppies are set
- to the primary addresses, correct DMA channel, and whatnot).
-
- I would look for possible DMA conflicts (the floppy drive does use
- DMA). Network card, perhaps?
-
- --
- Timothy F. Sipples | Read the OS/2 FAQ List 2.0g, available from
- sip1@ellis.uchicago.edu | 128.123.35.151, anonymous ftp, in /pub/os2/all/info
- Dept. of Econ., Univ. | /faq, or from LISTSERV@BLEKUL11.BITNET (send "HELP")
- of Chicago, 60637 | [Read the List, THEN post to ONE OS/2 newsgroup.]
-