Startup

[Jakemaster]

Where do I go to change the settings for what programs start at computer start up?  I seem to have forgotten...

[Gunny04]

start, run, msconfig Cheers, Gunny

[Jakemaster]

Thanks Gunny, I knew it was something like that, I just couldnt remember what came after 'ms' lol

[Gunny04]

yes I know the feeling, I forget everything.... (lol its true when it comes to website links, documents, payware site logins and such) So I try to remember them, Cheers, Gunny

[Alonso]

That's common, 1 week ago I forgot command was command

[Gunny04]

isnt it cmd? Cheers, Gunny

[GeForce]

COMMAND is for native 16-bit applications, which CMD cannot run.

However, COMMAND cannot support long filenames, such as "C:\Program Files\xxx\yyy" and nor does it have a way to quote them.

The bottom line is actually quite simple: use CMD unless you know you need COMMAND for compatibility with some older 16bit program. And even then, if you try and run a 16 bit program in CMD, it will typically run it within COMMAND for you anyway, so you may not need to know or care.

Jon

Edit: Terrible spelling!

[Gunny04]

Yea I tried both... I rarely use the run function! Cheers, and thanks for the info, Gunny

[NicksFXHouse]

THE START REGISTRY: VERY IMPORTANT

After a system has been installed and all the software is in, typically your system will have a-lot of programs starting with Windows boot you DO NOT NEED. There are programs/drivers that MUST start in order for them to function correctly such as video drivers, sound drivers and a few other items.

This is an area which can be dangerous because if you are not experienced with the Windows registry or do not know what is critical and must stay, and what can be removed without issues you can end up with problems that cannot be fixed without reinstalling the software that was crippled.

The goal is to remove as many items as possible that show in the MS System Configuration Utility on the STARTUP tab without hindering the system or needed boot items. Also, kill as many tray apps as possible you do not need unless you use them at boot.

Many people go to that utility and uncheck items, leaving them in the list but set to not run. This method is fine for doing diagnostic tests to find out what is safe to delete and what is not, however:

UNCHECKING ITEMS FROM THE SYSTEM CONFIGURATION UTILITY DOES NOT KEEP THE ITEM FROM LOADING INTO THE MEMORY. IT ONLY STOPS IT FROM STARTING UP. IT IS IMPORTANT TO FIND OUT WHAT ITEMS CAN BE REMOVED SO THE SYSTEM IS CLEAN AND NOT RUNNING IN DIAGNOSTIC START MODE WITH ITEMS SIMPLY UNCHECKED.


===============================


BACKUP BEFORE EXPERIMENTING:
There is a method to help protect yourself when you are experimenting with removing startup items which requires backing up the registry keys

[born_2_fly]

Nick, why say to leave antivirus alone? I always shut down all of my McAfee from msconfig, and have never had any problems, It's one of the biggest resource hogs.

Basically, what I do:

Start > Run > msconfig > startup (uncheck everything except: atiptaxx, and cli)

Then click apply,

Then go into Services, check the hide all Microsoft Services box, and uncheck everything bar: ATi smart and Intel NCS NetService)

Click apply again, and restart...
|Alex|

[NicksFXHouse]

I said to not remove AV. I did not say anything about not shutting it down before game play.

My post was about removing un-needed startup items perminantly from the registry so no MSCONFIG editing is needed, at all.


And as a side note...  I fly with NOD32 enabled. NOD32 AV will not interfere with FS9 performance.

[cheesegrater]

I said to not remove AV. I did not say anything about not shutting it down before game play.

My post was about removing un-needed startup items perminantly from the registry so no MSCONFIG editing is needed, at all.


And as a side note...  I fly with NOD32 enabled. NOD32 AV will not interfere with FS9 performance.

You monster!

[NicksFXHouse]

You monster!