Specifications
Page 12 Blue Chips Magazine —December 2010
migration! A single license of PCmP
allows you to migrate from a single old
(source) computer to a single new (des-
tination) computer. Additional com-
puter migrations require the purchase
of additional licenses. As part of the
checkout process, you will be given the
option to purchase additional licenses
at a 25% discount.
“In the nightmare world of PC mi-
gration, PCmover is a rare pleasant
dream. Transferring from one system to
another via PCmover was an amazingly
simple and pleasant experience. The
results were outstanding. Everything
landed exactly where it belonged…. in
ve migrations (three Vista-to-Vista,
and two XP-to-Vista), the results were
amazing - every single time…PCmover
performed as advertised, which is a rare
thing in today’s software environment.
While all software publishers brag about
how amazing their goods are, Laplink
actually has reason to.”- Joel Durham,
PC Magazine
Some Extra Caveats
After you use PCmP to set up your
new (destination) PC, you may need to
remove certain programs or les from
either your old (source) PC or your new
(destination) PC to remain in compli-
ance with the End User License Agree-
ments (EULAs) of your software. Also,
to maximize system compatibility, PC-
mover may not transfer certain system
settings. This may affect system utilities
(such as antivirus and antispyware) and
other applications that install system
services. You may need to reinstall those
applications on the destination PC. Ad-
ditionally, PCmover does not transfer
hardware conguration information, so
printers and other hardware may need
their drivers installed on the destination
computer.
Files with Digital Rights Manage-
ment (such as certain music les) and
applications that require keys or serial
numbers with a hardware ngerprint
may require reactivation or may not
function properly on the destination PC.
While reactivation or reinstallation will
usually resolve any problems, you may
need to contact the appropriate vendor
for specic instructions.
Note. Also refer to the Laplink web
site Knowledge Base (KB) for additional
help with any PCmover problems, plus
you can always get in touch with their
Tech Support (See above).
And Now, The “Dreaded”
Migration Story
I use the term “dreaded” advis-
edly, maybe even, ill-advisedly,
simply because of my history of
problems with, you know my by-
line, HIAWC? To begin with, I actually
had four (4) options to choose from to
make the actual migration. In the end I
chose the Laplink USB 2.0 Cable migra-
tion method over all of the other Con-
nectivity Options (See above).
Well, I followed the PCmover
User Guide to the letter. I even printed
it out so I wouldn’t make any mistakes.
Surprisingly, you know, it turned out
to be very simple, in actuality. Whew!
Pre-Installation checklist
(both PCs)
After making doubly sure I had
all the System requirements for
each PC (See Part 1), Installing PC-
mover (both PCs), Pre-Migration
Checklist (both PCs) and Migra-
tion Information Sections covered
like a blanket, as indicated in the User
Guide, I installed the PCmP software
without a hitch on the Destination PC
5
rst (like the User Guide said to do), I
attached the Laplink (orange) transfer
USB cable to a Dlink USB 2.0 4-port
hub, and then installed the PCmP soft-
ware on the Source PC
5
(like the User
Guide said to do), I attached the other
end of the Laplink (orange) transfer USB
cable to a USB 2.0
port on the Source
PC (like the User
Guide said to do),
Then, I started the
Migration (like the
User Guide said to
do), Oh! No! It’s
HIAWC, syndrome time again.
The destination PC (Vista)
Acts Up
The destination PC (Vista) started
off real good, the only thing was I got an
Error message stating that the “Snap-
shot of the PC did not start properly!”
That may not be the same identical
wording, but it’s trouble spelled with a
capital “T”. At least that’s what “immedi-
ately” went through my mind, given my
proclivity for “PC Troubles, especially
with a capital ‘T’?”(See Part 1)
Well, here are my thought process-
es, in maybe not exact order, but, since
I only had about a day and a half before
my publishing deadline to solve the
problem(s) with tech Support, I “Froze”
the Error Message up on the monitor
screen, didn’t touch it again, and im-
mediately started the processes so very
well known to me - getting in touch with
TS. Turns out, I missed the rst window
of opportunity to talk to TS, i.e., in my
half-day time frame, because they are
on EST (not PST, a 3-hour difference, to
begin with) plus, I didn’t see the answer
to the problem as pointed out to me in
an e-mail from PR/TS, the next day:
Laplink e-mail: “This issue is
mentioned on page 16 of the User Guide:
(http://www.laplink.com/documenta-
tion/pdf/pcmover/pcmpro/PCmover_
Pro_QSG.pdf).
You can also nd steps to resolve
this issue here: (http://www.laplink.
com/faq214.html”).
We now continue the saga, as
it is unfolding rapidly for me in a
“hyper-sweat.”
OK! The cheese definitely is
getting more binding now. But
no sweat, “mai pen lai,” as they