erik_demon

Link is working again

Yeah, I can confirm that the link is down

Yes you can slim down the size of yor DVD Check here

PERFECT, GOOD JOB Although my approach will be a little different, I now know this method works. About the double .CAB file, I may have found something Look at this place in the registry: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup] There you will find: DriverCachePath = %SystemRoot%\Driver Cache It is binary code like this: SEE ATTACHMENT We can change this to DriverCachePath = %SystemRoot%\Driver Cache\i386 like this: SEE ATTACHMENT Maybe now we need only one .CAB file in the %SystemRoot%\Driver Cache\i386 folder EDIT: For some reason, the binary code looked wrong when I posted it with the code tag. You can now see the code in the attachment EDIT 2: @X-Savior: usb100m.cat = 100,,,,,,,44,3,3 Why do you copy a .cat file to system32\dllcache? driver_cache.zip

The last time I tried was with the 5.04 version of the BASE pack, and the MassStorage pack (same version) I tested this with VMware, and I had the same error as TowlieMatrix. The file however was present in the i386 folder. I sadly don't have any time to test it with the latest versions. I will test it soon (I think wednesday).

@ Bashrat I agree, if we should make everything one language, it should be Chinese (or Dutch, YEAH!! ). I believe, that with a few billon people this is biggest language there is. However my Chinese is a bit *rusty*

I noticed that as well The goal of this topic was to let windows identify drivers when you plug them in, and use them even when the OS is already installed. like for instance, you just bought a wireless card and you want to use it without doing a format. (I would like that because my wireless card sucks ). after reading Serialzs topic My intention are to do this: - use your method 2 to extract the DP's and set the DevicePath like you did in method 2 - Use Cabarc to create a .CAB file from the extracted DP files (I still like to use the first step because .7zip is much smaller than .CAB) - Copy the .CAB file to %systemroot%\Driver Cache\i386 Of course they DRVINDEX.INF has to be edited before this. This also makes sure that I don't have to edit txtsetup.sif, and dosnet.inf except for the .INF file which need to be in the i386 folder (or I create another .7Zip file with only inf files that need to be copied during presetup to the %systemroot%\INF folder) This seems to be MUCH easier than I thought (I know, you said so ) There however still is one problem: How can i modify DRVINDEX.INF to look into subfolder of the .CAB file?? If this isn't possible, I won't create a .CAB file. Is it possible then to point DRVINDEX.INF in the direction of the normal subfolder. For instance: %systemroot%\Driver Cache\i386\DP\W\enz? (I don't know a great deal of INF files. I am learning though)

@ Bashrat: If we want to add new drivers, does it matter if I use 1, or 100?? I don't think it matter, because you use the following for presetup.cmd presetup.cmd= 1,,,,,,,2,0,0 And presetup ofcourse has nothing to do with the Vanilla version of XP. EDIT: I found this interesting post today, It comes from this forum (it didn't show up with the search function .) It seems that this is a perfect way to A: install the drivers, B: let windows recognize the drivers when you plug an play a device: THNX. ALOT Serialzs (seems that I was getting very close aswell )

how does [ForceCopyDriverCabFiles] work? Does it tell setup to copy the file over the one from DRIVER.CAB? or does it tell setup to copy the file from the DRIVER.CAB over the on in the i386 folder? The one is DRIVER.CAB is much older than the on that u use now. EDIT: I also had this error: I install with winnt32.exe, and I know that DOSNET.INF playes an important role here. I think that you may be right @TowlieMatrix, eikman2k and other people who get the Aliide.sys error: Do you guys install by using either winnt.exe or winnt32.exe??

I do the same as SiMoNsAyS, even though I install from a second harddrive and I have plenty of space And if it solves languages problems for users that will be great. I voted yes for both.

This problem is fixed for me in DP base version V5.04.2 (I only tried with method 2)

Hey Bashrat, Your site referce to the wrong base pack: http://www.btsunattended.net/Downloads/BTS_DriverPacks_BASE_V5041.exe Should be: http://www.btsunattended.net/Downloads/BTS_DriverPacks_BASE_V5042.exe EDIT: Or am I to early with my comment EDIT2: This problem is now fixed

Then I really don't have a clue. I doubt it is because your windows is a german version because the pack works great with many languages. I checked the files that you posted but your dosnet.inf and txtsetup.sif seem to be just fine. Maybe a stupid question, but when you intergrade drivers with Nlite, does that work??

Sorry, stupid double post

What happens when you install without the DP MassStorage??

