(!) Bootable media with a backup file can only be created when using Acronis True Image Home 2010 in Windows. It is impossible to create such media in bootable environment. See Standalone Version of Acronis Software.
Hello. I have True Image 2019, and use it for most purposes. However, I also have a bootable CD of the 2010 version that I'll use from time to time when 2019 doesn't cooperate for one reason or another. I'd like to put that on a USB drive, but when I've tried to use products like Rufus or ISO2USB, the process to create the boot USB disk fails. Has anyone had any success making a bootable older version Acronis USB disk with only the ISO file of a boot CD?
Acronis True Image 2010 Boot Cd Iso
The problem I am having is that when booting from the bootable rescue media that I created using the true image 2010 program it does not find/see any network drives at all. This shows up when I double click on the recovery tab and click browse (similar method yields the same result using the backup tab). What happens is that when I then click on Computers Near Me it comes up empty. But it sees the local hard drive (C:) during the boot mode just fine. I tried using the tools menu to modify network adapter settings as mentioned in the user guide and that didn't help. True image can see the entire network while inside the windows environment--no problem. But when booting from the rescue media it doesn't. It spends a lot of time looking too (like a minute or more).
I am guessing the problem has to do with bootable rescue media not having the correct drivers for my system so I created a system report in both windows and the boot mode. However, I can not find a way to send these files to anyone to obtain a working ISO boot image that will work with my system.
I forgot to add, if it makes a difference, that my internal intranet between computers uses static IP's. I needed to set up internal network this way for other reasons. I don't think that matters to this issue but I do note that whenever I am in the boot mode of acronis and I check on the ethernet settings it always seems to reset them to DHCP regardless of how I reset them to a static IP during previous boot mode sessions of acronis.
I read this forum article: I followed the suggestion in reply #2 from Alexander about literally typing in the path \\server\share and that seemed to solve the issue. After I had typed it just one time when specifying the path then from that point on the browser in acronis (during boot mode) was able to find it on its own. However, it seems to be pretty slow when it accesses the network to get to another computer. Once its in the other computer (my NAS box for example) it speeds up to something more normal. So for example, browsing starting from my local computer into the NAS box may take about 10 seconds just to get through the network. Then once inside the NAS box its more reasonable. I really don't understand that behavior but maybe it has something to do with booting from a CD or maybe how quickly it can query the network when booting from CD? Although if this is indeed a ramdisk type of setup I would think it should not be anywhere near that slow.
One more piece of information during this process. I recall that when I first explicitly typed the path to my NAS box it came up with the expected user authentication form asking for the login and pw to get into the NAS box which I supplied (and also asked if I wanted to test the network connection and I did and it was ok). Its like once that was done just one time during one booting from cd into acronis it remembered the permissions from that point on. In other words, subsequent reboots to the acronis rescue media did not require me to enter the login and pw to get into the NAS box. Although I don't know that if I truly powered down the entire network and then brought it up again if it then might ask me again for the login and pw. It seems like its remembering the login and pw when coming from the acronis boot loader but I don't understand how it can do that.
And I actually do not understand how typing it explicitly one time solves the problem (and it doesn't matter if I change the ethernet settings or not--it will still work although I need to retype the explicit NAS box network address path one time as above everytime I reboot to acronis rescue cd) and from that point on the browser can do it on its own? Any explanations as to what is going on and why it seems to access the network through the browser on its own after typing the path explicitly once? And why does browsing through the network seem to be slow?
Good idea about the ping. I did as you said and it does ping so the driver is supported and working. And I decided to time and wait to see how long it would take the network neighborhood to be populated and you were right about that--45 seconds to browse into the workgroup for both backup and recovery! I didn't need to enter any UNC path to the NAS either, I just waited long enough. Perhaps entering the path explicitly speeds it up? I had no idea it could be this slow in a non-OS environment. In windows its almost immediately but from the boot CD its really slow. In fact, some mouse clicks (depending on where you are and what you are doing in the acronis backup or recovery menu) while in the boot CD mode are very slow taking like 5 seconds or more to actually echo and do something. I wonder why it is so slow from the boot CD as compared to the windows environment. Any thoughts? More importantly, is this expected/normal for the way this software works or is it more the way its interacting with my particular setup here? Do you think that having a custom rescue ISO image from acronis might speed things up?
I am going to try a system backup and target it to the NAS box for storage. Then I will try to do a recovery in the boot CD mode by recovering from the NAS box to an external usb HD that I have. Finally, I will then attempt to restart the pc and have it reboot from the external usb HD. My thinking here is to test the system recovery process out without having to actually let acronis erase the internal HD of the pc before it writes the image back to it. Assuming that I can reboot from external usb drive do you see any issues with this idea? Is there any reason that I fundamentally won't be able to boot from the external usb drive assuming the .tib file is not corrupted?
Got very busy with work stuff so I didn't get a chance to act on your advice till now. As usual you were right and thanks again for the advice. I forgot that the external HD I had was a multi-interface type (usb, firewire, and esata). And I had the Dell guys remind me that on the back of my optiplex there was an esata port (guess I am not as with it as I should be perhaps). I read that esata is bootable so I went out and bought an esata cable. Then I switched off my internal raid SATA disks in the BIOS menu (under drives). Then I rebooted and voila I was booting from the external HD via the esata connection. And it booted perfectly. No problems so I was able to recover the image from the NAS box onto the external esata drive and it booted perfectly from there. And all from the boot CD recovery environment. That really does give me a lot of confidence in the TI swe. Time to make a purchase.
I had the same issue. Hit F2 when re-booting to enter cmos setup. Found a setting that said USB Legacy support was inactive and I activated it, saved and exited cmos. Re-booted with TI 2010 CD and ran the safe version. When doing a restore the external USB hard drive was now present and browseable.
Then, rather than reinstalling and reconfiguring all my programs, a several-day job, I tried to use my most recent True Image 11 Home image stored on an external USB hard drive. Trying to run it from the boot CD, and selecting the full backup image from a USB drive, I got:
Stephen c as GroverH suggested please download ISO image based on ISOLinux from your account under registered products and create Acronis bootable disc using third-party software. ISOLINUX Bootable Media is usually more up to date than the Acronis Loader one. This is due to the fact a new version of Acronis Bootable Media is uploaded to the website more frequently than regular product updates are released.
ISOLINUX Bootable Media has several boot parameters that may help overcome possible issues with booting. You can also set a specific VGA resolution in the ISOLINUX media if there an issue with the Graphical User Interface (GUI). Check the following article for more details. I have also sent you ISO image via PM.
Francisco if I understand you correctly the internal drive is not recognized under Acronis bootable disc.Is it correct? I have sent you ISO image based on ISOLinux loader via PM too, it has better hardware support and it will certainly solve the issue.
To restore the tib image, first create a new VM with the appropriate virtual disk size, then boot the VM from the Acronis Recovery CD or ISO to restore the tib file to the virtual disk. Once done run the VMware Converter selecting the "Configure Machine" option, to inject the necessary disk drivers into the restored virtual disk.
I had a HDD -soon to be removed from case- and wanted to "reincarnate" the existing semi-inactive windows xp installation in VBOX.As long as i had no usb drive, i followed the next procedure which worked like a charm.(more time consuming though, i think)REQUIRED SOFTWARE : a. Acronis True image boot CD, b. UltraISO
2) uninstalled all ide/vga/sound drivers from native installation ->shutdown (DO NOT boot after this point again to the native OS)3) boot with "Acronis True Image Home 2010 boot cd" -> create backup of disk(max compression preferred)4) make a UDF/DVD .iso file from the previous acronis image, with UltraISO5) mount in 1st cdrom the Acronis Boot CD, and in 2nd the .iso you created b46) boot VM and restore disk form previous created image.7) let the system configure its devices at 1st boot and voila.
Your post on migrating a Windows OS to VirtualBox was helpful. I went through the steps you did and also could not get past the "mup.sys" hang after many, many tries, but finally I did this: on the source machine, before capturing the disk image, go to the device manager and change the IDE driver from whatever it is to the "standard IDE driver". (Select update, don't have the OS search, tell it you have your own driver, then it will give you a dialog where you can select the standard IDE driver.) Save that, reboot, then reimage the drive, convert the image to a .vdi. It then worked on first boot in VirtualBox! I did not have to reinstall or even do a repair install, hooray. 2ff7e9595c
Komentarze