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 16:22:36 PST8
From: "Steven Levine" <steve53@earthlink.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: HPFS.IFS bootup system trap

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

In <42191C1B.1E55@peterskye.com>, on 02/20/05
at 03:24 PM, Peter Skye said:

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

IFSs are not device drivers in this sense. They don't have a device
driver header, so they can not appear in the device driver chain. If
exeinfo does not work, it takes a module table scan to convert the cs:eip
to a module name. This is cumbersome and newer kernels do this for you.

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

This is the point when the device drivers are activated, so hardware
problems tends to show up here as traps.

I recommend you try:

<http://www.memtest86.com>

This will rule out failing RAM to some extent.

You probably also should let dfsee check out the partition. Of course if
you can zip, format and restore the partition, that would be useful too.

IIRC, the trap addresses are pretty consistent, so you could have a data
problem on the drive.

While working on this, get:

<http://home.earthlink.net/~steve53/os2diags/DumpTrapScreen.zip>

and a blank diskette and save yourself some writing.

Steven

--
----------------------------------------------------------------------
"Steven Levine" MR2/ICE 2.67 #10183 Warp4.something/14.100c_W4
www.scoug.com irc.fyrelizard.com #scoug (Wed 7pm PST)
----------------------------------------------------------------------

=====================================================

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.