rog

Everything is fine yet!

It worked quite well for me. Just Graphics_A 5071 isn´t recognized as the newest version, it askes for 507.

You are welcome!

Did you download the Fix? That should correct the ASH1205 issue.

Dann übernehm ich mal den job, das auf deutsch zu formulieren Bei OemPnPDriversPath sind zu viele Anführungszeichen ("). Entweder löscht du die manuell oder du lädst dir - wie djbe gesagt hat - das update für fedit runter oder du wartest, bis Bashrat ein neues fix bereitstellt. Bei Möglichkeit 2 und 3 mußt du allerdings nochmal die DriverPacks neu einbinden.

The links haven't been updated. So just copy the link and replace "V504x" with "V505". Then it should work again.

I got the same problem with the SI 3112. I Used Base 50413. The drive was recognized during setup and is accessable in Windows but in Device Manager the driver is not loaded. Strange!

What is the problem with deleting the folders? They will be recreated at the next logon!

No, they are not the same. It is Graphics A and B, and Sound A and B. There are different drivers in those packs. For example Graphic A is for nVidia and ATI, and Graphics B for the rest.

Thats why you are supposed to use nlite. I think its to much work to remove everything manually. Why not use nlite? Just give it a chance.

Did you try nlite to reduce the size of your installation cd. You can remove any components you do not need. e.g. the Windows Tour (~17 MB)

@sonic The problem with nlite is the "End of file" character in the txtsetup.sif. It is a small square. OK, not really a square Just move it to the end of the txtsetup.sif and the problem is gone

I got the same error. Everything is up to date. Using a Gigabyte GA 7 VAXP Ultra board with SiI 3112 Controller and the driver is installed automatically.

To use the new DriverPack (Methode 2) I just have to replace the old one on my CD with the new one and remove the version info in the name, am I right?

Just download the new DriverPack Base 4.10.2 and the problem is gone. It was because of the version number of the DriverPacks.

Then I got something wrong. You wrote a few post before: But that does not work for me. If I use the DriverPack after nlite, my SATA controller is not recognized. I gave it a lot of tries, removing everytime less Windows components. But no success. The only way - at least for me - is to use nlite after the DriverPacks.

I have no problems using nlite after the DriverPack, but if I use nlite before my SATA controller (SiI 3112) is not recognized during setup and also I can not install the drivers from a floppy disk. So my advice is to use the DriverPacks first and nlite afterwards. Nlite will keep the entries to txtsetup.sif, so nothing to worry about. @Bâshrat By the way, thanx a lot for that excellent piece of work