Any risks of using ghost on a laptop...?

MooCow

[H]F Junkie
Joined
Apr 13, 2000
Messages
8,209
Simple question...


Besides backing stuff up and all, is there anything different between ghosting desktops and laptops?

A friend of mine just got a new laptop and he wanted to move all his stuff over the the new one. My plan was to just ghost over the new laptop's HD. Assuming we can make a boot disk for a NIC w/ drivers, dump the image to a ghostserver, then ghost to the new laptop, overwriting everything on the new HD. Before swapping it in, we'll pop the new HD into the old laptop, and run sysprep on it, before popping the new HD into the new laptop.

Just wanting to make sure before we make the switch.
 
nope, you should be okay.. we ghost laptops at work, like all the time, never ran into any problems.

go for it!
 
mjz_5 said:
nope, you should be okay.. we ghost laptops at work, like all the time, never ran into any problems.

go for it!


I use ghost on my lappy just fine, shouldn't have a problem like he said "go for it!"
 
Might I suggest using Ghost 2003 for this. I've got 2003 and Ghost v9 and I think you'll find the experience rather unpleasant using v9. It does, however, make an excellent boot disk for restoring images from my external usb drive - but it's raw evil trying to create an image to use on a bare system unless you're making it with 2003.

I tried using Acronis to image it, and it's much much slower to go from image -> drive than ghost v9, but it's almost identical image -> drive and drive -> image as ghost 2003.
 
I will agree that Acronis is slower than Ghost, however I love the DOS networking support that Acronis has built into their product. I will live with the speed, just need a real robust program that supports networking.
 
What about those EZ Gig thingies... I know someone who has one but never had a chance to really use it. I guess these could be useful if you just can't find the NIC drivers for the laptop?
 
BSOD after replicating the "ghosted image" onto the new machine... IRQ_LESS_OR_EQAL (or something along those lines) - No idea why... I've had mixed opinions, some say it's to do with chipsets etc but I understood SYSPREP was supposed to strip all hardware information etc...
 
Hmm, well we haven't had the time to do it yet, but I was thinking of installing the drivers of the other laptop to the current laptop before we do it. Maybe Windows will stick it in the driver cache directory? Is this right? Yeah, I've seen that IRQ_Notless equal bullshit before, but it was due to hardware overheating, nothing configuration based... oh boy.
 
Back
Top