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 [ 11 | May | 2006 ]

<< Previous Message <<


Date: Thu, 11 May 2006 11:01:39 -0700
From: J R FOX <jr_fox@pacbell.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: Live Help Desk at May general meeting?

Content Type: text/plain

--- Ray Davison wrote:

> Partitions do not change size during copy. The only
> issue is that the
> target space must be as large as the source - or
> maybe one sector larger
> depending on the copy tool.

No, I resize first (with DFSEE), then move the boot
partition farther down the drive.

> Relative position can effect drive letters.

All position is relative, otherwise there would be no
point to doing this expansion / migration. But I'm
talking about no additions or deletions in the
partition lineup, and nothing swapped or interjected
between the partitions that were there before. There
is, however, some intervening freespace blocks, while
one is still working on this.

> If you want an exact clone of the drive use DFSEE
> copy disk-to-disk.

I DID that, but from an 80G to a 120G. Now, I'm
enlarging the Dark Side partitions (and certain
others), which were beginning to "bang their heads on
the ceiling" for lack of ideal space, as things stood
on the smaller drive. This necessarily entails
sliding cloned partitions over a certain distance.
And Win is very unforgiving about this. If you'd care
to see more specific detail on this, I expect to be
posting to the DFSEE group shortly.

> If
> you want one partition at a time so you can resize,
> use PM 6.

Been there, done that -- with one tool or the other
(actually PM 8.01), or with a combination of both,
trying to take appropriate safeguards when they were
used in tandem. Different but comparable failures
have been the result.

Thus far, there has been no problem with the one eCS
boot partition I moved a distance of about 6G,
relative to its original location (I'm thinking it
would have worked at a distance even considerably
greater), but the one W2K boot partition I've tried to
move doesn't want to travel any distance at all and
still boot. Prior to that, it was expanded and
continued to function normally, although it is
necessary to CHKDSK /F (before the expansion), defrag
it (preferably before and after), and desirable to
adjust the file size to the new partition size.
Applications or data partitions have not posed a
problem with these procedures.

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

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


<< Previous Message <<

Return to [ 11 | May | 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.