[Nightlies] DP_MassStorage_wnt5_x86-32_1304-1412 - Public (Page 3 of 12)

Thanks for the update sir... looks like the betas may have broken something for PE.

Does normal DriverPacks BASE integrated install of the beta DriverPack MassStorage work when deploying from an ODD on that hardware?

How is this deployed, Network, Disc, Thumb. 
Are we talking about the normal PE stage of XP install?

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!

The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Hello, urbanriot!

Here are a couple of test packs for you.  ICH8 & ICH10D/DO should be fixed now.

  * - edit: link removed - updated near last post in this topic
  Bear in mind that these have not yet gone through rigorous testing.  I will post an updated Sound_A package later.

In some cases, hardware duplicates (such as video, sound or modem cards) can cause blue-screens during an install.  I am uncertain if this is true with PE.

    Also keep in mind the possibility of hardware issues, such as blown capacitors - especially in the "no user servicable parts" power supplies, which are a shock hazard when opened.  It would be rare for this to cause issue in HDD detection ($7B errors).  However; it can and does cause other instabilities.  Every ten degree Celsius drop in temperature doubles their life span.  Conversely, every ten degree Celsius rise in temperature halves their life span.  55°C is a good average.  Use a non-contact infrared thermometer to gauge thermal zones.  Ensure all dust is removed.  Some of it spontaneously emits electrostatic charge.

Please let us know how it works out for you.
  If there are any further changes needed, do not hesitate to reply here.

I thank you for your report.
============================================================

Hello, Outbreaker!

You will need to run mr_smartepants' gamut of nVidia MassStorage testing.
  here -->  http://forum.driverpacks.net/viewtopic.php?id=4742

Note that i cannot include any of Fernando's work without his expressed permit.
  Also, OEM sources are required as a base for any modification.  I require myself to justify where files are sourced, at least to the Testing Team.  Every project should reveal their sources for peer review.  Progress is much slower this way, yet i believe it supports trust and therefore worth every extra bit of time.

Last edited by TechDud (2013-10-26 06:53:40)

Forum Rules & Guidelines   HWID's tool   Unknown Devices (Win7-max) LatencyMon - NT6.x
MemTest86+    Video Memory Stress Test    D-P-C Driver Latency Tester (Win7-max)

I do not see anywhere on his page where it states "DriverPacks may include my work in their project if they credit me".
But this is beside the point.

mr_smartepants invested a lot of time and effort in at least the nVidia portion of the MassStorage pack.  To include the work of others would likely mean negating at least some of that.

It is a "kettle of fish" that i dare not open.

It works for most boards.  The few that it does not support can be added.  Yet it need be done his way.

I know of no other way.

What particular nVidia chipset is that?

Last edited by TechDud (2013-10-26 07:31:17)

Forum Rules & Guidelines   HWID's tool   Unknown Devices (Win7-max) LatencyMon - NT6.x
MemTest86+    Video Memory Stress Test    D-P-C Driver Latency Tester (Win7-max)

The MassStorage.ini already uses ..\N\7\nvgts7.sys {quote:  "From nForce 15.56 DriverVer=04/09/2010,11.1.0.43"} for textmode.  nvgts.inf seems to satisfy WHQL requirements.

Is that PCI\VEN_10DE&DEV_0AB9&CC_0106 or PCI\VEN_10DE&DEV_0AB9&CC_0104?

Are you using a clean or updated source?

This project doesn't officially support flash, yet it is a work in-progress. 
Disc install has greatest odds of success due to least variance in BIOS/uEFI support (except disc-USB).

You seem to be saying, in a way, that you are having issues with malware.  Are there problems with pixellation or random restarts, cut-outs, blue or black screens?  Any blown caps?  Is it clean, or clogged with detritus?
Certainly, it seems possible for what might appear to be malware at first could actually have hardware origins, perhaps even making a system more prone to malware.

How old is the coin-cell battery in it?  They get drained down to nothing if they are left with AC removed for many months.  You can only truly test them "under load", with a same coin-cell based accessory, such as a light or WiFi finder.

