The swap file can get on there.
Nope, not without the user telling XP to put it there it cant.
How it happens I am not sure.
Thats obvious.
When it *DOES* get on there, that is one of the things can really go
wrong.
Nope. If it discovers its gone for whatever reason, it just recreates it.
A more likely scenero is that the GUID's of the disk are the same
They certainly are initially, but wont stay the same for long.
and when he booted with the both drives attached, settings on the boot
drive point to the second disk.
The original drive, anyway.
A side symptom is that it is looking for a swap file in the wrong place.
Nope, when you clone the original, the swap file gets cloned too.
Granted, windows does not look for a disk with the most amount of space
and put the swap file there. If, for some reason, there is not enough
space on the primary partition for the swap file, it will find space
available somewhere else
Nope.
or balk.
Thats all that will happen. You get the usual moan
that there isnt enough space on the boot drive.
I am guessing that should that happen, then you will end up with a swap
file on a drive other than the boot drive.
Yes its a guess. No it doesnt do it like that.
I know I have put on an SATA and found the swap file unaccountably on
that disk.
You stuffed something up rather comprehensively.
Most likely you had already specified that the swap
file should be on other than the boot drive, and then
replaced the drive you told it to put the swap file on
with the sata drive. It noticed that the swap file was
no longer on the drive you told it to put it on, so it
recreated it on that drive, like it always does if you
just deleted it with XP not currently booted etc.
But then I had run out of space and
the disk was a disaster to start with.
I got on this thread late and do now know what the story is.
You presumably meant to say 'do not know what the story is'
Maybe it is a laptop
Nope.
with a hidden partiton that cant be copied and that is the real problem.
Nope. You can clone a drive with a hidden partition fine.
That wont stop XP booting the clone as long as the
original drive is not visible for the first boot of the clone.
I do know that acronis does not copy any swap file or hibernate files.
It does if you CLONE. It doesnt put it in an image file.
A clone of the boot drive will contain information as to where the swap
file is.
And XP will just create one if say you delete the
swap file outside XP, say after having booted
an OS on CD, and then just boot XP again.
I think his problem was caused by first booting the new drive with the
old one there.
Yes, but in this latest detailled list of what he did,
he did try to boot the clone with the old one unplugged.
It isnt yet clear why that didnt boot the clone.
And it appears that it didnt even attempt to boot
the clone in the sense that ntldr was run etc.
I think you have mentioned a number of times that
"bad things can happen" but you never say what it is.
Yes I have.
Yes, the XP boot uses stuff off the old drive and the boot
works fine as long as the old drive is still connected. As
soon as you remove the old drive, you can no longer
boot, because what is on the old drive is no longer there.
It is one thing to complain acount a problem and another to help out.
I've helped out plenty who had that problem
cloning, mostly before you ever showed up.
That isnt the symptom he is getting.
On three occasions I have had the error message "Your system has no
paging file, or the paging file is too small"
Yes, you can get that if the drive is very full.
that is what I meant by zero length page file.
Nothing to do with zero length.
While trying to debug this, occassionally it would not boot at all.
These all occured after using acronis to clone a disk and I failed to
remove the old disk after swapping master and slave. This is not a
problem with acronis, and i first saw a complaint like this on Drive
Image 7 (later Norton Ghost 9).
DI 7 isnt Ghost 9. Ghost 9 is V2i
In at least one case i did find the swap file not on the "C" drive like I
thought.
That would have been because you told XP to put it elsewhere.
I do not claim to be and expert on this,
Just as well.
but the symptom the poster represented seemed exactly like the one I ran
into that left me with a system that would no longer boot,
No its not. You can always boot the clone with the old
drive still visible to XP. The problem is that it will no
longer boot when the old drive is unplugged after you
boot the clone with the old drive visible to XP on the
first boot of the clone.
and when it did I would that that pagefile error.
For a different reason. No one else has reported any pagefile
error when they boot the clone with old drive visible during the
first boot of the clone. And there is no reason why they should,
there will be two pagefiles, one on each drive. And even if the
clone didnt copy the pagefile, XP would just create it on the
first boot with no pagefile. And by definition there must be
enough space for it since it was there on the old drive.
Thats completely mangled. You wont see the drive letters
change if you boot the old drive with the clone visible.
in a round-about way: the GUID gets rewritten and windows can find the
swap file since it now know the correct disk to use.
Utterly mangled. It doesnt work like that.
Thats a steaming turd riddled with errors.
acronis sold true image and easy migrate way back.
Correct.
If you only had true image (this would be version 6 I am thinking of)
then to clone your disk you make a backup and store it as a backup.tib
file. Then, to create a clone, you run the true image restore and give it
the name of the .tib file and have it look for a new drive.
What you mean is that it couldnt clone directly, you had
to create and image file and restore that to the new drive.
Thats nothing like 'required a TIB file to be booted up'
The best way to backup the "C" drive is to boot the recovery CD rather
than run the backup within windows.
And here you mean clone, not backup.
You can backup by cloning or by imaging.
If he has the latest then he doesnt need to do that.
He doesnt if he has 7 or 8 either.
He needs to make sure the new boot drive has the old VSN so it wont count
against him for a reactivation.
Thats automatic if you boot the clone
without the original being visible to XP.
If XP does that automatically that is fine. I suggest he record the VSN
of the original disk in case either or both of them get changed.
No need, just dont allow XP to see the
original on the first boot of the clone.
But then, I get tired of calling m$oft explaining I am not a product key
thief.
Then use Pro with a corp key.
