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 [ 03 | January | 2008 ]

>> Next Message >>


Date: Thu, 3 Jan 2008 08:02:11 -0800
From: "Steven Levine" <steve53@earthlink.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: Tricky disk

In <20080101010153.JITT22150.mta10.adelphia.net@[192.168.1.20]>, on
12/31/07
at 05:01 PM, "Michael Rakijas" said:

Hi,

Happy post New Year...

>> You might try using /!BM or /GBM. You can apply these to either th
>> adapter or the unit. See Dani506.doc.

>No joy. Neither parameter alters the non-appearance of the drive in
>either the volume manager or DFS.

You'll save yourself some time by checking the Danis506 output first. If
the drive is not visible to Dani506, it's not going to be visible to the
upper level components.

>Using ibm1s506.add causes the analysis machine to hang just like the
>source machine did.

That sort of implies that danis506 sees the drive and then decides it
can't be used because it's not responding properly. How ibm1s506 dies is
a bit irrelevant, since this is a case of GIGO. However, it is another
data point.

>stuff there that is non-recoverable (I know, I know ... backup but then
>this is one of the youngest drives in a pretty lightly used machine ...
>who'da thunk it?).

Well, think back on what you learned in your probability classes. There's
also the Murphy rule, which IIRC is taught in the class that covers fault
tree analysis.

A couple of more things to try. Try /!BIOS with Danis506. Try the dfsee
bootable CD and select the low performance drivers. This will effectively
use the BIOS to access the drive.

Steven

--
----------------------------------------------------------------------
"Steven Levine" MR2/ICE 3.00 beta 10pre #10183 eCS/Warp/DIY/14.103a_W4 etc.
www.scoug.com irc.ca.webbnet.info #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".

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


>> Next Message >>

Return to [ 03 | January | 2008 ]



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.