It is amazing how much of a difference a well-running proven power supply makes, first and foremost (like audio).  Components on the motherboard run much cooler when they have less electric noise in the power to dissipate as heat.
Warranty length (parts AND labour) is a good gauge for consumer.  By previous observation, products seemed engineered to last one and a half times the length of the original warranty.

Search is good, too.  http://forum.driverpacks.net/viewtopic. … 150#p32150

Last edited by TechDud (2013-10-27 22:00:03)

Forum Rules & Guidelines   HWID's tool   Unknown Devices (Win7-max) LatencyMon - NT6.x
MemTest86+    Video Memory Stress Test    D-P-C Driver Latency Tester (Win7-max)

TechDud, I appreciate your efforts. I have not yet had an ICH10 based system to test since you posted and I look forward to evaluating it.

However the aforementioned DG35EC still blue screened with the latest iterations of Driverpacks with the standard controller blue screen.

The BIOS has three settings:
Legacy - IDE
Native - IDE
Native - AHCI

The blue screen occurs regardless of which of those options you choose.

If we use a Driverpacks from February of 2013 it will work fine in any of those modes.

Unfortunately I no longer have the system here to test further but I figured I'd report back in the event this information helps anyone else.

A simple install of NT5 works fine with the two IDE modes but gives the standard non-supported controller blue screen (7B?), the same blue screen you get when using the newer DriverPacks. If I flip the system to AHCI mode and boot up an older PE disc with the older DP from February of 2013 then use the "fix_hdc" script it will insert the AHCI drivers into that Windows installation and work just fine.

Unfortunately I don't have access to this system to provide further insight into the particulars of this issue and I don't know which DP I used in February 2013 disc but it was probably whatever stable was around at that time. I didn't start using the DP nightlies until recently.

Just noting that i encountered BSOD's or "no drive" issues on a HP Pavillion m7570n (ICH7R/DH) in AHCI mode.
The BSOD's were STOP $7F, $50 in XP, and STOP $1E in W2k.
During the "no drive" screen for partitioning, i noticed a "^ More" at the upper right corner of the partitioning box.
I pressed the up arrow and was greeted with the BSOD particular to my case.

It turned out to be the HDD that was causing this.
After swapping out the Seagate 160G SATA drive for a different drive, i was able to successfully partition the replacement drive and install Windows in AHCI mode without resorting to "fix_hdc".
I have also encountered this with a Maxtor Diamond Max 10 80G drive.

Hopefully this helps.
If not, please provide more details as requested.
I am unable to make proper decisions based on vague or incomplete data.

Last edited by TechDud (2013-11-11 08:16:29)

Forum Rules & Guidelines   HWID's tool   Unknown Devices (Win7-max) LatencyMon - NT6.x
MemTest86+    Video Memory Stress Test    D-P-C Driver Latency Tester (Win7-max)

What's up with this "3rd-party" MassStorage packs? Should i integrate them all or only one? and if only one which one would be the best for old computers?

Last edited by Outbreaker (2014-01-15 12:43:18)

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.

Last edited by TechDud (2014-01-16 02:32:34)

Forum Rules & Guidelines   HWID's tool   Unknown Devices (Win7-max) LatencyMon - NT6.x
MemTest86+    Video Memory Stress Test    D-P-C Driver Latency Tester (Win7-max)

No, that is the preferred integration combination (DP_MassStorage in DriverPacks folder, DP_MassStorage_IntelIDE in 3rd-party folder).

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.     

Last edited by TechDud (2014-01-16 12:43:45)

Forum Rules & Guidelines   HWID's tool   Unknown Devices (Win7-max) LatencyMon - NT6.x
MemTest86+    Video Memory Stress Test    D-P-C Driver Latency Tester (Win7-max)

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.

Last edited by TechDud (2014-01-16 12:47:36)

Forum Rules & Guidelines   HWID's tool   Unknown Devices (Win7-max) LatencyMon - NT6.x
MemTest86+    Video Memory Stress Test    D-P-C Driver Latency Tester (Win7-max)