. The only thing with that is to make sure your new drive is equal or larger in size, to the original drive.
Sounds like a corruption of some sort.
I recently did the same thing...ending up with a full backup bootable OS....only time I had any trouble was when swapping and booting with BOTH connected.....both were primary...one on the Primary IDE [the actual boot] and one on the secondary IDE [second boot]....I think it was down to the fact the system was a wee bit confused to have two 'partitions' with identical info.
The problem was in opening a file manager....everything just sat there scratching its head.....however I'm currently running with both attached....C drive and D drive are both bootable OS systems [XP Pro]....and since the 2 of them are in caddies I can switch to either or both in the time it takes to shutdown and reboot.
When I did all this I partitioned and formatted the 'D' via the original OS.....then ran Drive Image 7 ....took about 6 minutes to back up and about 8 to restore to the new one....about 6 gig of data in a 20 gig partition.
Interestingly, XP Activation appears to be happy with both....[which always had me wondering]....
The plan is to make complete 'backups' periodically so the second drive is up to date and can be used if the primary has a terminal episode.
Work data is on a third physical drive and has redundancy backups to alternate partitions on the OS drives...updated daily.
Data such as proggy skins, Litestep themes...created and modded within the OS drive's standard program Files layout are also redundantly backed up to separate physical drives.
All you need then is a weekly data off-take to CD and you're laughing.
There's no excuse for losing work....
| copy my drive C to the E partition on the new |
Why did you have the new drive partitioned? Maybe try wiping it off and do a clone on a "bare" drive. Are you sure you did a clone and not a backup? (Which would be compressed, hence unbootable) Just a thought.

BTW, what kind of message/screen do you get when trying to boot?
[Message Edited]
bordfryr....it's referred to as a backup...and it's compressed....but restoring it decompresses it as well.
EG...my backup of a 20 gig drive...currently called 'C_Drive021.v2i' [it's the 21st backup] is 3.8 gig.....and that's default compression....there is a 'stronger' level....
do you have both drives installed?
if both drives are installed is it automatically booting from the origional drive?
if it does, if you load Administrative Tools does it show both drives and are the partitions *active* ( you might have to IMPORT the Drive into your drive tables for the OS even if it does show up in the list )
if they are, have you tried booting with only one drive installed *the new one*
if you did, did it post, see the drive, then display bios/cmos settings *ide device found int:13 yada yada yada
if so, did it give you any kind of error about *ROMBIOS* or the *OS* not being found
if not, where does it puke exactly? *BootScreen shows and hangs and so on?*
[Message Edited]
Yrag, it's Western Digital
I partitioned the drive so that I can install a Linux OS on the second partition for a dual-boot set-up. Would I be better off to wipe the new drive and copy the original drive to that, then let the Linux installer do the partitioning?
BTW, I'm moving from a 40G to an 80G, with about 25G worth of data on the original.
Thanks for all the responses, I think I may have to start over on this one.
[Message Edited]
When originally doing the back up they worked.
When physically changing the jumpers and possibly the order of the drives on the cable or removing one completely when the slave was changed to Master.
Things were moved about inside the box.
Lending the checking of, jumpers, cables being seated on the drives and also because of a dealing with ribbons and not having a huge amount of room floppy cables can get shifted. I've run into it more than one time where the floppy cable was either upside down or not seated and it would cause the system to not see the drives because they both (hard drive and floppy run off the rail and address the buse controller, int 11, int 13 and int 15)...
or it is/was a software issue...
seems to me that removing a jumper conflict or a cable issue would be first and for most in the process.

probably way off the mark with the above...
the other thing I would be checking would be to set the drives back up as they were when the back up was made and make sure the second drive it Imported into the drive tables of the NT OS. Just because they show up does not mean they will be usable. If they are not then they would show up and when you right clicked on the drive in the Admin Tools you would see that it is a Foreign Partition and or Drive with the option to import it.
I'll be mum now...

[Message Edited]
"I'll take out the garbage when I go to see Mistress China *cough* I mean, when I go to work tommorow"
*heads for computer*
yrag...DI7 is capable of transferring an OS without dramas...from within Windows and therefore much more efficiently.
There 'shouldn't' be a need to get additional proggies to do it when DI7 is such a competent master of it...
| from within Windows and therefore much more efficiently |
Isnt that an oxymoron?
Cerebro...try doing things in lower memory in Dos....640k gets you nowhere fast.
With a Gig of DDR3200 400fsb in parallel [800 thruput] you may just find a slight improvement over Dos....
| 19 by Admin Jafo - 7/27/2004 9:50:12 PM ...try doing things in lower memory in Dos....640k gets you nowhere fast. |
Gee. Paul...I transfer 12/13 GB to my backup drive just shy of 20 minutes...in DOS ...and I get all the files copied, including the Volume Files
/me thinks there must be a clog in that Aussie DOS
Welcome Guest! Please take the time to register with us.
- Richer content, access to many features that are disabled for guests like commenting and posting on the forums.
- Access to a great community, with a massive database of many, many areas of interest.
- Access to contests & subscription offers like exclusive emails.
- It's simple, and FREE!