Mail 2.1, two PBG4s, Migration Assistant and "Short Name" problems

I need to find an answer to these problems before I go nuts. The
situation:

PBG4 w/broken screen, running an external (duh) Samsung monitor. This
is my shop PB, it's currently masquerading as an immobile desktop.

Identical PBG4 with no problems. Mostly keep at home, but also on the
road.

BOTH PBs have the same dual (Airport/Comcast cable modem for home,
Ethernet/SBC DSL for the shop) network settings, user settings, etc.,
and BOTH receive mail from my Comcast AND SBC accounts.

LaCie 320GB external Firewire drive with OS X 10.4.9 installed.

I wanted a way to keep my work and home PBs synced -- especially Mail
-- without dragging the home PBG4 back and forth. Yes, I KNOW it's a
portable, but as I sometimes ride my bike to work, I'd rather risk the
loss of a $240.00 FireWire drive than an I-don't-know-how-much PB --
plus, the FireWire drive is a much smaller package to carry.

I used Migration Assistant to copy the "home" PB's "Users,
Applications, Network and Machine Settings, Files, and Volumes" (just
like the Migration Assistant Intro says) to the FireWire drive (which
already had OS X 10.4.9 installed), then selected the FireWire drive
in System Preferences as the Startup Disk.

The FireWire drive booted up both the shop AND home PBs just fine, but
I had the following problems:

1. The network and machine settings I had transferred from my "home"
PB to the FireWire drive didn't "take" when I used the FireWire drive
to boot up the shop PB. Neither my home Airport/Comcast cable nor shop
Ethernet/SBC DSL settings were available as choices in the Network
Preferences Pane. To use my shop (SBC DSL) connection while running
off the System on the FireWire drive, I had to manually reconfigure
the settings, always a RPITA.

2. I decided -- probably foolishly -- to try it the other way 'round:
I booted up from the shop PB's internal HD, and used Migration
Assistant to transfer the "shop" PBs settings, etc. to the FireWire
drive. Are you dizzy yet? *I* must have been, because -- just as an
experiment -- I tried booting the "home" PB from the FireWire drive.
Once again, the PB booted up just fine; but once again, neither the
home nor shop network settings were available as choices. As an added
joy, I ended up with a ton of duplicate files and folders on the
FireWire drive, labeled "(from old Mac)" including my ENTIRE 25+GB
iTunes library. Thank God it was 320Gig!

3. I think that one of the problems MIGHT be this -- PLEASE correct me
if I'm wrong:

When using Migration Assistant DURING a System install, IIRC there's
no install-process or Migration-process question about the heinous
"Short Name" (the existence/importance of which I was totally unaware,
though I've been installing Mac operating systems since 1989). Using
Migration Assistant OUTSIDE of the System install process allows you
-- if I'm correct here -- to royally screw things up IF you've already
used a "Short Name" during the install process on the Mac that you
now want to Migrate TO that is different from the "Short Name" of the
Mac you're Migrating FROM. I hope somebody else understands that last
sentence, because I know it's logically and grammatically convoluted.

To me, the importance of the "Short Name" should be emphasized
somewhere, either in the System install process, or in using Migration
Assistant AFTER a System install is complete,or -- preferably -- BOTH.
I had NO idea how important the "Short Name" is to the System, and
while I'm not the sharpest crayon in the box, I'm probably not the
*dullest* either.

Anyway, I'd really like to keep the two PBs synced as regards mail and
new or updated files (and settings), but I seem to have over-thought
(or UNDER-thought!) the means of doing so.

What am I doing wrong here, and what's the BEST way to keep my two PBs
(AND the FireWire drive) all singing the same tune, especially as
regards mail, settings, and docs?

Thanks!

Bart Brown

PBG4
OS X 10.4.9

.

Relevant Pages

  • Re: Sysfader shutdown problems
    ... No windows updates have been installed yet. ... It would appear that the problem is, the shop did not save settings ... depending on how the shop went about their install ...
    (microsoft.public.windowsxp.newusers)
  • Re: Win XP Pro Product Key
    ... the shop use an unauthorized method to install ... >No, you settings should not be changed, a Repair ... >> Just so's I understand this correctly, the shop I ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: Creating directories on Vista machines using .NET
    ... One thing that the Access database does is maintain settings relating to the ... dialog box asking which account to run the install under. ... even if I run the install using administrator rights, ...
    (microsoft.public.dotnet.framework)
  • Re: Going about a fresh reinstall
    ... Copy this folder to ... specific programs' settings. ... >the install. ... >those you don't have a clue how you'll restore later. ...
    (microsoft.public.windowsxp.moviemaker)
  • Re: WinSock Problem
    ... yes i did chk the lan settings and made sure nothing was checked in the lan ... i did not check the power management as this is the first ... get onto the update site long enough to do a full check and install. ... trying to be accessed that was not in the catalog yet the winsock fix did not ...
    (microsoft.public.windowsxp.help_and_support)