Image for Windows - New Version

Image for Windows version 2.54 was released on March 5, 2010.

Changes:

Improved support for dealing with non-partitioned devices.
Added new /MD (MakeDir) option to have target path automatically created.
Added new /CSIG (ChangeNTSig) option for full drive copies and restores.
Added option to use Volume Shadow Copy Service (VSS) on Windows 2003 or later.
Other Misc.

 

Downloaded and installed.

 

IFW works perfectly for me, their new windows 7 mbr code makes for easy backups for any Win OS. No more NTLDR is missing messages!!!

 

Yep. Good stuff.

If I could add only one feature, it would be the ability to restore to a smaller drive or partition (assuming the data wasn't bigger than the destination). I've asked and they don't plan on adding it.

 

valnar,

That feature has been present since ver 2 was introduced over two years ago. Are you still using ver 1?

You can restore to a target partition smaller than the souurce partition and you can also choose to have the target partition resized even smaller. But as you pointed out, no smaller than the data spread in the source partition.

 

No, I am using the latest, I cannot do it. Support agrees with me. I had to shrink the original partition first, then back it up, then restore it to my new smaller SSD. All instructions from TeraByte Support.

Perhaps you are talking about something else?

 

OK, lets make sure we are on the same wavelength.

I did this about an hour ago. The WinXP partition was 2000 MB. An image was created. I deleted the source partition and created an 1800 MB partition and also another partition, so there was no unallocated space. Using IFD I restored the image to the 1800 MB partition. I then restored the image to the same partition but chose to resize to 1700 MB. Easy.

Is this what you have tried?

 

In Image for Windows, click Backup (Full). Select your OS partition and click Information.

One of my WinXP partitions is 2997 MiB. The Information shows....

1191 MiB Used
1806 MiB Free
1819 MiB to Restore

So I have 1191 MiB of data in that partition but it is spread over the first 1819 MiB of the partition. A defrag may reduce the data spread but at present 1819 MiB is the smallest partition for an image restore. But that's not bad. Going from a 2997 MiB partition to a 1819 MiB partition.

 

Yep, exactly it, but it didn't work. However, now that my PC is working, I can't try it again.

Three caveats though that may have made a difference:
1) I used IFL
2) I had to create the (smaller) partition first on my SSD because I had to align it properly. I then restored TO that partition instead of letting IFL create the partition, because it would have not been aligned.
3) Used a couple different "align" options as instructed by Support, including align at 2K boundary (of course).

 

I don't understand how your setup differs except I don't have a SSD.

I just used an image of a cylinder aligned WinXP partition and restored it to unallocated space using IFL. I used the IFL geometry settings to get Align at 2KiB and that is what happened.

 

??
SSD issue there?

@valnar:
Does BING work on SSDs ?
Did you try shrinking/creating/restoring with BING ??

 

He did recommend I shrink it with BING first, yes. I used a different partition program, but same thing.

 

Did anyone notice with the latest release that you can now mount a TBI file to a drive? I was begging for this feature with terabyteunlimited for some time. Good to see that they listen to their userbase, I'm sure i'm not the only one asking for that feature.

 

Can IFW restore BING images?

 

BING creates ver 1 images so ver 1 IFW can restore these images. But ver 2 IFW has been available for the last 2 years and it is not compatible with ver 1 images.

We expect ver 2 BING to be released in the next few months. It will be a free upgrade for anyone who bought ver 1 BING after June 2009.

 

Thanks Brian

 

Good for the plodders like me who still need like their BINGV1.xx

( all these dangblammed newfangled stuffs )

 

I've been happily using IFW v 1.7x for years. It's saved my butt more times than I care to remember. The other day I checked the site for updates and found that I must have been living in a cave for several years -- all through the major upgrade to v 2.xx. I sent off an email to support to find out how much the upgrade costs. I got a reply with a link to d/l the latest version, with a sort of cryptic message about being able to d/l the latest version, or else get it for 50% off. When I followed the link, there was nothing about any discount -- just a link with a bunch of d/l options with key texts included in the links. Are these keys only for the 30 day trial? And if so, how much does it cost to upgrade to the full program as a prior user of v 1.xx? Thanks.

 

NOTE TO THE ABOVE POST: I looked through the IFD file I d/l'd/extracted, and after reading the User's Guide, I believe that I have the full version, not the trial version.

However, after reading through the Guide, I have questions about compatibility with IFD and SATA DVD writers, SSD boot drives, and current generation SATAIII HDDs. I have an Intel 40GB SSD boot drive, a Samsung 22x SATA DVD writer, and two WD SATA HDDs -- a 1TB 6.0Gbps Caviar Black, and a 2 TB WD Caviar Green Intellipower. Reading through the checkbox options of the "Make Disk" utility, it's not clear to me if there are going to be compatibility issues with this system and IFD because everything I have is SATA -- not PATA. Does anyone have any experience with this kind of configuration? My MoBo is an ASUS P7P55D-E, with an Intel Quad Core i5 750 CPU.

 

Aack
post your list over at the terabyte news group: you;ll get a reply

 

Whatever.

 

@skbaltimore

With the sata you should not have any problems with the default settings.(I have the same WD drives)
But maybe you should email the support about the SSD one.

Panagiotis

 

Thanks. The SSD drive is obviously the key, because that's the boot drive I'll be backing up. I emailed support and David replied and said there shouldn't be any problems with any of my new system's components.