microsoft

Vista Performance and Reliability Pack Unofficial Release

Steven Parker   on 30 July 2007 - 11:34 · 155 comments & 228845 views

Advertisement (Why?)
Thanks Nekrosoft for the news on this major update to Windows Vista that should for most of us improve the speed and reliability of Windows Vista significantly!

Please note: These fixes break all current methods of bypassing driver singing requirements except the good old F8 during boot (that you have to do every single time you start vista)

IF you are using Rivatuner, atitool and or Peerguardian on 64bit vista, you will have to use F8 every single time to disable driver signing requirements to use those two programs. x86 version is unaffected.

These updates should go official on the next patch Tuesday (in one weeks time). Please read more for the download links and information on these updates.

938979 Vista Performance and Reliability Pack
This update resolves a number of individual issues which may be affecting some computers running Windows Vista. These issues have been reported by customers using the Error Reporting service, product support, or other means. Installing this update will improve the performance and responsiveness for some scenarios and improves reliability of Windows Vista in a variety of scenarios. Some examples of the improvements contained in this update are:
  • Improves performance in resuming back to the desktop from the Photo and Windows Energy screensaver.
  • Resolves an issue where some secured web pages using advanced security technologies may not get displayed in Internet Explorer on Windows Vista.
  • Resolves an issue where a shared printer may not get installed if the printer is connected to a Windows XP or Windows Server 2003 system and User Access Control is disabled on the Vista client.
  • Resolves an issue where creating AVI files on Vista may get corrupted.
  • Improves the performance in calculating the ‘estimated time remaining’ when copying/moving large files.
  • Improves performance in bringing up Login Screen after resuming from Hibernate.
  • Resolves an issue where synchronization of offline files to a server can get corrupted.
  • Resolves a compatibility issue with RAW images created by Canon EOS 1D/1DS Digital SLR Camera which can lead to data loss. This only affects RAW images created by these two specific camera models.
  • Resolves an issue where a computer can lose its default Gateway address when resuming from sleep mode.
  • Improves the performance when copying or moving entire directories containing large amounts of data or files.
  • Improves the performance of Vista’s Memory Manager in specific customer scenarios and prevents some issues which may lead to memory corruption.
938194 Vista Compatibility and Reliability Pack
This update resolves a number of individual issues which may be affecting some computers running Windows Vista. These issues have been reported by customers using the Error Reporting service, product support, or other means. Installing this update will improve the reliability and hardware compatibility of Windows Vista in a variety of scenarios. Some examples of the improvements contained in this update are:
  • Improved reliability and compatibility of Vista when used with newer graphics cards in several specific scenarios and configurations.
  • Improved reliability when working with external displays on a laptop.
  • Increased compatibility with many video drivers.
  • Improved visual appearance of games with high intensity graphics.
  • Improved quality of playback for HD-DVD and Blue-Ray disks on large monitors.
  • Improved reliability for Internet Explorer when some third party toolbars are installed on Vista.
  • Improved Vista reliability in networking configuration scenarios.
  • Improved the reliability of Windows Calendar in Vista.
  • Improved reliability of systems that were upgraded from XP to Vista.
  • Increased compatibility with many printer drivers.
  • Increased reliability and performance of Vista when entering sleep and resuming from sleep.
Link: Neowin Forum Discussion Thanks Nekrosoft
Download: Vista Compatibility and Reliability Pack for x64 or x86 version

Post a comment · Send to friend Comments · There are 155 additional comments
#1 RanCorX2 on 30 Jul 2007 - 11:41
just to make sure people understand, the following ONLY applies to vista 64bit! Those using 32bit vista will be fine.

