Re: [Nightlies] DP_MassStorage_wnt5_x86-32_1304-1412 - Public

yeah... where is Jaak? we did this whole dance a couple years ago.

try this tech, instead of breaking them out. just change the order in the INI file.
in the past there were cases where the first found match wins. (Order can matter)

why did you not just disable them in the INI file?

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: [Nightlies] DP_MassStorage_wnt5_x86-32_1304-1412 - Public

I had a lot of success with Fernando's SATA Drivers, my first SATA driver i integrated was his Intel SATA Driver and nLike. smile
I didn't know that he was still alive and kicking after 10 years it looks like he only moved to his own forum, good to know. smile

Last edited by Outbreaker (2014-01-18 00:34:13)

Re: [Nightlies] DP_MassStorage_wnt5_x86-32_1304-1412 - Public

OverFlow wrote:

"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.

nuhi  wrote:

"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.

Last edited by TechDud (2014-01-19 02:04:45)

Re: [Nightlies] DP_MassStorage_wnt5_x86-32_1304-1412 - Public

... 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     smile

Last edited by TechDud (2014-01-19 02:34:24)

Re: [Nightlies] DP_MassStorage_wnt5_x86-32_1304-1412 - Public

IDK if removing them is worth the effort... if you think it is then OK big_smile

simple is better, stable is best.

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: [Nightlies] DP_MassStorage_wnt5_x86-32_1304-1412 - Public

PS to remove a driver... i have a method for that already

http://forum.driverpacks.net/viewtopic.php?id=5032


in this way it is never installed... I think...
if there are no hive entries this will remove it.

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: [Nightlies] DP_MassStorage_wnt5_x86-32_1304-1412 - Public

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!     smile

Last edited by TechDud (2014-01-21 18:24:32)

Re: [Nightlies] DP_MassStorage_wnt5_x86-32_1304-1412 - Public

i don't think the SAD script processes the ini files.

My way is easier if i am right and it doesn't.

the end result would be that the driver would be removed from the install source by BASE, and thus never installed to the target to begin with.

IE result is same... much less work.  try it and compare files, end result same?

KISS method big_smile

i need to dig into the code again. the finisher needs to be updated desperately. i see the finisher merging with sad 3.

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: [Nightlies] DP_MassStorage_wnt5_x86-32_1304-1412 - Public

"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.

Last edited by TechDud (2014-01-24 11:40:25)

Re: [Nightlies] DP_MassStorage_wnt5_x86-32_1304-1412 - Public

OverFlow wrote:

i don't think the SAD script processes the ini files.

It doesn't.  But DriverPacks Finisher DOES.

Re: [Nightlies] DP_MassStorage_wnt5_x86-32_1304-1412 - Public

I C.

SAD calls DriverPacks Finisher for XP... naturally - I'm getting old and slow, duh...

So both options are viable. 
One prevents driver from being installed,
the other removes an installed driver.

your remover should be a 3rd party DriverPack in case someone needs it
the DriverPack MassStorage should stay similar to how it was with notes on how to disable / enable options in the affected sections.

PS there is no negative effect, the original MS included drivers are used, and should be stable. the downside is they are not updated... no big deal.

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: [Nightlies] DP_MassStorage_wnt5_x86-32_1304-1412 - Public

If you are "old and slow", then a retired snail is faster than i!
  Perhaps you have simply forgotten more than most people have ever learned.
    If your forgotten knowledge could speak, it might quote the late Douglas MacArthur.
       "I shall return."

DP_MassStorage_wnt5_x86-32_1401282.7z - 10.24 MB   631C688225BBCC0832D3974E9DC157B2DE4C7C7C     smile
* - edit: link removed - updated near last post in this topic

for 3rd-party folder, if integrated with DPs_BASE:
DP_MassStorage_intelide_wnt5_x86-32_1401191.7z - 57.13KB   9B4D73B3B23C4DBB3EF769F5C98847E72CBAC1FB
DP_MassStorage_intel-pciide_wnt5_x86-32_1401191.7z - 58.12KB   C4A05B04963293D2B3E14BF2CA97F8E309BEE074
{pciide now includes test driver for intel eSATA}
* - edit: links removed - deprecated

