Topic: SAD-disc does not work completely...
Hi 
A day or two a go I tried to make a SAD-disc, that went okay.... I think.
But when I just tried using it, some of the needed drivers weren't installed during the 1st attempt, I still saw three devices with "code 28" in Windows XP's device manager.
Anyway, let's start with some info before I continue telling about what's going on:
DPBase 8.12.5, settings, log.
Specs of the computer I tested it on:
- Gigabyte GA-GC230D;
- Kingston ValueRAM KVR533D2N4/1G;
- 40GB Western Digital PATA harddrive (old one, but perfect for testing while the SATA drive, which is in use, remains untouched);
- NEC ND-3540;
- Belkin Gigabit Desktop Network PCI Card;
- clean XP Pro SP3 install, did that with an up-to-date XP disc (well, it was up-to-date a few months a go, thanks to ryanvm forum updatepacks).
Now the story continues: I first tried DP_Install_Tool.cmd, that did not install all the drivers. One of the NIC's had a code 28 ("The drivers for this device are not installed."), same with the GPU and the soundcard, those three were all onboard btw.
Maybe it has got something to do with what I saw while the batch was running, made some screenshots (thought those might come in handy):
1st thing I noted was the "toegang geweigerd" (XP is in Dutch, translation: "access denied") in the top window.
Next:
Don't think I need to explain why I made these 2 screenshots?
Then came this:
Rough translation: Windows "nagging" about important files that where replaced by unidentified versions and that they compromise the stability of the system, it's asking for the XP SP3 installation disc to put the originals back. I clicked cancel.
Some errors.
0x57: "De parameter is onjuist" -> "The parameter is incorrect".
0x4C7: "De bewerking is geannuleerd door de gebruiker" -> "The operation was canceled by the user". (Note, I didn't cancel anything. After the batchfile started, I didn't have to do anything besides clicking that window away from the previous screenshot (the "nagging" about important files being replaced), the batchfile kept going on it's own).
"Windows could not find the file DPsFnshr.exe", the file is present on the disc in the same folder as where DP_Install_Tool.cmd is located.
About 30 minutes after I started this whole thing it finished and started "ding.wav" (just looked at the commands in DP_Install_Tool.cmd, saw that was supposed to happen), but Windows could not play it because there was no sound device installed, which brings me to....
No explanation needed I think, that is what's left after running DP_Install_Tool.cmd.
After that I tried DPINST.EXE which was located in the D folder on the SAD-disc. Long(er) story short, after about 30 minutes of waiting all needed drivers (including the ones DP_Install_Tool.cmd didn't install) where installed, but did noticed some errors:
Before I forget, while DPINST.EXE was doing it's thing, Windows was "nagging" again about files being replaced and that it wanted to put them back from the XP SP3 disc. Hit cancel (again), and after that everything seemed to be okay
Note: I still have to try DPINST.EXE on a clean install, one where I didn't try DP_Install_Tool.cmd, that is something for later.
So.... anyone care to shed some light on what happened? I mean, why DPINST.EXE could finish the job that DP_Install_Tool.cmd could not?
And if the "nagging" of Windows is normal, is it possible to disable (or automaticly ignore) the "nagging" while the SAD-disc is doing it's thing?
(If someone mentions using unattended switches, I thought those where already used since I didn't have to do anything besides doubleclicking DP_Install_Tool.cmd and DPINST.EXE)
Anyway, thanks for the driverpacks btw, you guys (and girls?) have done one a great job (from what I can tell) 
With regards,
Bart Grefte
edit:
Just did a clean XP install and then DPINST.EXE. Well.... that one also can't seem to get it right"(on it's own).
I get these:
Clicked no.
File not found...
Clicked no.
Clicked no.
File not found...
Result:
Both the onboard soundcard and NIC don't work, although the GPU is now recognized properly while the driver for that one was not installed when using DP_Install_Tool.cmd....
Errors:
Last edited by bargrefte (2010-05-04 05:55:14)
. 
.
