Trouble with Ghosting

[MadeInJapan]

I just got a T30 and I already have a 600E. The drive in the 600E is a 40Gig 7200rpm so I want to use it in the T30 and use the origianl drive as one to back up the faster drive. I also have a 12Gig drive that originally came with the 600E. The data on my 40gig drive in the 600E is loaded with W2K Pro and has about 7gigs on it.

I have been trying to Ghost the 40gig drive to the 12gig drive with Norton Ghost 7.0 and it completes okay (I have the second drive in an ultrabay HDD adapter). The problem after I've ghosted and use the ghosted drive to boot the 600E, I get an error message that says "your computer has no paging file or the paging file is to small." It tells me what to do to correct this, but every time this warning comes up, the computer reboots and so I never get into windows to fix the problem. I need help. Can anyone offer it?

I'm currently defragging the 40gig drive that I ghosted from and will try to ghost from it again after defragmenting it. Thought this might have something to do with how the 12gig drive accepted the files. If the files were spread out over the 40gig drive, then I would think that the 12 gig drive would have trouble. Anyway, these are my thoughts right now, but if anyone has had a similar thing happen to them and know how to solve this problem, please post here and let me know what to do before I waste any more time.
Thanks!

[nenarek]

I'm not totally sure if this addresses your problem, but this web page discusses a problem that sounds really similar:

http://www.infinisource.com/features/ba ... p1-pf.html

And here is the second part that talks about a work-around:


http://www.infinisource.com/features/ba ... p2-pf.html

[ZPrime]

I had this happen on a machine that I upgraded from NT4 WS to XP Pro. Whenever I tried to actually GIVE it a paging file, it would never properly create it. I ended up reformatting the machine from scratch to fix it - a repair install did NOT solve the problem. I'm assuming you've tried using safe mode to get into Windows?

One thing I can ask - when you ghosted the 40 -> 12, did you leave the 40 in the system when you booted the 12 again? This could've caused the problem. After ghosting one drive directly to another, I always REMOVE the first drive from the system (or at least disconnect it) before trying to boot the freshly created image.

MS has a KBID about this, but it never solved my problem (even though the machine in question DID have an Intel motherboard as the KB article mentions).

Good luck... as I said I ended up reinstalling the machine in the end, but I also didn't try calling MS support because the data on the machine was very easy to backup/restore.

[MadeInJapan]

Ghost...wow, what a great program! After I defragged the source drive (40gig) the 12gig, destination drive took very well and the computer booted up with the 12gig drive without any problems....I did take the 2nd drive out as you suggested!

[jwschmid]

I had a similar problem when I ran W2K. I used to clone with source in the regular drive slot and the clone in the drive bay. If you leave both drives in and reboot after ghost finishes...the cloned drive gets assigned a "d" drive letter. When you swap it back into the drive slot, it comes up with the same error message. After hours of fun, the following is how I fixed this:

http://support.microsoft.com/default.as ... -us;223188

I do not have this problem with XP.

Hope that helps.

John