well someone might prove me wrong, but i did not notice any difference when resuming from hibernate, i think this is because when resuming from hibernate windows does not use the boot.ini file, but i could be wrong.
HiJackX1 UAMCB w/ The Tobiathin Core Android/Win 7 hybrid system!
4x 10inch Tablet
1x Win 7 / Rear Entertainment PC
ft/ Web Server Streaming
Sorry about posting a couple of months later, but I have to correct you guys.
Changing the numproc doesn't do anything. Windows uses all the cores all the times.
Also the /maxmem tag i think is also incorrect. Windows be default uses all RAM. /maxmem is used if want only a certain amount a RAM used.
software (like SQL 2005) requires cores to be in multiples of 2. Also can test programs against different numbers of cores for dev purposes.
Same with /maxmem. It is indeed used for limiting windows usable memory from what's available. In my carPC I use a /maxmem=384 setting to decrease my resume from hibernation times even though I have a 2gb Ram stick in there.Also the /maxmem tag i think is also incorrect. Windows be default uses all RAM. /maxmem is used if want only a certain amount a RAM used.
However I do disagree with what that lifehacker article says about disabling services. Disabling services will have a HUGE impact on boot times. Look at how fast an optimized version of Micro2003 boots vs a standard XP install.
The best resurrected frontend I've ever used, period.
Hey guys - the delay entry in boot.ini doesn't have anything with a single OS boot unfortunately - it is how long the multi-boot OS list is present for, until the top one is chosen. Thats if you have more than 1 os on your system.