WOF: Windows' biggest annoyances in your book

Can't find you now to give the @ sign, but your reply about disabling shadow copy with system restore points: The idea of shadow copy in Vista and later is that when restoring, all files are restored to the same state they were in at that restore point. However, it didn't work for me at home or where I work when the application of KB951847 failed. At home I had to restore from backup and at work he rebuilt the computer from scratch after the incident.
 
To improve boot times, and they are dreadfully slow, Windows should have a way of "gennning" its configuration like we did on the mainframe. You pick out all the devices you have from a list, and send it through a sort of compiler (assembler was used then), and it generates only the code used for those devices; it doesn't have to go thru 50,000 devices every startup. When you change devices, you regen. All devices need not be in the gen; some can still be plug and play, but let's get with the 21st century, or should i say, let's get with 1980?
 
you read me wrong cranky, i was just trying to say that my original statement was my solution for your every day user. you are absolutely correct in saying that you can use msconfig to configure your startup, i was leaving it out because that is really a power user feature. some were along the lines of editing your registry. sorry? i was actually agreeing with you and stating that you're way is valid.

now of course if you are referring to the comment i made about accessing the start menu before explorer has had a chance to load then yes you are absolutely wrong. you deserve to have fire balls shoot out of your power supply. (its possible, i have seen it happen to a friend's pc, lol)
 
Guest said:
i just want to say that any ***** who tries to access the start menu while explorer is still loading deserves a BSOD every time he tries it.
<next post>
you deserve to have fire balls shoot out of your power supply. (its possible, i have seen it happen to a friend's pc, lol)"
I take it you're not big on multitasking then?
Prefer to let each thing take it's own due time, ya'll get there eventually anyway eh?
Nevermind, I don't want to turn this into some flamebait argument over nothing...
Let's just say I like multitasking, and the problem I described is actually fully fixed by getting a SSD disk, because then everything is loaded once you see the desktop and taskbar (However my 150GB Raptor disk sure ain't no SSD)

Julio said:
@Per, your "Windows 7 x64 system" is that a desktop? Half of my problems above are gone when I'm using my desktop that uses a quad-core CPU, loads of RAM, SSD, etc. etc... but when running on a laptop wake from standby becomes way more relevant. As I said, on a Macbook Pro it can take anything from 5 seconds to up to 30 seconds to wake Windows 7 up, whereas OS X will do it in 2-3 seconds every time.
Yea, it was my desktop system, Quadcore with 8GB RAM (no SSD tho)

Just tried it on my Dell M1710 laptop, it has the Seagate Momentus XT 500GB Hybrid SSD in it and runs Win7 x64 with 4GB RAM (only 3.xxGB accessible due to chipset limitation tho...)
Resume from standby was 2.46 seconds, averaged over 3 times
All times it was below 3 seconds
This was to logon screen, but system was instantly responsive
 
Resume from standby was 2.46 seconds, averaged over 3 times
All times it was below 3 seconds
This was to logon screen, but system was instantly responsive

I asked this before, "since this is a Mac, are you (Julio) sure Apple didn't plan the slow resume when running Windows"? And if they didn't make it worse intentionally, is it possible the simply never bothered to optimize it? Window 7 reports on programs that are slowing down standby. Dunno about resume, though. I thought that part of the sales pitch of Windows 7 was directed at these particular issues. That, and boot times.
 
well per, i really meant during the start up, you really should let it do its thing. at any other point yeah go for it, thats what its there for, but in loading its a bad idea.
 
I don't like how my windows 7, on my laptop designed for Vista, has problems with drivers for certain devices like my WiFi adapter. I also find my printer from the XP era to be completely useless without Virtual PC. While it isn't a Microsoft problem necessarily, the most annoying factor about using Windows is that perfectly good hardware becomes useless because of poorly written drivers and no after-market support. At the very least, I think Windows should carry a set of all purpose drivers that work, even with basic functionality, with most devices.

I love the troubleshooter, but I do think it needs to be beefed up. It could be a lot smarter and more capable than it currently is.
 
Back