All these guys [AMD] have done is steal our ideas and copy us - Intel senior VP
MICROSOFT MUST BE FURIOUS after software upgrades from Vista to Windows 7 failed on some machines because they had an Intel storage driver.
For months before the launch the Vole worked with hardware makers to make sure that drivers working under Windows 7. It wanted to avoid a repeat of the Windows Vista fiasco, which was caused by the operating system shipping with too few working hardware drivers.
Most of the time this worked however according to Microsoft, there are users that experienced failures when upgrading from Vista to Windows 7 because of an Intel storage driver.
When people try to upgrade they get a an error messsage: "\$windows.~bt\windows\system32\drivers\iastor.sys. Status: 0xc0000359. Windows failed to load because a critical system driver is missing or corrupt."
The machine would subsequently be rolled back to Vista and after a while the user would want to throw something out of the Window.
What is causing the fault are incorrect versions of the iastor file that are referenced during the move to Windows 7. Microsoft hasn't produced an update or hotfix designed to resolve this particular issue yet.
Users have to manually fix the problem using a fairly complex upgrade which will require some fairly brave person to try.
The Vole tells us to:
"1. Access Driver Repository Folder under C:\Windows\System32\DriverStore\FileRepository and move any folders that contain the file: iastor.inf to a temporary location.
2. Search for references to iastor within the oem inf files in the c:\windows\inf folder - Example Command: findstr /i /c:"iastor" %windir%/inf/oem*.inf.
3. Make a note of the oem##.inf files reported where ## is a numeral. Move the oem##.inf and corresponding oem##.pnf from c:\windows\inf folder to a temporary folder.
4. Delete $~bt, $~LS and $~Upgrade folders from c:\ drive if they exist
5. Download and install the latest version of the iastor.sys driver from Intel website on the Vista machine.
6. Start the Windows 7 upgrade process. It should complete successfully now."
Yikes. Hopefully there will be a patch soon. It is not clear how many people are affected by the bug. We guess we will hear all about it soon. µ
Microsoft is the only company that has the luxury of having all the hardware companies writing the drivers for them. Apple often does it in collaboration with the hardware manufacturers, while Linux and BSD developers often do all the work themselves, sometimes without any documentation.
Microsoft can blame everybody if they want to, but this is really an issue they should take responsibility for themselves.
I can't see why Microsoft should be writing drivers for 3rd party hardware devices.
The hardware manufactorers have to be competent enough at what they do, or atleast so one would think.
But this article clearly shows a different story, but it is the same old as with Vista and the Nvidia caused BSOD's
My brother was really happy when his win7 arrived on the release date. But less happy when his nvidia chipset refused to playball. Don't think they even have a vista driver for the motherboard chipset he has.
"MICROSOFT MUST BE FURIOUS after software upgrades from Vista to Windows 7 failed on some machines because they had an Intel storage driver."
Yup. I mean, who uses Intel chipsets these days, anway? ;)
dave, why I dont buy nVidia chipped mobos any more, (devil take the hindmost support philosophy).
nick, why I haven't bothered installing Win7 on my Intel chipped mobo yet even though I got it at launch because of the pricing.
Both of you, why AMD is looking better all the time.
When setting up a new system, it's safer not to install non-Microsoft chipset drivers. When I set up my current NVidia chipset sytem, I only installed NVidia HD Audio and Video drivers. I let Windows install its own storage drivers.
I have encountered an ACPI error in trying to upgrade a AMD 790FX chipset. Latest and greatest bios and W7 says it is not ACPI compliant. IEEE who wrote the standard says otherwise. An on line search shows that this is a repeat problem for Intel as well. MS got too cute with some of their code by trying to eliminate bogus upgrades. The fault belongs to MS not Intel,AMD or nVidia.
I had to revert back to crappy UDMA-100 drivers because of some botched IAStor driver on Windows XP which would just disconnect drives for no reason, locking up the machine. Sadly, I had hoped Intel would get its act together two OSes later, but it appears not.
It won't be Intel that gets the flak though. Microsoft will be blamed instead, as it always seems to be.
I 'll never understand those noobs that prefer to "upgrade" from shitty old versions of whatever OS they are using, instead of making a fresh start.
Why someone would want to upgrade from and OS like Windows Vista, which means keeping all the usual shitty drivers and bad registery entries of Vista that make it look even a worse kind of turd than it really is.
All you have to do is find a free afternoon, and devote it to format the hell out of the thing and start over.
You system will be faster, leaner and you will have more free space.
But since noobs do not understand even that simple language:
- LOL, if you format, you get more space for your pr0n, faster booting times and moar FPS at Crysis. Formating rulezzz. !!! -
Just before upgrading to Win 7, the only thing needed is to upgrade to the latest Intel Matrix driver. no digging in windows folders is needed.
I had the same issues when I tried to install Service Pack 1 and Service Pack 2 for Vista. This machine had the Intel Matrix Storage manager on boot up.
I would install the service pack and upon the first boot it would crash half way through boot up.
First of all this is a very easy fix if you have half a clue. 2nd, anyone who "upgrades" their PC from one OS to another is a damn IDIOT! Upgrading any OS is a retarded idea. Want to change your version of your operating system? Backup your data you want to save, format the system and load it from scratch. Holy Crap! No problems when doing things the right way!
When I installed W7 on my Dell notebook, WiFi did work.
However, it used on old Microsoft driver (from March I think).
Why the hell do I invest in an Intel platform and then get a bloody Microsoft driver for an important part of the Intel platform? Ha?
I went to the Intel web site, and it had an W7 driver with a recent date on it.
I chose to update, and it did - only to find out that the bloody program that I downloaded and ran went on to use Microsoft update and just download the bloody old Microsoft driver I definitely did not want.
A mail to Intel support did not result into an answer.
A bit later I found out the trick:
I chose to use the second link and downloaded did download a real driver file and not a bloody exe-file. This newly downloaded piece of software then finally installed the real original Intel W7 driver.
I mean:
What is this?
Microsoft and Intel are sending prayers to heaven to make W7 a success and inspire more people to open their wallets.
Dear Intel:
I consider this as a piece of blunder that has cost me way too much time to sort out.
Intel, YOU HAVE WASTED MY TIME.
Intel, you have committed a management failure - unnecessarily. What do you pay your managers for? I would like to get real life performance, not just in terms of MIPS.
Tick-tock, you know, like a Swiss clock. And drivers are a part of my expectations, especially when it comes to a brand new operating system Intel had way enough time enough to prepare for.
From a company like you Intel I expect something different.
Shame on you, Intel.
You better learn from that blunder.
Tick-tock is also important for the little things that can make a customers life a pain or a pleasure.
If not even mighty Intel is unable/incapable to distribute a driver that is already done and ready in an orderly fashion when a new important OS is released to the world and rather prefers to be numb and inattentive - than we better close our ears the next time the industry tells us about this new wonderful product.
Whatever the industry tells us, its better to wait for at least six month if not a year before even paying a closer look.
There are too many highly paid managers at Intel and in the industry who are extremely busy to work on internal reports, statements, PORs, PPTs and CYAs rather then on something than getting their stuff done that is actually helpful for the customers who at the end of the day do pay the bills.
This industry is full of management blunderers and non-performers.
This is why one never should buy a new product after its release to the market.
Its probably better to buy the 3rd-best product.
Its always good enough and always will work reliably.
This in turn means, that XP on a old two core CPU is the best deal you can get - including peace of mind.
Is this what you want ?????
If not, please get rid of those blunderers in your divisions that kill the time of your customers. Customers don't need wonderful press releases - customers need immediate traction in whatever the need to do.
Remember that.
Basta.