What to keep in "starting programs"

What to keep in "starting programs" (Nobody's interesded ?)

Hello,
I'm writing from France, so, sorry for my English. I'm using "PC Cloneur", which is the french version of True Image.
I've made the bootable CD, and I ask myself if it's usefull to keep this in the "starting programs" (see attachment).
Thanks a lot for your answers,
Bye

 

Re: What to keep in "starting programs" (Nobody's interesded ?)

You're English is better than my French. I just recently removed all references of TI from Startup to speed up the booting. The removal has not had any adverse effect on TI and it performs well, (as it had in the past).

If you want to experiment without delving into the registry, use this free program. It allows you to uncheck startup programs at the click of a mouse.

http://www.mlin.net/

 

Re: What to keep in "starting programs" (Nobody's interesded ?)

Just to give a different view :-
If saving a few seconds at boot up is very important to you by all means disble those items in start up. If you are only going to use TI from the rescue CD for imaging and recovery there will be no noticable effect on operations. However if you want to use the TI from within Windows you will have to enable them to get full functionality.

There have been several threads on this subject that a search will find. I leave all the TI items in start up as I much prefer using TI in the Windows environment when making scheduled images.

 

Thank you for those very quick answers. It's now more clear for me.
Bye.

 

Re: What to keep in "starting programs" (Nobody's interesded ?)

If you're using Win, you can also get a copy of the free microsoft program, msconfig.exe, which will allow you to check/uncheck the startup programs.
It should come as part of XP but it's missing from Win2000 although the XP version works with 2000. If you don't have a copy, you can get it here:

http://www.techadvice.com/specs/files_st1.asp?fnid=3398288

You can get the msconfig.exe enhancements from this url, but you need a valid copy of Win to get the download:

http://www.microsoft.com/downloads/...e9-aded-44b8-bbbb-beae1b4a4bc9&DisplayLang=en

sh

 

I have disabled all start up references and services for TI, and whenever I run the program, it runs just fine. It is not just a few seconds with a faster start, it is another 'resource user' running in the background, that is not needed, unless you are running scheduled backups daily.

 

Hello everyone,

Please take a look at these previous threads: Registry, Startup, how to turn off?, Trueimagemonitor.exe and timountermonitor.exe?? explaining what schedul2.exe, schedhlp.exe, TrueImageMonitor.exe and TimounterMonitor.exe processes are and why it is not recommended to disable them. You may also find this thread interesting.

You can find more information on how to use Acronis True Image 9.0 Home in the respective User's Guide.

We also recommend that you take a look at the Acronis True Image 9.0 Home FAQ page, Acronis Public Knowledge Base and this article providing the illustrated instructions on Acronis True Image 9.0 Home installation and usage.

If you have any further questions concerning Acronis software, please feel free to submit a request for technical support or post any of them on this forum. We will certainly try to help you in resolving any issues.

Thank you.
--
Alexey Popov

 

I looked through the references you posted and still contend that if you are not using the program for scheduled backups, or in the case of read/write image operations, the there is no good reason to run the background programs when not in use, especially as they do start when you manually start TI. (This would include not only the resource use, but also the extra time it takes to start these programs.)

I find StartupCPL or Autoruns works for for disabling Run services, and disable the schedule services (set to manual) in the Services section (WinXP).

When I am done using the program, I use 'process_explorer' to turn of the running background scheduler.

I will agree with you in that TI running in the bacground does keep a very low profile.

 

The resources used in background are terribly piddling.