can you test this one for us, please?
http://rapidshare.com/files/22957253/DP … nightly.7z
--------------------
-M-M
Update marvell Driver
replaced Ver= 11/14/2006,1.1.0.51 with marvell downloaded from intel 02/09/2007,1.2.0.24
(this version does not conflict with iastor)
[Marvell]
%mv61xxDesc%=mv61xx_Inst,PCI\VEN_11AB&DEV_6101
%mv61xxDesc%=mv61xx_Inst,PCI\VEN_11AB&DEV_6111
%mv61xxDesc%=mv61xx_Inst,PCI\VEN_11AB&DEV_6121
%mv61xxDesc%=mv61xx_Inst,PCI\VEN_11AB&DEV_6122
%mv61xxDesc%=mv61xx_Inst,PCI\VEN_11AB&DEV_6145
-M-M-O
old marvell DriverVer= 01/06/2006,1.0.0.3 Edited out HWID supported by newer version
Enabled for these three
PCI\VEN_11AB&DEV_6120
PCI\VEN_11AB&DEV_6140
VEN_11AB&DEV_6141
Massstorage INI update
removed a duplicate entry
[V-3] appeared twice
adjusted drivercount
edit to Highpoint [H-1] (reported by overflow, confirmed jtdoom)
a Fix for win2003, driver does not exist in XP. (also a Bart_PE fix)
Fixed (Muiz)
ATI (Siliconimage) 3112 driver
-\M\S\4 10/23/2006, 1.3.67.0
this is more important to YOU
Test
edit in Mass storage ini makes Silicon Image raid mode drivers load before Silicon Image NON-raid
---------
there are reports that this solved conflicts, which we all suspect is happening, (Bâshrat the Sneaky again mentions it in this topic)
---------
a last note (sorry, I must. We all learn to use search sooner or later.)
>> tut tut, you could have used search, and see posts about silicon, and then you would have seen this test version.
I first used NLITE 1.3 Final, including the latest sil3114r5 drivers.
After that I ran the latest Driverpack Base inlcuding ALL unmodified driverpacks.
Booted like a charm, seeing my raid5 drive as one piece instead of 4 different disks.
Regards,
The Toolman
muiz3 wrote:Any news on this Toolman?
If not close this one for now.Still busy with converting the batch (first a disection of the jumps, to see if it is chronologicaly the same as the AutoIt script, witch in turn is a beautifull piece of clever coding I must add to this ! )
But you may close this thread if it suites you...
No its no problem, i was just wondering.
]]>Any news on this Toolman?
If not close this one for now.
Still busy with converting the batch (first a disection of the jumps, to see if it is chronologicaly the same as the AutoIt script, witch in turn is a beautifull piece of clever coding I must add to this ! )
But you may close this thread if it suites you...
Hi toolman,
could you please post the finisher log?I've no idea wether Ruudboek or muiz have this old driverpack. (I haven't got a copy.)..
a link to the asus supplied floppy for your motherboard could be handy.
Found the log:
2007-01-29 21:46:46 : <INIT> DriverPacks Finisher 7.01.5 initialized.
2007-01-29 21:46:46 : <INIT> Splash screen initialized.
2007-01-29 21:46:46 : <INIT> Detected platform wnt5_x86-32.
2007-01-29 21:46:46 : <DBG> Start logging of constants used in this program:
2007-01-29 21:46:46 : <DBG> $_DEBUG: True
2007-01-29 21:46:46 : <DBG> $_DPSTMP: C:\tmp
2007-01-29 21:46:46 : <DBG> $_LOGFILE: C:\WINDOWS\DPsFnshr.log
2007-01-29 21:46:46 : <DBG> $_NF: not found
2007-01-29 21:46:46 : <DBG> $_SETTINGSFILE: C:\DPsFnshr.ini
2007-01-29 21:46:46 : <DBG> $_SPLASHSCREEN: True
2007-01-29 21:46:46 : <INIT> Start logging of system variables available for use by the exceptions:
2007-01-29 21:46:46 : <INIT> %finisherdir% = C:
2007-01-29 21:46:46 : <INIT> %systemdrive% = C:
2007-01-29 21:46:46 : <INIT> %systemroot% = C:\WINDOWS
2007-01-29 21:46:46 : <INIT> %windir% = C:\WINDOWS
2007-01-29 21:46:46 : <INIT> %programfiles% = C:\Program Files
2007-01-29 21:46:46 : <INIT> %dpsroot% =
2007-01-29 21:46:46 : <INIT> %dpstmp% = C:\tmp
2007-01-29 21:46:46 : <INIT> Start logging of the HWIDs for relevant devices present in this system.
2007-01-29 21:46:46 : <INIT> 1. ACPI devices
ACPI\ATK0110\1010110 : ATK0110 ACPI UTILITY
ACPI\AUTHENTICAMD_-_X86_FAMILY_15_MODEL_43\_0 : AMD Athlon(tm) 64 X2 Dual Core Processor 3800+
ACPI\AUTHENTICAMD_-_X86_FAMILY_15_MODEL_43\_1 : AMD Athlon(tm) 64 X2 Dual Core Processor 3800+
ACPI\FIXEDBUTTON\2&DABA3FF&0 : ACPI Fixed Feature Button
ACPI\PNP0000\3&2411E6FE&0 : Programmable interrupt controller
ACPI\PNP0100\3&2411E6FE&0 : System timer
ACPI\PNP0200\3&2411E6FE&0 : Direct memory access controller
ACPI\PNP0303\3&2411E6FE&0 : Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
ACPI\PNP0401\1 : ECP Printer Port (LPT1)
ACPI\PNP0501\1 : Communications Port (COM1)
ACPI\PNP0700\3&2411E6FE&0 : Standard floppy disk controller
ACPI\PNP0800\3&2411E6FE&0 : System speaker
ACPI\PNP0A08\1 : PCI bus
ACPI\PNP0B00\3&2411E6FE&0 : System CMOS/real time clock
ACPI\PNP0C01\2&DABA3FF&0 : System board
ACPI\PNP0C02\1 : Motherboard resources
ACPI\PNP0C02\4 : Motherboard resources
ACPI\PNP0C02\5 : Motherboard resources
ACPI\PNP0C04\3&2411E6FE&0 : Numeric data processor
ACPI\PNP0C0B\2&DABA3FF&0 : ACPI Fan
ACPI\PNP0C0C\2&DABA3FF&0 : ACPI Power Button
ACPI\PNPB006\3&2411E6FE&0 : NVIDIA(R) nForce(TM) MIDI UART
ACPI\PNPB02F\3&2411E6FE&0 : Standard Game Port
ACPI\THERMALZONE\THRM : ACPI Thermal Zone
ACPI_HAL\PNP0C08\0 : Microsoft ACPI-Compliant System
ROOT\ACPI_HAL\0000 : ACPI Multiprocessor PC
26 matching device(s) found.
2007-01-29 21:46:46 : <INIT> 2. PCI devices
PCI\VEN_1022&DEV_1100&SUBSYS_00000000&REV_00\3&2411E6FE&0&C0: PCI standard host CPU bridge
PCI\VEN_1022&DEV_1101&SUBSYS_00000000&REV_00\3&2411E6FE&0&C1: PCI standard host CPU bridge
PCI\VEN_1022&DEV_1102&SUBSYS_00000000&REV_00\3&2411E6FE&0&C2: PCI standard host CPU bridge
PCI\VEN_1022&DEV_1103&SUBSYS_00000000&REV_00\3&2411E6FE&0&C3: PCI standard host CPU bridge
PCI\VEN_104C&DEV_8023&SUBSYS_808B1043&REV_00\4&13699180&0&5848: Texas Instruments OHCI Compliant IEEE 1394 Host Controller
PCI\VEN_1095&DEV_3114&SUBSYS_81671043&REV_02\4&13699180&0&5048: Silicon Image SiI 3114 SoftRaid 5 Controller
PCI\VEN_10DE&DEV_0050&SUBSYS_00000000&REV_A3\3&2411E6FE&0&08: PCI standard ISA bridge
PCI\VEN_10DE&DEV_0052&SUBSYS_815A1043&REV_A2\3&2411E6FE&0&09: NVIDIA nForce PCI System Management
PCI\VEN_10DE&DEV_0053&SUBSYS_815A1043&REV_F2\3&2411E6FE&0&30: NVIDIA nForce4 Parallel ATA Controller
PCI\VEN_10DE&DEV_0054&SUBSYS_815A1043&REV_F3\3&2411E6FE&0&38: NVIDIA nForce4 Serial ATA Controller
PCI\VEN_10DE&DEV_0055&SUBSYS_815A1043&REV_F3\3&2411E6FE&0&40: NVIDIA nForce4 Serial ATA Controller
PCI\VEN_10DE&DEV_0059&SUBSYS_812A1043&REV_A2\3&2411E6FE&0&20: Realtek AC'97 Audio
PCI\VEN_10DE&DEV_005A&SUBSYS_815A1043&REV_A2\3&2411E6FE&0&10: Standard OpenHCD USB Host Controller
PCI\VEN_10DE&DEV_005B&SUBSYS_815A1043&REV_A3\3&2411E6FE&0&11: Standard Enhanced PCI to USB Host Controller
PCI\VEN_10DE&DEV_005C&SUBSYS_00000000&REV_A2\3&2411E6FE&0&48: PCI standard PCI-to-PCI bridge
PCI\VEN_10DE&DEV_005D&SUBSYS_00000000&REV_A3\3&2411E6FE&0&58: nForce4 PCI-Express Root Port
PCI\VEN_10DE&DEV_005D&SUBSYS_00000000&REV_A3\3&2411E6FE&0&60: nForce4 PCI-Express Root Port
PCI\VEN_10DE&DEV_005D&SUBSYS_00000000&REV_A3\3&2411E6FE&0&68: nForce4 PCI-Express Root Port
PCI\VEN_10DE&DEV_005D&SUBSYS_00000000&REV_A3\3&2411E6FE&0&70: nForce4 PCI-Express Root Port
PCI\VEN_10DE&DEV_005E&SUBSYS_815A1043&REV_A3\3&2411E6FE&0&00: nForce4 HyperTransport Bridge
PCI\VEN_10DE&DEV_0092&SUBSYS_21821682&REV_A1\4&243D7BD0&0&0070: NVIDIA GeForce 7800 GT
PCI\VEN_1102&DEV_0004&SUBSYS_10021102&REV_04\4&13699180&0&3848: Creative SB Audigy 2 (WDM)
PCI\VEN_1102&DEV_4001&SUBSYS_00101102&REV_04\4&13699180&0&3A48: OHCI Compliant IEEE 1394 Host Controller
PCI\VEN_1102&DEV_7003&SUBSYS_00601102&REV_04\4&13699180&0&3948: Creative Game Port
PCI\VEN_11AB&DEV_4320&SUBSYS_811A1043&REV_13\4&13699180&0&6048: Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller
25 matching device(s) found.Which part of the log do you want also, because the file is 239Kb big, and can't be posted here (site limit 64Kb on postings)
]]>Hi toolman,
could you please post the finisher log?I've no idea wether Ruudboek or muiz have this old driverpack. (I haven't got a copy.)..
a link to the asus supplied floppy for your motherboard could be handy.
It's not on the drive I installed my unattended ... where would it be ?
The driverpack 5.0.5.4 I still have, where can I post it ?
Regards,
Toolman
ps.: The sourcecode for the finisher I've already ripped (very easy to do I must say), so it will not be a problem to change the code to work with massstorage driverpack 5.0.5.4. (I think, because I still have the .bat files to see what I have to change...).
]]>ps.: Asus has never had any separate motherboard firmware update for the sil3114 chipset ... and they never will have any ...
ps2.: Can I use massstorage driverpack 5.0.5.4 with the newest driverpack base or do I have to rebuild/rename anything inside the archive to use it ?
no seperate sata bios? put it in your self.
And no, you cant use 5.0.5.4.
]]>I've no idea wether Ruudboek or muiz have this old driverpack. (I haven't got a copy.)..
a link to the asus supplied floppy for your motherboard could be handy.
Running on my Asus A8N-SLI Premium with latest firmware, 1013 beta, it's still a no go with Massstorage driverpack version 7.0.1.5 ...
Massstorage driverpack 5.0.5.4 still does the job perfectly right !!!
Regards,
Toolman
ps.: Asus has never had any separate motherboard firmware update for the sil3114 chipset ... and they never will have any ...
ps2.: Can I use massstorage driverpack 5.0.5.4 with the newest driverpack base or do I have to rebuild/rename anything inside the archive to use it ?
ps3: After the setup of Windows XP Professional, the raid 5 array is recognized correctly, so only the textmode-drivers are faulty ...
]]>