TI2010 on Windows 7 64bit
Hi,
just a simple question: does TI2010 Home (build 5055) run on a Windows 7 64bit?
I just installed the trial TI 2010 on a Windows 7 64-bit machine and it does run, but not properly. I just posted my problem and am awaiting a solution before I purchase it.
Hello all,
Thank you for using Acronis Products
At the moment, the following Acronis products support Windows 7:
(!) Acronis Backup & Recovery 10 supports Windows 7 with the following limitations:
- Mounting backups stored in Acronis Secure Zone is not possible;
- Mounting backups located on a network share in read/write mode is not possible;
- The Active Restore feature is not available when restoring a system volume in Windows from a backup stored in Acronis Secure Zone;
- User accounts generated for Acronis services during the product installation may appear on the Windows 7 logon screen;
- Acronis Storage Node does not support tape drives. See Acronis Backup & Recovery 10 Tape Support in Windows Server 2008 R2 and Windows 7.
Dmitry!
do you have an idea when Director suite 10 will be update du Win7
I bought the program too soon
I've installed TI 2010 on a Dell Studio 15 and it worked fine creating the image and recovering the image also. The Boot disk was created but when it is loading it display some messages very quickly in dos window and restart... it never get past that point, no matter how much I try. The only thing that I can read on the very fast display of messages is something related to "group"... any clues?
Thanks
Have you downloaded the TI 2010 ISO file from your Acronis account and created a CD from it? It uses a different loader and (usually) more updated drivers. It also has a different menu with preset startup options to help with troubleshooting. One of them may allow TI to start successfully.
I just installed TI2010 (version 10.0.0.4871) on Windows 7 Enterprise SP1 64-bit, but when I try to run TI, it says there's a compatibility issue. What gives? The PDF said it works on all editions of Windows 7.
Shoeless,
I think you might have installed TI 10 by mistake, version 2010 has an internal version/build number of v13.7160.
TI 10 won't work in W7, TIH 2010 will.
FYI: ATI 2010 won't support USB 3.0 ports.
It's True Image Home 10 The PDF states the following:
1.4.2 Supported operating systems
Acronis True Image Home has been tested on the following operating systems:
Windows XP SP3
Windows XP Professional x64 Edition SP2
Windows Vista SP2 (all editions)
Windows 7 (all editions)
My copy, apparently, isn't compatible even though the PDF states it should be. Someone else said they were having the same problem. I just wonder if it's a Service Pack or update issue, and if there's a workaround.
Shoeless,
Versions 10, version 11 and version 2009 did not include support for Windows 7. Support for win 7 began with the 2010 version.
Here is online pdf for Acronis 10, note on page 8 that Win 7 is not listed. Perhaps the version you examined was a 2010 version.
page 8 of this link
http://pdfsb.com/readonline/5a566c4866517838563364394148786b-42968
However, you may find this posting of interest as it is an example of version 10 being somewhat used with Win 7.
http://forum.acronis.com/forum/5908
Thanks, GroverH. Good info to have. I learned that there's a TI10 and a TI2010. How confusing, and thanks for that, Acronis!
Guess I can deal with the BCD issue and still use TI10 till I get a newer version. Sounds like people aren't thrilled with the newer versions, though. Maybe I could hunt down TI2010 and use that for the restore like the one poster said which saved them having to deal with the BCD issue altogether.
If you intend to buy any version, I would buy version 2013 for its updated support. This release has been out for 6 months so a fix issue is a possibility whch will be available free to all owners of 2013.
Shoeless, you might keep an eye on someplace like eBay for TI-2010, if that is what you want to use. I have every release of ATIH since True Image 11, and I'm using TI-2010 for my backups. It seems to be very reliable and I've not had any problems with it at all. Be sure to download the current build (7160) when you install it. If you would like to run it in a "stand alone" environment (which is how I do my backups) let me know, I can send you scripts to install the TI-2010 Media Addon in WinBuilder (Win7PE and Win8PE) - it runs very well with both of them.
I can not use TI-2013 for my backups due to the cockamamie naming convention they force on the backup names.
I can not use TI-2013 for my backups due to the cockamamie naming convention they force on the backup names.
No, you choose not to use 2013 because you dislike the naming format. I want to be clear for the benefit of others reading this thread: nothing technical prevents you from using 2013, you choose not to do so because you don't want the suffixes that True Image 2013 appends to backup names.
Mr Tuttle, I didn't mean to twang any nerves or ruffle any feathers. ATIH-2013 does work well in the testing I've done with it. However... I do backups weekly in a stand-alone mode, to two external hard drives, and name the backups Week1 through Week5. ATIH-2013 and the forced naming convention cause that to not work - ergo it does technically prevent me from using it. Again, I'm sorry if I offended you or anyone else with the comment.
You did not offend me. I just wanted to correct the information, since many other users may read this thread.
You can still name your backups however you like. All that will happen is that True Image will append some more information to your names.
Speed Master,
TI 2010 is reasonably old now and wasn't perfect when it came to SATA drivers etc. Since all computers these days have SATA cd-drives and hard drives, this support is necessary.
There is a work around in the BIOS you can try that might work but I am not sure if its advisable to perform the restore once the workaround has been applied.
Anyway, you can go into your BIOS, and under the HDD section look for something that say IDE/SATA/RAID mode etc.
If its in SATA mode, you can temporarily change it to IDE mode (for legacy hardware etc) and then try booting the Acronis disk. It may well for for you but its not really a great solution since your prior image would have been based on HDD being set to SATA mode. What that means is that until you set BIOS back to SATA mode, the restored image probably wouldnt' boot up.
Best solution is to get a newer version of Acronis since the boot disk that is created will have better driver support for things like SATA etc.
If your on a tight budget, you could probably download a trial version of TI 2013 and create the boot disk from that. There are some limitations when creating the disk from a trial version (can't remeber what they are), but it should do most of the basic functions for you.
TI 2013 can happily restore your TI 2010 backups (which you could continue to use if you wish).
Hadn't thought about the SATA issue, but since I have two SATA drives now, TI2010 might be a problem, huh? Thanks for the offer, Paul. It would be nice to set up something like WinBuilder on a bootable CD or flash to do the backups. Hadn't thought about scripts. I do need to get something worked out for a regular backup schedule, if nothing else than for my own piece of mind.
Question: Anyone have issues with trying to image a drive that perhaps has bad sectors? Long story short, I had a drive going bad on another computer, and used DDRESCUE in Linux to clone it to another drive. I then attempted to image the cloned drive so I could tinker around with it in VMWare, but never could get TI10 to image it. Well, let me clarify, and here's the confusing part: TI10 would image it and validate it, but when I would validate it with my installed copy of TI10, it would burp saying the image was corrupt.
The idea was to tinker with the virtual image instead of the cloned drive so I didn't have to mess up the "original", but so far I've not had any luck even getting the virtual drive to boot. Perhaps it's more trouble than it's worth? I did have most things backed up, and reinstalled Windows and the backed up files to the new drive, so it's up and running. Just thought I'd see what I could work out from the dying drive by cloning and tinkering with that.
Hey Shoeless,
Regarding SATA drivers, we are probably talking more like newer SATA/RAID controllers like Intel/Marvell Sata6Gbps that might cause issues since the drivers won't be loaded in the recovery disk. So if your using motherboards that are say 1 or 2 years old, you may have some issues. If your BIOS is set to IDE mode, then you won't have any problems.
Once you have make your boot disk, try it out. If it fails to load when BIOS is set to AHCI/SATA mode but works fine when in IDE mode, then it means the boot disk needs updated SATA drivers.
Regarding imaging disk with bad sectors: this is what I think.
Apparently, the big data recovery companies swear by imaging damaged disks before working on them anymore to prevent further stress on the mechanics of the drive. So, the theory is you take the image, and then perform all the recovery work on the image and not the pyhiscal drive.
However, in my experience this approach only works with software corrupted disks, i.e. corrupted file system, unintentional wipes/formats etc.
When the disk actually has physical damage (i.e. bad sectors), I have always found Acronis to report the "bad I/O" error which essentially means the image will fail to be created.
The only time you might be lucky is if the bad sector is somewhere on the drive that isnt holding O/S information etc. But most physical failures involve multiple bad sectors so this situation is going to be pretty rare.
So in summary, taking an image of a drive with bad sectors in theory is the correct thing to do. In practice, I have found it rarely works. Although I am sure a lot of the Acronis folks will say otherwise.
If you were to try it, I think imaging would be better than cloning because don't forget cloning does a byte for byte copy so you have more chance of hitting a bad sector. If you choose the standard disk image option, it doesnt copy across the free space etc.