Swapfile

[GW]

I ghosted an image from one drive to another. When I boot
the new drive - I get a "swapfile too small" message. I
tried increasing the size and redoing the image - NG.

 

[George Hester]

Make sure the NTFS permissions on the drive where the pagefile.sys exists has Everyone Full permissions.

 

[Bill Crocker]

Try setting it to zero, then re-create it.

Bill Crocker

 

[Dave Patrick]

This article may help.

Unable to Log on if the Boot Partition Drive Letter Has Changed
http://support.microsoft.com/?id=249321


--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft MVP [Windows NT/2000 Operating Systems]
Microsoft Certified Professional [Windows 2000]
http://www.microsoft.com/protect.


:
| I ghosted an image from one drive to another. When I boot
| the new drive - I get a "swapfile too small" message. I
| tried increasing the size and redoing the image - NG.

 

[Guest]

Do you know WHY this happens

Because the amateur progammers didn't foresee people wanting to CLONE hard drives out of sheer convenience. WHY? Probably because its convenient

When you clone a drive, and then proceed to boot up Windows with your cloned drive visible, two C: drives exist. A stark dilemma for amateur programming. Rather than program a "smart" OS that can track C: drives by the drive manufacturer tag, the amateurs went ahead and programmed the OS to AUTOMATICALLY RE-LETTER any additional C: drives that the OS may encounter - foregoing all thought to the REGISTRY SETTINGS. This causes the swapfile record in the registry to look for the C: drive but can no longer FIND IT because the OS has brilliantly AUTOMATICALLY REASSIGNED the drive letter. This can ALSO happen when you break the link between RAID drives in a SERVER for heaven's sake - as if they don't want us to recover from a RAID failure!!

To solve this, you need to disconnect ALL HARD DRIVES except for the troubled clone drive, find a machine with a working copy of DOS, make a DOS floppy boot disk with the old DOS fdisk.exe program and type A:\FDISK /MBR

This will effectively delete the problematic MBR with the problematic drive assignments on the problematic hard drive with the problematic OS and allow you to boot it successfully - files, applications, domain permissions and all - as if it were suddenly a "smart" OS

This boneheaded programming caused me deep pain during my most imminent hour - when a failed primary server drive could not boot from its mirror. Backup Domain Controller you ask??? Destroyed in another office building that burned to the ground in a fire. Disaster recovery? This OS is definitely not designed for it

Just more venting

Cheers.

 

[Guest]

I missed you flame there except for the last posting but it sounds as if you
cloned your drive and had problems.

Care to re-explain as I also have used IMAGES on my servers and am able to
restore them to a working state in 20 minutes or less.

As far as your little comment on disastor recovery, it almost seems as if
you blame MS for a bad recovery scheme that you may have done.

When you had the idea on cloning a partition, did it ever occur to you that
you needed to HIDE the original partition? I have a feeling that you opted
NOT to HIDE the partition since you seem to have 2 C:'s

Also, why r u cloning the C: instead of making MULTIPLE IMAGES?

I have 4 images that I can fall back, do you?

 

[Bob I]

Because the programmers can't forsee every boneheaded thing users can
manage to do to mess up a working operating system, that's why.

 

[Guest]

hey ... . . Karl . . . ..

I'm the "idiot" that actually FOUND THE BUG 7 years ago and posted to MS knowledgebase

OK now

Stay tuned for more flames

Bye.

 

[Guest]

touché Bob

.. . . touchÃ

Blu

 

[Guest]

and another thing . . ... K a r l ..

I have 20 images in 4 different locations to fall back on

Sometimes, those darkest hours of our lives propel us forward in ways that you cannot ever imagine

BluScara
CIO/CT

p.s. I'm still going to flame. so nannynannybooboo

 

[Guest]

BluScarab
CIO/CTO <-- ???

p.s. I'm still going to flame. so nannynannybooboo

===============================================

CIO / CTO of what company? PeeWee's Playhouse?

Seriously, you say you posted this issue 7 years ago? Why now are you
discussing it? You really hold your grudges.
What issue exactly is that BTW? Cloning you C: and not hiding it causes
your system to get confused? Well, no kidding. It's so simple to understand
that I am a bit confused over your posting about it. Again, since I don't
have your original posting to read, I am only going on what I read.

So what is your problem?
Do you not know how to properly clone a system?