NetNews Usenet Archive 1992 #20/NN_1992_20.iso/spool/comp/os/os2/316

Internet Message Format | 1992-09-09 | 1.8 KB

Xref: sparky comp.os.os2:316 comp.os.os2.misc:29624 comp.os.os2.apps:5985 comp.os.os2.programmer:4832 comp.os.os2.advocacy:5150
Newsgroups: comp.os.os2,comp.os.os2.misc,comp.os.os2.apps,comp.os.os2.programmer,comp.os.os2.advocacy
Path: sparky!uunet!zaphod.mps.ohio-state.edu!moe.ksu.ksu.edu!ux1.cso.uiuc.edu!ux1.cts.eiu.edu!cfdwe
From: [e-mail] (David Ebdon)
Subject: Boot Failures--Was<IS IBM UK STILL IN THE STONE AGE???>
Message-ID: <[e-mail]>
Date: Tue, 08 Sep 1992 21:47:11 GMT
References: <[e-mail]> <[e-mail]> <[e-mail]>
Organization: Eastern Illinois University
Lines: 21

Tom Wilson's remark in a previous post reminds me how I solved a boot
failure problem when I first put OS/2 on my 486-33 clone.  Actually my 20
year old son solved it.  We were using the dual boot procedure, and the
system "forgot" how to come up in OS/2.  First we "sys-ed" it back to life
and then changed MS-DOS 5.0 for the IBM version (keeping qbasic.exe from
MS-DOS so that it and edit.com would remain functional).  We then
reinstalled OS/2, again in the dual boot mode.  So far there have been
no more boot failures.  Is there some problem with generic MS-DOS and
OS/2?  Or would I have had the same good luck by simply reinstalling OS/2?
I tend to think not since some problems with the DOS windows, experienced
before the change in DOS, disappeared.  One of my colleagues today reported
that some network software which had frequently failed became very reliable
when MS-DOS was replaced by IBM-DOS 5.0--even on non-IBM (Zenith)
hardware.  Our network software is from IBM.  Hmmm.


--
David Ebdon
College of Liberal Arts and Sciences
Eastern Illinois University
[e-mail]