Jump to content

Toolman

Member
  • Posts

    44
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Germany

Everything posted by Toolman

  1. Yes it is indeed supposed to be this way, you can of course select not to keep the drivers and the DPack will remove the folder.. ← Except that the Driverpacks will also be kept in the root (*.7z files), those sould be gone after setup, but are not removed ...
  2. Nope, it keeps de D-folder AND the *.7zips in the root of C: ...
  3. Another bug found: Using method 3, Guirunonce, keep drivers, keeps the driverpacks in the root of the systemdrive ...
  4. Tested method 3 - v5.05.2, GUI RunOnce, keep drivers: FLAWLESS !
  5. When will it be up again ? 20 minutes ago I started downloading the lot, but came half way ...
  6. Yep, I pressed G ...
  7. After setup and first login, it can't find c:\d\drivesignpolicy.exe ...
  8. Yes indeed, there are entry's with a quote (") in front, but not afterwards ... "D\xxxx;"D\xxxx; etcetera ..... (I removed a lot of them with search and replace on "D\ changing to D\)
  9. DOSNET.inf and TXTSETUP.sif are modified, the entrys exist, the files are non existent in the \i386 directory. I used Method 3 on an original WXPSP2 cd ...
  10. Method 3 problems... during Windows text setup part i'm getting error that following files are missing: hdaprop.dll hdashcut.exe hdaudbus.inf hdaudbus.sys hdaudio.inf hdaudio.sys hdaudres.dll KB888111 is not properly slipstreamed is my guess ... Maybe here it goes wrong: GOTO DP_S_%ME% REM ### To avoid that the Realtek ALC880 driver won't get installed (because it's HD audio), we have to add the necessary entry to the DOSNET.INF file. ### :DP_S_1 %INE% %DPDIR2%\S\R\HD GOTO Control_Panels GOTO KB888111 :DP_S_2 %INE% OEM\%D%_%SA%_V*.7z GOTO Control_Panels GOTO KB888111 :DP_S_3 GOTO DP_S_2 :KB888111 ROBOCOPY KB888111 I386 *.* /MOV %RS% > NUL SET T1=Fedit -add -create -f I386\DOSNET.INF -s ForceCopyDriverCabFiles %T1% portcls.sys SET T1=Fedit -add -create -f I386\DOSNET.INF -s Files %T1% d1,hdaprop.dll %T1% d1,hdashcut.exe %T1% d1,hdaudbus.inf %T1% d1,hdaudbus.sys %T1% d1,hdaudio.inf %T1% d1,hdaudio.sys %T1% d1,hdaudres.dll SET T1=Fedit -add -create -f I386\TXTSETUP.SIF -s SourceDisksFiles %T1% "hdaprop.dll = 100,,,,,,,2,0,0" %T1% "hdashcut.exe = 100,,,,,,,2,0,0" %T1% "hdaudbus.inf = 100,,,,,,,20,0,0" %T1% "hdaudbus.sys = 100,,,,,,,4,0,0" %T1% "hdaudio.inf = 100,,,,,,,20,0,0" %T1% "hdaudio.sys = 100,,,,,,,4,0,0" %T1% "hdaudres.dll = 100,,,,,,,2,0,0" ECHO. ECHO _ KB888111 slipstreamed... GOTO Control_Panels
  11. There is still a bug, I placed a WINNT.SIF of my one, and now OEMpath is filled in, before (no winnt.sif there) it didn't make an entry OEMPath using Method 3 ...
  12. Oeps, now I did, and my winnt.sif does now look like this: ;Generated by Bashrat the Sneaky's DriverPacks BASE [Data] MsDosInitiated = "No" [Unattended] NonDriverSigningPolicy = "Ignore" DriverSigningPolicy = "Ignore" OemPreinstall = "Yes" [GUIUnattended] DetachedProgram = "CMD /C %SystemDrive%\D\BTS_DPs_M3.cmd" [GUIRunOnce] command9 = "%SystemDrive%\D\BTS_DPs_finish.cmd" Would this be oke ? I've not tested it yet ...
  13. My WINNT.SIF looks like this after using methode 3: ;Generated by Bashrat the Sneaky's DriverPacks BASE It was non existing and now it's empty ... :-(
  14. I've tested methode 1 and 2 and I will use methode 2 in future ... With methode 1 not all devices are detected / installed ...
  15. Thanks for the tips. I will try this and report back ! Edit: Your solution does the job ... Next problem is that the setup BSOD when installing the Realtec ac'97 onboard soundcard drivers ... (See also: Realtec ac'97 )
  16. I'm using version 5.04.4 basepack and all the driverpacks. Methode used: 2 WXP + SP2 + Hotfixes. Still getting the following error (It never has worked for me, by the way, I tried all versions of the driverpacks) : After the text part of the setup, rebooting: Fatal Error: Internal Setup data structures are corrupted (phase 0) Initial I had no winnt.sif, after running the driverpack I got a winnt.sif inside i386 ... Is this file really needed to get those driverpacks working ??? Do I have to have a winnt.sif, before I integrate the driverpacks ?
  17. I'm sorry to disappoint you, but the problems with your MassStorage DriverPack are still there or sneaked in again ... with both methodes ... I'm using WXP Professional+SP1+slipstreamed SP2+all of your driver packs... Versions: DP Base 5.03.2 DP Graphics A 5.02.1 DP Graphics B 5.02 DP LAN 5.02 DP MassStorage 5.03 DP Sound A 5.03.1 DP Sound B 5.03 DP WLAN 5.02 Used it on a IBM 8183 ...
×
×
  • Create New...