Search options (Page 2 of 6)

Does the new base recognize and remove the old formats automatically?  That might be why...

Sometimes if I copy a scratched up source disk to my hard drive, I have that problem with the files being unable to extract during setup.  I eventually solved it by downloading the problem files from a 3rd party website.  As far as I can tell, DriverPacks doesn't mess with the rspndr.inf file.

Also be sure that you don't do anything except create the .iso when you use nLite.  If you do anything with nLite (especially with drivers) you can screw things up.  DriverPacks should be the last step before iso creation.

If I were you, I'd look over the updates you're getting...  If that website has a forums, do a search on that file name or post a question about it, surely someone will know if it's a file that gets altered during the update process.

Do you have a winnt.sif inside the I386 directory?  If so, is it a plain text file?

Also, does the directory you're working in have read-only access?  You won't be able to slipstream anything if you can't write to the directory.

EDIT:
Another thought that crossed my mind is that it could also indicate that you're running DPBase from a directory that is read-only.  I believe that there is another backup file created there.

I hate files.to....  Their image capcha isn't compatable with Opera.

Next time use code blocks...  Here are capacity's files:

DPs_BASE.ini

[General]
; preferred language
prefLang	= "English"
; yes/no, enable or disable the wizard-style buttons, if not specified: yes
wizardButtons	= "yes"
; yes/no, enable or disable the GUI, if not specified: yes
GUI		= "yes"


[Settings]
; disc/bartpe/multibootDisc
instPlatform	= "disc"
; trailing backslash is allowed, but not necessary
location	= "C:\XP_ORI_SP2"
; none/all/select, if select, specify them below, if not specified: all
DriverPacks	= "all"
; 1/2, method to install the DriverPacks, if not specified: 2
DPsMethod	= "2"
; GUIRunOnce/RunOnceEx/custom, if not specified: GUIRunOnce
finisherMethod	= "GUIRunOnce"


; this section is optional!
[OptionalSettings]
; none/all/select/paths/patterns, enable or disable Keep The Drivers (KTD) , if not specified: none
KTD		= "false"
; <path>, to specify a custom KTD cache location, if not specified: default (%SystemRoot%\DriverPacks)
KTDlocation	= "%SystemRoot%\DriverPacks"
; yes/no, enable or disable QuickStream Cache (QSC), if not specified: yes
QSC		= "no"


; this section is optional!
[OptionalSettingsOther]
; CCC/CCP, use ATI Catalyst Control Center or ATI Catalyst Control Panel (only relevant when slipstreaming DriverPack Graphics A)
ATI_cpl		= "CCP"

DPs_BASE.log

2007-09-28 20:29:07 : <INIT> DriverPacks BASE 7.05.2 initialized.
2007-09-28 20:29:07 : <INIT> Host environment: WIN_XP Service Pack 2 on X86 CPU.
2007-09-28 20:29:07 : <INIT> Old temporary working directory deleted.
2007-09-28 20:29:07 : <INIT> Created temporary working directory.
2007-09-28 20:29:07 : <INIT> Imported proxy settings from Internet Explorer.
2007-09-28 20:29:07 : <INIT> Start scanning for DriverPacks for the wnt5_x86-32 platform.
2007-09-28 20:29:07 : <INIT> 	Detected DriverPack Chipset 7.09!
2007-09-28 20:29:07 : <INIT> 	Detected DriverPack CPU 7.04.1!
2007-09-28 20:29:07 : <INIT> 	Detected DriverPack Graphics A 7.09.1!
2007-09-28 20:29:07 : <INIT> 	Detected DriverPack Graphics B 7.09.2!
2007-09-28 20:29:07 : <INIT> 	Detected DriverPack Graphics C 7.09.1!
2007-09-28 20:29:07 : <INIT> 	Detected DriverPack LAN 7.09.1!
2007-09-28 20:29:07 : <INIT> 	Detected DriverPack MassStorage 7.09.1!
2007-09-28 20:29:07 : <INIT> 	Detected DriverPack Sound A 7.09!
2007-09-28 20:29:07 : <INIT> 	Detected DriverPack Sound B 7.07.1!
2007-09-28 20:29:07 : <INIT> 	Detected DriverPack WLAN 7.09.2!
2007-09-28 20:29:07 : <INIT> 	Detected 3rd party DriverPack(s).
2007-09-28 20:29:07 : <INIT> 	Finished scanning.
2007-09-28 20:29:07 : <INIT> Detected settings file "D:\DPs_BASE_7052\DPs_BASE.ini".
2007-09-28 20:29:07 : <INIT> No OS could be detected.
2007-09-28 20:29:07 : <INIT> Imported settings from settings file.
2007-09-28 20:29:07 : <INIT> [Settings]\DPsMethod not specified: default (2) was set.
2007-09-28 20:29:07 : <INIT> [Settings]\finisherMethod not specified: default (GUIRunOnce) was set.
2007-09-28 20:29:07 : <INIT> [OptionalSettings]\KTD not specified: default (none) was set.
2007-09-28 20:29:07 : <INIT> [OptionalSettings]\QSC not specified: default (yes) was set.
2007-09-28 20:29:07 : <INIT> [OptionalSettingsOther]\ATI_cpl not specified: default (CCC) was set.
2007-09-28 20:29:07 : <INIT> [OptionalSettings]\KTD default (false) was set.
2007-09-28 20:29:07 : <INIT> [OptionalSettings]\QSC default (no)    was set.
2007-09-28 20:29:07 : <GUI>  Initialized GUI.
2007-09-28 20:29:07 : <GUI>  Created a list of all available language files.
2007-09-28 20:29:07 : <GUI>  Set the last used language, English, as the GUI language.
2007-09-28 20:29:20 : <GUI>  Changed Windows installation files OR export (depending on the installation platform) location to C:\XP_ORI_SP2.
2007-09-28 20:29:21 : <GUI>  Windows XP Professional -  SP2 detected.
2007-09-28 20:29:21 : <GUI>  The platform wnt5_x86-32_disc will be used (which is the 'disc' installation platform for the OS family 'wnt5_x86-32').
2007-09-28 20:29:39 : <GUI>  Refreshed UpdateChecker with success.
2007-09-28 20:29:49 : <GUI>  Saved settings!
2007-09-28 20:29:49 : <GUI>  Closed GUI.
2007-09-28 20:29:49 : <SEL>  Selected module: mod_slip_wxp_x86-32_disc_m2.

That is one HECK of a transformation pack if it's not vista.  Oh...  Haha, I just noticed that Ubuntu logo at the start menu location for the first screen shot.

Edit:
Oh wait, you just switched images on me...  Nevermind.

Is that really a problem?  The finisher (as I understand it) just installs the extra software that should get installed for specific devices.  For example, the ATI control center and/or catalyst, or the nVidia configuration utilities...

Why do you need to know how it does what it does?

Be sure you've got the order right...

Slipstream a service pack if you need to (if you use nLite to do it, make sure you don't do anything else)
WMP11 slipstream (if you want it)
RVM
RVM Addon Packs (IE7, .Net 1.1, WGA, anything else really - although they're safe to add into the nLite step)
nLite
DriverPacks

Other than that, I don't know what to say.  It sounds like it could be a problem with the chipset/CPU drivers.  Have you tried only integrating only a 3rd party pack (something like printers)?  If you can get past it with a single 3rd party pack, then I'd start sifting through each pack determining which one is killing your install (use a CD-RW for this step).

Also, it's not usually the problem but try slowing down your burn speed (it's at least worth a try).  Some CD drives don't like it when you burn over a certain speed.  You'll definetly be okay with 4x, but 8x is usually fine.  12x and 16x have given me issues with CD players before, but only 32x and higher has given me problems on a computer's CD drive.

From what I understand, a RIS install uses unattended.txt by default instead of winnt.sif (it's the exact same thing as winnt.sif, but with a different name - go figure).  The base really should alter/create one of those...  But it doesn't since it expects the install platform to be a disc.

Those files that get altered are in the I386 directory (get used during install), and I would think that they use relative paths to refer to the OEM directory for the drivers.  So if you put the OEM directory side by side with I386, then it shouldn't have a problem...  I only mentioned opening the files to look for absolute paths because an absolute path would definetly screw something up (but I seriously don't think that you have to worry about absolute paths).

DriverPacks get put in the OEM folder, which is not to be confused with the $OEM$ folder.  Have you tried just putting the OEM folder side by side with the I386 folder on your RIS drive?

Here's a list of the files that get changed and backed up by DriverPacks (may or may not be complete):

ADPU160M.sy_ -> adpu160m.org
ALIDE.sy_ -> ALIDE.org
DAC2W2K.sy_ -> dac2w2k.org
DAC960NT.sy_ -> dac960nt.org
dosnet.inf -> dosnet.org
DPTI2O.sy_ -> DPTI2O.org
MRAID35x.sy_ -> mraid35x.org
QL12160.sy_ -> ql12160.org
txtsetup.sif -> txtsetup.org
ULTRA.sy_ -> ultra.org
WINNT.sif -> winnt.org

The .org is a backup of the original.  I recommend expanding the modified files, and looking to see if there's are direct paths which you can alter to your network location.

The only thing that gets put in the $OEM$ folder is the finisher.  The finisher doesn't install drivers, nor does it make the computer recognize drivers - it's designed to add in the necessary software like the ATI Control Panel.  Just little things like that.  You should have drivers just fine, although you might experience a problem with the call to the finisher (GUIRunOnce or RunOnceEX - but all you have to do is take it out of there and you won't get the error).

Oh I see.  Does DriverPacks base pop up an error message?

It's all good.

Or you know... You could click on the update tracker link on that page.... Here it is if you're too lazy - http://driverpacks.net/DriverPacks/UpdateTracker.php

Also, there's an RSS feed so you can subscribe to that and get updated notifications.

Finally, the DriverPacks base has a version checker in it - to see if you're up to date right before you slipstream the drivers...

Seems to me like adding the versions to the page you're talking about wouldn't just be over-kill, but it'd also be like beating the dead horse with a 10 ft. pole that also contained an electric prod in an attempt to get the horse to move (gotta love the exasperated imagery).