"These fixes break all current methods of bypassing driver singing requirements except the good old F8 during boot (that you have to do every single time you start vista)"
(1 reply) #2 :: Lyon :: on 30 Jul 2007 - 11:47
Yay Yay!
Downloading now
#2.1 excalpius on 31 Jul 2007 - 11:05
This was probably what those MS leakers were talking about when they discussed "Vista SP1 beta" coming out this week. Since, for all intents and purposes this sounds like some major overhaul updates.
(5 replies) #3 stgeorge on 30 Jul 2007 - 11:48
Sounds like a mini-SP1. I wonder why MS doesn't just abandon the idea of "Service Packs" and just release these fixes through Windows Update throughout the year. They are very easy to slipstream into a Vista install unlike in XP.
#3.1 randomnut on 30 Jul 2007 - 12:01
Because service packs are tested, tested again, then re-tested before release (or should be anyway). Hotfixes are thrown together in 5 mins and chucked out there.
#3.2 cork1958 on 30 Jul 2007 - 12:19
Quote - (randomnut said @ #3.1)
Because service packs are tested, tested again, then re-tested before release (or should be anyway). Hotfixes are thrown together in 5 mins and chucked out there.


I think they should be issued as single, monthly patches also instead of some massive 200MB plus service pack. Heck, a service pack is nothing much more than ALL the updates thrown together anyway and usually not tested well enough either. Just like the whole VistaMe2 OS!!
#3.3 MMaster23 on 30 Jul 2007 - 12:47
Quote - (stgeorge said @ #3)
Sounds like a mini-SP1. I wonder why MS doesn't just abandon the idea of "Service Packs" and just release these fixes through Windows Update throughout the year. They are very easy to slipstream into a Vista install unlike in XP.


for reference purposes ... eg costumers find it easier to compare systems marked with service packs. XP SP2 is a proven platform while XP "vanilla" sucks. I have found out that this is not the case with Vista tough. heavily tested and developed with an different business/development model.

thus eliminating the "need" for an first SP. still vista SP1 is in people's mind a "major improvement". these days the systems run better with "hotpacks" like these.

Just installed .. saw some improvement in explorer (copy/delete etc) performance. Dare i say with caution .. this update rocks.
#3.4 randomnut on 30 Jul 2007 - 12:51
Quote - (cork1958 said @ #3.2)
Quote - (randomnut said @ #3.1)
Because service packs are tested, tested again, then re-tested before release (or should be anyway). Hotfixes are thrown together in 5 mins and chucked out there.


I think they should be issued as single, monthly patches also instead of some massive 200MB plus service pack. Heck, a service pack is nothing much more than ALL the updates thrown together anyway and usually not tested well enough either. Just like the whole VistaMe2 OS!!


Yeah good point, they do take far too long to fix some major issues, just because they're not 'critical security issues' etc.
#3.5 +Brandon Live on 30 Jul 2007 - 16:17
Quote - (cork1958 said @ #3.2)
Heck, a service pack is nothing much more than ALL the updates thrown together anyway and usually not tested well enough either.


Well that's just not true at all. A Service Pack goes through extremely rigorous testing (basically the same as any OS release).
(1 reply) #4 FloatingFatMan on 30 Jul 2007 - 11:52
Umm.. This story's already been posted to the front page news...

http://www.neowin.net/index.php?act=view&id=41687
#4.1 Shane Pitman on 30 Jul 2007 - 11:57
That was just a "heads up" and didn't actually include any downloads.
#5 lordofangels on 30 Jul 2007 - 12:33
the next patch Tuesday is 2 weeks tomorrow, the 14th Aug
(1 reply) #6 gadean on 30 Jul 2007 - 12:39
WOW. Lots of updates rolled into just two hotfixes? Excellent, glad to see some of the performance issues being addressed.

Now I'd like to see the SD memory problem fixed.
#6.1 NPGMBR on 30 Jul 2007 - 12:50
No doubt. I've been disappointed by the performace of Vista. I still think its a great OS but I have to reboot at least once a day because something has made the OS unstable.

I had gotten so used to how stable XP was that I just assumed Vista would be the same. But I had also forgotten that when I was Beta testing XP it was also qutie unstable even after the official release but it got dramatically better over time.
#7 Zip on 30 Jul 2007 - 12:41
thank you! finally my file transfers are xp speed!
(3 replies) #8 graigchq on 30 Jul 2007 - 12:42
Quote -
Improves the performance in calculating the ‘estimated time remaining’ when copying/moving large files.


thats what i was looking for. Assuming this works, i'll no longer have to boot into XP just to transfer music onto my mp3 player, or copy files to my laptop.

THat particular problem was doing my head right in.
#8.1 miguel_montes on 30 Jul 2007 - 12:46
About time!! It only took... what... about 9 months...?
#8.2 EduardValencia on 30 Jul 2007 - 14:16
I guess all that hotfixes need alot of work

So If u were the guy coding these fixes,we would never get them! so shut up!
#8.3 Chicane-UK on 30 Jul 2007 - 15:34
Quote -
So If u were the guy coding these fixes,we would never get them! so shut up!


Are you a share holder in Microsoft or something? Stop defending them so much! Microsoft deserve a little criticism from time to time!
(7 replies) #9 InsaneNutter on 30 Jul 2007 - 12:44
This might mean I can actually use sleep and hibernate on my laptop now, at the moment when ever I try to use either one the network connection does not work when the laptop resumes, the only way to fix it is by shutting down which kind of makes sleep and hibernate pointless.
#9.1 buletov on 30 Jul 2007 - 12:47
Yes but with Vista you get shiny user interface and blurry fonts!
You can't work without that, now can you?
#9.2 JiveMasterT on 30 Jul 2007 - 13:07
Vista News also comes with free trolls! Nice!
#9.3 ZombieFly on 30 Jul 2007 - 13:35
Quote - (JiveMasterT said @ #9.2)
Vista News also comes with free trolls! Nice!


only ultimate edition has trolls, which are still in alpha.
#9.4 MioTheGreat on 30 Jul 2007 - 14:22
Quote -
and blurry fonts!


On very high resolution monitors (1920x1200 15.4" ) , text looks like crap without cleartype. It's only "Blurry" on weird LCDs, or on CRTs.
#9.5 InsaneNutter on 30 Jul 2007 - 17:25
Nope this update does not fix it, I still need to re start after hibernating or putting the computer to sleep if I want to use the net
#9.6 Budious on 30 Jul 2007 - 17:31
Quote - (MioTheGreat said @ #9.4)
Quote -
and blurry fonts!


On very high resolution monitors (1920x1200 15.4" ) , text looks like crap without cleartype. It's only "Blurry" on weird LCDs, or on CRTs.


I wondered why it looked like crap on my 1920x1200 17" laptop screen. I have 120 dpi enabled also. Where is the "cleartype" feature enabled/disabled at?
#9.7 reddragon72 on 31 Jul 2007 - 20:54
Quote - (InsaneNutter said @ #9.5)
Nope this update does not fix it, I still need to re start after hibernating or putting the computer to sleep if I want to use the net


don't reboot, just open device manager, right click on your device that is failing to reconnect and select disable. now wait 5 seconds or so then reenable it. connection restored. Also drivers that are downloaded or ITB(in the bo from microsoft have this issue, but drivers from the actual manufacturing company do not, so if you have a wireless intel device go to intel and get there driver. I have this issue on most of my systems, and getting the driver from the actual manufacture of the device resolves the problem.
#10 Bryan84 on 30 Jul 2007 - 12:57
So not for me who uses Vista Home?
#11 usman767 on 30 Jul 2007 - 13:03
Dude, i think it will work for all the vista editions...
#12 gizbug on 30 Jul 2007 - 13:09
So what is this about driver signing in vista 64?
If we install both these updates, we can't use peerguardian?
(2 replies) #13 Flint2 on 30 Jul 2007 - 13:09
I do hope that Neowin realizes that posting download links to these Hotfixes is a violation of the rules stated on Connect since these Hotfixes are not supposed to be publicly available yet.
#13.1 MrCobra on 30 Jul 2007 - 16:48
Yet if you had posted these you'd be warned for posting "warez" because they aren't official yet. A link to this page has been sent to those in charge of Connect.
#13.2 +Xtreme2damax on 02 Aug 2007 - 00:55
Quote - (MrCobra said @ #13.1)
Yet if you had posted these you'd be warned for posting "warez" because they aren't official yet. A link to this page has been sent to those in charge of Connect.


I think someone forgot to take their medicine

Read below, yes they stated for them not to be public but technically they can't do anything about it since these are going to be released for free anyways. Warez/Piracy only applies to commercial products, not those that will be released for free.

Even if it got as far as court, it would likely be thrown out as soon as it was mentioned these would be released for free.

I mean how is a freely released fix going to harm a company financially since there is no revenue to be had to begin with.

Stop whining, shut up, download them and be happy instead of acting like an ass. Don't ruin it for all of us because you were having a bad day. I know what it is, you will get rewarded by M$ for reporting these and live like a king with no worries because you are a perfect, modest, honest citizen that does no wrong, right? Call me when you get that check from Miracle Soft as a reward for reporting this, better yet send me a postcard form the resort you are spending time in from the tropics. I sure such honesty and modesty don't deserve to go unrewarded does it?

I'm sure this news post would of already been taking care of and deleted if there was anything that could be done by M$ if this is supposed "Warez" Like you claim it is.

These may not be official, but it is not warez either.

Last edited by Xtreme2damax on 02 Aug 2007 - 01:09
(1 reply) #14 usman767 on 30 Jul 2007 - 13:14
I think neowin should remove the links as they are not legal at the moment. Also because i already got the files on my disk
#14.1 Flint2 on 30 Jul 2007 - 13:17
Heh, its not really about having them, they should probably/hopefully be out next month and in better quality, its that Neowin is not meant to be a site that posts illegal download links.
(1 reply) #15 gizbug on 30 Jul 2007 - 13:15
Stop crying about the links. IF you dont want to dl it, dont. A lot of people appreciate the links.
#15.1 Flint2 on 30 Jul 2007 - 13:19
It is *not* about wanting or not wanting to download it, I'm sure many people would love to have it, but guess what, under MS's License Terms on Connect, it is *illegal* and Neowin is the *only* MS Community site that is posting download links to them (ActiveWin/AeroXP/WinBeta are not) and this story originated from the AeroXP forums after all.
#16 Uncle_Bingo on 30 Jul 2007 - 13:25
I don't suppose on the "compatibility" end of this they will be fixing the Admin Tools functionality? I still don't see how MS can market Vista in any business capacity when its practically useless for Active Directory and Exchange Admins. Expecting us to remote desktop to a server or use some half-baked sort-of works hack to install the Admin tools is a sad joke. Either fix the tools or make a Vista Admin Edition!
(19 replies) #17 Azmodan on 30 Jul 2007 - 13:32
Funny, I just upgraded to my old Windows XP x64 after the continuous and crazy lock-ups. Microsoft, ASUS nor Nvidia would give me proper support, after telling each one of them that Vista suddenly stops responding in a total freeze, where even the LED's are stuck, and I've got the latest drivers for each one of them.

I've got to the point that I had to make an ISO with nLite, insert Nvidia's RAID drivers into my Windows installation (the ones that came with the CD, because the most recent ones produces an instant BSOD trying to load Windows) to use a stable, non-freezing system that I can listen to online radios without Winamp being closing every 5 seconds.

Oh, i've saved a copy of my Vista in my HDD. If Vista ever get's stable (or gets out of the public beta stage -- troll intended), i'll try to install it. Meanwhile, my dog is having tons of fun times with the shinny cd.

Specs:
ASUS W2N32-SLI Wireless Edition
AMD FX 2.8Ghz Windsor
EVGA GeForce 8800GTS
#17.1 ZombieFly on 30 Jul 2007 - 13:59
Quote - (Azmodan said @ #1)
Funny, I just upgraded to my old Windows XP x64 after the continuous and crazy lock-ups. Microsoft, ASUS nor Nvidia would give me proper support, after telling each one of them that Vista suddenly stops responding in a total freeze, where even the LED's are stuck, and I've got the latest drivers for each one of them.

I've got to the point that I had to make an ISO with nLite, insert Nvidia's RAID drivers into my Windows installation (the ones that came with the CD, because the most recent ones produces an instant BSOD trying to load Windows) to use a stable, non-freezing system that I can listen to online radios without Winamp being closing every 5 seconds.

Oh, i've saved a copy of my Vista in my HDD. If Vista ever get's stable (or gets out of the public beta stage -- troll intended), i'll try to install it. Meanwhile, my dog is having tons of fun times with the shinny cd.

Specs:
ASUS W2N32-SLI Wireless Edition
AMD FX 2.8Ghz Windsor
EVGA GeForce 8800GTS



somehow i doubt the problems you experienced are to do with vista. Sounds like you have some dodgy memory or something. I've been using vista on a number of different hardware configurations and i've yet to see any such behaviour.
#17.2 Azmodan on 30 Jul 2007 - 14:37
Quote - (ZombieFly said @ #17.1)
somehow i doubt the problems you experienced are to do with vista. Sounds like you have some dodgy memory or something. I've been using vista on a number of different hardware configurations and i've yet to see any such behaviour.


* Memtest ranned perfectly. 5 out of 5 times it completed perfectly. No errors, since it doesn't runs on Windows.
* Prime95 ends frozen up in Vista, in 7 out of 8 tests it ends up in a complete lock-up. Prime95 completes perfectly in WinXP x64, 5 out of 5.

If you think my tests are fake, you could buy my system and test it out. I've given the specs in my first post. Oh, you'll be surprised by it's behavior, by the point that you would send your system back to where you bought it because you think it's defective when it's Vista. (I live in Panama, and I've bought it on USA. Monetary reasons, this thing is valued 3,500$ in here)

You could Google for Vista Freeze ASUS M2N32-SLI, one of the guys making those articles is me (Icrontic has a whole thread about it, with 45+ pages of complains, since the companies I mentioned doesn't give a bloody hell to help you)
#17.3 HeartsOfWar on 30 Jul 2007 - 15:26
I'm running an Asus Striker Extreme using latest bios and nForce drivers on Vista x64 and I haven't had any problems (I think anyone "in the know" of Asus knows this mobo has been plagued to death with problems).

I'm also running an Asus 8800 ultra using the latest forceware...

I highly doubt Vista is the problem. Either your RAM isn't completely compatible (did you consult the Qualified list?) or you're over clocking...
#17.4 Azmodan on 30 Jul 2007 - 15:37
Quote - (HeartsOfWar said @ #17.3)
I'm running an Asus Striker Extreme using latest bios and nForce drivers on Vista x64 and I haven't had any problems (I think anyone "in the know" of Asus knows this mobo has been plagued to death with problems).

I'm also running an Asus 8800 ultra using the latest forceware...

I highly doubt Vista is the problem. Either your RAM isn't completely compatible (did you consult the Qualified list?) or you're over clocking...


No... read the post above...

Doesn't makes sense to me, why would a defective/incompatible RAM would die in Vista and not in XP after doing exactly the same stress tests and using the exact applications? Occam's Razor
#17.5 Raptor on 30 Jul 2007 - 16:59
Quote - (Azmodan said @ #17.4)
Quote - (HeartsOfWar said @ #17.3)
I'm running an Asus Striker Extreme using latest bios and nForce drivers on Vista x64 and I haven't had any problems (I think anyone "in the know" of Asus knows this mobo has been plagued to death with problems).

I'm also running an Asus 8800 ultra using the latest forceware...

I highly doubt Vista is the problem. Either your RAM isn't completely compatible (did you consult the Qualified list?) or you're over clocking...


No... read the post above...

Doesn't makes sense to me, why would a defective/incompatible RAM would die in Vista and not in XP after doing exactly the same stress tests and using the exact applications? Occam's Razor


Vista's memory management model is vastly different than XP's that's why. I work for a software company and we've seen Vista cause issues in programs that *appeared* to run fine before. When we'd actually take a look, we'd find issues with the programs that while they worked in the past, weren't guaranteed to (addressing an invalid memory range, etc).

Vista is a very stable OS. Your issues are all but guaranteed to be caused by hardware issues. Just because your program passes a diagnostic program in a limited environment does not guarantee the hardware is working fine. All it takes is one single memory corruption to bring down a system, and that's far more likely while you're using CPU/GPU/Ram all at once (i.e. it could be a voltage issue).

Vista is an extremely solid OS. I've been using it since it came out without issue.
Ironically I remember a similar issue with people upgrading from ME/98 on bad hardware and claiming XP was more unstable.
#17.6 jesseinsf on 30 Jul 2007 - 18:36
If you are getting the BSOD in Vista, this means it's a hardware/software problem. Go here:

http://www.microsoft.com/windows/products/...adeadvisor.mspx

Test your hardware for compatibility. And don't slipsteam yet because "nLite" is still in beta. Plus Don't install winamp since it is not compatible with vista yet (AOL is slow at rewriting the "WinAmp" program). WinAmp now will F-Up the graphics and ruin your system.

When you install Vista, install the drivers when Vista asks for them. And make sure the drivers are SIGNED. Plus do not install ANY PROGRAMS that are NOT in the SYSTEM REQUIREMENTS of the program's specs. btw, when vista asks for drivers at install, it's different than how XP does it...you can actually extract the drivers on a USB thumb drive and point vista to it....it's much easier than how XP does it.
#17.7 HeartsOfWar on 30 Jul 2007 - 19:33
As other people have mentioned, saying something works in XP is not a true testament that Vista is the problem.

First of all, one of the biggest changes in Vista Memory management is that it uses resources a lot more aggressively: caching HDD reads / writes to memory, effectively using all the memory it can. XP does not take the aggressive stance and only *tries* to use what it needs... so you could effectively have a bad RAM module and not even know it... until you switch to Vista.

Second, how many memory modules do you have? The ASUS Striker Extreme motherboard had an issue with instability when all four slots were in use. Thankfully, this has been fixed but could be a source of trouble for you as well.

Third, you never answered if you were over clocking... if you're over clocking, back it down and see what happens. No offense, but I find it amusing that people have the nerve to over clock their processors and then balk at instability issues.
#17.8 Azmodan on 30 Jul 2007 - 19:34
Quote - (jesseinsf said @ #17.6)
If you are getting the BSOD in Vista, this means it's a hardware/software problem. Go here:

http://www.microsoft.com/windows/products/...adeadvisor.mspx

Test your hardware for compatibility. And don't slipsteam yet because "nLite" is still in beta. Plus Don't install winamp since it is not compatible with vista yet (AOL is slow at rewriting the "WinAmp" program). WinAmp now will F-Up the graphics and ruin your system.

When you install Vista, install the drivers when Vista asks for them. And make sure the drivers are SIGNED. Plus do not install ANY PROGRAMS that are NOT in the SYSTEM REQUIREMENTS of the program's specs. btw, when vista asks for drivers at install, it's different than how XP does it...you can actually extract the drivers on a USB thumb drive and point vista to it....it's much easier than how XP does it.


Well, Windows XP x64 installed without any problems when I added the Nvidia NRaid driver. Windows XP x64 doesn't recognizes the RAID because there aren't any textmode drivers that supports it on installation, so I had to do it.

Strangely, Winamp was running on legacy mode (Selected to run as Windows XP SP2), and it was working properly until a Vista update.

I did select the drivers when Vista told me about them. (Tip: You can select individual drivers and their locations in Windows XP. It's written as an advanced select option.)

The problem with Vista was NOT a BSOD, it was a TOTAL FREEZE. (Like, you can't move the mouse, keyboard doesn't responds, screen is frozen, LED signals are frozen too. A total LOCK-UP)

Vista's memory management... don't know about that because it was weird when the system crashed while viewing photos using the Photo Viewer application that came with Vista (or whatever the name of that program is)... If that's the case, people at Microsoft needs to write their programs properly...
#17.9 Azmodan on 30 Jul 2007 - 19:41
Quote - (HeartsOfWar said @ #17.7)
As other people have mentioned, saying something works in XP is not a true testament that Vista is the problem.

First of all, one of the biggest changes in Vista Memory management is that it uses resources a lot more aggressively: caching HDD reads / writes to memory, effectively using all the memory it can. XP does not take the aggressive stance and only *tries* to use what it needs... so you could effectively have a bad RAM module and not even know it... until you switch to Vista.

Second, how many memory modules do you have? The ASUS Striker Extreme motherboard had an issue with instability when all four slots were in use. Thankfully, this has been fixed but could be a source of trouble for you as well.

Third, you never answered if you were over clocking... if you're over clocking, back it down and see what happens. No offense, but I find it amusing that people have the nerve to over clock their processors and then balk at instability issues.


No, there's nothing overclocked on it. I have 2 2GB Mushkin sticks (4GB total), I've even changed positions from 1 & 2 to 3 & 4, and I saw the same results. I've adjusted the memory to fit the CAS latency of it on the BIOS tool. If I had a bad memory, I guess memtest would had discovered it? I used the x64 version of the program.
#17.10 jesseinsf on 30 Jul 2007 - 20:25
Quote - (Azmodan said @ #17.
Quote - (jesseinsf said @ #17.6)
If you are getting the BSOD in Vista, this means it's a hardware/software problem. Go here:

http://www.microsoft.com/windows/products/...adeadvisor.mspx

Test your hardware for compatibility. And don't slipsteam yet because "nLite" is still in beta. Plus Don't install winamp since it is not compatible with vista yet (AOL is slow at rewriting the "WinAmp" program). WinAmp now will F-Up the graphics and ruin your system.

When you install Vista, install the drivers when Vista asks for them. And make sure the drivers are SIGNED. Plus do not install ANY PROGRAMS that are NOT in the SYSTEM REQUIREMENTS of the program's specs. btw, when vista asks for drivers at install, it's different than how XP does it...you can actually extract the drivers on a USB thumb drive and point vista to it....it's much easier than how XP does it.


Well, Windows XP x64 installed without any problems when I added the Nvidia NRaid driver. Windows XP x64 doesn't recognizes the RAID because there aren't any textmode drivers that supports it on installation, so I had to do it.

Strangely, Winamp was running on legacy mode (Selected to run as Windows XP SP2), and it was working properly until a Vista update.

I did select the drivers when Vista told me about them. (Tip: You can select individual drivers and their locations in Windows XP. It's written as an advanced select option.)

The problem with Vista was NOT a BSOD, it was a TOTAL FREEZE. (Like, you can't move the mouse, keyboard doesn't responds, screen is frozen, LED signals are frozen too. A total LOCK-UP)

Vista's memory management... don't know about that because it was weird when the system crashed while viewing photos using the Photo Viewer application that came with Vista (or whatever the name of that program is)... If that's the case, people at Microsoft needs to write their programs properly...


Again, "WinAmp" is not "DESIGNED" for Vista. To be technical, WinAmp uses a part of DirectX 9 that vista no longer supports. So it messes with the "Remote Procedure Call" service that will make your system do allot of bad stuff. Try viewing pictures before you install Winamp on a fresh install. Now if you are using a "CRACKED" version of vista then there is no help to ya. And make sure ALL Drivers are "MADE" for windows "VISTA". And MAKE sure 110% of all your programs are not "CRACKED" programs and that they are "MADE" for windows VISTA. (If you are running 64bit edition then make sure you see 64bit edition in the requirements as well)If any of your programs "DON'T" say that they are MADE for Vista on their website (or on the BOX" then this may be the problem...so don't install them. Last is to make sure (When installing) you have a copy of VISTA that is fresh from the press and not tampered with or slipstreamed.
#17.11 ZombieFly on 30 Jul 2007 - 20:46
Quote - (jesseinsf said @ #17.6)
If you are getting the BSOD in Vista, this means it's a hardware/software problem. Go here:

http://www.microsoft.com/windows/products/...adeadvisor.mspx

Test your hardware for compatibility. And don't slipsteam yet because "nLite" is still in beta. Plus Don't install winamp since it is not compatible with vista yet (AOL is slow at rewriting the "WinAmp" program). WinAmp now will F-Up the graphics and ruin your system.

When you install Vista, install the drivers when Vista asks for them. And make sure the drivers are SIGNED. Plus do not install ANY PROGRAMS that are NOT in the SYSTEM REQUIREMENTS of the program's specs. btw, when vista asks for drivers at install, it's different than how XP does it...you can actually extract the drivers on a USB thumb drive and point vista to it....it's much easier than how XP does it.


what are the problems with winamp you speak of? i've never had a single problem, it's my most used application and i have it running constantly.. what's it supposed to "F-Up" with the graphics?
#17.12 +rm20010 on 30 Jul 2007 - 22:47
Quote - (jesseinsf said @ #17.10)
Again, "WinAmp" is not "DESIGNED" for Vista. To be technical, WinAmp uses a part of DirectX 9 that vista no longer supports. So it messes with the "Remote Procedure Call" service that will make your system do allot of bad stuff. Try viewing pictures before you install Winamp on a fresh install.


Could installing Winamp be the reason why the fullscreen slideshow is so stuttery for me?
#17.13 jesseinsf on 30 Jul 2007 - 23:27
Quote - (rm20010 said @ #17.12)
Quote - (jesseinsf said @ #17.10)
Again, "WinAmp" is not "DESIGNED" for Vista. To be technical, WinAmp uses a part of DirectX 9 that vista no longer supports. So it messes with the "Remote Procedure Call" service that will make your system do allot of bad stuff. Try viewing pictures before you install Winamp on a fresh install.


Could installing Winamp be the reason why the fullscreen slideshow is so stuttery for me?


Yes, it also made my media center stutter. Graphics were shot to hell. And then I did a disk cleanup and to my surprise I realized that it really did a disk cleanup. Everything under "C" was deleted...had to reinstall...thanks to winamp.....This is why I say to make sure VISTA is in the system requirements of any program or driver. if you only see 2000/xp then don't install the program unless you are beta testing...
#17.14 +rm20010 on 30 Jul 2007 - 23:34
Apart from Winamp installing Sonic's burning engine that has been problematic for some, I can't see what Winamp installs that will cause things to screw up that bad. You also mentioned Winamp calls some part of DirectX 9 that is no longer supported. Will installing the DX9 runtime for Vista fix that?

In any case, I'll do another clean Vista install without Winamp and see how it goes. Thanks for that heads up.
#17.15 jesseinsf on 31 Jul 2007 - 05:38
Quote - (rm20010 said @ #17.14)
Apart from Winamp installing Sonic's burning engine that has been problematic for some, I can't see what Winamp installs that will cause things to screw up that bad. You also mentioned Winamp calls some part of DirectX 9 that is no longer supported. Will installing the DX9 runtime for Vista fix that?

In any case, I'll do another clean Vista install without Winamp and see how it goes. Thanks for that heads up.


I Believe that DirectDraw is emulated in Direct3D now. Just as DirectX 1-5 is now in XP with DX9. anything that uses DirectDraw apps will cause unpredictable problems. Winamp uses DirectDraw (A part of DX9). So wait for a Vista version to be released.
#17.16 Azmodan on 31 Jul 2007 - 13:31
Quote - (jesseinsf said @ #17.10)
Again, "WinAmp" is not "DESIGNED" for Vista. To be technical, WinAmp uses a part of DirectX 9 that vista no longer supports. So it messes with the "Remote Procedure Call" service that will make your system do allot of bad stuff. Try viewing pictures before you install Winamp on a fresh install. Now if you are using a "CRACKED" version of vista then there is no help to ya. And make sure ALL Drivers are "MADE" for windows "VISTA". And MAKE sure 110% of all your programs are not "CRACKED" programs and that they are "MADE" for windows VISTA. (If you are running 64bit edition then make sure you see 64bit edition in the requirements as well)If any of your programs "DON'T" say that they are MADE for Vista on their website (or on the BOX" then this may be the problem...so don't install them. Last is to make sure (When installing) you have a copy of VISTA that is fresh from the press and not tampered with or slipstreamed.


Ok, so what are you trying to tell me that the legacy mode option is just a fancy thing that doesn't haves an actual function? Woah, Microsoft programmers should've been very lazy to just making a drop-down menu without any function at all...

Second, almost all the software I use is GPL (or freeware): OpenOffice.org, GIMP, X-Chat, Pidgin, ect... I don't have to "CRACK" any software, and my Vista is LEGAL. All the drivers where made for Vista, I've got them in the ASUS website.

My copy of Vista wasn't tampered with anything, my Windows XP x64 is.

God, I don't know why I've ever mentioned about my problem with Vista, I'm not a kid that's trying to build a tank out of a PC case, I did everything anyone could do to make it work, and IT DIDN'T.
#17.17 jesseinsf on 31 Jul 2007 - 19:38
Quote - (Azmodan said @ #17.16)
Quote - (jesseinsf said @ #17.10)
Again, "WinAmp" is not "DESIGNED" for Vista. To be technical, WinAmp uses a part of DirectX 9 that vista no longer supports. So it messes with the "Remote Procedure Call" service that will make your system do allot of bad stuff. Try viewing pictures before you install Winamp on a fresh install. Now if you are using a "CRACKED" version of vista then there is no help to ya. And make sure ALL Drivers are "MADE" for windows "VISTA". And MAKE sure 110% of all your programs are not "CRACKED" programs and that they are "MADE" for windows VISTA. (If you are running 64bit edition then make sure you see 64bit edition in the requirements as well)If any of your programs "DON'T" say that they are MADE for Vista on their website (or on the BOX" then this may be the problem...so don't install them. Last is to make sure (When installing) you have a copy of VISTA that is fresh from the press and not tampered with or slipstreamed.


Ok, so what are you trying to tell me that the legacy mode option is just a fancy thing that doesn't haves an actual function? Woah, Microsoft programmers should've been very lazy to just making a drop-down menu without any function at all...

Second, almost all the software I use is GPL (or freeware): OpenOffice.org, GIMP, X-Chat, Pidgin, ect... I don't have to "CRACK" any software, and my Vista is LEGAL. All the drivers where made for Vista, I've got them in the ASUS website.

My copy of Vista wasn't tampered with anything, my Windows XP x64 is.


God, I don't know why I've ever mentioned about my problem with Vista, I'm not a kid that's trying to build a tank out of a PC case, I did everything anyone could do to make it work, and IT DIDN'T.


You know Vista has a memory test feature. the same way you choose to boot to safe mode. there should be an option that tests your memory. Try that......also keep in mind that vista handles memory differently than in the previous OSes. So that memory tester you were using is obsolete. (Hopefully this will solve your problem)

oh, and reading above, you say you use the following: OpenOffice.org, GIMP, X-Chat, Pidgin....I'll tell you that the only program that seems to not have a problem is OpenOffice. all those other programs use DirectDraw which can make your Vista do unpridictable bad things. all the IRC freeware chat programs are bad news to Vista on allot of machines. Just wait awhile for Vista to be added in the "System Requirements" of these programs.

Last edited by jesseinsf on 31 Jul 2007 - 19:53
#17.18 ZombieFly on 01 Aug 2007 - 07:34
Quote - (jesseinsf said @ #17.15)
Quote - (rm20010 said @ #17.14)
Apart from Winamp installing Sonic's burning engine that has been problematic for some, I can't see what Winamp installs that will cause things to screw up that bad. You also mentioned Winamp calls some part of DirectX 9 that is no longer supported. Will installing the DX9 runtime for Vista fix that?

In any case, I'll do another clean Vista install without Winamp and see how it goes. Thanks for that heads up.


I Believe that DirectDraw is emulated in Direct3D now. Just as DirectX 1-5 is now in XP with DX9. anything that uses DirectDraw apps will cause unpredictable problems. Winamp uses DirectDraw (A part of DX9). So wait for a Vista version to be released.


do you have any evidence to support these wild claims? like i say, i've been using winamp in vista since beta stage and i've never had a single issue with jumpy video, my c drive being erased or anything remotely strange happen.

Sources please + explain why i dont have an issue?
#17.19 jesseinsf on 01 Aug 2007 - 19:58
Quote - (ZombieFly said @ #17.1
Quote - (jesseinsf said @ #17.15)
Quote - (rm20010 said @ #17.14)
Apart from Winamp installing Sonic's burning engine that has been problematic for some, I can't see what Winamp installs that will cause things to screw up that bad. You also mentioned Winamp calls some part of DirectX 9 that is no longer supported. Will installing the DX9 runtime for Vista fix that?

In any case, I'll do another clean Vista install without Winamp and see how it goes. Thanks for that heads up.


I Believe that DirectDraw is emulated in Direct3D now. Just as DirectX 1-5 is now in XP with DX9. anything that uses DirectDraw apps will cause unpredictable problems. Winamp uses DirectDraw (A part of DX9). So wait for a Vista version to be released.


do you have any evidence to support these wild claims? like i say, i've been using winamp in vista since beta stage and i've never had a single issue with jumpy video, my c drive being erased or anything remotely strange happen.

Sources please + explain why i dont have an issue?


Please tell me about your system? Different systems have different results.
(1 reply) #18 Flint2 on 30 Jul 2007 - 13:59
Since no one seems to care about the illegality of posting the above download links, perhaps we should starting posting public download links to *every* private download from Connect...

PS: I do hope that Neowin's Admins remember what happened when TheHotfix posted private WHS downloads
#18.1 Aeden on 30 Jul 2007 - 15:49
i was thinking the same thing....naturally someone will come to their senses
(1 reply) #19 Express on 30 Jul 2007 - 13:59
I can wait for two weeks for the official release.
I keep my machine clean of third-party software running at startup and loading themselves in browsers. So I haven't had any problems with reliability.
#19.1 8-n-1 on 30 Jul 2007 - 19:14
Quote - (Express said @ #19)
I can wait for two weeks fo