[820] in OS/2_Discussion
Fixpack 17
daemon@ATHENA.MIT.EDU (Andrew Twyman)
Sun Feb 18 04:21:30 1996
To: os2partners@MIT.EDU
Date: Sun, 18 Feb 1996 04:21:03 EST
From: Andrew Twyman <kurgan@MIT.EDU>
Thanks to everyone who gave suggestions on how to get my
system running again after Fixpack 17 killed it. Backing out on the
service process turned out to get it going again. However, I then
installed the fixpack by booting from the service disks (which are the
latest, unless there's a different version for Warp Connect that I
don't know about), thinking that could be the problem. However, after
installing the fixpack this way the same problem came back. My system
froze just after the openning desktop animation, sometimes before and
sometimes after the launchpad had shown up, but always before anything
else did. Now that it seems that this is indeed a reproduceable
problem, either with my system or the fixpack, does anyone have any
idea what it could be? I downloaded and made the fixpack disks before
installing again, so they should be fine. Is there another fixpack
which is required before 17? The only ones I've installed before this
are fixpack 5 and fixpack 10 (which was for Warp Connect only, I
think). Is there any change made by fixpack 17 which I would need to
deal with? I noticed that it said the tasklist wouldn't run without a
change to CONFIG.SYS, but I use TaskBar anyway so I didn't make the
change, and it certainly shouldn't keep the system from booting. Any
other ideas?
Thanks.
Andrew
