As the driverpacks are being updated, should we delete their respective folder in the cache directory?
76 2006-05-29 08:39:13
Topic: SOLVED: QuickStream Cache: A question (1 replies, posted in Feedback and Support - DriverPacks Base)
77 2006-05-29 08:14:48
Re: DriverPack LAN 6.05 (12 replies, posted in DriverPack LAN)
hmm..it's probably me. But I keep getting page not found after terms of use (Download Driverpack!). 
78 2006-05-29 06:56:59
Re: Congratulations (26 replies, posted in Other)
Compatible with nLite?? did I over sleep...again??
79 2006-05-29 03:02:09
Re: SOLVED BUG #24 & SOLVED BUG #39: invalid entries in \I386\TXTSETUP.SIF (21 replies, posted in Feedback and Support - DriverPacks Base)
SP2 yes. MCE flavor.
80 2006-05-29 02:10:42
Re: SOLVED BUG #24 & SOLVED BUG #39: invalid entries in \I386\TXTSETUP.SIF (21 replies, posted in Feedback and Support - DriverPacks Base)
uh oh, me too bashrat.
81 2006-05-28 13:17:39
Topic: Script to rename your previous driverpacks! (2 replies, posted in Feedback and Support - DriverPacks Base)
Just cut and paste to a text file and save as WHATEVER.CMD. Run from directory with old DriverPacks.
@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"
EXITThnx Denney for pointing out my shortcomings...... 
82 2006-05-28 07:07:25
Re: [SOLVED BUG #84] M1: fails to copy the Intel .inf files to $OEM$ (50 replies, posted in Feedback and Support - DriverPacks Base)
About the only things I could think of are
1) Corrupted pack
2) Corrupted\non-compatible \QSC\wnt5_x86-32_m1_DP_Chipset_605 directory
and possibly 3) Long directory names (with spaces) although it's very unlikely.
Try redownloading and erasing the above directory (if you're using Quickstream cache).
83 2006-05-28 06:21:27
Re: SOLVED: New DriverPack naming (I must be stupid!) (17 replies, posted in Feedback and Support - DriverPacks Base)
There are a lot of programs that I USED to call from guirunonce (I've sinced moved on to runonce).
I noticed that a lot of my app calls weren't doing crap, specifically an important one called VidChngxxxx.exe. After a few months I finally decided to rename that exe and change the reference in winnt.sif to read vidchng.exe and behold. It worked. (8.3 filename)
The reason for the renaming is this...
DPGA603.7z : What the h*ll is this??
DP_Graphics_A_wnt5_x86-32_603.7z : Oh, I see. It's graphics pack A!
Easier to read.
84 2006-05-28 06:14:21
Re: SOLVED: New DriverPack naming (I must be stupid!) (17 replies, posted in Feedback and Support - DriverPacks Base)
I believe they've been renamed for clarity (long filenames). Strictly for clarity.
85 2006-05-28 06:05:50
Re: [SOLVED BUG #84] M1: fails to copy the Intel .inf files to $OEM$ (50 replies, posted in Feedback and Support - DriverPacks Base)
Reproduced. Had both chipset packs in directory (the old renamed using new naming convention). I'm curious...could it be you renamed the old chipset pack with new name? Because there IS a new chipset pack released yesterday...
How many kb is your chipset pack?
86 2006-05-28 05:51:32
Re: [SOLVED] M2: no more \$OEM$\$$\INF dir for Intel .inf files? (2 replies, posted in DriverPack Chipset)
Right on. I'll slipstream upon release of your next build (with the fixed $OEM$ issues).
Good Job 
87 2006-05-28 05:31:00
Topic: [SOLVED] M2: no more \$OEM$\$$\INF dir for Intel .inf files? (2 replies, posted in DriverPack Chipset)
I'm a big fan of M2 and hence have been using M2 since the previous incarnation of DPBase.
Using M2 in the previous version (with no KTD...ever), I noticed the Intel INFs located in \$OEM$\$$\INF. Was this a bug in the previous version being that I use M2?
I'm asking because I can't find them using M2 in 6.05CP. Normal?
88 2006-05-28 05:22:51
Re: DUPLICATE OF BUG #24 (7 replies, posted in Feedback and Support - DriverPacks Base)
Deleting one of the extra '=' would work much better.
Method 2 is slightly quicker than Method 1 when it comes to setup.
Setup using method 1 will actually show what it's doing (copying driver files) during textmode minus the yellow progress bar.
Setup using method 2 will have you staring at a blue/green blank screen for about 5 mins after first reboot (after textmode).
89 2006-05-28 04:45:01
Re: SOLVED BUG #24 & SOLVED BUG #39: invalid entries in \I386\TXTSETUP.SIF (21 replies, posted in Feedback and Support - DriverPacks Base)
Floppy wrote:
Changed to;
; *_NVRAIDBUS="nvraid"
; *NVRAIDBUS=="nvraid"Running a quick test on VM --->Ok
Will run a complete test on a PC later today.Q.
Have I done somthing wrong,or is it just a slip-up :-) ?
Uh, Floppy. Bashrat has fixed the issue. It WAS a slip-up. Now we just wait for a fixed release.
The fix is not to put semicolon...it is to remove the extra equal sign '='.
Like this: *NVRAIDBUS="nvraid"
90 2006-05-27 23:31:07
Re: SOLVED: New DriverPack naming (I must be stupid!) (17 replies, posted in Feedback and Support - DriverPacks Base)
LMAO!
91 2006-05-27 13:49:57
Re: SOLVED BUG #24 & SOLVED BUG #39: invalid entries in \I386\TXTSETUP.SIF (21 replies, posted in Feedback and Support - DriverPacks Base)
done
92 2006-05-27 13:23:15
Re: SOLVED BUG #24 & SOLVED BUG #39: invalid entries in \I386\TXTSETUP.SIF (21 replies, posted in Feedback and Support - DriverPacks Base)
Ok...everything seems fine for textmode. However, there are a few missing descriptions for drivers during textmode.
They appear as such: ()
93 2006-05-27 12:54:46
Re: SOLVED BUG #24 & SOLVED BUG #39: invalid entries in \I386\TXTSETUP.SIF (21 replies, posted in Feedback and Support - DriverPacks Base)
cool in that case, I'll fix that nvraid line and report back
94 2006-05-27 12:52:13
Re: SOLVED BUG #24 & SOLVED BUG #39: invalid entries in \I386\TXTSETUP.SIF (21 replies, posted in Feedback and Support - DriverPacks Base)
so far...as soon as you clear it, setup up should continue parsing and let me know since it won't continue after detecting errors.
95 2006-05-27 12:48:28
Topic: SOLVED BUG #24 & SOLVED BUG #39: invalid entries in \I386\TXTSETUP.SIF (21 replies, posted in Feedback and Support - DriverPacks Base)
BUGTRACKER LINK (#24)
BUGTRACKER LINK (#39)
Line 11174 of the Inf file \i386\txtsetup.sif is invalid.
Line 11174 looks like this:
*NVRAIDBUS=="nvraid"
Also...is there any way to REMOVE certain controllers...for example JAHCI drivers, since Intel seems to have a hard time with them?