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 [ 02 | September | 2001 ]

>> Next Message >>


Date: Sun, 2 Sep 2001 14:26:31 PDT
From: "J. R. Fox" <jr_fox@pacbell.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: Re: Sysinstx

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

Rocky wrote:

> Normally, when you do an XCOPY /h /o /t /s /e /r /v from a drive that
> you boot to, to a drive to which you are "upgrading" assuming HPFS to
> HPFS, the system files are supposed to copy with position information in
> tact. IOTW, OS/2 should boot to the new drive with no problem when it is
> swapped in the old drive's place. That didn't happen for me once
> (although I'm not sure why it didn't work, then), which is what prompted
> me to do the SYSINSTX again, just to make sure.

I was speaking in a much more general sense: Forget the h/d cloning scenario. If, for some
reason, one needed to re-apply the Sysinstx to a partition previously so initialized (I
guess, due to symptoms similar to those you experienced, where the correct boot partition
does not seem to be pointed to), could any harm be done ? That was really my question. It
is even possible I had to do this once, but if so I cannot recall the circumstances. If it
ever did come up, it must have worked, because conspicuous failures I definitely do tend to
recall. And if a partition that should be there for boot purposes is missing in action, I
guess one would have little to lose by trying.

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

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


>> Next Message >>

Return to [ 02 | September | 2001 ]



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.