I'm not sure I understand.  It sounds like both Wlan 802 and 803 have problems.  I'm currently using Wlan 802 with base 7052.  I was thinking of switching to base 801RC2 to fix KTD saving to C:\Windows\Driver Packs\D\D\ (using M2).  Should I wait for the next version of Wlan to be released or use Wlan 803?

I know I said the upload was done in haste..
Let me explain that.
I had to update the changelog and adjust supported device list. (without doing that, the file just takes space.)
I uploaded the driverpack and minimally adjusted PHP files so the pack would register as an update, and then I worked my way through the 275 entries in device list, and finetuned the changelog txt.
That was it. The pack itself had been in testing for a while, and all I did before I uploaded it was undo the folder changes.

IE don't put it in in your scripts anywhere at all.
Once everything is all done just double click on it in windows explorer.

in this way one could prove that their script was the issue and not the finisher itself...

This will probably not make it into the tutorial. the DriverPacks are aimed at the technically savvy user.
It is assumed our users are already aware of the signifigance of the basic settings.
I frequently refer noobs to read up and come back... (you provided good details and were polite so...)
It is our position that you should at least understand the contents of this guide as a prerequisite for getting the best support from us.

Glad your here and that we could help...

jeff

......
I think that is it completely obvious to 98% of our users that:
IF you shut the computer off in the middle of a task then it won't be completed.

LMAO!  Now that I re-read this, it makes me laugh the way you worded it.  Hehe.  That may be true, but to a n00b like me, I didn't see anything that tells me that GUIRunOnce runs after RunOnceEx.  I was just basically trying to say that it might save other n00bs like me a lot of time if the tutorials warned about what would happen if you reboot at the end of RunOnceEx.  I forget which forum I got the shutdown in cleanup.cmd from, but I mostly used DP Finisher in GUIRunOnce because the tutorial didn't say anything about the pros and cons and GUIRunOnce was the default, so I figured it must be the safest option.  Yeah, I should know what happens when I assume something. 

I gotta say that I'm so thankful that this unattended community is a very helpful bunch.  Everyone seems to help as much as they can and I hope I can give back by helping others.  Oh, speaking of which, when I researched the desktop.ini error, I did not see anything that states that rebooting before DP Finisher finishes could be the cause of the desktop.ini error, but that is exactly what caused it for me.  Also, I saw a lot of messages of people making cleanup routines to cleanup DP files in their root folder instead of trying to figure out why DP Finisher did not finish.  I'm not sure but am wondering if at least some were because of the same reason as me.  After all, I did get the shutdown found in cleanup.cmd, run at the end of RunOnceEx from one of the forums in this unattended install community.  I hope this helps someone. 

Ed

Wlan 802 bust KTD
Wlan 803 was uploaded (( in haste  )) and the older folder structure what worked with legacy base and base 7052 is again live.

Jeesh.
A rare few test KTD and M1.
Wlan802 had created an almost imperceptible error.
KTD threw no error, but was not applied. That was it.
Rarely used features get tested less fequently, and I apologise for not having  looked at every windows\INF\ folder in the few live KTD tests I did.

hey. it worked. Not as intended, but it worked.

select custom for the finisher method then add this line to your cleanup command

   cmdow @ /HID
   start /wait %SystemDrive%\DPsFnshr.exe
   shutdown.exe -r -f -t 60 -c "Windows XP will now restart in 1 minute..."
   DEL ***some stuff here for cleanup***
   EXIT

I updated the title of this thread.
I think that is it completely obvious to 98% of our users that:
IF you shut the computer off in the middle of a task then it won't be completed.

OK, if you have:
1) DP Finisher set to GUIRunOnce and
2) KTD enabled and
3) Have a reboot set at the end of RunOnceEx (I do in a Cleanup.cmd I found on one of the forums).

this will fail every time since guirunonce runs after runonce exe.
this means that there is just enough time to start the finisher (60 seconds into the GUI)
i am aware there is some documentation that says they run at the same time... but humor me anyway.

switch the order of operations.
1) DP Finisher set to RunOnceEx and
2) KTD enabled and
3) Have a reboot set at the end of Cleanup.cmd run from GUIRunOnce.

Hi
a more informative tute is linked to in my sig (and overFlow's, and Helmi's).
It mentions some 'peculiarities' we recently discovered.

Although I see the extra info in that tutorial, I still don't see anything that talks about how the DP cleanup/KTD is started or more importantly, how I can do a reboot after it is done.

Yes, I did run DP as my last stage (thanks to tutorials). 

I'm afraid I didn't keep the logs.  Its very reproducable tho... Just enable KTD and have RunOnceEX reboot.  Hmm, I'm not sure if this matters, but I have RunOnceEx run a CleanUp.cmd that has:

   cmdow @ /HID
   shutdown.exe -r -f -t 60 -c "Windows XP will now restart in 1 minute..."
   DEL ***some stuff here for cleanup***
   EXIT

This at the very least will leave stuff in C:\D\ and not finish copying KTD to C:\Windows\DriverPacks\ and sometimes give a desktop.ini error.

Sorry, but I'm a bit too busy ATM to mess with it more.  Maybe in a week or 2.  Removing the reboot in cleanup.cmd eliminates all these problems.  I watched the install and saw the DriverPacks starting to do things right after the RunOnceEx ended (which was during the shutdown.exe countdown timer. 

I hope this helps someone.
Ed

there are lots of ways - that is one i use (select "custom" for the finisher)

I will assume you built your source with DriverPacks as last stage.
If that is true, please give us all the detail you can.
We should see logs of each stage, and the last stage in building a source should be DriverPacks.

A useful report includes at least the base log, base INI, and finisher log.

Hmm, I need to reboot after KTD is done, but I don't see how to do that.  Any ideas?

OK, if you have:
1) DP Finisher set to GUIRunOnce and
2) KTD enabled and
3) Have a reboot set at the end of RunOnceEx (I do in a Cleanup.cmd I found on one of the forums).

Then the reboot will happen before KTD is finished, so:
1) KTD not finished in %SystemRoot%\DriverPacks and
2)  the driverpacks will not be cleaned up and
3) I got the desktop.ini error I see some other people have gotten.

I did a few searches and did not see anything about this.  If this was already posted then I'm sorry.  :-S