Search options (Page 14 of 159)

DriverPacks don't support Win32 "upgrades".  This is in our FAQ and Tutorial.  You'll need to back up your data then format and install clean otherwise you can install clean to a new hard drive and copy your files over.
(the winnt.sif entries break the win32 upgrade process).
I don't know how to fix what you broke.

http://forum.driverpacks.net/viewtopic.php?id=4468

Having multiple OS on the same drive isn't a problem in itself, provided that there's no problems with each OS that would prevent it from booting (BSOD).

Yes, removing the OS install source during any phase of the install would cause a critical failure because not all the source files are copied to the target drive.  The installer looks to the original install source for certain files throughout the install process.
The only time it's safe to remove the install medium is after first login and you're sitting at the desktop and all is quiet.

It would be best to disable the KTD option.  It causes more problems than it solves.
Are you sure that HWID list is from your Dell 1525?  It looks as if zero drivers were installed!  Normally for a Dell notebook I would expect to see some ACPI\DLL**** devices.

The drive controller in the above HWID list is supported by dpms \D\M\I3\, an old driver that we haven't had problems with for years.

Implemented for 12.08r1 in work.

I will receive any email sent to admin -at- DriverPacks.net.  But so will the other two admins: Wim & Jeff.  Wim is the owner.
We haven't received any email to the admin box since June.

Here's a guide written by our own IcemanND
MSFN link: http://www.msfn.org/board/topic/144914- … -using-pe/
Contains a comprehensive .pdf file for download too!
Make sure to read; "Appendix A: Using Windows 7 Driverpacks from Driverpacks.net"

Well, assuming you didn't modify your source after integrating with DriverPacks, then the log file would be at the root of your source directory: "C:\Users\*****\Desktop\windows xp sp3"
Or in the backup directory: Create a DPs_Base.log backup @ C:\Users\******\Desktop\drivers pack\LogFiles\DPs_BASE_12-08-10_09-24.log
The other logs are found by reading the Read BEFORE you post. link in my signature.

finisherMethod    = "GUIRunOnce"
This method modifies the winnt.sif file.  If you run nlite AFTER integrating DriverPacks BASE, then nlite will corrupt the install.  This is specifically why we say to integrate DriverPacks LAST before finalizing the .iso.

BTW, the CPU DriverPacks are all obsolete since they were incorporated into DriverPack Chipset about 2 years ago.

You could kick it off with an optional "start /wait..." command.  It would be nice to integrate that functionality directly within SAD2 but you wouldn't have the pretty GUI.
Also, the resulting code would be huge.  This is a nice compromise.

@Damian666, if you want to take a stab at recoding SAD2 in Autoit you are welcome to try.  The code is open source and you can do what you want with it.  All the methodology/comments are in there, you'd just need to translate it.

What sound drivers are you trying to use?  If we're missing them, we could add them.
It's also likely that something broke your GUIRunOnce/RunOnceEx DriverPacks Finisher execution.  We have no way to tell because you haven't posted your DPs_BASE.log or DPsFnshr.log.

You can use the $OEM$ folder method.

It should load the driver automatically during a normal XP install.  Your HWID is matched by PCI\VEN_14e4&DEV_1646.
You didn't specifically mention your install method.
If you're using UBCD4win, then you can try editing the DriverPack LAN .ini file to change the following:

[b]
; BartPE Code
ms_count	 	= 1
ms_1_tag 	= "B_Proliant"
ms_1_sysfile 	= "bxnd52x.sys"
ms_1_exc_skipIfOS="w2k,wxp,w2k3"

to

[b]
; BartPE Code
ms_count	 	= 1
ms_1_tag 	= "B_Proliant"
ms_1_sysfile 	= "bxnd52x.sys"
ms_1_exc_skipIfOS="w2k,w2k3"

We introduced this code because of reports of conflicts, but let us know how this works for you.

I may have to shuffle some files around to fix the UBCD4win problems.

Stickied!