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 [ 25 | April | 2006 ]

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


Date: Tue, 25 Apr 2006 09:35:27 PST8
From: "Steven Levine" <steve53@earthlink.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: trap 0008

In <200604251552.k3PFpjSO230470@pimout7-ext.prodigy.net>, on 04/25/06
at 07:53 AM, sshapiro@ucsd.edu (Sandy Shapiro) said:

>>to list the loaded device drivers. Scan down the Strategy column for the
>>driver with 818 to the left of the colon. This is the CS value assigned
>>to the driver.

>Here is the Theseus output. I am not sure what to do with it.

Neither am I. ;-)

>There is a
>driver with 0 next to it. Is there a way to delete it that is safe?

You don't want to delete this, unless you want to run your system to stop
running :-)

The image is a bit hard to read. Would you please do Output->Saveas and
save the driver list to a text file? The Theseus menus are a bit
non-standard, but if you hunt around, you can find all the typical file,
clipboard and search operations.

Since the trap in is os2dasd.dmd, this points to either a driver problem
or a disk hardware problem. Since the trap 8s occur only when booted from
this volume, I'd suspect a driver first, although there could be a problem
with the boot volume.

First thing to check is the driver versions for

os2dasd.dmd
os2lvm.dmd
danis506.add

If these match the versions on the working volumes, I'll have to try to
figure out what os2dasd was doing based on the trap address. If the
version match, I'll need the bldlevel output for each driver.

Steven

--
----------------------------------------------------------------------
"Steven Levine" MR2/ICE 2.67 #10183 Warp/eCS/DIY/14.103a_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 [ 25 | April | 2006 ]



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.