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 [ 15 | November | 2002 ]

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


Date: Fri, 15 Nov 2002 19:44:02 PST7
From: "J. R. Fox" <jr_fox@pacbell.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: Re: Cable / Connector / H-D

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

> >If the cable itself was going bad, I might expect to see some problem re
> >the other H/D connected to it. This leads me to suppose it is more

Steven replied:

> I wouldn't.

By which I take it you mean that some "lines" (cable filaments, or whatever they're called) are working properly, and
others not, such that one might get quite different results from the two drives -- i.e., even if the connectors & / or
the hard drives themselves are not misbehaving ?

> >I'd still like to hear the answers to the questions I posed re the best
> >procedure for cloning the boot H/D to its spare twin.
>
> Well, this is not something I do a lot. Last time was while migrating to
> a larger drive, I used PM 3.05 to copy the partitions without resizing
> anything. I did this later. Next time, I might use dfsee.

Initially, I was thinking more in terms of the preliminaries. Presumably, I would temporarily disconnect H/D #2, and
connect the bare drive duplicate for H/D #1 in its stead, having set the SCSI i.d. of the duplicate-to-be to what the
SCSI i.d. of the 2nd. H/D had been, to avoid any conflict. Assuming this hardware arrangement still boots, then what
? I probably would not partition or format anything, because that is probably superfluous. (This also removes the
chance to confirm no bad spots or do burn-in testing ?) I would probably use GHOST or Drive Image 4.0 for
drive-to-drive cloning, because I have some basic familiarity with these. Other than that, I'm kind of stumbling
around in the dark without a flashlight.

I can't make the meeting tom'w., so we'll have to continue this on the Help List.

Jordan

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

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
"rollin@scoug.com".

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


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

Return to [ 15 | November | 2002 ]



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.