mark49

1.my friend told me there r NO different betwen [sourceDisksFiles] and [sourceDisksFiles.x86] for nearly allmost system. I think maybe MS will use new string (maybe [sourceDisksFiles.x64] ) for 64bit system. 2.I'm sure there'r two ultra.sys entry. Anyone else has the same problem?

@erik_demon, thank u very much. and RunOnceEx works at T13 procedure ,also after device scanning and installing. it can also have the same effect with M1/M2 ? i want to slipstream 3rd drivers and want to install xp normally(attened) too.

the version of viaidexp is already in pic . it's 5.1.2600.120 by VIA about ulsata.sys i don't . that's a frined's PC.but i ask for it.

thanks erik_demon your doc is useful for me .and i've othe Q in that topic.

this method must use winnt.sif/unattach..txt ? i want to add 3rd drivers but also want to boot from CD and go into Console to do something such as /fixmbr /fixboot . another Q: in mydriver.CBA ,can i use subfolder ?

after patch txtsetup.sif,i found two ultra.sys entries . one for [sourceDisksFiles] and other for [sourceDisksFiles.x86] .which one is right?

@BTS, DP 50412, in dosnet.inf line 197 and 645 there r dupli- [files] , such d1,hdaudres.dll ..... r duplicated. and in [ForceCopyDriverCabFiles], portcls.sys ultra.sys ql12160.sys mraid35x.sys hpt3xx.sys dpti2o.sys dac960nt.sys dac2w2k.sys aliide.sys adpu160m.sys be deleted . i'm comfused this entries need or no need?

i think should be : PCI\VEN_105A&DEV_3375 = "ulsata" because in [sCSI] ,he use ULSATA as entry

3

ids and driver files

k8vse-d 1

sorry for replay here ,i've a Q : can we use MS's CAB to slipstreaming the driver (not need to especiall install .cpl )? like driver.cab ,we pack driver to DP.CAB and add the DP.CAB's entry to txtsetup.sif and dosnet.inf, then when setup system will look up driver in DP.CAB as driver.cab . this method is avalibale ?

$OEM$\$1\DP\S\V\CRLDS3D.DLL $OEM$\$1\DP\S\V\ENVYSENS.SYS this 2 files r not included in ori VIA driver packs . ?

ehmm

@BTS, i don't add entry to txtsetup and dosnet.sif ,but only add siside.sys/sis.inf files into DP\M and add reasch route to winnt.sif . then it's OK . my moard is K7S5A (should sis730)

sorry post error

@BTS, maybe u miss Promise FastTrak 571/519/579 ?

@BTS, i found this , http://support.microsoft.com/kb/828930/en-us ,maby useful for u point is section for 5.4.15.0 or more higher version of Update.exe

@BTS, winnt.sif with and only copy SCSI/RAID/SATA driver file .sys to \i386 ,not use DP\ folder. then: 1. F6 load floppy driver is avaliable? 2. SRS drivers can be right loaded by GUI installaion? while some times i don't want to full automatic installation but need SRS kernal driver. Also need F6, can use Recovery Consule(boot from CDrom),can overwrite-install .

redo and it's indeed function! maybe last time i use old txtsetup.sif already modified by DB 5048 ,stead use a CLEAR orignal one. sorry EDIT: i use ori drvindex.inf from xp.sp2.pro.vol. ( language SC) ,DP 5049,and found such ultra.sys/ql12160.sys/aliide.sys.... not be del from drvindex.inf again ?

DP BASE 5049 txtsetup.sif i found no this string: aliide.sys = 1,,,,,,3_,4,1,,,1,4 and because of so i think and should be del anyways we need to ONLY add aliide.hw.ids to txtsetup,others no modify

new drivers released: 1. VIA Hyperion 4in1 4.56V 2. ATi Radeon IXP150/IXP200/IXP250/IXP300/XPRESS 200 SouthBridge 4/8/05 For Win2000/XP（2005年4/11 release） 3. IT8212F ATA133 RAID controller v1.7.2.0 interesting things: 2. ati driver contains a si3112r driver DriverVer=08/27/2004, 1.5.0.51 and add more HW ids! but Si3112r.sys is the same one from SI v1.0.0.51

Anythins is possible,any strange thing also possible...

A7V880 . 8237( ?8237R) 1st pic is instance device id 2nd is device id 3rd is matching id 4rd is compatibale id