FSAutostart is a completely different story - sorry, zaphod, but reading fs_Pilot's post would have been better than flying over it...
Slow computer, he? I also always kill processes before flying!
One important thing, you have to differ between processes and services!
Processes are those you can see in your task-manager.
By googling you can get infos fur pretty sure nearly every or even all of your tasks.
You can kill many processes without any problems while others make your system crash. Google helps!
Services, however, are not tasks that are permanently blocking your RAM space.
Often, they're also integrated into tasks, as they are no independent working files.
Tasks/processes can differ from user to user depending on who is logged in.
But services who are often used to enable processes accessing hardware are already running before you log in.
So you can't disable services for one user - either enabled for all or disabled for all.
So the only thing I can suggest is, keep away from services - disabling them may kill your sys forever, if you don't know how to bring it back, but killing a process: no problem, just reboot and it's there again!
So try out killing processes with your task manager or an alternative one like "Process Explorer" (can easily be found with - again Google
).
Crash!
rev
Intel i7 960 quad 3.2G LGA 1366, Asus P6X58D Premium, 750W Corsair, 6 gig 1600 DDR3, Spinpoint 1TB 720
