Hi Gorkster To me the ultimate way to verify an image is just restore it. Then you know all the pieces will work together. Peete
I believe v7 automatically starts two background processes that v6 doesn't have. For me they are added overhead and complexity to support features I have no use for. Can anybody tell me if there is a setting to prevent these processes from starting.
Try installing Autoruns and stop them that way. Another thing I've done at times, is fine the exe's that are starting those processes and just rename them.
@AlphaOne - The processes are required due to the slightly new architecture of v7. v6 used to run the scheduled tasks at the user's Login. They abandoned that due to changing of user's redentials which were never picked up after the change, causing scheduled tasks to stop running. To solve this (and create new issues in the meantime ), they now run your scheduled tasks under the SYSTEM moniker instead of the user. When this happens, the user will never see any of the starts/stops/results of a scheduled operation (since they aren't the SYSTEM account <not Admin>). So, Macrium created these new tasks which interface between the SYSTEM account and the user account, providing the same information that used to exist before. You can't turn them off... but they use little or no System resources doing what they have to do (a few mBs maybe).
Thanks for the detailed and useful reply Froggie. At least one of those suckers is supporting CBT and is continually writing to disk causing at least some system wear and tear with no benefit for me. But since I now know that they're needed I won't waste any time trying to find a way to turn them off. It makes the product less than perfect for me but I can tolerate less than perfect from a product I like so much. At this point I expect to be using v6 for at least a few more months if not until they stop supporting it. Thanks again Friend, Ron
Yeah, that's what I'm interested in avoiding. Maybe those two additional two processes I asked about have nothing to do with it or maybe they do, but it was the overhead associated with Continuous Increments that I wanted to avoid.
Ron, if you have no use for CBT, you should first deselect it under "edit defaults/Advanced/Advanced Incrementals." Next you should find and run Reflect's mrCBTtools program (should be on your System somewhere), run it, and in the File Menu, uninstall the driver. Following that, reSTart your System and CBT should be gone. I'm not sure one of those tasks has anything to do with CBT... but it may. The reason I'm fuzzy about this is I went back to v6 from v7 and will await more useful features... I don't have v7 in front of me anymore.
So, since I have 64 bit Windows 10 Pro and an i7-4790k in this system, can I enable vt-x in my ASUS BIOS and then get into Windows and enable Hyper-V In my Program Setting Windows Features? Will that be all I need for ViBoot to try, once I reboot? I am on V7 Build 2079.
Since I upgraded to build 2079 CBT incrementals are no longer working for me, either. The session start time changes even without the PC shutting down or sleeping for some unknown reason, and the new "racing person" icons in the GUI show gray (as opposed to blue, thus indicating CBT will not be used on the next diff/inc) even though an incremental has run and the computer hasn't shut down or restarted.
Hi Gorkster What I am saying it the best way to test restore is to restore. That way you know the image is good and it will restore.
Froggie, I appreciate the workaround and will save the information, but I think there's increasing reason for me at least to stick with v6 for the foreseeable future.
Well, ViBoot seemed to work although it did not let me change the directory from Program Data. I fixed it by telling it to not log data and then removing data it already put in the new directory. This let me boot a 32 bit XP image on this 64 bit Win 10 Pro system, but I then had to tell it many times to ignore the found new hardware. Can I save some data when in ViBoot to a thumb drive? I seem to have to "play" in order to sisconnect the Virtual drive. I can not just shut down.
There is an freeware app, which lets you use other VM software while you got Hyper-V also installed. You simply run the app, and choose whether you want to have hyper-v on or off, and it reboots your computer, and that's it! (There is a bit complex way to do it manually aswell, but why bother when this app does it for you so easily.) The application is open-source too, and you can also download it's source-code if you want to... See more in HERE (Hyper-V-Switch). So in short, you can have any VM software installed along with Hyper-V, but when you want to use them,you have to disable Hyper-V ... The app works just great on my Windows 10 Pro x64. Best of all,it is portable and only 22 kilobytes exe!
This release is looking like whack-a-mole just from my casual viewing of the experiences described here, together with my still being unable to find anything that would benefit me.
OH...the time for the log in viboot in the program directory is correct but the log file contents is in GMT. Also, I connect and the first time it says I was disconnected as another user logged on. If I retry it is OK, but why will it only see my drive C in the virtual Image?
Yeppers, that is a bummer as one needs to open the main UI to check if the imaging has run successfully. Also seem to have stopped getting notifications of start & completion.
With last release I got confirmation / postpone message on SUA desktop back, but systray icon is also not showing for me during backup.
Well, if I do boot an Image, how can I get data from it? I put in a thumb drive but it only sees my C: drive. Of course I can still mount my image as a drive letter, but I thought ViBoot would let me do more. I assume I just select the Image and tell it to boot. Not sure if I should boot a partition like 2 and not C:. I am asking here as the ViBoot forum on Macrium is moderated and there has been no new posts for a few days now...including mine. I also do not have any internet connection.
