When I have time, I'll make a picture to show what I meant, bit busy with work this week so could take a few days 
I'm guessing it's because Windows has not been started, maybe that's what made the difference to get this working.
1 2010-05-19 06:42:10
Re: SAD-disc does not work completely... (15 replies, posted in Feedback and Support - DriverPacks Base)
2 2010-05-16 00:19:50
Re: SAD-disc does not work completely... (15 replies, posted in Feedback and Support - DriverPacks Base)
Update:
This is what I see now after the install with the driverpacks integrated finishes (and the computer has done a reboot which I entered in my batchfile which installs NOD32 AV, JRE and something else I doubt isn't allowed mentioning here.... But that "thing" keeps some potential trouble away....).
Anyway..... it works 
. Added all the packs to my almost (as you can see) up-to-date XP dvd. No unknown hardware, sound works, both NIC's too, and the GPU is recognized as well, yay!
I just noticed one weird thing. When I first created it, I noticed (a bit late) that the command for the DriverPacks Finisher came second in the winnt.sif at the guirunonce part. My batchfile was run first, but since it had a reboot command in it, XP wasn't able to boot completely because the DriverPacks Finisher took some time. Anyway, I switched the command for the DriverPacks Finisher and my batchfile, causing the DriverPacks Finisher to start first (which I intended) but then I did not see the actual DriverPacks Finisher window. I did see a black rectangle (same size as DriverPacks Finisher window) where the window was supposed to be, but it did it's job okay.
Anyone know why?
3 2010-05-14 07:33:25
Re: SAD-disc does not work completely... (15 replies, posted in Feedback and Support - DriverPacks Base)
Haven't gotten around to try integrating the drivers directly in the Windows installation disc, hope to get to that this weekend. Let you guys know how that turns out.
Helmi wrote:
Just a long shot, but as it happened to me once...
Defective RAM may result in corrupted drivers being extracted/copied from the source, hence driver install will fail.As for the RWs:
I know it might not be the most clever idea to just introduce another possible source of error when you are troubleshooting but if you've got a spare USB stick with about 2 GB of capacity, http://www.msfn.org/board/topic/120444- … -with-gui/ might actually help you save on the RW.
Been using it quite successfully myself for a while and I found it to be more reliable than an RW, as DVD readers may dislike them.
OTOH, it requires the BIOS to boot from USB, but most of those post 2000 offer such an option.
Besides that I always check RAM before I put it into use (like I did with this particular computer), it's the same drivers with all attempts that don't work, plus that the OS on the main HDD works perfectly fine. Doesn't really sound like RAM problems to me....
Another possible source of error? Hmm, every time I burn a cd/dvd I let Nero do a verification, to rule out that cause...
Installing from USB might be an idea, I'll keep that in mind , thanks for the tip!
OverFlow wrote:
Hiya Helmi! Nice to see you
The tutorial is quite old but the features, options and step by step instructions have not changed since then. (for a Disc install). SAD and BartPE have been added and the instructions for those are not relevant to slipstreaming the drivers to a disc
. YES it is the same as in version 8 of BASE LOL.
I don't know why DPINST.EXE does not work as well as windows SETUP.EXE... You will have to ask MicroSoft who wrote both of those executable programs. (SAD is simply a wrapper for the MS supplied file DPINST.EXE.)
Wow... Yeah that is a wild error
Hmm, okay.
Some error huh , no idea what that's about. You would think someone would have noticed it by know....
4 2010-05-10 07:01:43
Re: SAD-disc does not work completely... (15 replies, posted in Feedback and Support - DriverPacks Base)
MD5's match, WinRAR (which I prefer for working with archives) tested the archives and did not report any errors.
5 2010-05-10 04:31:34
Re: SAD-disc does not work completely... (15 replies, posted in Feedback and Support - DriverPacks Base)
Hmm, 'kay.
This howto? http://users.telenet.be/jtdoom/basetute/Eng_tut6b.htm isn't that one a bit outdated? (or is it the same in v8 of BASE).
Just tried SAD M2, the 2nd (the onboard one) NIC is now recognized and installed too, soundcard as well but that one does not work. Windows claims there is no audio device present :S. The GPU is not recognized.
Out of curiosity, what causes SAD to not work (completely) on a "vanilla" system? The dev and ven ID's of unknown devices are available, so it's not about recognition of unknown hardware I think. Or is it because what you mentioned in post "2010-05-04 03:09:15", the (absence of) reboots.
If it's just that, can't the SAD-installer do an automatic reboot after installing chipset-drivers and continue? (Or is this to complicated to implement, not a clue if that's the case.)
O well, Disc method it is, now if I could just find a store which sells 1 DVD+RW. It's always 5 or 10-packs, I only need one .
edit: regarding the soundcard, this is one h*ll (huh? I can't say h-e-l-l?) of a weird error:
Translation: Soundrecorder can not record or play because there is no sounddevice installed. Click on Printers and other hardware in the configuration screen and then on add printer to install a sounddevice.
Like huh/WTF?
6 2010-05-09 21:13:36
Re: SAD-disc does not work completely... (15 replies, posted in Feedback and Support - DriverPacks Base)
Hmm.... I thought it looked like they where already uncabbed, since it needed a little over 1GB of space on a dvd and there where over 10,000 of files. But after trying the M1 SAD disc with just CPU and unpacking everything after that, it was about 2.4GB :S
Anyway, that method had the exact same result (and the same missing file errors) that I mentioned in my 1st post.
Gonna try M2 later today I think.
If that also does not work, I think I'm just gonna fully integrate the LAN, WLAN and (for the text-based setup) massstorage drivers (for AHCI-mode) in my XP disc, see if that helps. And download the remaining needed drivers manually after that.
7 2010-05-08 20:06:32
Re: SAD-disc does not work completely... (15 replies, posted in Feedback and Support - DriverPacks Base)
M1 is old and abandoned? Then why is it still in BASE?
Hmm, I wanted to use it for an initial drivers installation.... So if a SAD-disc is not designed for that, are there alternatives that are? (If I can't get this to work completely.)
I'll try M2 later, and just making a cpu SAD-disc + extracting everything after that too, see if one of those makes a difference.
Uhm, extracting instead of cabbing? All files (a little over 1GB and about 10,493 total) where already extracted on the SAD disc (I did not do that), no cabbing was done.
8 2010-05-04 03:49:50
Topic: SAD-disc does not work completely... (15 replies, posted in Feedback and Support - DriverPacks Base)
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:
