Have you tried re-creating the ISO image from scratch? $20 says it works then.
1 2006-05-29 13:02:44
Re: SOLVED: New DriverPack naming (I must be stupid!) (17 replies, posted in Feedback and Support - DriverPacks Base)
2 2006-05-28 13:44:29
Re: SOLVED: New DriverPack naming (I must be stupid!) (17 replies, posted in Feedback and Support - DriverPacks Base)
Known problem: http://forum.driverpacks.net/viewtopic.php?id=9
Simple fix, remove one of the 2 "=" signs on that line.
3 2006-05-28 13:36:22
Re: Script to rename your previous driverpacks! (2 replies, posted in Feedback and Support - DriverPacks Base)
I think you should remove the Chipset line because the old Chipset DriverPack isn't compatible with v6.05.
Edit: Don't mean to rain on your parade, but the file should look like this:
@ECHO OFF
REM RUN THIS UTILITY FROM DIRECTORY CONTAINING THE FOLLOWING DRIVER PACKS!
IF EXIST "DriverPack_CPU_V603.7z" REN "DriverPack_CPU_V603.7z" "DP_CPU_wnt5_x86-32_603.7z"
IF EXIST "DriverPack_Graphics_A_V603.7z" REN "DriverPack_Graphics_A_V603.7z" "DP_Graphics_A_wnt5_x86-32_603.7z"
IF EXIST "DriverPack_Graphics_B_V603.7z" REN "DriverPack_Graphics_B_V603.7z" "DP_Graphics_B_wnt5_x86-32_603.7z"
IF EXIST "DriverPack_Graphics_C_V603.7z" REN "DriverPack_Graphics_C_V603.7z" "DP_Graphics_C_wnt5_x86-32_603.7z"
IF EXIST "DriverPack_LAN_V6032.7z" REN "DriverPack_LAN_V6032.7z" "DP_LAN_wnt5_x86-32_6032.7z"
IF EXIST "DriverPack_MassStorage_V6031.7z" REN "DriverPack_MassStorage_V6031.7z" "DP_MassStorage_wnt5_x86-32_6031.7z"
IF EXIST "DriverPack_Sound_A_V603.7z" REN "DriverPack_Sound_A_V603.7z" "DP_Sound_A_wnt5_x86-32_603.7z"
IF EXIST "DriverPack_Sound_B_V603.7z" REN "DriverPack_Sound_B_V603.7z" "DP_Sound_B_wnt5_x86-32_603.7z"
IF EXIST "DriverPack_WLAN_V603.7z" REN "DriverPack_WLAN_V603.7z" "DP_WLAN_wnt5_x86-32_603.7z"
EXITRemoved Chipset line and fixed CPU line.
4 2006-05-28 05:48:41
Re: SOLVED BUG #30: Critical Error! - No suitable slipstream module found (5 replies, posted in Feedback and Support - DriverPacks Base)
Just awaiting my activation email for the bugtracker.
Edit: Reported.
5 2006-05-28 02:45:27
Re: SOLVED BUG #30: Critical Error! - No suitable slipstream module found (5 replies, posted in Feedback and Support - DriverPacks Base)
Worked out something: Running DPs_BASE.exe without a DPs_BASE.ini file in the same directory causes this error. I generally delete that file after first running it to start with a clean slate. If you leave it there after the first failure, it runs fine...
6 2006-05-28 02:41:47
Topic: SOLVED BUG #30: Critical Error! - No suitable slipstream module found (5 replies, posted in Feedback and Support - DriverPacks Base)
This is a rather annoying error.. 
I have no idea why it's coming up with this error... I have no clue as to what's wrong... Below is my "DBs_BASE.ini" and "DBs_BASE.log" files.
DPs_BASE.ini:
[General]
; 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/multibootDisc/multibootPlatform
type = ""
; trailing backslash is allowed, but not necessary
location = "C:\Documents and Settings\Denney\My Documents\My Development\UOS\UOS_0506"
; 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
finishMethod = "custom"
[OptionalSettings]
; none/all/select/specify/pattern, enable or disable Keep The Drivers (KTD) , if not specified: none
KTD = "all"
; yes/no, enable or disable QuickStream Cache (QSC), if not specified: yes
QSC = "yes"DPs_BASE.log:
2006-05-28 01:08:32 : <INIT> DriverPacks BASE 6.05 CP initialized.
2006-05-28 01:08:32 : <INIT> Could not detect settings file.
2006-05-28 01:08:32 : <INIT> [General]\wizdButtons not specified: default (yes) was set.
2006-05-28 01:08:32 : <INIT> [General]\GUI not specified: default (yes) was set.
2006-05-28 01:08:32 : <INIT> Detected DriverPack Chipset 6.05!
2006-05-28 01:08:32 : <INIT> Detected DriverPack CPU 6.03!
2006-05-28 01:08:32 : <INIT> Detected DriverPack Graphics A 6.03!
2006-05-28 01:08:32 : <INIT> Detected DriverPack Graphics B 6.03!
2006-05-28 01:08:32 : <INIT> Detected DriverPack Graphics C 6.03!
2006-05-28 01:08:32 : <INIT> Detected DriverPack LAN 6.03.2!
2006-05-28 01:08:32 : <INIT> Detected DriverPack MassStorage 6.03.1!
2006-05-28 01:08:32 : <INIT> Detected DriverPack Sound A 6.03!
2006-05-28 01:08:32 : <INIT> Detected DriverPack Sound B 6.03!
2006-05-28 01:08:32 : <INIT> Detected DriverPack WLAN 6.03!
2006-05-28 01:08:32 : <INIT> Detected 3rd party DriverPack(s).
2006-05-28 01:08:32 : <INIT> DriverPacks scanned sucessfully.
2006-05-28 01:08:32 : <GUI> Initialized GUI.
2006-05-28 01:08:40 : <GUI> Changed Windows installation files location to C:\Documents and Settings\Denney\My Documents\My Development\UOS\UOS_0506.
2006-05-28 01:08:40 : <GUI> Detected Windows XP Professional SP2 in C:\Documents and Settings\Denney\My Documents\My Development\UOS\UOS_0506.
2006-05-28 01:08:51 : <GUI> Saved settings!
2006-05-28 01:08:52 : <GUI> Closed GUI.
2006-05-28 01:08:52 : <CRIT> No suitable slipstream module was found.
2006-05-28 01:10:07 : Program terminated.Any ideas? Only thing I seemed to have changed this time around is changing finish method to "custom"...
7 2006-05-28 02:31:22
Re: [SOLVED] CLI.exe error (8 replies, posted in DriverPack Graphics)
You can get a silent installation of the .NET Framework from Ryan's website: http://www.ryanvm.net/msfn/
Follow these instructions to install it:
You need to open a command prompt window (cmd.exe) and navigate to your I386 directory (of the XPCD on your harddrive).
Once there run:
expand -r svcpack.in_
Then, open the svcpack.inf file in Notepad and under the "[SetupHotfixesToRun]" section, add "dotnet11sp1.exe".
Save the file and delete the "svcpack.in_" file.
Once you've downloaded the "dotnet11sp1.exe" file (from Ryan's site) put it in the I386\SVCPACK directory. It should work then.
Hope you can understand my rambling, I never was any good at teaching other people things. Any questions, just ask.
Edit: The CLI.EXE file isn't actually from the ATI drivers. It stands for "Common Language Interface" and is part of the .NET Framework install. That is the reason for your problem.
8 2006-05-28 00:20:42
Re: IMPLEMENTED: custom KTD location option (3 replies, posted in Feature Requests)
Ah ok kool. I'll just edit the scripts for now.
You've edited the presetup.cmd file now and removed the variable to set where it's stored... Damn you... 
9 2006-05-27 23:45:55
Topic: IMPLEMENTED: custom KTD location option (3 replies, posted in Feature Requests)
According to the MSFN post (http://www.msfn.org/board/index.php?showtopic=66854) there is support for a custom path for the KtD option. I can't seem to find that option though.
I like to keep the drivers in the "%SystemRoot%\D" directory (not "%SystemDrive%\D") and I've always changed it via manually editing the .cmd files. I hoped not to have to do this with the new version.
Was this option scraped at the last minute or is it hidden somewhere?
10 2006-05-27 23:29:49
Re: SOLVED: New DriverPack naming (I must be stupid!) (17 replies, posted in Feedback and Support - DriverPacks Base)
How come you always notice what you've done wrong JUST AFTER you tell the world about it?
Nevermind, I fixed it... I forgot about the wnt5_ bit... :S
11 2006-05-27 23:26:38
Topic: SOLVED: New DriverPack naming (I must be stupid!) (17 replies, posted in Feedback and Support - DriverPacks Base)
I don't know why but I can't get v6.05 to recognize some of the DriverPacks. I've named the DriverPacks like so:
DP_MassStorage_x86-32_6031.7z
DP_Sound_A_x86-32_603.7z
DP_Sound_B_x86-32_603.7z
DP_WLAN_x86-32_603.7z
I've also renamed my 3rd party DriverPacks to:
DP_HID_x86-32_11.7z
DP_Misc_x86-32_13.7z
DP_Monitor_x86-32_171.7z
DP_VMware_x86-32_11.7z
But none of them are recognized. What do I seem to be missing? The log and INI files are no help:
2006-05-27 21:53:56 : <INIT> Imported settings from settings file.
2006-05-27 21:53:56 : <INIT> Detected DriverPack Chipset 6.05!
2006-05-27 21:53:56 : <INIT> Detected DriverPack CPU 6.03!
2006-05-27 21:53:56 : <INIT> Detected DriverPack Graphics A 6.03!
2006-05-27 21:53:56 : <INIT> Detected DriverPack Graphics B 6.03!
2006-05-27 21:53:56 : <INIT> Detected DriverPack Graphics C 6.03!
2006-05-27 21:53:56 : <INIT> Detected DriverPack LAN 6.03.2!
2006-05-27 21:53:56 : <INIT> Could not detect any 3rd party DriverPacks.
2006-05-27 21:53:56 : <INIT> DriverPacks scanned sucessfully.
So, what should these files actually be named? Other than that, love the new interface and I look forward to the DriverPack updates.