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 [ 31 | August | 2001 ]

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


Date: Fri, 31 Aug 2001 19:24:20 PDT
From: Michael Rakijas <mrakijas@oco.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.
=====================================================

** Reply to note from scoug-help@scoug.com Fri, 31 Aug 2001 17:45:20 PDT
> Can this be applied retroactively and remedially -- *safely* ? I guess so,
> simce that seems to be what you did.
>
> Jordan

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. Of course, that's what
caused the problem for me. However, whatever space was allocated to the
system files then would have reserved the space needed for any
retroactive reissuing of the SYSINSTX command. That's why I wasn't
worried, but I am not sure to what extent one is protected in its
retroactive use where this process was not followed. It's certainly
possible that files occupying the needed space are safely moved but I
can't say for sure whether this happens.

-Rocky

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

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 [ 31 | August | 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.