SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, 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.

The Southern California OS/2 User Group
USA

SCOUG-HELP Mailing List Archives

Return to [ 20 | February | 2005 ]

<< Previous Message << >> Next Message >>


Date: Sun, 20 Feb 2005 15:24:21 PST8
From: Peter Skye <pskye@peterskye.com >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: HPFS.IFS bootup system trap

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.
=====================================================

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.