hehe, you´re right - in future I will :-)
btw.: I think we can close this thread now
thx Juku
1 2006-08-15 19:57:20
Re: [SOLVED] Problems with 6.08.2 and RunOnceEx Session (8 replies, posted in Feedback and Support - DriverPacks Base)
2 2006-08-15 07:47:11
Re: [SOLVED] Problems with 6.08.2 and RunOnceEx Session (8 replies, posted in Feedback and Support - DriverPacks Base)
okay, was definitely my fault!
It seems my cleanup.cmd messed up the whole thin, because without it, nearby all works fine.
nearby, because I found something wrong in the logfile.
Some exceptions and it tells me it couldnt delete the C:\D folder.
heres the DPsFinishr - log file anyway:
2006-08-14 21:12:30 : <INIT> DriverPacks Finisher 6.08.2 initialized.
2006-08-14 21:12:30 : <INIT> Detected platform wnt5_x86-32.
2006-08-14 21:12:30 : <INIT> Start logging of the HWIDs for relevant devices present in this system.
2006-08-14 21:12:30 : <INIT> 1. ACPI devices
ACPI\AUTHENTICAMD_-_X86_FAMILY_6_MODEL_10\_0 : AMD Athlon(tm) XP 2500+
ACPI\FIXEDBUTTON\2&DABA3FF&0 : ACPI-Schalter
ACPI\PNP0001\4&5289E18&0 : Programmierbarer EISA-Interruptcontroller
ACPI\PNP0100\4&5289E18&0 : Systemzeitgeber
ACPI\PNP0200\4&5289E18&0 : DMA-Controller
ACPI\PNP0303\4&5289E18&0 : Standardtastatur (101/102 Tasten) oder Microsoft Natural Keyboard (PS/2)
ACPI\PNP0400\5&324D5432&0 : Druckeranschluss (LPT1)
ACPI\PNP0501\1 : Kommunikationsanschluss (COM1)
ACPI\PNP0501\2 : Kommunikationsanschluss (COM2)
ACPI\PNP0700\5&324D5432&0 : Standard-Diskettenlaufwerkcontroller
ACPI\PNP0800\4&5289E18&0 : Systemlautsprecher
ACPI\PNP0A03\2&DABA3FF&0 : PCI-Bus
ACPI\PNP0A05\4&5289E18&0 : Standardbus
ACPI\PNP0B00\4&5289E18&0 : System CMOS/Echtzeituhr
ACPI\PNP0C02\1F : Hauptplatinenressourcen
ACPI\PNP0F13\4&5289E18&0 : PS/2-kompatible Maus
ACPI_HAL\PNP0C08\0 : Microsoft ACPI-konformes System
ROOT\ACPI_HAL\0000 : ACPI-Uniprozessor-PC
18 matching device(s) found.
2006-08-14 21:12:31 : <INIT> 2. PCI devices
PCI\VEN_1022&DEV_2000&SUBSYS_20001022&REV_10\3&61AAA01&0&80 : Ethernetadapter der AMD-PCNET-Familie
PCI\VEN_1274&DEV_1371&SUBSYS_13711274&REV_02\3&61AAA01&0&88 : Audiocontroller für Multimedia
PCI\VEN_15AD&DEV_0405&SUBSYS_040515AD&REV_00\3&61AAA01&0&78 : Videocontroller (VGA-kompatibel)
PCI\VEN_8086&DEV_7110&SUBSYS_00000000&REV_08\3&61AAA01&0&38 : Intel 82371AB/EB PCI-zu-ISA-Brücke (ISA-Modus)
PCI\VEN_8086&DEV_7111&SUBSYS_197615AD&REV_01\3&61AAA01&0&39 : Intel(R) 82371AB/EB PCI-Bus-Master-IDE-Controller
PCI\VEN_8086&DEV_7112&SUBSYS_197615AD&REV_00\3&61AAA01&0&3A : Intel(R) 82371AB/EB PCI-zu-USB universeller Hostcontroller
PCI\VEN_8086&DEV_7190&SUBSYS_00000000&REV_01\3&61AAA01&0&00 : Intel 82443BX Pentium(R) II Prozessor-zu-PCI-Brücke
PCI\VEN_8086&DEV_7191&SUBSYS_00000000&REV_01\3&61AAA01&0&08 : Intel 82443BX Pentium(R) II Prozessor-zu-AGP-Controller
8 matching device(s) found.
2006-08-14 21:12:31 : <INIT> 3. HDAUDIO devices
No matching devices found.
2006-08-14 21:12:31 : <INIT> 4. USB devices
USB\ROOT_HUB\4&3788CC09&0 : USB-Root-Hub
1 matching device(s) found.
2006-08-14 21:12:32 : <INIT> Logging of HWIDs complete.
2006-08-14 21:12:32 : <INIT> Processed settings.
2006-08-14 21:12:33 : <FLTR> Collected the HWIDs for this system.
2006-08-14 21:12:33 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0006__D-L-NV-123] (1 of 15 exceptions).
2006-08-14 21:12:33 : <FLTR> 2. +hwids (ANY +hwids must matched
2006-08-14 21:12:33 : <FLTR> ! Could not match any of the +hwids.
2006-08-14 21:12:33 : <FLTR> => This exception will not be applied.
2006-08-14 21:12:33 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0007__D-S-CR-1] (2 of 15 exceptions).
2006-08-14 21:12:33 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-14 21:12:33 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\ha20x2k.sys' (1 of 2 tagfiles).
2006-08-14 21:12:33 : <FLTR> => This exception will not be applied.
2006-08-14 21:12:33 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0008__D-S-CR-2] (3 of 15 exceptions).
2006-08-14 21:12:33 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-14 21:12:33 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\ha10x2k.sys' (1 of 3 tagfiles).
2006-08-14 21:12:33 : <FLTR> => This exception will not be applied.
2006-08-14 21:12:33 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0009__D-S-CR-3] (4 of 15 exceptions).
2006-08-14 21:12:33 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-14 21:12:33 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\P17.sys"' (1 of 2 tagfiles).
2006-08-14 21:12:33 : <FLTR> => This exception will not be applied.
2006-08-14 21:12:33 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0010__D-S-H-2] (5 of 15 exceptions).
2006-08-14 21:12:33 : <FLTR> 4. +infFiles (ANY +infFiles must matched
2006-08-14 21:12:33 : <FLTR> ! Could not match any of the +infFiles.
2006-08-14 21:12:33 : <FLTR> => This exception will not be applied.
2006-08-14 21:12:33 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0011__D-S-N] (6 of 15 exceptions).
2006-08-14 21:12:33 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-14 21:12:33 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\nvapu.sys' (1 of 1 tagfiles).
2006-08-14 21:12:33 : <FLTR> => This exception will not be applied.
2006-08-14 21:12:33 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0012__D-S-S-U] (7 of 15 exceptions).
2006-08-14 21:12:33 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-14 21:12:33 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\sthda.sys' (1 of 1 tagfiles).
2006-08-14 21:12:33 : <FLTR> => This exception will not be applied.
2006-08-14 21:12:33 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0013__D-S-SI-1] (8 of 15 exceptions).
2006-08-14 21:12:33 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-14 21:12:33 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\sis7012.sys' (1 of 1 tagfiles).
2006-08-14 21:12:33 : <FLTR> => This exception will not be applied.
2006-08-14 21:12:33 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0014__D-S-SI-2] (9 of 15 exceptions).
2006-08-14 21:12:33 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-14 21:12:33 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\sis7018.sys' (1 of 1 tagfiles).
2006-08-14 21:12:33 : <FLTR> => This exception will not be applied.
2006-08-14 21:12:33 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0015__D-S-T-2] (10 of 15 exceptions).
2006-08-14 21:12:33 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-14 21:12:33 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\FM801.sys' (1 of 1 tagfiles).
2006-08-14 21:12:33 : <FLTR> => This exception will not be applied.
2006-08-14 21:12:33 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0016__D-S-T-3] (11 of 15 exceptions).
2006-08-14 21:12:33 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-14 21:12:33 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\cmaudio.sys' (1 of 1 tagfiles).
2006-08-14 21:12:33 : <FLTR> => This exception will not be applied.
2006-08-14 21:12:33 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0017__D-S-T-4] (12 of 15 exceptions).
2006-08-14 21:12:33 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-14 21:12:33 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\TT1724ht.sys' (1 of 1 tagfiles).
2006-08-14 21:12:33 : <FLTR> => This exception will not be applied.
2006-08-14 21:12:33 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0018__D-S-T-5] (13 of 15 exceptions).
2006-08-14 21:12:33 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-14 21:12:33 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\dmxsens.sys' (1 of 1 tagfiles).
2006-08-14 21:12:33 : <FLTR> => This exception will not be applied.
2006-08-14 21:12:33 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0019__D-S-V-1] (14 of 15 exceptions).
2006-08-14 21:12:33 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-14 21:12:33 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\envysens.sys' (1 of 1 tagfiles).
2006-08-14 21:12:33 : <FLTR> => This exception will not be applied.
2006-08-14 21:12:33 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0020__D-S-V-2] (15 of 15 exceptions).
2006-08-14 21:12:33 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2006-08-14 21:12:33 : <FLTR> ! Could not find tagfile 'C:\WINDOWS\system32\drivers\vinyl97.sys' (1 of 2 tagfiles).
2006-08-14 21:12:33 : <FLTR> => This exception will not be applied.
2006-08-14 21:12:33 : <FLTR> Finished filtering exceptions.
2006-08-14 21:12:33 : <EXEC> No exceptions left to execute: none have met all requirements!
2006-08-14 21:13:10 : <ERR> Could not delete the DriverPacks, which are located in 'C:\D'.
2006-08-14 21:13:16 : <CLNP> Deleted 'C:\DPsFnshr.ini'!
2006-08-14 21:13:16 : <CLNP> Deleted 'C:\devcon.exe'!
2006-08-14 21:13:16 : <CLNP> Deleted 'C:\makePNF.exe'!
2006-08-14 21:13:16 : <CLNP> Deleted 'C:\addUsepmtimer.exe'!
2006-08-14 21:13:16 : <CLNP> Deleted 'C:\ATICCC.ins'!
2006-08-14 21:13:16 : <CLNP> Added new value to the RunOnce key in the registry: the DriverPacks Finisher itself will get deleted after the next reboot.
2006-08-14 21:13:16 : Program terminated.
But I think I should opeb another thread, should I?
thx,
Juku
3 2006-08-15 05:15:05
Re: [SOLVED] Problems with 6.08.2 and RunOnceEx Session (8 replies, posted in Feedback and Support - DriverPacks Base)
Bâshrat the Sneaky wrote:
Please post your DPsFnshr.ini and DPsFnshr.log!
ahm..ok..I need to alter my cleanup file and reinstall it again, cause your ini files were deleted too with my cleanup... :-o
4 2006-08-15 04:45:33
Re: [SOLVED] SiI 3112r controller doesnt work: 0x7B BSOD (102 replies, posted in DriverPack Mass Storage)
Ok, I give up!
I've tried nearby every bios with every driver I found on the web, but it resulted all in a BSOD :-(
My solution to this was to replace the SATA disk with a common PATA disk, which worked perfectly.
Anyway - thx to all for your help!
Juku
ps.: perhaps another find a solution for this? :-)
5 2006-08-15 04:39:51
Topic: [SOLVED] Problems with 6.08.2 and RunOnceEx Session (8 replies, posted in Feedback and Support - DriverPacks Base)
Hi,
I´ve made a fully unattended XP DVD using RunOnceEx to install further programs, which worked perfectly all versions before 6.8. (in the DriverPack options I always used RunOnceEx as finisher method with ID 59, which is between my last program I want to install and a batchfile where I make some Cleanup-operations)
I've changed nothing in it, but now, everytime the RunOnceEx Session starts, every Program which should be installed makes an error saying, their setupfiles are missing. Futhermore the Cleanupoperation which should be afterwards the driverpack stuff (has actually ID 65) starts before the Driverpack Finisher, which is now the last in the RunOnceEx Window.
Do I make something wrong or have you changed something between 6.7 and 6.8 reagrding the finisher method?
Juku
6 2006-08-14 05:16:40
Re: [SOLVED] SiI 3112r controller doesnt work: 0x7B BSOD (102 replies, posted in DriverPack Mass Storage)
OK :-) had the same thoughts, just wanted to be sure
7 2006-08-14 04:42:13
Re: [SOLVED] SiI 3112r controller doesnt work: 0x7B BSOD (102 replies, posted in DriverPack Mass Storage)
Bâshrat the Sneaky wrote:
The one on your installation disc, of course.
installation disc = my slipstreamed WinXp DVD?
or the SATA disc where my aborted XP Installation resides?
:-)
8 2006-08-14 03:54:54
Re: [SOLVED] SiI 3112r controller doesnt work: 0x7B BSOD (102 replies, posted in DriverPack Mass Storage)
Bâshrat the Sneaky wrote:
You don't have to look in any of those folders. When you have the 0x7B BSOD, it will never get that far. But I honestly do not understand why you get that BSOD... The only thing you can do is replacing the driver in the I386 folder (si3112r.sys) by an older one and retry, as you suggested.
Do you mean the i386 folder of my dvd or the one on my SATA disk. The one of my sata disk is nearby empty ;-( There are only two cab files. Do you mean I have to extract them, replace my drivers, compress them again and try it?
9 2006-08-14 03:30:32
Re: [SOLVED] SiI 3112r controller doesnt work: 0x7B BSOD (102 replies, posted in DriverPack Mass Storage)
Bâshrat the Sneaky wrote:
That is OF COURSE possible
Good luck with the testing.
P.S.: I double-checked and your HWID is supported, so that's not the problem.
thx for doublechecking it,
I now looked in the system32\driver directory to search for the sil3112 SATA drivers come with your package and funny thing is: there is only the windows standard driver and no others (Si3112r.sys is completely missing)
Strange isnt it?
Is it also possible to simply copy si3112r.sys in the driver and the inf file in the inf directory to make this driver work for installation or not?
I guess not, is there any other way to do that?
And what to do with those vxd and cpl files shipped with the sys and ini file for the driver?
I know many questions but it seems that this is the real problem - missing drivers, not in your package but on my SATA HD, where the files were copied, am I wrong?
juku
10 2006-08-14 02:56:31
Re: [SOLVED] SiI 3112r controller doesnt work: 0x7B BSOD (102 replies, posted in DriverPack Mass Storage)
Helmi wrote:
Hm, don't quite understand what you're planing to do but to verify whether a driver supports your hardware, you can simply have a look at the .INF file.
The HWIDs exctracted with Bâshrat the Sneaky's tool should be listed in the .INF if it is supported.
If they aren't listed, no drivers will get installed for the hardware.Granted, this may take some time if you do not know exactly which .INF file to look at, but ususally you can narrow it down if you know the hardware in question (ususally the case if it's your own system!
), so you can directly look at a specific file.
HTH!
thx for your response,
do I understand you correctly, that my hardware (in this case the sata driver, si3112.inf) mst be in the windows\inf directory? or have I to search all files for the hardwareID of tghe sata driver?
11 2006-08-14 00:20:21
Re: [SOLVED] SiI 3112r controller doesnt work: 0x7B BSOD (102 replies, posted in DriverPack Mass Storage)
Hope it´s not a too stupid question, but to verify which driver could work with my hardware, is it possible to do it faster than reinstall windows everytime with a new driver?
e.g.: all windows files are now on SATA disk to reboot to gui-mode of installation procedure. can I simply replace the 3112r.sys and all other drivers with the ones I want to test or is this impossible?
12 2006-08-13 22:27:15
Re: [SOLVED] SiI 3112r controller doesnt work: 0x7B BSOD (102 replies, posted in DriverPack Mass Storage)
:-) Ok, thx for this advice Helmi - I was wondering all the time what his signature was meaning...
So here it is:
===========
PCI devices
===========
PCI\A347SCSI\0000 : A347SCSI SCSI Controller
PCI\D347PRT\0000 : D347PRT SCSI Controller
PCI\VEN_1002&DEV_4150&SUBSYS_7C19174B&REV_00\4&102AC5BC&0&00F0: SAPPHIRE RADEON 9600 PRO ATLANTIS
PCI\VEN_1002&DEV_4170&SUBSYS_7C18174B&REV_00\4&102AC5BC&0&01F0: SAPPHIRE RADEON 9600 PRO ATLANTIS - Secondary
PCI\VEN_1095&DEV_3112&SUBSYS_61121095&REV_02\4&3B1D9AB8&0&5840: RAID-Controller
PCI\VEN_10B7&DEV_9201&SUBSYS_80AB1043&REV_40\4&35344E25&0&0860: 3Com 3C920B-EMB Integrated Fast Ethernet Controller
PCI\VEN_10DE&DEV_0060&SUBSYS_00000000&REV_A4\3&13C0B0C5&0&08: PCI Standard-ISA-Brücke
PCI\VEN_10DE&DEV_0064&SUBSYS_0C111043&REV_A2\3&13C0B0C5&0&09: NVIDIA nForce PCI System Management
PCI\VEN_10DE&DEV_0065&SUBSYS_0C111043&REV_A2\3&13C0B0C5&0&48: NVIDIA nForce2 ATA Controller (v2.6)
PCI\VEN_10DE&DEV_0066&SUBSYS_80A71043&REV_A1\3&13C0B0C5&0&20: NVIDIA nForce Networking Controller
PCI\VEN_10DE&DEV_0067&SUBSYS_0C111043&REV_A4\3&13C0B0C5&0&10: Standard OpenHCD USB-Hostcontroller
PCI\VEN_10DE&DEV_0067&SUBSYS_0C111043&REV_A4\3&13C0B0C5&0&11: Standard OpenHCD USB-Hostcontroller
PCI\VEN_10DE&DEV_0068&SUBSYS_0C111043&REV_A4\3&13C0B0C5&0&12: Standard erweiterter PCI-zu-USB universeller Hostcontroller
PCI\VEN_10DE&DEV_006A&SUBSYS_80951043&REV_A1\3&13C0B0C5&0&30: NVIDIA(R) nForce(TM) Audio Codec Interface
PCI\VEN_10DE&DEV_006B&SUBSYS_0C111043&REV_A2\3&13C0B0C5&0&28: NVIDIA(R) nForce(TM) MCP Audio Processing Unit
PCI\VEN_10DE&DEV_006C&SUBSYS_00000000&REV_A3\3&13C0B0C5&0&40: PCI Standard-PCI-zu-PCI-Brücke
PCI\VEN_10DE&DEV_006D&SUBSYS_00000000&REV_A3\3&13C0B0C5&0&60: PCI Standard-PCI-zu-PCI-Brücke
PCI\VEN_10DE&DEV_006E&SUBSYS_809A1043&REV_A3\3&13C0B0C5&0&68: OHCI-konformer IEEE 1394-Hostcontroller
PCI\VEN_10DE&DEV_01E0&SUBSYS_00000000&REV_C1\3&13C0B0C5&0&00: PCI Standard-Host-CPU-Brücke
PCI\VEN_10DE&DEV_01E8&SUBSYS_00000000&REV_C1\3&13C0B0C5&0&F0: NVIDIA nForce2 AGP Host to PCI Bridge
PCI\VEN_10DE&DEV_01EB&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&01: PCI-Speicher
PCI\VEN_10DE&DEV_01EC&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&04: PCI-Speicher
PCI\VEN_10DE&DEV_01ED&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&03: PCI-Speicher
PCI\VEN_10DE&DEV_01EE&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&02: PCI-Speicher
PCI\VEN_10DE&DEV_01EF&SUBSYS_80AC1043&REV_C1\3&13C0B0C5&0&05: PCI-Speicher
PCI\VEN_14F1&DEV_8800&SUBSYS_34010070&REV_03\4&3B1D9AB8&0&4040: Hauppauge WinTV 88x Video (+IR)
PCI\VEN_14F1&DEV_8811&SUBSYS_34010070&REV_03\4&3B1D9AB8&0&4140: Hauppauge WinTV 88x IR Decoder
27 matching device(s) found.
===========
USB devices
===========
USB\ROOT_HUB\4&36CE346&0 : USB-Root-Hub
USB\ROOT_HUB\4&37090E00&0 : USB-Root-Hub
USB\ROOT_HUB20\4&B74B78&0 : USB-Root-Hub
USB\VID_046D&PID_C03E\5&DF9F058&0&1 : USB-HID (Human Interface Device)
4 matching device(s) found.13 2006-08-13 22:17:58
Re: [SOLVED] SiI 3112r controller doesnt work: 0x7B BSOD (102 replies, posted in DriverPack Mass Storage)
Bâshrat the Sneaky wrote:
Everything seems to go right there... so that leaves me with only one choice: I need the HWID of your SiI 3112r controller, but the problem is that your installation doesn't start... If you have a spare PATA HDD, I'd suggest that you install Windows on that one, then get the HWID and then report it back. A lot of work, but I don't have a crystal ball either.
Ahm...I have another disk already running with winxp on the same machine. Is that adequate enought? Oh and from where can I extract the HWID?
Ohh and Bashrat: Thx!!
14 2006-08-13 21:57:54
Re: [SOLVED] SiI 3112r controller doesnt work: 0x7B BSOD (102 replies, posted in DriverPack Mass Storage)
Bâshrat the Sneaky wrote:
Are you using the latest DriverPack Sound B? Please post your DPs_BASE.log!
Wow - that was quick :-)
here it is:
2006-08-12 13:57:20 : <INIT> DriverPacks BASE 6.08.1 initialized.
2006-08-12 13:57:20 : <INIT> Host environment: WIN_XP Service Pack 1 on X86 CPU.
2006-08-12 13:57:20 : <INIT> Detected settings file "X:\Software\Treiber, Codecs & Patches\WinXP Stuff & Tuning\Tools\Slipstreaming\Hotfixes and Drivers\DriverPacks\DriverBase 6061\DPs_BASE.ini".
2006-08-12 13:57:20 : <INIT> The platform wnt5_x86-32_disc will be used (which is the 'disc' installation platform for the OS family 'wnt5_x86-32').
2006-08-12 13:57:20 : <INIT> Imported settings from settings file.
2006-08-12 13:57:20 : <INIT> Detected DriverPack Chipset 6.08!
2006-08-12 13:57:20 : <INIT> Detected DriverPack Graphics A 6.08!
2006-08-12 13:57:20 : <INIT> Detected DriverPack Graphics B 6.03!
2006-08-12 13:57:20 : <INIT> Detected DriverPack Graphics C 6.03!
2006-08-12 13:57:20 : <INIT> Detected DriverPack LAN 6.05.1!
2006-08-12 13:57:20 : <INIT> Detected DriverPack LAN 6.08!
2006-08-12 13:57:20 : <INIT> Detected DriverPack MassStorage 6.08!
2006-08-12 13:57:20 : <INIT> Detected DriverPack Sound A 6.06.1!
2006-08-12 13:57:20 : <INIT> Detected DriverPack Sound B 6.06!
2006-08-12 13:57:20 : <INIT> Detected DriverPack WLAN 6.05!
2006-08-12 13:57:20 : <INIT> Could not detect any 3rd party DriverPacks.
2006-08-12 13:57:20 : <INIT> DriverPacks scanned sucessfully.
2006-08-12 13:57:20 : <GUI> Initialized GUI.
2006-08-12 13:57:20 : <GUI> Created a list of all available language files.
2006-08-12 13:57:21 : <GUI> Set the last used language, English, as the GUI language.
2006-08-12 13:57:28 : <GUI> Refreshed UpdateChecker with success.
2006-08-12 13:57:38 : <GUI> Saved settings!
2006-08-12 13:57:38 : <GUI> Closed GUI.
2006-08-12 13:57:38 : <SEL> Selected module: mod_slip_wxp_x86-32_disc_m2.
2006-08-12 13:57:50 : <PREP> Removed all attributes from \I386.
2006-08-12 13:57:50 : <PREP> Deleted old DriverPacks.
2006-08-12 13:57:50 : <PREP> Deleted old method 2 related files.
2006-08-12 13:57:51 : <PREP> Restored original mass storage text mode driver adpu160m.sys.
2006-08-12 13:57:51 : <PREP> Restored original mass storage text mode driver ALIIDE.sys.
2006-08-12 13:57:51 : <PREP> Restored original mass storage text mode driver dac2w2k.sys.
2006-08-12 13:57:51 : <PREP> Restored original mass storage text mode driver dac960nt.sys.
2006-08-12 13:57:51 : <PREP> Restored original mass storage text mode driver dpti2o.sys.
2006-08-12 13:57:51 : <PREP> Restored original mass storage text mode driver hpt3xx.sys.
2006-08-12 13:57:51 : <PREP> Restored original mass storage text mode driver mraid35x.sys.
2006-08-12 13:57:51 : <PREP> Restored original mass storage text mode driver ql12160.sys.
2006-08-12 13:57:51 : <PREP> Restored original mass storage text mode driver ultra.sys.
2006-08-12 13:57:51 : <PREP> Deleted old DriverPack MassStorage text mode drivers.
2006-08-12 13:57:52 : <PREP> Cleaned up \I386\svcpack.inf.
2006-08-12 13:57:52 : <PREP> Unslipstreamed KB883667, KB888111, KB913425.
2006-08-12 13:57:52 : <PREP> Restored \I386\winnt.sif.
2006-08-12 13:57:52 : <PREP> Restored \I386\txtsetup.sif.
2006-08-12 13:57:52 : <PREP> Restored \I386\dosnet.inf.
2006-08-12 13:57:52 : <PREP> Restored original setup: method 2 was used previously.
2006-08-12 13:57:52 : <PREP> Cleaned up \$OEM$\cmdlines.txt.
2006-08-12 13:57:52 : <PREP> Created temporary working directory.
2006-08-12 13:57:52 : <SLIP> Extracted necessary files for method 2.
2006-08-12 13:57:52 : <SLIP> Created necessary directory structure for method 2.
2006-08-12 13:57:53 : <SLIP> Copied files necessary for method 2.
2006-08-12 13:58:08 : <SLIP> Copied DriverPacks to \OEM.
2006-08-12 13:58:08 : <SLIP> Extracted and deleted \I386\svcpack.in_.
2006-08-12 13:58:08 : <SLIP> Updated \I386\svcpack.inf file to support KB888111 and KB913425.
2006-08-12 13:58:09 : <SLIP> Updated \I386\txtsetup.sif file to support KB888111.
2006-08-12 13:58:10 : <SLIP> Updated \I386\dosnet.inf file to support KB888111.
2006-08-12 13:58:10 : <SLIP> Updated \I386\dosnet.inf file to support KB913425.
2006-08-12 13:58:13 : <SLIP> Extracted DriverPack MassStorage to a temporary working directory.
2006-08-12 13:58:29 : <SLIP> Created QuickStream Cache for DriverPack MassStorage text mode drivers.
2006-08-12 13:58:29 : <SLIP> Slipstreamed DP MassStorage text mode drivers using QuickStream Cache.
2006-08-12 13:58:33 : <SLIP> Removed entries from \I386\txtsetup.sif that will be updated.
2006-08-12 13:58:33 : <SLIP> Removed entries from \I386\dosnet.inf that will be updated.
2006-08-12 13:58:56 : <SLIP> Updated \I386\dosnet.inf and \I386\txtsetup.sif to support DP MassStorage text mode drivers.
2006-08-12 13:58:57 : <SLIP> Compressed setup.exe to SETUP.EX_.
2006-08-12 13:58:57 : <SLIP> Deleted old presetup.cmd file from \I386.
2006-08-12 13:58:57 : <SLIP> Created \I386\presetup.cmd file.
2006-08-12 13:58:57 : <SLIP> Updated \I386\txtsetup.sif to support method 2.
2006-08-12 13:58:57 : <SLIP> Updated \I386\dosnet.inf to support method 2.
2006-08-12 13:58:57 : <SLIP> Updated \I386\winnt.sif to support method 2.
2006-08-12 13:58:57 : <SLIP> Updated DPsFnshr.ini to disable KTD.
2006-08-12 13:58:57 : <SLIP> Updated \$OEM$\cmdlines.txt to execute ROE.exe.
2006-08-12 13:58:57 : <SLIP> Slipstream finished in 1 minutes and 19 seconds.
2006-08-12 13:59:12 : <CLNP> Temporary working directory successfully deleted.
2006-08-12 13:59:12 : Program terminated.15 2006-08-13 21:56:04
Re: [SOLVED] SiI 3112r controller doesnt work: 0x7B BSOD (102 replies, posted in DriverPack Mass Storage)
muniao wrote:
these driver can't simple integral
because when bios and setting is different, then the driver is different
when the bios setting is sata(not raid),si3112 maybe use "pciide" driver
I'm not sure if I understand you correctly. I know that a different SATA Bios version could need a new driver version. But as "muiz3" said: for the now in the driverpackage included drivers I need the latest SIL Bios, which is 4276. So this should work, because its exactly the bios I already have flashed on my computer.
what do you mean with with "bios and setting is different"? And why should si32212 use pciide, when SATA (not Raid) is activated in bios?
16 2006-08-13 21:45:40
Re: [SOLVED] SiI 3112r controller doesnt work: 0x7B BSOD (102 replies, posted in DriverPack Mass Storage)
well,
I've tried 5 different bios, the 1007, the 1008 orginal ones from asus, the modded version with the 4250er SATA SIL Version (which worked for most of the people and their SATA disks) and the lastest modded 1008r3 with the 4276er SATA Sil Version.
There was no difference, everytime I've tried, I got the same BSOD after the dosbased filecopy process of windows installation.
Funny thing: I also tried the original XP CD with slipstreamed SP2 in it, ut without driverpackages, and got the same bluescreen shortly after starting the installation, which tells me, your drivers are not as bad as I thought :-)
@your new driverpack: I slipstreamed the massstorage package and your new basedriver package, which worked without errors. But now an error occured during the filecopy process of the dosbased windows installer, saying newdev.dll can't be copied. Perhaps only an error in image creation? I will test it tomorrow....I´ve tried that 4 times, everytime it was the same dll.
17 2006-08-12 00:29:04
Re: [SOLVED] SiI 3112r controller doesnt work: 0x7B BSOD (102 replies, posted in DriverPack Mass Storage)
Hi folks!
Sorry to reopen this thread but I still have serious troubles with installing XP on a SATA disk with the actual driverpack. The Bluscreen 0x0000007B appears after the computer tries to start GUI Mode of Setup routine.
I have an ASUS A7n8x Deluxe rev. 2.0 board with 1008 Bios and SATA BIOS v4.2.47
I´ve tried all possible BIOS settings (switched to SATA, RAID, tried to set SCSI as first boot device and so on...) but it seems all senseless ;(
Its now the third day trying that, and im out of ideas by now.
Those are the procedures, I've tried by now:
1) Slipstreamed your original driverpacks MassStorage, Chipset, Lan, Sound and WLAN (did i understand that correctly that the corrected Sil drivers are already included?) -> BSOD
2) replaced drivers in folder 4 and 5 with the new SIl drivers, slipstreamed them -> BSOD
3) deleted directory 4 as well as 5A and replaced the driver in 5 with the original ASUS driver (which worked pretty fine all the last years when loaded from floppy disk. But at those times my bios was only 1006)
I´ve tried this, cause someone wrote only the 3112r driver is needed not the 3112 (makes sense, ASUS only put this driver on his cd)
Any way it failed to ;-( -> BSOD
4) I put the new SIl driver 3112r on floppy disk pressed F6 when asked for additional drivers, selected the correct driver but then Windows said there is an Error in the sysfile with Errorcode 4 (I've tried both, the Windows Xp and the Windows NT/2000 driver)
5) Meanwhile I´ve found a Microsoft Sil driver from Feb2006, tried to install it with F6, but the result was the same -> BSOD
[EDIT] I've switched now to a bios mod from trats whichs is a modified version of 1008 but with SIl version 4274. I tried all the above tings again -> still BSODs ;-(
Well and here I am now - I do not have any ideas what to do now
Have I forgotten something?
Is there something wrong replacing your drivers manually in your Massstorage driver pack?
I'm open for any suggestions
thx a lot
Jukuhullui