You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by TechDud
... "what i should do" ...
That first error is something i see sometimes when a read error occurs on a DVD+RW disc, as the DriverPacks are being unpacked.
If your disc can be read completely by a program such as CDCheck, then you might want to start from scratch with a clean source. 
Putting this "on the shelf" until i have access to a system that supports Win2k.
It is listed in "Known Issues", that is enough for now.
"i don't think the SAD script processes the ini files."
An install with the DP_Graphics_A package, and some 3rd-party Graphics expansion packs, such as DP_Graphics_ATi_Hydravision & OpenCL/VC2k10 showed that in at least the Graphics packs, the .Ini is actually processed. The lack of aticcc.ins causes many routines to be skipped though, unless aticcc.ins is manually and strategically placed. Logs have been retained for anybody that requests.
It would seem possible that using SAD3 to install MassStorage drivers could be a risky proposition though.
I would have considered simply disabling those libraries, yet needed to ensure that there are no negative consequences to those that install with supported hardware.
Whoops! That warning about AMD's USBFilter was a false alarm.
It was my installation method that was flawed.
"Active Install" caused the USB ports to not function.
When installing using the correct method, it works fine. 
That included version of USBfilter may not be suitable for NT5!
Avoid installation of that included USBFilter.inf period (exclaimation-mark), for now.
It "borked" my USB ports!
The previous version worked fine. (2.0.10.266, IIRC)
...efforting to confirm...
Noting that in Win2k, setuperr.log always lists the following errors:
Error:
Setup detected that the system file named [c:\winnt\system32\drivers\adpu160m.sys] is not signed properly
by Microsoft. This file has been restored to the correct Microsoft version to maintain system stability.
***
Error:
Setup detected that the system file named [c:\winnt\system32\drivers\cpqarry2.sys] is not signed properly
by Microsoft. This file has been restored to the correct Microsoft version to maintain system stability.
***
Error:
Setup detected that the system file named [c:\winnt\system32\drivers\dac960nt.sys] is not signed properly
by Microsoft. This file has been restored to the correct Microsoft version to maintain system stability.
***
Error:
Setup detected that the system file named [c:\winnt\system32\drivers\sym_hi.sys] is not signed properly
by Microsoft. This file has been restored to the correct Microsoft version to maintain system stability.
***
Error:
Setup detected that the system file named [c:\winnt\system32\drivers\symc810.sys] is not signed properly
by Microsoft. This file has been restored to the correct Microsoft version to maintain system stability.
***
Error:
Setup detected that the system file named [c:\winnt\system32\drivers\symc8xx.sys] is not signed properly
by Microsoft. This file has been restored to the correct Microsoft version to maintain system stability.
***I know it is just Win2k, yet it is on my "NT5 Bucket List".
fearless' script/inf worked like a charm.
A word of warning by mr_smartepants in that topic helped to theoretically make this SAD3-safe too.
Driver updated to v1.2.0.1038.
This approach should be "future-proof", considering it seems highly unlikely Marvell will update any NT5 driver.
Here's the .Ini entry:
; REQUIRED
exc_count = 1
; OPTIONAL
exc_1_tagFiles = 3
exc_1_tagFile1 = "%SystemRoot%\System32\drivers\mvxxmm.sys"
exc_1_tagFile2 = "%SystemRoot%\System32\drivers\mv61xxmm.sys"
exc_1_tagFile3 = "%SystemRoot%\System32\drivers\mv64xxmm.sys"
exc_1_+hwids = 0
exc_1_-hwids = 68
exc_1_-hwid1 = "PCI\VEN_11ab&DEV_5040"
exc_1_-hwid2 = "PCI\VEN_11ab&DEV_5041"
exc_1_-hwid3 = "PCI\VEN_11ab&DEV_5080"
exc_1_-hwid4 = "PCI\VEN_11ab&DEV_5081"
exc_1_-hwid5 = "PCI\VEN_11ab&DEV_6041"
exc_1_-hwid6 = "PCI\VEN_11ab&DEV_6042"
; following HWID shared with Highpoint RocketRaid 2220 SATA
exc_1_-hwid7 = "PCI\VEN_11ab&DEV_6081&SUBSYS_11ab11ab"
exc_1_-hwid8 = "PCI\VEN_11AB&DEV_6101"
exc_1_-hwid9 = "PCI\VEN_11AB&DEV_6111"
exc_1_-hwid10 = "PCI\VEN_11AB&DEV_6120"
exc_1_-hwid11 = "PCI\VEN_11AB&DEV_6121"
exc_1_-hwid12 = "PCI\VEN_11AB&DEV_6122"
exc_1_-hwid13 = "PCI\VEN_11AB&DEV_6140"
exc_1_-hwid14 = "PCI\VEN_11AB&DEV_6141"
exc_1_-hwid15 = "PCI\VEN_11AB&DEV_6145"
exc_1_-hwid16 = "PCI\VEN_11AB&DEV_6440"
exc_1_-hwid17 = "PCI\VEN_11AB&DEV_6480"
exc_1_-hwid18 = "PCI\VEN_11AB&DEV_6485"
; following HWID shared with HighPoint RocketRAID 2300/231x series SATA
exc_1_-hwid19 = "PCI\VEN_11ab&DEV_7042&SUBSYS_11ab11ab"
exc_1_-hwid20 = "PCI\VEN_1B4B&DEV_9023"
exc_1_-hwid21 = "PCI\VEN_1B4B&DEV_9028"
exc_1_-hwid22 = "PCI\VEN_1B4B&DEV_90A3"
exc_1_-hwid23 = "PCI\VEN_1B4B&DEV_90A8"
exc_1_-hwid24 = "PCI\VEN_1B4B&DEV_9110"
exc_1_-hwid25 = "PCI\VEN_1B4B&DEV_9111"
exc_1_-hwid26 = "PCI\VEN_1B4B&DEV_9120"
exc_1_-hwid27 = "PCI\VEN_1B4B&DEV_9122"
exc_1_-hwid28 = "PCI\VEN_1B4B&DEV_9123"
exc_1_-hwid29 = "PCI\VEN_1B4B&DEV_9128"
exc_1_-hwid30 = "PCI\VEN_1B4B&DEV_9130"
exc_1_-hwid31 = "PCI\VEN_1B4B&DEV_914D"
exc_1_-hwid32 = "PCI\VEN_1B4B&DEV_9170"
exc_1_-hwid33 = "PCI\VEN_1B4B&DEV_9171"
exc_1_-hwid34 = "PCI\VEN_1B4B&DEV_9172"
exc_1_-hwid35 = "PCI\VEN_1B4B&DEV_9181"
exc_1_-hwid36 = "PCI\VEN_1B4B&DEV_9182"
exc_1_-hwid37 = "PCI\VEN_1B4B&DEV_9190"
exc_1_-hwid38 = "PCI\VEN_1B4B&DEV_9191"
exc_1_-hwid39 = "PCI\VEN_1B4B&DEV_9192"
exc_1_-hwid40 = "PCI\VEN_1B4B&DEV_91A0"
exc_1_-hwid41 = "PCI\VEN_1B4B&DEV_91A1"
exc_1_-hwid42 = "PCI\VEN_1B4B&DEV_91A2"
exc_1_-hwid43 = "PCI\VEN_1B4B&DEV_91A3"
exc_1_-hwid44 = "PCI\VEN_1B4B&DEV_91A8"
exc_1_-hwid45 = "PCI\VEN_1B4B&DEV_91B0"
exc_1_-hwid46 = "PCI\VEN_1B4B&DEV_91F3"
exc_1_-hwid47 = "PCI\VEN_1B4B&DEV_9200"
exc_1_-hwid48 = "PCI\VEN_1B4B&DEV_9215"
exc_1_-hwid49 = "PCI\VEN_1B4B&DEV_9220"
exc_1_-hwid50 = "PCI\VEN_1B4B&DEV_9230"
exc_1_-hwid51 = "PCI\VEN_1B4B&DEV_9235"
exc_1_-hwid52 = "PCI\VEN_1B4B&DEV_9440"
exc_1_-hwid53 = "PCI\VEN_1B4B&DEV_9445"
exc_1_-hwid54 = "PCI\VEN_11AB&DEV_9480"
exc_1_-hwid55 = "PCI\VEN_1B4B&DEV_9480"
exc_1_-hwid56 = "PCI\VEN_1B4B&DEV_9485"
exc_1_-hwid57 = "PCI\VEN_11AB&DEV_948F"
exc_1_-hwid58 = "PCI\VEN_1B4B&DEV_948F"
; from mv91xx.inf in 03/17/2010,1.0.0.1036.
exc_1_-hwid59 = "PCI\VEN_1B4B&DEV_9125"
exc_1_-hwid60 = "PCI\VEN_1B4B&DEV_91A5"
; from mvs91xx.inf in 09/05/2013,1.2.0.1039
exc_1_-hwid61 = "PCI\VEN_1B4B&DEV_9179"
exc_1_-hwid62 = "PCI\VEN_1B4B&DEV_917A"
exc_1_-hwid63 = "PCI\VEN_1B4B&DEV_9186"
exc_1_-hwid64 = "PCI\VEN_1B4B&DEV_918A"
exc_1_-hwid65 = "PCI\VEN_1B4B&DEV_918E"
exc_1_-hwid66 = "PCI\VEN_1B4B&DEV_91A6"
; from mvs91xx.inf in 01/24/2013,1.2.0.1035
exc_1_-hwid67 = "PCI\VEN_1B4B&DEV_91F2"
exc_1_-hwid68 = "PCI\VEN_1B4B&DEV_91F5"
exc_1_+infFiles = 0
exc_1_-infFiles = 0
exc_1_commands = 1
exc_1_command1 = "%DPSROOT%\D\M\M\4\MarvellCleanup.cmd"One less long-standing issue in my "NT5 Bucket List", thanks to fearless, and to you too!
... and fearless had the answer to the "Three Amigos"!
reference: http://forum.driverpacks.net/viewtopic. … 631#p44631
If this is included, i will credit fearless even if script is modified.
PS: Please point me to an OEM source for Marvell's 91xx XP driver v1.2.0.1038 or 1.2.0.1037.
If available on Microsoft Update Catalog, i am unable to search there currently (non-MS OS).
edit: found miniport here --> http://www.highpoint-tech.com/BIOS_Driv … 0.1038.rar
"why did you not just disable them in the INI file?"
I assume that you are referring to the "Three Amigos" also known as mvxxmm, mv61xxmm & mv64xxmm, which are installed in the non-PnP section of Device Manager on every install.
If so, my plan of attack was to add an exception in DP_MS.ini to remove them if no Marvell controller was found. That way, the change shouldn't negatively impact those with supported hardware.
Here is the untested exception added to [M-4], although i believe DPINST won't get the job done:
; REQUIRED
exc_count = 1
; OPTIONAL
exc_1_tagFiles = 0
exc_1_+hwids = 0
exc_1_-hwids = 70
exc_1_-hwid1 = "PCI\VEN_11ab&DEV_5040"
exc_1_-hwid2 = "PCI\VEN_11ab&DEV_5041"
exc_1_-hwid3 = "PCI\VEN_11ab&DEV_5080"
exc_1_-hwid4 = "PCI\VEN_11ab&DEV_5081"
exc_1_-hwid5 = "PCI\VEN_11ab&DEV_6041"
exc_1_-hwid6 = "PCI\VEN_11ab&DEV_6042"
; following HWID shared with Highpoint RocketRaid 2220 SATA
exc_1_-hwid7 = "PCI\VEN_11ab&DEV_6081&SUBSYS_11ab11ab"
exc_1_-hwid8 = "PCI\VEN_11AB&DEV_6101"
exc_1_-hwid9 = "PCI\VEN_11AB&DEV_6111"
exc_1_-hwid10 = "PCI\VEN_11AB&DEV_6120"
exc_1_-hwid11 = "PCI\VEN_11AB&DEV_6121"
exc_1_-hwid12 = "PCI\VEN_11AB&DEV_6122"
exc_1_-hwid13 = "PCI\VEN_11AB&DEV_6140"
exc_1_-hwid14 = "PCI\VEN_11AB&DEV_6141"
exc_1_-hwid15 = "PCI\VEN_11AB&DEV_6145"
exc_1_-hwid16 = "PCI\VEN_11AB&DEV_6440"
exc_1_-hwid17 = "PCI\VEN_11AB&DEV_6480"
exc_1_-hwid18 = "PCI\VEN_11AB&DEV_6485"
; following HWID shared with HighPoint RocketRAID 2300/231x series SATA
exc_1_-hwid19 = "PCI\VEN_11ab&DEV_7042&SUBSYS_11ab11ab"
exc_1_-hwid20 = "PCI\VEN_1B4B&DEV_9023"
exc_1_-hwid21 = "PCI\VEN_1B4B&DEV_9028"
exc_1_-hwid22 = "PCI\VEN_1B4B&DEV_90A3"
exc_1_-hwid23 = "PCI\VEN_1B4B&DEV_90A8"
exc_1_-hwid24 = "PCI\VEN_1B4B&DEV_9110"
exc_1_-hwid25 = "PCI\VEN_1B4B&DEV_9111"
exc_1_-hwid26 = "PCI\VEN_1B4B&DEV_9120"
exc_1_-hwid27 = "PCI\VEN_1B4B&DEV_9122"
exc_1_-hwid28 = "PCI\VEN_1B4B&DEV_9123"
exc_1_-hwid29 = "PCI\VEN_1B4B&DEV_9128"
exc_1_-hwid30 = "PCI\VEN_1B4B&DEV_9130"
exc_1_-hwid31 = "PCI\VEN_1B4B&DEV_914D"
exc_1_-hwid32 = "PCI\VEN_1B4B&DEV_9170"
exc_1_-hwid33 = "PCI\VEN_1B4B&DEV_9171"
exc_1_-hwid34 = "PCI\VEN_1B4B&DEV_9172"
exc_1_-hwid35 = "PCI\VEN_1B4B&DEV_9181"
exc_1_-hwid36 = "PCI\VEN_1B4B&DEV_9182"
exc_1_-hwid37 = "PCI\VEN_1B4B&DEV_9190"
exc_1_-hwid38 = "PCI\VEN_1B4B&DEV_9191"
exc_1_-hwid39 = "PCI\VEN_1B4B&DEV_9192"
exc_1_-hwid40 = "PCI\VEN_1B4B&DEV_91A0"
exc_1_-hwid41 = "PCI\VEN_1B4B&DEV_91a1"
exc_1_-hwid42 = "PCI\VEN_1B4B&DEV_91A2"
exc_1_-hwid43 = "PCI\VEN_1B4B&DEV_91A3"
exc_1_-hwid44 = "PCI\VEN_1B4B&DEV_91A8"
exc_1_-hwid45 = "PCI\VEN_1B4B&DEV_91B0"
exc_1_-hwid46 = "PCI\VEN_1B4B&DEV_91F3"
exc_1_-hwid47 = "PCI\VEN_1B4B&DEV_9200"
exc_1_-hwid48 = "PCI\VEN_1B4B&DEV_9215"
exc_1_-hwid49 = "PCI\VEN_1B4B&DEV_9220"
exc_1_-hwid50 = "PCI\VEN_1B4B&DEV_9230"
exc_1_-hwid51 = "PCI\VEN_1B4B&DEV_9235"
exc_1_-hwid52 = "PCI\VEN_1B4B&DEV_9440"
exc_1_-hwid53 = "PCI\VEN_1B4B&DEV_9445"
exc_1_-hwid54 = "PCI\VEN_11AB&DEV_9480"
exc_1_-hwid55 = "PCI\VEN_1B4B&DEV_9480"
exc_1_-hwid56 = "PCI\VEN_1B4B&DEV_9485"
exc_1_-hwid57 = "PCI\VEN_11AB&DEV_948F"
exc_1_-hwid58 = "PCI\VEN_1B4B&DEV_948F"
; following HWID's are not included in DP_MS:
; from pcidevs.txt {version ha_merged, 16 Oct 2012 08:43:36}
exc_1_-hwid59 = "PCI\VEN_11AB&DEV_11AB"
; following HWID is RocketRAID 640 SATA
exc_1_-hwid60 = "PCI\VEN_1B4B&DEV_0640"
exc_1_-hwid61 = "PCI\VEN_1B4B&DEV_9125"
exc_1_-hwid62 = "PCI\VEN_1B4B&DEV_917A"
exc_1_-hwid63 = "PCI\VEN_1B4B&DEV_91A4"
; from mvs91xx.inf in 09/05/2013,1.2.0.1039
exc_1_-hwid64 = "PCI\VEN_1B4B&DEV_9179"
exc_1_-hwid65 = "PCI\VEN_1B4B&DEV_9186"
exc_1_-hwid66 = "PCI\VEN_1B4B&DEV_918A"
exc_1_-hwid67 = "PCI\VEN_1B4B&DEV_918E"
exc_1_-hwid68 = "PCI\VEN_1B4B&DEV_91A6"
; from mvs91xx.inf in 01/24/2013,1.2.0.1035
exc_1_-hwid69 = "PCI\VEN_1B4B&DEV_91F2"
exc_1_-hwid70 = "PCI\VEN_1B4B&DEV_91F5"
exc_1_+infFiles = 0
exc_1_-infFiles = 0
exc_1_commands = 4
exc_1_command1 = "%DPSROOT%\D\M\M\4\dpinst.exe /U %DPSROOT%\D\M\M\4\mv64xx.inf /D"
exc_1_command2 = "cmd /c copy /y %DPSROOT%\D\M\M\4\dpinst.* %DPSROOT%\D\M\M"
exc_1_command3 = "%DPSROOT%\D\M\M\dpinst.exe /U %DPSROOT%\D\M\M\mv61xx.inf /D"
exc_1_command4 = "%DPSROOT%\D\M\M\dpinst.exe /U %DPSROOT%\D\M\M\mv91xx.inf /D"Am noting that the last dozen HWID's listed have no corresponding driver in DP_MS.
edit: updated HWID list above
Why attempt removal?
That way no Marvell software is installed on non-Marvell hardware, even though they are harmless.
Perhaps i need to first understand how it is that they are installed in the first place.
Will review Jaak's & your posts (et al) regarding this before assembling packs for a series of test installs.
@Outbreaker:
nLite has had an issue in the past of some corruption of the source, which has previously been discussed elsewhere in this forum (IIRC).
Am not certain if this still applies to the latest release, although it appears that 7zip v9.20 is being utilized now & LZMA2 is supported.
"upd: 7z.exe to 9.20"
quoted from: http://www.msfn.org/board/topic/163701-nlite-1493/
What i do know is that DPs_BASE has no requirement for .NET2 and doesn't corrupt source.
I see that too now.
It would seem that i didn't follow proper naming conventions for those DriverPack.ini's.
The downside with the existing 3rd-party MassStorage packs is that exceptions will not be processed within.
The upside is that there are no exceptions to process.
The one consequence, the leftover Ini files, you have already discovered.
Thank you.
A fix for my "noobish" mistake to follow soon.
Towards another subject, was searching for a newer Intel RSTe, and stumbled upon Fernando's win-raid site.
Within, he has a modded RST v11.2 pack for integration with nlite.
He states that that driver will work with the Intel 8-series chipset.
Without downloading his pack(s), i will modify existing .Inf files for testing & credit Fernando for the idea.
I wonder if something similar will work with Win2k for ICH9R & ICH10R.
There should be no difference with DP_MS/DP_MS_IntelIDE compared to the previous DP_MS packs (other than for those few with ICH7 issues).
If one includes both IntelIDE & pciIDE, IntelIDE will install.
"Will there be any conflict if i use the IntelIDE with the DP_MassStorage pack?"
No, that is the preferred integration combination (DP_MassStorage in DriverPacks folder, DP_MassStorage_IntelIDE in 3rd-party folder).
..."what was included before in the DP_MassStorage, IntelIDE or pciIDE?"
Both were included. However; the ICH7&8 IntelIDE driver (ich78id2.inf) was archived for those few who had issues using IntelIDE on some ICH7 systems (refer to link two posts up). Also, Windows always chose the IntelIDE driver over the pciIDE-based drivers. Now people can choose.
The use of pciIDE means that hotswap cannot be supported, as apparently only IntelIDE can, if i have researched that correctly. One might require a third-party utility in order to use such feature if "Safely Remove Hardware" is unavailable (such as HotSwap! or SafelyRemove). An alternative is to disable the drive in Device Manager.
The support of TRIM by either driver is unconfirmed by myself as of yet (no SSD).
Ask any question, even if it sounds "noob-like".
Others likely have similar questions.
I am grateful somebody asked for clarification.
If you have any further questions, do not hesitate to ask.
PS: Come back, Jaak!
I recommend integrating the DP_MassStorage pack (in DriverPacks folder) with the DP_MassStorage_IntelIDE (in the 3rd-Party folder) pack for most integrations.
Some ICH7 systems will bluescreen with IntelIDE integrated, so a pciIDE pack is made available.
In that instance, one could leave out the IntelIDE pack, as IntelIDE drivers take precedence in Windows' driver preferences.
Refer to: http://forum.driverpacks.net/viewtopic.php?id=8112
Now a driver can be created to allow IntelIDE vs. pciIDE testing on Intel eSATA-specific ports.
From what i have read, one need disable write caching too for those specific external ports.
The big question i have is, 'How does this all affect BartPE'?
Am now working on removing mvxxmm, mv61xxmm & mv64xxmm non-PnP drivers on systems that have no Marvell mass storage controller (no .Inf copied to %SystemRoot%\Inf). Have also found an AMD utility for AMD USB3.0 controllers in an AMD Win7 driver package (The executables have NT5.1 listed in their respective PE Headers). This give me a chance to test exceptions in the MassStorage pack.
Also noting that some USB cardreaders might not have their drivers installed if they are greyed out in Device Manager when unpopulated.
Check out Digital FLEM --> http://digitalflem.mydiscussion.net/
The latest MassStorage includes some new AMD AHCI & RAID drivers in support of the latest chipsets.
The SB8x0 driver has also been updated.
A new pair of "3rd-party" MassStorage packs enable the integrator to choose between IntelIDE or PCIIDE.
DP_MassStorage_wnt5_x86-32_1401041.7z - 9.69 MB faf88344e51cc5ffef71be12500ae2bf02643e96
* - edit: link removed - updated near last post in this topic
DP_MassStorage_intelide_wnt5_x86-32_1401041.7z - 0.05 MB 673eceaa4fa5363994425e4316ebf4219f5acf55
DP_MassStorage_intel-pciide_wnt5_x86-32_1401041.7z - 0.06 MB ef0dfc1e757cf73866c4ce27b439657c88edf345
* - edit: link removed - deprecated
Found an OEM link for Intel Chipset v9.4.4.1006!
Note that the Chipset pack does not install AMD's USBfilter, contrary to what is noted in the changelog.
Avoid installation in Virtual Environments, as it causes known issues.
DP_Chipset_wnt5_x86-32_1401031.7z - 9.64 MB 2eb9e67274d6f9a10dd5e179982e90c68d26c2d6
edit: link removed - updated near topic end
Fixed a muck-up mistake or two.
DP_Modem_wnt5_x86-32_1401021.7z - 31.83 MB 77737975ab5046544e9a24ed81d7c85057427579
*edit: link removed - updated below
Alcor Micro USB Smart Card Reader updated.
DP_SmartCard_wnt5_x86-32_1401031.7z - 51.03 MB adc3d38cc367f7ded3585248e45c8e14fc0d8d29
Many device updates for Acer, Google, Motorola & Samsung.
Use this pack only at your own risk.
DP_Phone_wnt5_x86-32_1401031.7z - 11.55 MB 85475bef6a0d27010bc089aee946388311b04ca8
* edit: link removed - updated below
Updated Alcor Micro CardReader driver.
DP_Misc_wnt5_x86-32_1401031.7z - 16.24 MB c452e48b5353e6229691c6ccd3f37e10528a10ba
*edit: updated in last post.
Updated Realtek PCIe & Red Hat VirtIO drivers.
Added Realtek USB3.0 LAN driver, which includes support for the latest lenovo devices.
SMSC LAN7500 & LAN9500 USB device drivers have been updated, too.
This should prove a boon for all those dongles.
The BartPE plugins will receive an update if somebody can tell me if any of them work.
DP_LAN_wnt5_x86-32_1401031.7z - 11.17 MB 1bd55ed5f800422908d9074ca1d78f577b49f5a3
edit: link removed - updated in last post
Added more Conexant Sound drivers and archived existing included sound utilities to shorten path length.
Additional Conexant Sound drivers required a drastic altering of the distribution of folders between the two official packs.
The file sizes have also been drastically altered.
As a consequence, DP_Sound_B_wnt5_x86-32_1401021.7z and later should only be used with DP_Sound_A_wnt5_x86-32_1401021.7z and later.
The last older revisions of both shall remain here, should anyone need to revert to older packs, they can be used as a pair.
DP_Sound_B_wnt5_x86-32_1401021.7z - 271.34 MB cd513eed0226c4371e32763e7808904ece44af12
* edit: link removed: updated below
Realtek HDA has been updated.
Additional Conexant Sound drivers required a drastic altering of the distribution of folders between the two official packs.
The file sizes have also been drastically altered.
As a consequence, DP_Sound_A_wnt5_x86-32_1401021.7z and later should only be used with DP_Sound_B_wnt5_x86-32_1401021.7z and later.
The last older revisions of both shall remain here for a time, should anyone need to revert to older packs, they can be used as a pair.
DP_Sound_A_wnt5_x86-32_1401021.7z - 199.98 MB 7c267c716e7d0a1b0fba27f5c23f7c8512e3c2f5
edit: link removed - updated below
Updated Atheros & Ralink drivers.
Also updated Intel drivers (where applicable) and resolved a missing file problem.
WiMAX drivers have been updated and and should install properly now.
Also shortened path length. One consequence is that DP_WLANutils had to be modified.
DP_WLAN_wnt5_x86-32_1401031.7z - 43.46 MB 6a70c0e442eaf4776b6fcfcd37730357d8b1ddce
DP_WLANutils_wnt5_x86-32_1401021.7z - 115.46 MB 1d098f18d585a30dee51154b347472825a3e77fc
The changelog and TOC is still on my TODO list once i get a round "tuit".
edit: link removed - updated below
DriverPacks.net Forum » Posts by TechDud
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.070 seconds, 6 queries executed ]