TeraByte Product Release Thread

You should be able to use 2.83.

The changes are made as part of the restore or copy. The IDs and GUIDs (if any) will be changed so they don't conflict with existing ones. More is involved than just changing the MountedDevices values.

 

thanks
can i ask you an advise?
is more healthy for the operation system in this case windows 7 , copy/restore to a new drive , shut donw , disconnect unplug the source and start the pc?

or are really unless with Change Disk ID and GUIDs ?

thanks MudCrab

 

If you change the IDs you can do the procedure in Windows. The source drive won't be affected since there is no "duplicate" drive. The source drive will, however, see the new drive. If it's important that they not see each other then doing the procedure outside of Windows is best.

For a normal copy/restore procedure done this way it's not necessary to shutdown and disconnect the source drive before booting the new drive -- just boot the new drive.

 

Hi MudCrab , it's offtopic , but software like acronis or macrium don't have such feature, in this case the only way it's unplug the source drive after the copy/restore

about

, did you test deeply ? does the destination copy to be activated again ,or other steps to get it work like a fresh install

thanks again!

 

If the activation of Windows or other software is tied to the IDs then it may cause deactivations. This is no different than any time the IDs are changed.

I wouldn't recommend you use that option for repeated restores. For example, people that daily/weekly clone and swap drives -- probably better to keep the IDs in that case.

Keep in mind that regardless of the options used you are still going to be running Windows from a different physical drive and it will be detected as such by Windows.

 

Hi Mudcrab

reading around the forum there is a nasty case https://www.wilderssecurity.com/showpost.php?p=2316076&postcount=60

is image for windows affected too?
i mean copy a solid disk to a bigger(larger) solid disk, could remain space unallocated?


in short should i enable some option or should check some option to copy/restore a solid disk 128 to 256 correctly without unallocated space?

thanks

 

Hi Mantra,

There is nothing wrong with the above situation, neither it is a nasty case. Basically, if you clone a 140GB hard drive to a larger Disk, the clone will produce a 140GB exact cloned copy and the rest of the space will be unallocated. Then you can with any Partition Manager Program or in Windows Disk Management allocated this space. You can size, re-size, allocate, un-allocate to your heart content. This is the normal behavior of any cloning program. You cannot clone to a smaller Disk, even thought the complete Data on the OS Drive is less than the replacement Disk.

CASPER is something special. If you clone a 140GB hard drive to a larger drive, it will show all the space allocated. After that, then you can with any Partition Manager Program or in Windows Disk Management allocated this space. You can size, re-size, allocate, un-allocate to your heart content.

What is special about CASPER is that you can setup an replacement Disk for your OS Disk and they both can be connected all the time. CASPER will do an initial clone and then any changes to your OS Disk, CASPER will clone only those changes to the replacement Disk. The idea is that in case of your OS Disk failure, you can substitute the cloned replacement Disk anytime. You can boot with both of these connected and both will show up in Windows Disk Management.

The replacement Disk can be bigger or smaller in size than the OS Disk, but it has to have enough space to accommodate the complete data on the OS Disk. Again, this is something special to CASPER.

Best regards,

Mohamed

 

You can use the Scale to Fit option to resize the partitions to use the larger space.

 

does someone restore/copy to a new solid disk (bigger) without the option Change Disk ID and GUIDs ON , and lost windows 7 activation or software activation like photoshop cs5/cs6?

thanks

 

mantra,

What concerns you about copying the OS partition to a new drive? Windows will still be activated on the new drive. So will Photoshop.

 

Thanks Brian , did you test them ?
again super kind Brian!

 

I copied Win8 from HD0 to HD1. Both OS are Activated. Photoshop is too. This was a Partition Copy, not an Entire Drive Copy so the Disk IDs were already different.

I boot both OS with BIBM.

 

Image for Windows: Upgrade History

Image for DOS: Upgrade History

Image for Linux: Upgrade History

BootIt® Bare Metal: Upgrade History

OSD Tool Suite: Upgrade History

 

hi
i did notice in the winpe ,in the default settings there is Write Standard MBR Code ON

is normal?

thanks


Merry Christmas

 

Ugh. Looks like they changed the file format again.

 

Not a problem. Just create a new restore disk. If you don't want to do that, (I don't know why one would want to restore images using an old version and create images using a new version) then use the "Backwards Compatible" option when creating images.

 

No kidding.

It's not that, but WHY he changed it is what I am concerned about. Problem with the last format? Just faster or more efficient?

 

Yes it might be for better compression and faster

 

This program is updated quite frequently. While I appreciate the effort that goes into maintaining and improving the program, not everyone wants to make changes for something that works well. I just checked and on one of my pc i am using Version 2.69, so I guess the update is overdue. I looked at the FAQ on their website and while they have a listing for update, it does not specify the procedure in detail. Can I just install on top or should I uninstall the old version first? I also saw in one of these threads that I should do a new recovery disk -for future reference where can I find out if an update requires burning a new recovery disk?

 

Sure. That's OK.

But there have been a huge number of improvements since 2.69

http://www.terabyteunlimited.com/upgradehist-image-for-windows.htm

To update, just install the new version over the top of the old. I always use recovery media of the latest version. An IFL flash drive is my favourite recovery media.

See above link. For example, you can't restore a 2.86 image with 2.85 recovery media unless the image has been created with "Backwards Compatibility".

 

Thanks Brian - very helpful as always

 

beethoven,

I'm sure you know but for other who have IFW, you are also licensed for IFD, IFL and TBOSDT Pro.

 

Thanks Brian, yes I am aware of this but need to study the manual again how to properly use the programs. I installed the latest version over the top of my old version and this was easy. Taking a new image again was fine and basically this is what I did in the past - (taking images just in case). Only very early on I had to actually use an image to revert back after some corruption issue.
Getting the rescue disks is still a bit unclear. I did the make disks using both IFD and IFL and while the creation of the rescue disk is so quick, I am not quite ready for using it. IFD boots up fine but it does not find my new image on the external drive plugged in via USB. Not sure if I need to use a second internal harddrive or should have used some other of the options during the rescue disk creation to allow IFD to use external usb drives.
IFL seemed to have some issues with respect to the video card and again I probably have overlooked some of the options during the creation process.

 

beethoven,

This is a common issue with IFD. Try choosing BIOS instead of USB when searching for your image. With images on USB external HDs, IFL works better. Or you can use IFW in TBWinRE.

Does IFL work?

Yell out if you would like to create a TBWinRE.

 

Not sure what you mean, the bootsequence in Bios is IDE CD-Rom Device, then Hard-Disk Drive C. So the actual boot using IFD works fine but once IFD opens I am not given any chance to search for the image. I can see 3 options (backup to an alternate drive, restore a backup or validate a backup) and no matter which option I choose, TFD tells me "no backups were found" wondering if the drive is plugged in. Yes, it is and once I boot normally, the image can be accessed.

not really, I end up with a screen of colourful lines - that's why I suspected some issue with the video card. Not sure if in building the recovery disk I should pay more attention to the hundreds optional ticks I can make - I basically left things as per default hoping this would do.

Edit: Just tried again and changed the option for screen resolution from 1 (best) to 2 and this time TFL showed up fine, giving me 4 options. Just for testing I choose validate and could access the relevant image without issues. It's doing the validation now. I suppose this is all I really need in case of an emergency?

I recently went through the exercise of building the relevant windows rescue disk with Macrium and while this took some time with lots of downloads, at the end I had a fully operational disk with nice gui that even I could follow. If the TBWinRe is similar, yes, please - maybe I should give this a try.