| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 97026 | 2009-02-01 11:14:00 | Slow boot up and App start in Vista Ultimate | johcar (6283) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 743993 | 2009-02-01 21:51:00 | Cheers Speedy - I'll give those a try. Alcohol has been installed since day one also and I have it set so that it doesn't reload the previously mounted image on restart of the machine, but you never know.... |
johcar (6283) | ||
| 743994 | 2009-02-01 22:25:00 | Great Speedy - seems to have sorted it. I just ticked the Google Updater (which didn't appear to work particularly well anyway) and the Gopher Prefix (whatever that is!) items and things appear to have gone back pretty much to normal. Thanks for your help (yet again)!!! |
johcar (6283) | ||
| 743995 | 2009-02-01 22:40:00 | Cool, good to hear one of them fixed it ! | Speedy Gonzales (78) | ||
| 743996 | 2009-02-01 23:51:00 | One other tool that Vista has is right at your fingertips - click the start orb, type in performance when Performance information and Tools appears, click it, on the left click Advanced tools, Then click on This as Shown (www.imagef1.net.nz) and it will tell you exactly what the problem is. Vista has a truck load of features that most people have no idea they are there. |
wainuitech (129) | ||
| 743997 | 2009-02-02 00:29:00 | Cheers wainuitech - that makes for interesting reading too. I still have four items listed there that I need to deal with, two of which relate to an NVidia driver causing problems with resuming from sleep or going into hibernation. I assume I can just update my video driver and this will fix the problem (I ask because I know my old Tosh would not let me update my video driver - it had a specifically-written-for-Toshiba driver...) | johcar (6283) | ||
| 743998 | 2009-02-02 06:31:00 | If you upgrade the nVidia drivers make sure you do two things - Make A restore point BEFORE you try to do the upgrade Get the drivers from nVidia's site, dont try through windows update, as it will more than likely make thing worse. The error on mine ( as shown) was nod32 taking 20.3 seconds to load this morning - But the whole system loads fast enough - so unless its referring to updating, which I have Nod set to do on every startup. ( Trade Secret ) :lol: if you want to exactly know whats causing problems, in the search box, when you type in Performance, select the other one, "Reliability and performance" - on the left look for Reliability Monitor" if you look at the graph, you will see X's, thats failure someplace, click it then expand out the lists below and it will give you all the information on "whats going on" ( or not as the case may be) Example (www.imagef1.net.nz) |
wainuitech (129) | ||
| 1 2 | |||||