SCOUG-HELP Mailing List Archives
Return to [ 20 |
February |
2005 ]
<< Previous Message <<
>> Next Message >>
Content Type: text/plain
=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================
Peter,
I don't have any experience with your problem, but I have a suggestion:
If your PC isn't too ancient or limited in resources, I'd suggest
updating to a much more current OS/2. That could make your problem go
away, or at least, make it easier for someone to understand and diagnose.
My "old" PC, which is the one I'm still using for e-mail as I get my
"new" Dell fully up and running, came from Indelible Blue, and I think
the OS/2 system was built on or about May 30, 2000. It is at Warp 4, FP 12.
I added another partition and installed eCS 1.0, followed by eCS 1.1,
and that's what I always boot these days.
I'm not bragging about being more current, nor am I implying anything
about your system being too old to use. But, if you're having trouble,
there are perhaps 5 years of fixes "out there" which you haven't yet tried.
And think of all the hours you can spend, and the fun you can have
_trying_ to update the OS!
Colin
Peter Skye wrote:
> I'm using Warp 4 Fixpak 10. I'm getting occasional system traps while
> booting and always at the exact same point in the bootup process.
>
> Steven suggested ExeInfo. I ran it and specified the CSLIM value from
> the trap screen, and it located my HPFS.IFS driver. (Steven -- I tested
> and ExeInfo displays anything that is within +- 2 bytes of the specified
> CSLIM.)
>
> I also tried Theseus -> System -> General System -> Device Drivers which
> listed every single driver I have *except* HPFS.IFS and didn't have any
> Limit entries for my CSLIM. Go figure.
>
> The trap occurs on about 50% of my boots, and almost always doesn't
> occur when I reboot again. The failure point is after all drivers have
> loaded and all CALLs and RUNs executed, after which the screen clears to
> black and the cursor appears in the upper left corner. If the cursor
> doesn't appear, the trap screen appears a couple of seconds later. The
> trap screen always displays the same CSLIM (f01b).
>
> Anybody have any experience with this particular failure or ideas for
> further testing to determine the cause?
>
> - Peter
=====================================================
To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".
For problems, contact the list owner at
"postmaster@scoug.com".
=====================================================
<< Previous Message <<
>> Next Message >>
Return to [ 20 |
February |
2005 ]
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS
RESERVED.
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International
Business Machines Corporation.
All other trademarks remain the property of their respective owners.
|