(added usbmonitor utilities for NEC/Renesas USB 3.0 controllers, which seem very similar to that for AMD USB 3.0 controllers;
   mvxxmm, mv61xxmm & mv64xxmm removal included - by fearless if no Marvell controller found;
      HighPoint driver global updates;
        ASmedia driver v2.01 included - scsiport & storport;
           Intel 8-series support tentatively added - awaiting feedback;
there's probably more, but i have forgotten ... hmm ... see changelog for complete list)

Last edited by TechDud (2014-01-29 19:28:01)

Re: [Nightlies] DP_MassStorage_wnt5_x86-32_1304-1412 - Public

Note that the Renesas utilities may require a manual install.
  Finisher doesn't seem to like the compatible HWID used in the .Ini.

Has anybody tested DP-integrated AHCI installation on intel 8-series, Asmedia, or Highpoint?
  Looking for any commentary upon intel eSATA devices too, please.
    Any comments are appreciated.

Last edited by TechDud (2014-02-24 10:37:15)

Re: [Nightlies] DP_MassStorage_wnt5_x86-32_1304-1412 - Public

TechDud wrote:

Has anybody tested DP-integrated AHCI installation on intel 8-series, Asmedia, or Highpoint?
  Looking for any commentary upon intel eSATA devices too, please.
    Any comments are appreciated.

Whatever the latest nightly was as of February 22, 2014, it blue screens native AHCI with Intel Q87 chipset.
I can test this for you if you like.

I did not blue screen if I chose IDE native mode... but it also didn't see the drive.

Last edited by urbanriot (2014-02-28 02:45:47)

Re: [Nightlies] DP_MassStorage_wnt5_x86-32_1304-1412 - Public

Thank you for the reply, urbanriot!
  Can you provide any details, like when bluescreen occurs, bluescreen code, DriverPacks integrated, HWID's, manufacturer/model, etc.?
    Any info is appreciated.

Re: [Nightlies] DP_MassStorage_wnt5_x86-32_1304-1412 - Public

urbanriot wrote:

"I did not blue screen if I chose IDE native mode... but it also didn't see the drive."

This seems to indicate that your bluescreen occurred during textmode partitioning.
  I wonder what would happen if an older SATA drive were used.

Re: [Nightlies] DP_MassStorage_wnt5_x86-32_1304-1412 - Public

You can use any driver you like in textmode since it will be updated properly when PnP re-installs all the drivers in PE Mode

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: [Nightlies] DP_MassStorage_wnt5_x86-32_1304-1412 - Public

I have some ideas there.

Last edited by TechDud (2014-03-11 17:40:08)

Re: [Nightlies] DP_MassStorage_wnt5_x86-32_1304-1412 - Public

Thanks for your continuous hard work on the Mass Storage drivers pack TechDud!

Overall integration seems fine on Windows XP, but I noticed a small change from previous release.

In the ini file you changed section H, the integration settings for "HighPoint Rocket 100/133/HPT3xx, Adaptec 1200A"

ms_1_tag="hpt3xx" to ms_1_tag="hpt3xxx".

Is this an intentional change?

Re: [Nightlies] DP_MassStorage_wnt5_x86-32_1304-1412 - Public

Groeten!
That was necessary so as to allow 2k3 exclusive use of that tag to update a pre-existing driver named "hpt3xx".

Did the non-Plug&Play drivers remain after install?
  reference:  mvxxmm, mv61xxmm & mv64xxmm

Dank u.

edit:  Updated.
DP_MassStorage_wnt5_x86-32_1403071.7z - 10.72 MB   6bdc0177c1a05debeb36cecd0fa4ead3916f9a77
* - edit: link removed - updated near last post in this topic

3rd-party:
DP_MassStorage_intelide_wnt5_x86-32_1403071.7z - 47.19 KB   c84ff0d462d21107931285901f61b4cca5048046

---integrate in place of MassStorage_intelide only if bluescreens occur---     wink
DP_MassStorage_intel-pciide_wnt5_x86-32_1403071.7z - 49.8KB   9b578510edc9e5c475d51a57e11b3d528d2e4dce ***
*** note:  use MS_intelide for most applications, it takes precedence over intel-PCIIDE if both are included

* - edit: links removed - deprecated

Last edited by TechDud (2014-11-06 17:43:15)

Re: [Nightlies] DP_MassStorage_wnt5_x86-32_1304-1412 - Public

Thanks for your answer about the driver naming. As I use a different method to integrate the driverpacks the method I use does not run the DPFinisher tool at the moment. Some time ago I was working on a new tool to parse the ini file and run the commands, but I have no complete code yet.

Do you have the source code of the DPFinisher program? It would help my project a bit.


When running the MarvellCleanup.cmd manually it failed with an access denied error and the registry keys were not removed.

I found on my system under HKLM\\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_\0000

not only "Control", but also a "LogConf" directory. When permissions are not updated on both directories the Marvell driver cannot be removed.

Here's my modified version of the MarvellCleanup.cmd which fixes the issue.

::Delete Marvell drivers installed by DriverPacks.
::by fearless
::Requires MarvellCleanup.inf

:: WARNING: This script will indescriminately delete Marvell mass storage drivers
:: MV61XXMM, MV64XXMM, and MVXXMM. If DriverPacks was used to integrate mass
:: storage drivers into a Windows installation source, then those drivers will
:: always be installed whether needed or not.

@Echo Off
TITLE MarvellCleanup by fearless
Setlocal EnableExtensions
Set name=%~n0
Set iniRoot=\Registry\Machine
Set regRoot=HKLM
Set key=\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_
Set subkey=0000 Control
Set subkey2=0000 LogConf
Set iniPerms="[1 8 17]"
Set initmp="%temp%\%name%.ini"
Set regdelarg=%iniRoot% %regRoot% %key% %iniPerms%
Call :regdel %regdelarg% MV61XXMM %subkey% 
Call :regdel %regdelarg% MV61XXMM %subkey2%
Call :regdel %regdelarg% MV64XXMM %subkey% 
Call :regdel %regdelarg% MV64XXMM %subkey2% 
Call :regdel %regdelarg% MVXXMM %subkey%
Call :regdel %regdelarg% MVXXMM %subkey2%
Del %initmp%
Pushd "%~dp0"
rundll32 setupapi,InstallHinfSection DefaultInstall 132 .\%name%.inf
Popd
goto :EOF

:regdel
::Use regini to give Administrators full control then delete the key.
Echo.%1%3%5 %~4>%initmp%
If "%~6" NEQ "" Echo.%1%3%5\%6 %~4>>%initmp% 
If "%~7" NEQ "" Echo.%1%3%5\%6\%7 %~4>>%initmp% 
If "%~8" NEQ "" Echo.%1%3%5\%6\%7\%8 %~4>>%initmp% 
If "%~9" NEQ "" Echo.%1%3%5\%6\%7\%8\%9 %~4>>%initmp% 
regini %initmp%
Reg Delete %2%3%5 /f

I don't know if other people experienced this problem, as I install the DriverPacks at a different moment during setup.

Re: [Nightlies] DP_MassStorage_wnt5_x86-32_1304-1412 - Public

Hi
I notice that the INI file section names no longer correspond to the driver directory names.
For instance, in the INI file we have

[I-5]

but the folder is called .\D\M\I5  not .\D\M\I-5


This is a change from the last release version. Is there a reason for this? It is causing problems with Easy2Boot and "DPMS" because I need to know what the folder name is for the driver by looking at the INI file. With the latest Nightly INI file this is not possible.

Some folders don't even exist - e.g. [I-a]  or Ia.

Last edited by SteveSi (2014-03-20 02:51:27)

Re: [Nightlies] DP_MassStorage_wnt5_x86-32_1304-1412 - Public

@Acheron:
  You Rock!

Acheron wrote:

"Do you have the source code of the DPFinisher program?"

No, i do not.  However; OverFlow will know.
  Will include your update & add notes of your contribution.  Thank you!     smile

---------------------------------------

@SteveSi:
Hello again!
  Those hyphenated directory names refer to subfolders.
                [I-5] refers to I\5  -  [I-a] refers to I\a
    It's not my syntax, although i do have to conform to it!
      The primary reason for change being to simplify folder names and thereby shorten path length.

PS:  Have the previous issues with ICH9 been eliminated?

Last edited by TechDud (2014-03-20 11:36:36)

Re: [Nightlies] DP_MassStorage_wnt5_x86-32_1304-1412 - Public

Hi
The new Easy2Boot seems to work fairly well with the new INI format now - thanks.
I was contacted by someone trying to install XP to a Intel Series 8 Z87 mainboard using DP_MassStorage_wnt5_x86-32_1403071.7z and the new Easy2Boot v1.31.
The controller is identified as 8086 8C02, but the only matching PCI ID in the INI file is for w2k3  (D\M\I\A) so the install didn't work.
He said that the INF file in D\M\I\9  was actually successfully picked up and used by XP when he pointed XP at it.

So 8086 8C02 does not seem to be supported yet by this build for XP?

P.S. AsMedia 106x SATA controller  PCI 1B21 0612  D\M\AS worked OK though.

Last edited by SteveSi (2014-04-01 01:49:01)

Re: [Nightlies] DP_MassStorage_wnt5_x86-32_1304-1412 - Public

The INI format is not new. Wim wrote it that way in the original code, ten years ago. It simply was not used much, it has been used in the past and has always been built into the BASE code.

Again, Nothing was changed! You were simply not aware of that convention / option big_smile. That is not our fault.

PS I LOVE easy2boot!
PSS I am hurt that you announce that "WE changed something" on your site, which is not true.

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.