Jump to content

draku

Member
  • Posts

    6
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Romania

About draku

Profile Information

  • OS
    none specified

draku's Achievements

0

Reputation

  1. I looked at my Microsoft\Windows\Registry\RegIdleBackup task trigger wich is set to Monday @anathematized1 good to know you "combofixed" your PC =)
  2. You can try to restore the Registry Hives from Backup The files are located in C:\Windows\System32\config\RegBack\ and are generated every Monday Once you are in Recovery Console go to Command Prompt navigate to C:\Windows\System32\config\ do a backup of current registry with: xcopy *.* *.old and after that copy over the backup files with xcopy RegBack\*.* *.* You will need to reinstall any software/driver you added after the date of the backup wich in your case i think is 26 March
  3. AMD 1090T, 8GB DDR3, SAMSUNG Spinpoint F1 1TB it might seem faster but i instaled the loader at a friend with AMD x2 6400+,4GB DDR2 , SAMSUNG 500GB not spinpoint and he boots in 30-32 seconds but does not have all the crap i have in startup list After seeing how good this preloader is now i want to buy a hybrid hdd or ssd like ocz synapse cache to accelerate all my hdd not only the boot
  4. This is from my Event Viewer ID 100: SystemBootInstance 257 UserBootInstance 250 BootTime 44042 MainPathBootTime 26142 BootKernelInitTime 14 BootDriverInitTime 606 BootDevicesInitTime 1144 BootPrefetchInitTime 6837 BootPrefetchBytes 79327232 BootAutoChkTime 0 BootSmssInitTime 16286 BootCriticalServicesInitTime 421 BootUserProfileProcessingTime 321 BootMachineProfileProcessingTime 165 BootExplorerInitTime 982 BootNumStartupApps 14 BootPostBootTime 17900 BootIsRebootAfterInstall false BootRootCauseStepImprovementBits 0 BootRootCauseGradualImprovementBits 0 BootRootCauseStepDegradationBits 0 BootRootCauseGradualDegradationBits 0 BootIsDegradation false BootIsStepDegradation false BootIsGradualDegradation false BootImprovementDelta 0 BootDegradationDelta 0 BootIsRootCauseIdentified false OSLoaderDuration 1648 BootPNPInitStartTimeMS 14 BootPNPInitDuration 1184 OtherKernelInitDuration 6308 SystemPNPInitStartTimeMS 7488 SystemPNPInitDuration 566 SessionInitStartTimeMS 8059 Session0InitDuration 14183 Session1InitDuration 232 SessionInitOtherDuration 1869 WinLogonStartTimeMS 24345 OtherLogonInitActivityDuration 327 UserLogonWaitDuration 1245 Time varies betwen 43 and 46 seconds in event id( wich from my knowing is bigger with 10 second than real since its waiting for iddle resources) even if i delete prefetch folder in Windows with loader.The only times its increase is when windows apply updates or i update drivers and then i saw is betwen 56-65 seconds. The worst time i got when windows needed to check the hdd for errors because the loader then its not loading anything and sets all prefetch as dirty This is what i start at boot + ati catalyst : All the programs appear instanly in my systray after welcome screen wich usualy takes 1-2 seconds. You need to try it to see for yourself. I send you a pm. I will make a trace with it and then without it but i tell you i had never under 60 seconds. ------------------------------------------------------------------------------------------------------------------------- L.E. Ok so i made 2 traces with loader installed Trace 1 : Windows start time in Event Viewer 53 seconds : event1.zip Trace: Loader hit 84,7% : Trace 2 : Windows start time in Event Viewer 47 seconds : trace2.zip Trace: Loader hit 98,4% : If i make another trace i belive it will be again 44-45 seconds since every restart it learns
  5. No its a software i found in some coments from reviews on hybrid hdd and ssd on anandtech i think. It works the same way ReadyBoot in Windows 7 should have worked. And also works on Windows XP and Vista. The only downside is that in order to install it in Windows 7 x64 i had to use Driver Signature Enforcement Overrider (http://www.ngohq.com/home.php?page=dseo) to put Windows in Testing Mode so i does not block its driver at boot and crash Windows (on readme it say to press F8 and chose disable driver signing in x64 but thats not an option). On 32bits it works without problems. It works like this : It install a driver wich monitor all the hdd sectors loaded at boot.After boot it takes all that sectors and put them in a prefetch.bin file wich load at next boot in memory. It monitors every boot so every time it adds or delete sectors from prefetch that does not match.In a way is like xbootmgr -trace boot It work because its much faster to copy 1 big file in memory that to copy 10.000.... small files from all over the hdd =) You can even set limits : I can write a little tutorial how to make it to work on x64 without problems if anyone is interested.
  6. Well the -prepSystem method works very good but its a lot of time comsuming in may case it took almost 40 minutes. The results are good but the optimization don't last forever. I used WinPrefetchView (http://www.nirsoft.net/utils/win_prefetch_view.html) to look up in the NTOSBOOT-xxxxx.pf to see what Windows load at boot and also used the defrag C: /u /v -b for boot optimization. Now i use a boot preloader wich makes my windows boot very fast everytime. P.S. I know it's my 1st post here so i deleted the bootloader name so you don't think i'm spamming , and because its beta and does not have singned driver for x64.
×
×
  • Create New...