Yeah, this looks very promising, I can't wait to see the result EDIT: I found something a bit suprising, there are NO .inf files in Driver.cab or SP2.cab EDIT2: It seems like all .inf files are directly in the i386 folder, and they all get copied to the %systemroot%\inf folder by txtsetup.sif, this should mean that using the $$\Inf folder also works EDIT3: Okay, it seems that every file in the Driver.CAB and SP2.CAB file have a reference inside txtsetup.sif just some examples from both DRIVER.CAB and SP2.cab files: hpcjrrps.dll = 100,,,,,,,,3,3 hpwm535m.gpd = 1,,,,,,,,3,3 hpwm5con.ini = 1,,,,,,,,3,3 eplvcd00.dll = 1,,,,,,,,3,3 eplvcd00.ini = 1,,,,,,,,3,3 lxaacln4.out = 1,,,,,,,,3,3 epndde01.dat = 1,,,,,,,,3,3 epndde02.cfg = 1,,,,,,,,3,3 cn160.hlp = 1,,,,,,,,3,3 ir_begin.wav = 1,,,,,,,,3,3 atievxx.exe = 1,,,,,,,,3,3 kodak.jpg = 1,,,,,,,,3,3 ncss4406.icm = 1,,,,,,,,3,3 It seems like 3,3 tells setup to do *something* with the files in the .CAB file I think that this is very important (maybe also for installing drivers via the new made CAB file) does anyone know what it means?? ****, I can't wait till I have some time to help testing, I think we now are very close!! EDIT 4: It seem to be a bit different with .sys files: apmbatt.sys = 1,,,,,,,4,1,1 enum1394.sys = 1,,,,,,,,3,3,,1,4 cmdide.sys = 1,,,,,,3_,4,1,,,1,4 exabyte2.sys = 1,,,,,,,4,1 ndisip.sys = 100,,,,,,,4,1 rio8drv.sys = 1,,,,,,,4,0,0 riodrv.sys = 1,,,,,,,4,0,0 ql12160.sys = 1,,,,,,4_,4,1,,,1,4 But still also here there is pretty much the same Also I think that = 1,,,,,,4_,4,1,,,1,4 and = 1,,,,,,3_,4,1,,,1,4 is for Masstorage drivers, they also exist under [sCSI] EDIT 5: Yes, I seem to be write about the Masstorage drivers: abp480n5.sys = 1,,,,,,4_,4,1,,,1,4 amsint.sys = 1,,,,,,4_,4,1,,,1,4 aliide.sys = 1,,,,,,3_,4,1,,,1,4 These files are inside driver.cab Edit 6: these value are used by windows for the nvidia drivers: nv4_disp.dll = 100,,,,,,,,3,3 nv4_disp.inf = 100,,,,,,,20,0,0 nv4_mini.sys = 100,,,,,,,,3,3 nv4_disp.dll, and nv4_mini.sys are in SP2.CAB, and nv4_disp.inf is in the i386 folder It now seem that *added* drivers in .CAB files (I mean drivers that are not windows core driver, and are no part of the *originale* windows setup files) = 100,,,,,,,,3,3 for all their files, except the INF, it uses = 100,,,,,,,20,0,0 and is located in the i386 folder

Why do I only have one Now to get back to your question. There are two things that you need to do here. 1. You need to verify if most of the drivers aren't already in Bashrats pack. 2. You can rip all ohter drivers from the CD, and create your own 7-Zip file. for instance, I created my own pack: DriverPack_Erik_V502. After you created it, all you have to do, is to put it in the DriverPacks folder of your BASE pack, and start slipstreaming. I tested this with method 2, and it works great

@ celo I tried method 1 today, and I didn't get the error, Could you please give use some more info about what driver packs you use, and could you attach you RUN_ME.CMD ? I however do have this kind of errors (both with M1 and M2 and the V503* DP base): 'adpu160m.sy_' is not recognized as an internalor external command, operable program or batch file (see celo's screenshot) I found a fix in this topic, but I don't understand it. For some reason %C1% isn't used, so you have to fully type it out

@ celo, NO!! dont use it!! it will mess eveything up I ment to say: Re-make the base pack without using UpdateChecker_V5041

Problem solved Topic can be closed

everybody, DO NOT USE UpdateChecker_V5041!! For some reason it deletes all the files, and replaces them with the V504 files After said this, I can confirm that my two problems are solved. At first, it looked like it still didn't work, this was because I used UpdateChecker_V5041, and all the batch files where replaced with the ones from V504 $OEM$\$$\INF is now created and presetup.cmd and setuporg.exe are now added to dosnet.inf Great job EDIT: @celo Did you use UpdateChecker_V5041? If so Re-created the base pack, and try again.

Thanks Bashrat, You're the best

No, the folder isn't created EDIT: I found the problem: %INE% OEM\%D%_%M%*.7z ( ECHO _ DriverPack MassStorage NOT slipstreamed! GOTO Control_Panels ;some stuff :DriverPack_Chipset REM ### This is the work-around to get the Intel inf files in the $OEM$\$$ directory. ### GOTO DP_C_%ME% :DP_C_1 %INE% $OEM$\$1\DP\C GOTO Control_Panels ROBOCOPY $OEM$\$1\DP\C\I $OEM$\$$\INF *.inf /NS /NC /NFL /NDL /NP /NJH /NJS GOTO DP_C_done :DP_C_2 %INE% OEM\%D%_%C%*.7z GOTO Control_Panels OEM\bin\7za.exe x -y -bd OEM\%D%_%C%*.7z -aoa -o%TEMP%\%D%_%C%_TMP ROBOCOPY %TEMP%\%D%_%C%_TMP\DP\C\I $OEM$\$$\INF *.inf /NS /NC /NFL /NDL /NP /NJH /NJS RD /S /Q %TEMP%\%D%_%C%_TMP GOTO DP_C_done :DP_C_done ECHO. ECHO _ Intel Chipset .inf files copied to $OEM$\$$\INF... GOTO Control_Panels :Control_Panels Basicly this is the same problem that I had with setuporg.exe and presetup.cmd line not being copied to dosnet.inf Because DP MassStorage isn't used, it goes directly to the Control_panel part. The batch will never reach :DriverPack_Chipset this way

There is nothing wrong with that one, I confirmed that on to work The other link which is revering to the same problem as celo has is the problem EDIT 2: OEPS, I did indeed

That is GREAT news , I will try to experiment with INF files this weekend. ATM, I really know absolutly nothing about INF files , I think that I will pay Gosh's site a visit. EDIT: Is it really necessary to create a CAB file?? can't we just put the DP folders uncompressed in the "%Systemroot%\Windows\Driver Cache" folder? This worked for X-Savior (okay, he only did it with 2 files, but should that matter?), the only thing he didn't do was to make references in DRVINDEX.INF