Search options (Page 31 of 77)

Please mention next time in your first post that you're using a multibootDisc. That's a critical difference!

This was the same bug as the one described in this topic.

Topic closed.

Considering your timezone, that won't be any time soon I guess

Just tell me what motherboards those are... it's definitely some missing SoundMAX/Sigmatel drivers. When I add the necessary drivers, the BSODs will disappear.

I'm sorry coucou, but if you did slipstream RyanVM's UpdatePack, then I don't see why it should not work. This might be an isolated issue.

You say that you are using Sysprep. Then have you applied the appropriate changes? Did you for example extract DPsFnshr.7z to %systemdrive% and copy DPsFnshr.ini there too?

Hm in the first post the problem is described as

Fragbert confirmed that.

RogueSpear had another problem though:

... and then another one by RogueSpear, describing the same issue, but with different drivers.

I do not see the link. And I do not see how 2 cmd windows could get started... that's very strange!

Your HWID is supported, it should have been detected.

The relevant part:

2006-10-10 16:01:51 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0005__D-G-A-5] (4 of 20 exceptions).
2006-10-10 16:01:51 : <FLTR>     1. tagFiles (ALL tagFiles must be found)
2006-10-10 16:01:51 : <FLTR>         Found tagfile "I:\ATICCP.ins" (1/2).
2006-10-10 16:01:51 : <FLTR>         Found tagfile "I:\D\G\A\1\ATICCP.exe" (2/2).
2006-10-10 16:01:51 : <FLTR>     4. +infFiles (ANY +infFiles must be matched)
2006-10-10 16:01:51 : <FLTR>         ! Could not match any of the +infFiles.
2006-10-10 16:01:51 : <FLTR>     => This exception will not be applied.

The one but last line shows that none of the .inf files could be matched. But that strange thing is that it did not list the .inf files.

If possible, could you please run the Finisher again, but now in debug mode? You can enable debug mode by adding the following line to the Settings section:

debug = true

Thanks!

Please post your entire DPsFnshr.log, so we can confirm this was indeed tested on a system with a supported ATI GPU.

QSC is simply a cache from where the compressed drivers are copied into the \$OEM$\$1 directory. I do not see how that could affect the desktop.ini problem - though we must keep all possibilities open.

I think jtdoom is closer though.

I'm sorry mikelm, but try to put yourself in my place: it's a bug that only popped up during betatesting, and even then it was not sure that it was caused by the DriverPack Sound B. And it's STILL only you, jtdoom, and some one else. There's no known way to reproduce it, and therefore no known way to remove the bug.

My best guess is that it's caused by the implementation of KTD: since the last versions it moves the directories instead of copying them. That's really the only true change since version 6.08.6 (apart from bug fixes, which certainly have not caused it). Now, if you move the C:\D\whatever directory to C:\WINDOWS\DriverPacks\, how do you think that would cause the desktop.ini file to be opened?

As I said, this problem is so obscure, that it will be very difficult to track the exact cause.