Follow-up to my earlier posts about the hang-up early in the boot process
after installing FP35 on my Cyrix 6×86 system:
Taking the advice of several people, I replaced OS2LDR and OS2LDR.MSG with
the versions from FP26. Since everything then booted up fine, this seems to
have worked around the problem. Thus, it appears that the problem is with
OS2LDR possibly being incompatible with certain Cyrix processors.
I don’t yet know if there are any deleterious side-effects from using an old
OS2LDR (I haven’t tried booting with alt-F2, for example). I also haven’t
seen the keyboard or task-switching problems I’ve read about here, but I have
already noticed some improvement in the efficiency of Win-OS/2.
I have Charles Petzold’s digital clock utility whose border turns green,
yellow, or red depending on CPU loading. Previously, the border would always
turn yellow whenever any Win-OS/2 program was running, indicating a CPU load
of 33% or greater. With FP35, the border remains green except when I’m moving
a seamless session, or when running something processor-intensive like
RealAudio.
I just wish there were a way to notify IBM’s FixPak people about the broken
OS2LDR. Using an old version might work with FP35, but it may not be
compatible with some future release.
TRM
—–== Posted via Deja News, The Leader in Internet Discussion ==—–
http://www.dejanews.com/ Now offering spam-free web-based newsreading