How could I know that? RyanVM's UpdatePack was detected, that should handle it. Can you confirm that you did slipstream it?
If you extract your svcpack.inf and then open it, does it look messed up?
You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by Wim Leers
How could I know that? RyanVM's UpdatePack was detected, that should handle it. Can you confirm that you did slipstream it?
If you extract your svcpack.inf and then open it, does it look messed up?
So basically when you ran the thing in AHCI mode, you would need to disable the ITE RAID controller? That ITE controller is really starting to piss me off... it's caused problems in the past too!
Could you verify that workaround, Fragbert?
I know. When the problem first arose, I've been working on it like a mad man, only to find NO solution whatsoever. I will start workign on it again very soon, probably tomorrow.
These drivers are a real PITA! *sigh
Well... *DID* you slipstream RyanVM's UpdatePack? Since it is detected... That's why the BASE assumes that the HDA hotfix doesn't need to be slipstreamed, since it is already included in the UpdatePack.
for what is this bug tracker for ? and need i a new account there?
i didn´t know my password here ,because i use cookies and so i forgot it ..
Yes, currently you still need to set up a different account for that (though preferably with the same username).
Note that you can change your password in your profile
Please submit this issue to the bugtracker and also upload the original svcpack.inf file!
Please submit the corrupted svcpack.inf issue to the bugtracker. Do not forget to upload the corrupted svcpack.inf file as well as the original non-corrupted one.
Remove the comma in the ROE.exe entry. I think you've put it there accidentally?
The HDA hotfix is NOT slipstreamed because Sereby's UpdatePack was detected!
2006-10-08 11:08:38 : <SLIP> German (Sereby's) UpdatePack detected: no HDA hotfix will be slipstreamed.
And I can assure you there's not a single connection to the desktop.ini file in the KTD routines. Not even remotely!
Yes Sereby, I'm aware of it It'll be included in the next update of DriverPack LAN!
Could you please post the DPs_BASE.log then?
I'm thinking of automatically copying the DPs_BASE.log into the \I386 directory, so that you can ALWAYS retrieve that file. People tend to overwrite it, which is of course perfectly normal. I hope you still have yours.
I checked it out and it appears that this greatly increases the amount of resources required, due to the amount of e-mails that would have to be sent. Therefore I will add RSS support in the near future instead of what you requested, that should forfil your needs equally, without increasing the load of the server (or at least by a much lesser degree).
Thanks, now I know where to look.
There's two remarks to make though:
1) how is it possible that you start the Finisher TWICE? Did you add it to your RunOnceEx.cmd too, or somewhere else?
2) I can derive from the DPsFnshr.log that only the C:\D directory is present, and within that nothing. I think you're still suffering from a bug that was present in DriverPack Sound B 6.09, but according to the DPsFnshr.log you're using DriverPack Sound B 6.10. Could you please post a screenshot of your \$OEM$\$1 directory and one of your \$OEM$\$1\D directory?
And no, if the DriverPack Sound B warns you that the maximum length of the OemPnPDriversPath entry was exceeded, then it is exceeded and that will not just work. It will work for every directory listed, except for those after the 4096th character. I strongly suggest you use method 2 instead. Why do you prefer to use method 1?
Where did the "ROE.exe" entry go?
Can you please post your cmdlines.txt?
I think you posted somewhere that the error disappeared when using DriverPack Sound B 6.10? Is that correct? Not that I have changed anything in that version to possibly fix this problem, but I find it very strange that this error is reoccurring.
I have never seen that BSOD stop code before. Are you sure it's the correct one? (Even google doesn't return a single search result!)
How did that work out, JBL?
Please add this to the Settings section of your DPsFnshr.ini
debug = true
, rebuild the ISO and run the installation again.
Can't you just use the del /f /q command?
That's not a redesign, but a forum modification. I'll see what I can do though.
Thank you for your response, but I didn't burn it. I made the iso and tried it with VMware.
Then please recreate the ISO.
kof94 wrote:Thanks, may be this topic will help when people search for an answer.
Yes, if they search!
Very good point
Possibly a bad burn. Please rebuild the ISO and reburn it to your CD-RW or DVD-RW.
hi
about that desktop.ini popupI think we should help in trying to narrow down on what causes it.
so; what did I try so far. (so you don't have to, or can verify..)NO RVM (clean source CD), all packs, KTD all, m2, does it
a suspicion I had about DotnetFX,
I selected the ATI control panel (does not use it), on clean source, m2, ktd.
and got the popup.unpacked all drivers
searched for a desktop.ini. (nada, zilch)searched drive what contains the clean source folders.
none in OSes.will try to eliminate packs, one by one. (each time, M2, KTD all).
will get on the machine I looked at this morning and look at its finisher log.
I'm always amazed by your neverending energy for tracking down these nasty small but annoying bugs! Just saying thanks
DriverPacks.net Forum » Posts by Wim Leers
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.105 seconds, 5 queries executed ]