Bâshrat the Sneaky

Glad it's solved

... and up. Next time rather mail me than starting a new topic. Yes this is somehow a 'new policy', but if I don't do this, I'll keep getting posts in several of the DriverPacks forums, which is useless.

robnjay, the problem is that your motherboard has been reported before, and it has been working with the viamraid driver... But please try this: go to your I386 folder, open the txtsetup.sif file and use CTRL+F to search for this line: PCI\VEN_1106&DEV_3149&SUBSYS_04701462&REV_80 = "viamraid" and change it to: PCI\VEN_1106&DEV_3149&SUBSYS_04701462&REV_80 = "viasraid" (note the 's') This shouldn't work ... but it just might

M1 worked fine... M2 indeed has a problem :s EDIT: tested with V5.07.4 without noticing :@ Now testing with V5.07.7... M2 works fine with GUIRunOnce, KtD no. now testing RunOnceEx, KtD yes.

Are you sure your laptop's specs are high enough to run Windows XP?

VPC is indeed MUCH slower than VMWare when it comes to (unattended) Windows installations. As rikgale said, just change the settings...

What guide did you follow?

Aha. And does this have to be fully automatical? Because that will complicate this thing much more than just using the method I suggested first. May I ask why you don't want the drivers to be on the CD?

You cannot use VMWare/VirtualPC to test your drivers. You'll have to use a REAL pc. http://www.btsunattended.net/wiki/doku.php...testing#drivers EDIT: Question answered, topic closed.

:s You're right :s I'll update it.

The latest version of this driver is already included in DriverPack LAN

Sorry for the late reply. If you can find some drivers that I don't have yet, it'd be great if you'd link to them! P.S.: I'll add support for those Xircom drivers in the next version of DriverPack LAN.

Most of the time this is because of the DDoS attacks on the datacenter, at least that's what my hosting provider says... And he also says that this is normal - unless you buy dedicated hosting... I trust this guy because he's a friend of a friend... Well... :|

@mjc: your Silicon Image SiI3114r will be supported in the next update of the DriverPacks BASE. And yes, your AMD driver is already supported by DriverPack MassStorage, that's why it works just fine @VoYaGeRTM1977: your problem will be solved too. I added another work-around.

@robnjay: are you now using the VIA SATARAID controller or the Silicon Image SiI3112r controller? Your latest posts make me doubt. @VoYaGeRTM1977: if I understand you correctly (also after looking at the post you linked too), I think you've got problems with the Silicon Image SiI3112r? Though that would amaze me... the nForce 2 controller that's giving problems would be more probable... Let me know. EDIT: so that was the SiI3112r... your problem is fixed in the next update

Erm... Why could you possibly not do that? :s

strange... the batch file creates a new winnt.sif file if it' isn't found. I'll try to reproduce this as well. P.S.: do you have administrator rights? Anything special with policies or something on that pc?

This card is supported by Windows XP out of the box. EDIT: Moved to DriverPack Graphics.

@coucou, laza & Thauzar: that's not normal. I'm testing it here ATM, I'll report back in a couple of minutes. (testing M1 & M2) @muiz: working on it.

Any clues/sneak peaks? What kind of big changes do you have in mind...

Check the topic title: "M2, KtD: Driver Signing Policy popups". I think you're NOT using the KtD option - don't understand me wrong: you don't have to. It isn't working for ANY driver? (i.e. endless popups)

Forgot to add NeroVision Express... fixed that now.

← Hate to say it (especially since it's my first post!!) but I think it's still broke! Just finished compiling and building my first XP SP2 combo CD with Ryans Patches & of course your DP. Everything went swimmingly (after a few hiccups ) until the final section where lo behold the Unsigned Driver warning pops up. Now I did Method 2 (as I plan to image this machine to another) using the GuiRunOnce. I'm using DP Base v5077.exe looking at RUN_ME.cmd ... CODE ... Now I might be WAY off the mark here but shouldn't method 2 also have the DriverSigning set to ignore? Rob ← Nope, that's what WatchDriverSigningPolicy.exe is for Though, if you look some further in the batchfile, you'll find this: :KtD_activate DEL /Q %DPDIR2%\BTS_DPs_cleanup.cmd ECHO. ECHO _ drivers won't be removed after the installation is complete. ROBOCOPY "%CD%" %DPDIR2% SetupCopyOEMInf.exe /MOV %RS% > NUL ROBOCOPY "%CD%" %DPDIR2% WatchDriverSigningPolicy.exe /MOV %RS% > NUL IF %M%=M2 ( Fedit -add -create -f I386\WINNT.SIF -s Unattended " DriverSigningPolicy = \"Ignore\"" Fedit -add -create -f I386\WINNT.SIF -s Unattended " NonDriverSigningPolicy = \"Ignore\"" ) Where you can clearly see it is being added to the winnt.sif file, but only if the KtD option has been enabled...

It's at the frontpage now

**** you You beat me by 25 minutes A funny note: