51

(5 replies, posted in Other)

Question: Does DevPath reset after reboot?

I'm looking to decompress drivers to my unattend (exactly like M1), but have nothing to do with install.
I myself use M2, I want no drivers on my HD. Just want them uncompressed on my unattend. Reason I CAN'T use M1 is because of the sheer number of paths which will exceed the 4096 limit on WINNT.SIF. I just need a batch to tell Windows to look at my DVD, at the directory where I put the uncompressed drivers each time it detects a new device. Also, I could do it another way and decompress files temporarily to HD and have Windows look there.

Any suggestions on this batch?

yikes I noticed that dps_fnsh.cmd does hardware specific cleanup, but I don't think it's dependent upon the system the slipstream was done on! It can't be true! Could it? smile

I finally slipstreamed an official unattend DVD using the new GUI DPBASE (as opposed to vmware). I'm streaming all DriverPacks (including textmode), M2, Custom and No KTD). I've compared txtsetup.sifs from both batch and gui dpbase' and iastor entries APPEAR fine. I don't even know where to begin to figure this one out. Please help out here ppl. sad


HWID:

 
=========== 
PCI devices 
=========== 
 
 
PCI\VEN_10DE&DEV_00F9&SUBSYS_025410DE&REV_A2\4&37AD8B77&0&0008: NVIDIA GeForce 6800 Series GPU
PCI\VEN_1106&DEV_3044&SUBSYS_028D1462&REV_46\4&23C0B1C&0&18F0: VIA OHCI Compliant IEEE 1394 Host Controller
PCI\VEN_14E4&DEV_1677&SUBSYS_028C1462&REV_01\4&10CDB71B&0&00E2: Broadcom NetXtreme Gigabit Ethernet
PCI\VEN_8086&DEV_244E&SUBSYS_00000000&REV_D3\3&11583659&0&F0: Intel(R) 82801 PCI Bridge - 244E
PCI\VEN_8086&DEV_2580&SUBSYS_00000000&REV_04\3&11583659&0&00: Intel(R) 915G/P/GV/GL/PL/910GE/GL Processor to I/O Controller - 2580
PCI\VEN_8086&DEV_2581&SUBSYS_00000000&REV_04\3&11583659&0&08: Intel(R) 915G/P/GV/GL/PL/910GE/GL PCI Express Root Port - 2581
PCI\VEN_8086&DEV_2640&SUBSYS_00000000&REV_03\3&11583659&0&F8: Intel(R) 82801FB LPC Interface Controller - 2640
PCI\VEN_8086&DEV_2652&SUBSYS_70281462&REV_03\3&11583659&0&FA: Intel(R) 82801FR SATA RAID Controller
PCI\VEN_8086&DEV_2658&SUBSYS_70281462&REV_03\3&11583659&0&E8: Intel(R) 82801FB/FBM USB Universal Host Controller - 2658
PCI\VEN_8086&DEV_2659&SUBSYS_70281462&REV_03\3&11583659&0&E9: Intel(R) 82801FB/FBM USB Universal Host Controller - 2659
PCI\VEN_8086&DEV_265A&SUBSYS_70281462&REV_03\3&11583659&0&EA: Intel(R) 82801FB/FBM USB Universal Host Controller - 265A
PCI\VEN_8086&DEV_265B&SUBSYS_70281462&REV_03\3&11583659&0&EB: Intel(R) 82801FB/FBM USB Universal Host Controller - 265B
PCI\VEN_8086&DEV_265C&SUBSYS_70281462&REV_03\3&11583659&0&EF: Intel(R) 82801FB/FBM USB2 Enhanced Host Controller - 265C
PCI\VEN_8086&DEV_2660&SUBSYS_00000000&REV_03\3&11583659&0&E0: Intel(R) 82801FB/FBM PCI Express Root Port - 2660
PCI\VEN_8086&DEV_2664&SUBSYS_00000000&REV_03\3&11583659&0&E2: Intel(R) 82801FB/FBM PCI Express Root Port - 2664
PCI\VEN_8086&DEV_2668&SUBSYS_70281462&REV_03\3&11583659&0&D8: Microsoft UAA Bus Driver for High Definition Audio
PCI\VEN_8086&DEV_266A&SUBSYS_70281462&REV_03\3&11583659&0&FB: Intel(R) 82801FB/FBM SMBus Controller - 266A
PCI\VEN_8086&DEV_266F&SUBSYS_70281462&REV_03\3&11583659&0&F9: Intel(R) 82801FB/FBM Ultra ATA Storage Controllers - 266F
18 matching device(s) found.
 
 
=========== 
USB devices 
=========== 
 
USB\ROOT_HUB\4&1CFA0043&0                                   : USB Root Hub
USB\ROOT_HUB\4&1F1AA1E6&0                                   : USB Root Hub
USB\ROOT_HUB\4&31EF7094&0                                   : USB Root Hub
USB\ROOT_HUB\4&78AB7D0&0                                    : USB Root Hub
USB\ROOT_HUB20\4&F31A718&0                                  : USB Root Hub
USB\VID_046D&PID_C216\5&29DB93E5&0&2                        : Logitech Dual Action USB
USB\VID_0471&PID_0815\PH00HDWX                              : eHome Infrared Receiver
USB\VID_2040&PID_2900\5&E0FD799&0&4                         : Hauppauge WinTV PVR2 USB2 Encoder
8 matching device(s) found.

BASELOG

2006-05-30 15:46:02 : <INIT> DriverPacks BASE 6.05.2 initialized.
2006-05-30 15:46:02 : <INIT> Detected settings file.
2006-05-30 15:46:02 : <INIT> Imported settings from settings file.
2006-05-30 15:46:02 : <INIT> Detected Windows XP Professional SP2 in C:\XPCD.
2006-05-30 15:46:02 : <INIT> Detected DriverPack Chipset 6.05!
2006-05-30 15:46:02 : <INIT> Detected DriverPack CPU 6.03!
2006-05-30 15:46:02 : <INIT> Detected DriverPack Graphics A 6.03!
2006-05-30 15:46:02 : <INIT> Detected DriverPack Graphics B 6.03!
2006-05-30 15:46:02 : <INIT> Detected DriverPack Graphics C 6.03!
2006-05-30 15:46:02 : <INIT> Detected DriverPack LAN 6.05!
2006-05-30 15:46:02 : <INIT> Detected DriverPack MassStorage 6.03.1!
2006-05-30 15:46:02 : <INIT> Detected DriverPack Sound A 6.03!
2006-05-30 15:46:02 : <INIT> Detected DriverPack Sound B 6.03!
2006-05-30 15:46:02 : <INIT> Detected DriverPack WLAN 6.05!
2006-05-30 15:46:02 : <INIT> Detected 3rd party DriverPack(s).
2006-05-30 15:46:02 : <INIT> DriverPacks scanned sucessfully.
2006-05-30 15:46:02 : <GUI>  Initialized GUI.
2006-05-30 15:46:51 : <GUI>  Saved settings!
2006-05-30 15:46:51 : <GUI>  Closed GUI.
2006-05-30 15:46:51 : <SEL>  Selected module: mod_wxp_x86-32_disc_m2.
2006-05-30 15:46:53 : <PREP> Removed all attributes from \I386.
2006-05-30 15:46:53 : <PREP> Deleted old DriverPacks.
2006-05-30 15:46:53 : <PREP> Deleted old method 2 related files.
2006-05-30 15:46:53 : <PREP> Restored original mass storage text mode driver adpu160m.sys.
2006-05-30 15:46:53 : <PREP> Restored original mass storage text mode driver aliide.sys.
2006-05-30 15:46:53 : <PREP> Restored original mass storage text mode driver dac2w2k.sys.
2006-05-30 15:46:53 : <PREP> Restored original mass storage text mode driver dac960nt.sys.
2006-05-30 15:46:53 : <PREP> Restored original mass storage text mode driver dpti2o.sys.
2006-05-30 15:46:53 : <PREP> Restored original mass storage text mode driver mraid35x.sys.
2006-05-30 15:46:53 : <PREP> Restored original mass storage text mode driver ql12160.sys.
2006-05-30 15:46:53 : <PREP> Restored original mass storage text mode driver ultra.sys.
2006-05-30 15:46:53 : <PREP> Deleted old DriverPack MassStorage text mode drivers.
2006-05-30 15:46:53 : <PREP> Restored \I386\winnt.sif.
2006-05-30 15:46:53 : <PREP> Restored \I386\txtsetup.sif.
2006-05-30 15:46:53 : <PREP> Restored \I386\dosnet.inf.
2006-05-30 15:46:53 : <PREP> Restored original setup: method 2 was used previously.
2006-05-30 15:46:54 : <PREP> Cleaned up \$OEM$\cmdlines.txt.
2006-05-30 15:46:54 : <PREP> Created temporary working directory.
2006-05-30 15:46:54 : <SLIP> Extracted necessary files for method 2.
2006-05-30 15:46:54 : <SLIP> Created necessary directory structure for method 2.
2006-05-30 15:46:54 : <SLIP> Copied files necessary for method 2.
2006-05-30 15:47:01 : <SLIP> Copied DriverPacks to \OEM.
2006-05-30 15:47:01 : <SLIP> English UpdatePack detected: no HDA hotfix will be slipstreamed.
2006-05-30 15:47:01 : <SLIP> QuickStream Cache available for DriverPack MassStorage text mode drivers!
2006-05-30 15:47:02 : <SLIP> Slipstreamed DP MassStorage text mode drivers using QuickStream Cache.
2006-05-30 15:47:13 : <SLIP> Removed entries from \I386\txtsetup.sif that will be updated.
2006-05-30 15:47:15 : <SLIP> Removed entries from \I386\dosnet.inf that will be updated.
2006-05-30 15:48:46 : <SLIP> Updated \I386\dosnet.inf and \I386\txtsetup.sif to support DP MassStorage text mode drivers.
2006-05-30 15:48:47 : <SLIP> Deleted old presetup.cmd file from \I386.
2006-05-30 15:48:47 : <SLIP> Created \I386\presetup.cmd file.
2006-05-30 15:48:47 : <SLIP> Updated \I386\txtsetup.sif to support method 2.
2006-05-30 15:48:48 : <SLIP> Updated \I386\dosnet.inf to support method 2.
2006-05-30 15:48:48 : <SLIP> Updated \I386\winnt.sif to support method 2.
2006-05-30 15:48:48 : <SLIP> Slipstream finished in 2 minutes and 2 seconds.
2006-05-30 15:49:03 : <CLNP> Temporary working directory successfully deleted.
2006-05-30 15:49:03 : Program terminated.

I tried a CLEAN slipstream with the above issue. This log is from a second slipstream on top of the first.

Just to clarify (because you closed previous topic related to this while I was replying smile ), dps_fnsh.cmd error still present in 6052.

Will be fixed in 6053, along with sfx overwriting bin and doc? Correct?

So did you fix in 6052? Because it still looks the same!  lol

:KTD_M2
SET tagfile=\OEM\bin
FOR %%i IN (c d e f g h i j k l m n o p q r s t u v w x y z) DO IF EXIST "%%i:%tagfile%" SET CDDRIVE=%%i:
IF %CDDRIVE%==: GOTO KTD_M1
IF EXIST %CDDRIVE%\OEM\bin\makePNF.exe (

IF %CDDRIVE%=NUL: GOTO KTD_M1  ? Does that make sense?

I was wondering about that line. I don't know much about batch, but is that line supposed to signify NUL?

Promix can just email me if he wants.

promix wrote:

se integran antes de pasar el windows por el nlite o despues.


Disculpen por no escribir en ingles.

Do you integrate before nliting or after? Sorry for not posting in english.

tongue

true bashrat...he doesn't know WHEN to apply DriverPacks.

Al momento antes de hacer ISO. Yo uso nlite, pero uso cdimage gui para hacer la ISO. no importa la manera de hacer la ISO. Tienes que integrar los driverpacks al momento antes hacer ISO.

DriverPacks se integran despues de todos. (nLite, integrator, hotfix...etc)

I have it too...oddly enough, it doesn't bother me. Kinda like it, all freaky like that. smile

Make sure you download the new 605 LAN and WLAN packs!

Put all of bashrat packs in DriverPacks directory and third party in 3rd party DriverPacks directory. Make sure all packs are named accordingly.

DP_MassStorage_wnt5_x86-32_6031.7z (example)

I'm guessing you have your driver packs in the wrong directory?

I'll post this in the bug tracker.

""D:\DriverPacksCP\bin\Fedit.exe" -add -create -f "C:\XPCD\I386\txtsetup.sif" -s "files.atiide" -| "pciidex.sys,4"" dialog box

I got this four times with different .sys.   and is that a -| (pipe symbol)?

1 for atiide:pciidex.sys
1 for atiide:atiide.sys
1 for aliide:pciidex.sys
1 for aliide:aliide.sys

M2, RUNONCEEX, KTD NO

Bâshrat the Sneaky wrote:

What does that have to do with the F6 feature? roll

twig123 wrote:

Well for instance, I've posted about the SIS964 SATA/RAID chipset in the past, it will BSoD for some reason with your pack, But if it is used from F6 it works without a hitch...... strange huh. I sent the 'correct' drivers b4, but we found out that they were the exact same one that was included..... so, i'm lost. But, I guess this wouldn't be needed if we could figure out what is causing the BSoD issues with this particular chipset.

I think using textmode 'as is' causes a BSOD. So he needs to use F6 instead. I had the same problem. However, after REMing all drivers, one by one, I found that JMicron (JAHCI) was causing an issue with intel sata raid. I posted the driver entries so that someone with this issue could try experimenting with suppressing the loading of drivers. smile

These are the lines added to txtsetup.sif in the [SCSI.LOAD] section:

3ware9k=3ware9k.sys,4
3ware78k=3ware78k.sys,4
3waregsm=3waregsm.sys,4
aec6210=aec6210.sys,4
aec6260=aec6260.sys,4
aec6280=aec6280.sys,4
aec68x5=aec68x5.sys,4
aec6880=aec6880.sys,4
aec6897=aec6897.sys,4
aec67160=aec67160.sys,4
aec671x=aec671x.sys,4
ahpt3xx=ahpt3xx.sys,4
aac=aac.sys,4
aar1210=aar1210.sys,4
dpti2o=dpti2o.sys,4
adpu160m=adpu160m.sys,4
adpu320=adpu320.sys,4
aadpu320=aadpu320.sys,4
a320raid=a320raid.sys,4
cda1000=cda1000.sys,4
aarich=aarich.sys,4
amdbusdr=amdbusdr.sys,4
arcm_x86=arcm_x86.sys,4
m5228=m5228.sys,4
m5281=m5281.sys,4
m5287=m5287.sys,4
m5288=m5288.sys,4
m5289=m5289.sys,4
cercsr6=cercsr6.sys,4
hpt3xx=hpt3xx.sys,4
rhpt3xx=rhpt3xx.sys,4
hpt374=hpt374.sys,4
hptmv=hptmv.sys,4
hpt366=hpt366.sys,4
hptmv6=hptmv6.sys,4
rr2320=rr2320.sys,4
rr404=rr404.sys,4
rr2310=rr2310.sys,4
ipsraidn=ipsraidn.sys,4
nfrd960=nfrd960.sys,4
iastor=iastor.sys,4
raidsrc=raidsrc.sys,4
iteraid=iteraid.sys,4
;jahci=jahci.sys,4
megaide=megaide.sys,4
mraid35x=mraid35x.sys,4
dac2w2k=dac2w2k.sys,4
dac960nt=dac960nt.sys,4
symmpi=symmpi.sys,4
nvatabus=nvatabus.sys,4
nvraid=nvraid.sys,4
fasttrak=fasttrak.sys,4
fasttx2k=fasttx2k.sys,4
aftx2k=aftx2k.sys,4
s150sx8=s150sx8.sys,4
fastsx=fastsx.sys,4
sptrak=sptrak.sys,4
ulsata=ulsata.sys,4
ulsata2=ulsata2.sys,4
ultra=ultra.sys,4
ql2100=ql2100.sys,4
ql2200=ql2200.sys,4
ql2300=ql2300.sys,4
ql12160=ql12160.sys,4
pnp949r=pnp949r.sys,4
pnp680=pnp680.sys,4
pnp680r=pnp680r.sys,4
si3112=si3112.sys,4
si3112r=si3112r.sys,4
ati3112r=ati3112r.sys,4
si3114=si3114.sys,4
si3114r=si3114r.sys,4
si3114r5=si3114r5.sys,4
si3124=si3124.sys,4
si3124r=si3124r.sys,4
si3124r5=si3124r5.sys,4
si3132=si3132.sys,4
si3132r5=si3132r5.sys,4
sisraid1=sisraid1.sys,4
sisraid=sisraid.sys,4
sisraid2=sisraid2.sys,4
viamraid=viamraid.sys,4
viapdsk=viapdsk.sys,4
vmscsi=vmscsi.sys,4

If you notice, I keep JMicron from loading by putting a semi colon in front per Bashrat.

;jahci=jahci.sys,4

You can try putting semi colons down the list and try to find out which ones are conflicting. You can start with jahci  tongue

I had the same problem with Intel sata raid. However, my workaround involves the long, arduous, tedious, time consuming and back breaking task of REMing out JAHCI in SCSI.LOAD tongue    Seems that some drivers are incompatible with others.

<shrug>

Maybe you should try ridding JAHCI? or some other driver.   Go down the line.

lmao...leave it to bashrat to cause an international incident.

I run a small cleanup batch from runonceex to get rid of those.

Yes it should. And to clarify, it's back. So the previous link has no bearing. It's slightly different this time.

[Data]
Autopartition = 0
MsDosInitiated = 0
UnattendedInstall = "Yes"
    MsDosInitiated= No


LMAO!

Maybe you should be looking for 0 and No and "No".

Again. tongue

WinDirSpace32K = 1403872
WinDirSpace64K = 1647104
WinDirSpace128K = 2190720
WinDirSpace256K = 3366656

; Customized by nLite - www.nliteos.com

atiide.sys,4
aliide.sys,4



See...but now it's two entries, instead of four.

nlited BEFORE driverpack
mce
M2
Custom
No KTD