Quote
cmonex - 2006-05-08 5:33 PM
hey, C:Amie the only thing ive not done is disabling system restore though i really should disable it, it has NEVER helped me when i was in trouble!!
all the other stuff is quite natural to do IMO.
ok now i have had a 640x480 wallpaper for a few days, will soon get bored with it though, thats why i very rarely have one.
oh and i MUST have quick launch..
any other ideas please, i'm not sure how much the system eats but my programs use 100 MB now and 90 is available. so i guess around 200 including the video ram..
I've never given SR a chance to help me, it's something of a non-no for me... I'd consider it humiliating to use it. It eats disk space anyway.
Agreed
I use Quick Launch too.
What does the system say the RAM allocation is at boot time? Yes, I know you never reboot, but may be just this once.
Disabling unecessary hardware, therefore freeing system IRQ lines, and preventing drivers from loading in the first place. Drivers. just sit in RAM. Kill Parallel Ports & COM ports if you can afford to do so - especially integrated NIC/Sound/Video.
Kill balloon notifications - HKEY_CURRENT_USER\ EnableBalloonTips=0x00000000
By by search assistant - HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\CabinetState & set the value of Use Search Asst to "no"
Disable the darn indexing service on all volumes and then kill the service off My Comp > <drive letter> > properties > Allow indexing service > all files and sub folders, then hit the services manager
Prevent Windows Messenger from bothering you >EVER< again:
Start > Run > RunDll32 advpack.dll,LaunchINFSection %windir%\INF\msmsgs.inf,BLC.Remove
If you can live without the UI fluff and a start-up sound, disable the Themes service
Disable system sound events completely
Don't use the welcome screen
Disable themes on the log-on screen
(otherwise all you're doing is loading and then unloading the themes services
)
If you're really stuck for RAM:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\AlwaysUnloadDLL set the default to 1. This will force unload link libraries from RAM after request fulfilment... however it will add milliseconds to load times and program access i/o. P.S. there are arguments over whether this does anything under XP, as I said above, I have not used it since the days of 9x.
Remove as much as you can from the Windows Comp list in Add / Remove