wrote:
> First, it installed on a clean primary where it
> would not on a
> partitioned drive, right. If so that matches much
> of my experience.
Yes, BUT -- quite to the contrary -- we dropped the
1.2GA install right down into E: of an already heavily
partitioned drive, with an assortment of FAT-16, HPFS,
NTFS, and one FAT-32 (incl. two functioning boot
partitions of W2K, a DOS C:, one boot partition of eCS
1.1; the rest are data or storage partitions belonging
to one or another of these), and it worked. Not
immediately and completely, but we finally got there,
courtesy of a couple Help Desks and Steven leaning on
it heavily throughout the process. However, I did all
the original partitioning *myself*, using much the
same tools in -- as nearly as I can tell -- much the
same way. The major difference seems to be a somewhat
larger HDD from a different mfr.
> But you still don't quite get it. Don't install it
> on the drive you want to use it on.
This is probably *not* the drive that is going to go
into the Shuttle, for other reasons.
> Don't you have an old, small
> drive,
No, not anymore. I think they've all gone to be
raffle prizes.
> and a normal desktop machine?
No, my "normal" desktop machine is all-SCSI. Remember
? Steven described this machine (the Shuttle) as
being rather Vanilla. So, I *should* be able to just
attach a fresh HDD to the controller and get the sort
of results you are describing.
> Make a basic install on that and
> keep it in storage.
> It's called make the backup first.
That's kind of what I'm trying to do here, except that
the install(s) can be the re-useable basis for trying
other things as well.
> And don't get
> so hung up on
> images of partitions. The full, real partition
> doesn't take much
> longer to copy. And you can actually use it as a
> boot drive.
Just a convenient means to an end. If a good boot
partition exists, it can be relocated by one method or
the other.
> But the biggie is; if you wanted it E:, why did you
> let it be called
> C:? Install LVM lets you give it any drive letter
> you wish.
I didn't know you could do that. The point is that
all the hardwired location Pointers within the boot
partition (not just in CONFIG.SYS, where they are easy
enough to change, but in the system INIs and wherever
else such info gets stored) that rely on a drive
letter need to be what they're supposed to be in the
end. I think Jim Read or Larry Martin told me that
one of the ideas behind UNIMAINT'S Portable Restore
was to get free of that issue, but it was never
actually achieved. (If it had been, that would be
something pretty remarkable.) Anyway, if you can have
LVM enforce this result -- on any install that you do
-- that would solve one big problem.
> I have
> now made about six installations to a 3G drive,
> copied them to a 160G
> storage drive, and then copied the one I wanted to a
> working drive.
> That way when you - or the gremlins - make a mess of
> things, you get
> one from storage and start from there.
I'm trying very hard to get to where you already seem
to be. Except that I'm ultimately more ambitious in
regard to the final result -- via Migration or other
means -- because I'd like to leap ahead to encompass
all the app. installs and customization I already have
in the existing partitions. But, first things first.
You need to build fancier from more modest structures.
> If at some
> point you get an
> installation that you like copy that to storage and
> make that your backup.
I will.
In the meantime, what's up with that flakey partition
I just installed to ?
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 <<
>> Next Message >>
Return to [ 28 |
February |
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.
