101 Reply by TechDud

(294 replies, posted in DriverPack Mass Storage)

Sadly, those HWID's you posted don't help at all.  We need the specific HWID from a lenovo G405/G505.
Until then, this issue can only be added to the "Known Issues" list (with thanks to you for noting it).

symbios24 wrote:

"i don`t want to get into the same problem of another erroneous storage controller when formatting. or you hardly suggest to use the official v12.09 masstorage driverpack for my work ?? "

How about making two discs?  One would use DP_MassStorage_wnt5_x86-32_1209.7z, and the other - your primary install disc) would use DP_MassStorage_wnt5_x86-32_1405176.7z in it's stead.

That way, if you do encounter hardware that doesn't work with the latest [Nightly], such as apparently the lenovo G505, you will have two discs for testing and reporting what works, so we can fix it and credit you for reporting solutions too!

Disc install is the primary installation method supported by DriverPacks, by the way.
  There are faster ways to install Windows (integrated with DriverPacks).  {see Easy2Boot & WinSetupFromUSB.}

If you do go on to use USB for installs, keep the two discs for hardware that doesn't cooperate.

Sas efcharisto.  (Thank you)  smile

Go to forum: DriverPack Mass Storage

102 Reply by TechDud

(16 replies, posted in Site & Forum Issues And Feedback)

There is one very good reason to deprecate DP_LAN_wnt5_x86-32_8053.7z, and that is because of the Vista drivers somehow included in ..\D\L\I1 & ..\D\L\i3

Also, the weird driver ..\D\L\AM1\amdl7n5.inf has been updated to a proper NT5 driver in the latest LAN [Nightlies].

Am uncertain as of yet of potential impacts to the W2k compatibility of nVidia networking drivers.  <under-study>

Go to forum: Site & Forum Issues And Feedback

103 Reply by TechDud

(75 replies, posted in DriverPack Chipset)

"Weren't there at least a couple of Vista drivers in what you sent there?  I cannot yet confirm, though strongly suspect."

Yes, to correct that, indeed there are.  Despite the fact that the drivers in question are WHQL'ed for 2k, xp, & 2k3, NT5 doesn't have a MSAHCI.inf, like Vista and greater do, as referenced in those few drivers.  The inclusion of those drivers years ago caused some people bluescreens.

Go to forum: DriverPack Chipset

104 Reply by TechDud

(294 replies, posted in DriverPack Mass Storage)

Ah, you could use either Chipset pack with the official MassStorage v12.09 release.
For Known Issues and other notes, check the changelogs & other documents included with the individual packs.

Could you contact your friend and guide him or her to the Device Manager to determine the HWID of that controller from the Details tab?

It should look like PCI\VEN_1102&DEV_xxxx&CC_0106 or 0104.  <Examples>

That information may yet prove useful.
Otherwise,  there is nothing more i can do to identify problems or solutions, let alone reproduce the issue here.
Was the Root Certificates Update included with the install media that finally worked for you?

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

[off-topic]  True friends don't let friends use XP for internet access, in my humble opine.

Debian 7.6 is out now, Ubuntu & co. just released 14.10 utopic.  Dual-boot systems are popular and easy to setup after Windows installation via Disk Manager.  Don't partition whole drive for Windows, use DM to create extended partitions, one about memsize called "swap", and another for the linux partition then install linux, and you get GRUB or similar for bootmenu.  Somehow it also seems Virtualization is another option whilst in linux, and also Wine, yet network access should be disabled for Windows (isolated wired net prolly OK), other than for activation.

Xp is such a downgrade from 8 unless you have a specific application or hardware forcing one to downgrade, or a specific requirement for low system latency unencumbered by a signature based antivirus, yet something behavioral based.

Was 8 really that bad?  Were there problems with an 8.0 recovery partition and 8.1 Update?  [/off-topic]

Go to forum: DriverPack Mass Storage

105 Reply by TechDud

(30 replies, posted in Software)

Am not yet a member there.  It does give me impetus to move towards finalizing the NT5 packs here for a release though.  We are a ways off yet, unfortunately.
Any help i can get is appreciated and often credited in changelogs (FWIW), and possibly fitting, as this is a community project.  Without community assistance and the will for such, any group endeavour is likely to wither and die of apathy at least.

[off-topic](Without having checked for the last few weeks ...)  Things are so dry in Southern California, desalination has become a seemingly overnight staple source of good clean H2O, if i have heard that correctly.  Is cheap solar gaining prominance yet as a source of the tremendous energy needed for evaporation?  Are they using the WOW process yet or "rifled" piping or other technologies to increase efficiency when consuming carbon-based fuels?  (thanks to Bill Duff for the link)[/off-topic]

Go to forum: Software

106 Reply by TechDud

(294 replies, posted in DriverPack Mass Storage)

No, that is not correct, but it seems to be an interesting effect  you might have uncovered there.  Many of the brightest ideas in science have come because of "happy" accidents, or serendipity.

I need for you to post your HWID's please.  There is a tool linked in our signatures.
Post to Pastebin (etc), or here (within code tags).

The usage of nLite, as nice as it is, after having used DPs_BASE on a source is known to at least potentially cause undesired results.  This has been so far unconfirmed on the latest revisions.  Who knows?  Maybe you have accidentally confirmed that too.  Waste is the inevitable unwanted byproduct of haste.  Haste makes eWaste.  Then again, if you have extra time, you might as well rush things, cause you never know exactly what you'll end up with, possibly even a cure for the common cold.  tongue  Another method would have been ...

Part of science is the describing the means with how results are obtained to ensure repeatibility for others attempting to confirm results.  If science isn't your thing, put on your "Sherlock Holmes" hat, por favor.

Do try a seperate integration from scratch with the official release v12.09.  That is key to understanding this affect for your controller.

Aloha.

Go to forum: DriverPack Mass Storage

107 Reply by TechDud

(16 replies, posted in Site & Forum Issues And Feedback)

An update, if it helps.

So far, the only missing 2k drivers comparing DP_LAN 8053 support to the latest [Nightly] for LAN, is an ASIX AX88772 USB-FastLAN.    Also noting that modern atheros devices not included in either.
Having double checked, yet to triple-check, with fixes impending, i can confidently recommend even the current LAN nightly to supersede DP_LAN_wnt5_x86-32_8053.7z for Win2k.

The latest Win2k/NDIS5.0 drivers should install even with stock certs, except for Broadcom b57, which installs a WHQL'ed 2010 revision, however; some drivers need a newer individual certificate (or rootsupd) to validate as WHQL (after manual update - or otherwise adding b57.cat file to system, if i have that right)  The .Inf files have it all sorted out for the most part, which files to use.

For those devices entirely lacking NDIS5.0 support, either a Win9x driver could be sourced, or a non-WHQL Null-Driver created specifically to block Win2k installation.  This would go a long way to preventing the possibility of bluescreens, which could affect either old or new pack, until corrected.

I'll take this all one pack at a time, if i have to.  neutral

Go to forum: Site & Forum Issues And Feedback

108 Reply by TechDud

(524 replies, posted in Windows 7 tools)

Now we are cooking with solar!   big_smile

Go to forum: Windows 7 tools

109 Reply by TechDud

(30 replies, posted in Software)

Awesome!  I can't wait to try it, although need to.
Can anybody share their experience with the XP-SP4 final and integration with DPs_BASE_1006(+) and the current nightly for MassStorage?  Should unofficial SP4 be noted in changelog as "available"?
Thank you.

Go to forum: Software

110 Reply by TechDud

(75 replies, posted in DriverPack Chipset)

Don't make me go through those files again.  Argh.  That is a potential causal factor for "Angina Gluteous Maximus".

Win2k and those certificate issues, and usb2 "landmines" were a tough nut to crack, so-to-speak.
Had to go through it all file by file, double checking sha1 hashes versus .cat files & certificates and all that jazz.
 
You might have a hard time  believing that a significant portion of their drivers do not play well on multiple operating system major iterations.  zawakened, and others, have noted this a while ago.  See:  http://forum.driverpacks.net/viewtopic. … 719#p53719

"Even the WHQL certification for Win2k of the newest files are bogus for non-updated media, at least.  All those newer files are seen as non-WHQL."

  Also, the bigger the Security Catalog, the longer it takes to process which is not so bad when you have few, yet if they were all the latest (again), it would (& did) take noticeably longer for Windows to process drivers.  see:  http://forum.driverpacks.net/viewtopic. … 123#p57123

  (see http://forum.driverpacks.net/viewtopic. … 135#p58135 for last NT5 revision of chipset drivers)

Weren't there at least a couple of Vista drivers in what you sent there?  I cannot yet confirm, though strongly suspect.

As for the existing set in the current [Nightlies] of MassStorage & Chipset; it works, doesn't it?  hmm
I would like to reintroduce the DP_MassStorage-IntelIDE pack & default to PCIIDE in main pack, though.

If you do spot individual driver update possibilities, certainly by-all-means-necessary, point them out.

Go to forum: DriverPack Chipset

111 Reply by TechDud

(294 replies, posted in DriverPack Mass Storage)

Hello again.

Here is one thing you might try.

Extract the contents of DP_MassStorage_wnt5_x86-32_1405176.7z to  the folder DP_MassStorage_wnt5_x86-32_1410261\

  Make a new folder DP_MassStorage_wnt5_x86-32_1410261\D\M\AM\8\1\ and move the contents of ..\D\M\AM\8 to ..\D\M\AM\8\1

    Copy the files from the last official release DP_MassStorage_wnt5_x86-32_1209.7z\D\M\AM8\ to DP_MassStorage_wnt5_x86-32_1410261\D\M\AM\8\

    Using 7-zip v9.20, make a new 7-zip archive called "DP_MassStorage_wnt5_x86-32_1410261.7z" using the settings LZMA-256-32M, and do a test integration from a virgin source, using only DP_MS, Chipset, & LAN.

If it works, link a copy of your version, if you like.  If that doesn't work, then there is more work yet to be done.  That would be to try an integration (ensuring QSC is deselected & cleared if necessary) with DP_MassStorage_wnt5_x86-32_1209.7z

The goal here is to use v3.3.1540.26 for textmode, and for the v3.3.1540.33 to install @T36.
If the driver need ultimately be rolled back, i'll simply archive the updated revision for manual installation.  Whatever works for you.   smile

Go to forum: DriverPack Mass Storage

112 Reply by TechDud

(8 replies, posted in DriverPack LAN)

Staples used XP for POS, it has been alleged elsewhere on 'da net.  Did kmart?  I found a list that included Best Buy, etc.  Even i noted elsewhere back in February that Home Depot had been alleged to be running XP for POS.  How many months will it be until their customers regret parts of their relationship?

I'm starting to see some common threads amongst these, and other, reports.

Quote:  "The end of Windows XP support will also reportedly leave nearly all of the world’s ATMs vulnerable, boding ill for Japan’s banks, which have lost ¥760 million to Internet hackers as of Oct. 15, 2013."
http://www.japantimes.co.jp/news/2014/0 … t8ErRDTldg

Quote:  "“These systems run older operating systems like older versions of Windows Embedded, Windows XP, or even DOS,” he said. “To make matters worse, the network they are deployed to is usually treated as isolated so there are minimal security controls deployed.”"
http://www.cardconnect.com/protecting-p … e-devices/

Why is it Australian retailers don't seem to be getting pinched, for instance?

Quote:  "Pfft, thats nothing.
The NHS in the UK still predominantly uses Windows 98."
http://www.escapistmagazine.com/forums/ … k#20639490

If you like your Windows upgrade plan (linux or MS - dep. on TOS), you can keep it!

Go to forum: DriverPack LAN

113 Reply by TechDud

(30 replies, posted in Software)

ChiefZeke?  Is there any new development on the XP-SP4 front?

Go to forum: Software

114 Reply by TechDud

(16 replies, posted in Site & Forum Issues And Feedback)

That list of affected drivers can be simplified to:

1)      the aforementioned intel 9.4.0.1027 Chipset driver (w2k usb2 etc. buggy as is)

2)      the latest driver for Realtek PCIe LAN (w2k compat.)

3)     the latest Realtek HD-Audio driver (w2k compat.).

Finally found link to those old packs.  Will work to ensure all drivers still included in nightlies, if not updated or superseded.

Go to forum: Site & Forum Issues And Feedback

115 Reply by TechDud

(524 replies, posted in Windows 7 tools)

... also, if i have this correct:

Quote of mr_smartepants:   "This is why we (continually) recommend people to start with a factory-fresh Microsoft hologramed CD image."

I swear the odds are good that if you integrated that nightly with DPs_BASE (QSC=off see QuickStream Cache + delete existing cache folder in DPs_BASE tree) and a virgin source you wouldn't get a $7B blue screen.

Until you give that a try, your existing image is for the most part, only good for ATAPI installs.

If however; after trying a test integration and test install (copy logs setup*.log, dp*.log), please post your HWID's via the HWID's tool linked in many of the signatures here at the following topic to avoid further dilution of this topic with a unrelated matter.  http://forum.driverpacks.net/viewtopic. … 592#p57592

Please start a new topic from time to time, in a relevant area to remain on-topic.
That makes it easier for readers to find the information they need.(though that may sound ironic to some ... d'oh)

Go to forum: Windows 7 tools

116 Reply by TechDud

(524 replies, posted in Windows 7 tools)

If only there were a common methodology for the sake of repeatibility for those using updated sources.
I had been getting away from using stock sources myself for testing since May, and prolly must regress.
Anticipating that biggest impact would be on packages requiring updated MS installer, called by exceptions.

But YES, testing!  If one tests every step, one knows exactly where problems are to be found and corrections made.
That is science, is it not?  ie:  the ability for others to reproduce your own experimental results,.
That reminds me of Fleischmman & Pons, for some reason.

Go to forum: Windows 7 tools

117 Reply by TechDud

(16 replies, posted in Site & Forum Issues And Feedback)

For sake of repeatibility, there are some common drivers that could serve as examples.

For instance, the intel v9.4.1027 chipset drivers.  They include 2000 in the Security Catalog, yet they don't appear to install (manually) without latter certs.
  (win2k usb non-functional due to WHQL-signed editing errors - also take longer to verify than older sigs - i had to go file, by file to check & ... nevermind)

(from latest DP_Chipset_wnt5 nightly):
Certificate Issues:
- i\ drivers from 2013 and newer require "Microsoft Root Certificate Authority" CA (not incl. in W2k)
- i\6\HECI*.sys SymantecTimeStampingServicesCA-G2 (issued by GeoTrustGlobalCA)
- TM\Z\I386\tcm.sys has an expired certificate issued by zteic design co.,ltd
- VB\Balloon.*, VIOSER.*, blnsvr.exe, U3\FLxHCI*.sys
     VerisignClass3PublicPrimaryCertificationAuthority-G5 (issued by Microsoft Code Verification Root)

There are also intel "chipset" drivers in the latest nightly for MassStorage, yet have included 2k versions that need not newer certs.

Certificate Issues - XP-SP3 (before any updates):
         - recommend RootsUpd.exe is added to $OEM$\cmdlines.txt
		        or added to winnt.sif @ [GUIRunOnce] section DetatchedProgram="" (include Arguments="")
 - AM\a\1\rccfg.sys & rcraid.sys, AM\a\2\rcraid.sys, As\1\asahci32.sys & asstor32.sys,
   C\HpAHCIsr.sys, I\0\iSSetup.sys, VB\VIOSTOR.SYS
      VerisignClass3PublicPrimaryCertificationAuthority-G5 (issued by Microsoft Code Verification Root)
 - H\r750.*
      SymantecTimeStampingServicesCA-G2 (issued by GeoTrustGlobalCA)
 - I\ drivers from 2013 and newer require "Microsoft Root Certificate Authority" CA (not incl. in W2k)
 - V\VIDEX32.SYS, xfilt.sys
      VIATechnologiesInc. - certificate has expired or is not yet valid
Certificate Issues - XP-SP3 (post-updates):
 - L\msas2k3.* LSI Certificate revoked

Also, many of the latest LAN drivers require a selection of certificates for validation.

(from latest DP_LAN_wnt5 nightly):
Certificate Issues:
- newer drivers (incl. Atheros l1c51x86, Broadcomm bnxcdx, Intel e1c5132, e1e5132, e1q5132,e1r5132, ianswxp, ixn5132,
     ixt5132, Marvel yk51x86, Realtek rtu30nicxp & rtenic/rtenicxp, SMSC netx500 .cats, VirtualBox netkvm)
        use "Microsoft Root Certificate Authority" for digital signing (not included in w2k).
     Atheros l1c51x86, Broadcomm bnxcdx, Intel e1c5132, e1e5132, e1q5132,e1r5132, ianswxp, ixn5132,
     ixt5132, Marvel yk51x86, Realtek rtu30nicxp & rtenic/rtenicxp, & VirtualBox netkvm (etc) rely upon other Certificates not included in xp/2k3

That is, if i have that right.


The line about adding rootsupd.exe to one's cmdlines.txt seem incorrect, as that garners errors in setuperr.log, as does expanding rootsupd and manually executing it in a rootsupd.cmd (listed in cmdlines.txt).
Also, i have not yet been able to discern if they install @T33-6 like hoped.  Have kept logs....

Go to forum: Site & Forum Issues And Feedback

118 Reply by TechDud

(11 replies, posted in Other)

Bob's your uncle.  No soup.  Thank you.  smile

Go to forum: Other

119 Reply by TechDud

(16 replies, posted in Site & Forum Issues And Feedback)

It would appear that i was wrong, Kurt_Aust.  (I didn't claim to be the brightest LED in the chain though.)

Few people appear to have covered 2k updates, like the aforementioned person.
  I previously neglected to mention the few, such as yourself.

Do feel free to link to your work if you like, as i wasn't aware of your efforts.
  Others may find your updates helpful too, whom may also be previously unaware of your work.


Whilst you are here (presumably), am hoping you can help.

Am looking for a way to slipstream or otherwise install a RootCertificates update before Device Driver detection on a Windows 2000 Setup.

Newer valid windows 2000 drivers are either signed with "Microsoft Root Certificate Authority", or "Verisign Class 3 Public Primary Certification Authority - G5" and aren't seen as WHQL until after the update is installed (unconfirmed).  This also affects XP, and probably Win2k3 as well.

Have tried entering it in @T36 via the unattend file & $OEM$ folder, yet an error always results including in setuperr.log.


I hope to include any recommendations within the "Certificate Issues" sections of the DriverPacks changelogs, along with credit for such.  Thank you for your time and consideration.

Go to forum: Site & Forum Issues And Feedback

120 Reply by TechDud

(75 replies, posted in DriverPack Chipset)

Like Colin Hay (or other Men At Work) might be heard to remark "It's just overkill".  :lol

CIR drivers seem to belong in HID, along with hotkey drivers.
Where do IRDA drivers belong?  They can impair battery cycle duration via Windows "IR Discovery" service.
Can i isolate them in a small IRDA pack?

Go to forum: DriverPack Chipset

121 Reply by TechDud

(1 replies, posted in DriverPack Mass Storage)

Greetings and salutations, djuka88!

The MassStorage drivers for nVidia were last modified by mr_smartepants some years ago.  It may have been that the nForce 520/560 Chipsets (at least two RAID HWID's) had to be sacrificed for the sake of the widest HWID support.  His solution has been widely tested.

He was also kind enough to leave a means to research possible fixes, in his thread titled "[FEEDBACK-REQ] Nvidia Mass Storage test packs - TESTERS NEEDED".

It would seem that if confirmed, this info should be added to the latest MassStorage [Nightlies] as a "Known Issue", at least.

A regular ATAPI installation should work though.
If RAID is your requirement, surely a newer chipset that at least supports AHCI (TRIMcheck) would be a more efficient solution, would it not?

Does your motherboard have the latest BIOS?  Do note that bad flashing may "brick" your board, and should only be done at your own risk.

Please post the affected HWID's, if you are able (perhaps from licensed Vista-7).

Go to forum: DriverPack Mass Storage

122 Reply by TechDud

(11 replies, posted in Other)

Bonjour, monsieur CyberHaddad.
No need to translate, and no need to apologize for the usage of French or any other language.

It would appear the Graphics driver you are attempting to install is not properly WHQL signed.

In the DP_Graphics_D_wnt5_x86-32_1409241.7z "nightly", that driver is contained in D\G\I\c\, and yes it would appear the ialmnt5.inf has been modified in October of 2008 to coexist with other drivers in the pack.

[Intel.Mfg]
; %iMGM%  = i852GM,  PCI\VEN_8086&DEV_3582
%iSDG%	 = i865G, PCI\VEN_8086&DEV_2572
; %iGDGD0% = i915G0, PCI\VEN_8086&DEV_2582
; %iGDGD1% = i915G1, PCI\VEN_8086&DEV_2782
; %iALVD0% = i915GM0, PCI\VEN_8086&DEV_2592
; %iALVD1% = i915GM1, PCI\VEN_8086&DEV_2792
; %iLPGD0% = i945G0, PCI\VEN_8086&DEV_2772
; %iLPGD1% = i945G1, PCI\VEN_8086&DEV_2776

...

iSDG          = "Intel(R) 82865G Graphics Controller"

However; it would appear that nobody backed up the original ialmrnt5.inf.
Will you paste within code tags, or otherwise make it available for me to include, s'il vous plaît.
I can confirm the sha1 hash within the Security Catalog on this end.

Perhaps now that HWID's are specified in the DriverPacks_Graphics_D_wnt6_x86-32.ini file,  that entire WHQL driver could be archived installed utilizing a DPs_FnShR exception, so that user-input is no longer necessary.  That might be a detriment to BartPE/UBCD4Win integrators, yet that driver was only added experimentally and no feedback was presented, if i remember correctly.  That is to say, the downside of such fix should be minimal.

@OverFlow:  Was that "experiment" ill-implimented by turning on PE support on all drivers?  Don't competing files end up in the same i386 folder at the end (and thereby machine-incomprehensible "file soup")???

Go to forum: Other

123 Reply by TechDud

(30 replies, posted in 3rd Party DriverPacks)

DP_DriveProtection_wnt5_x86-32_1408135.7z - 27.57 MB   87C2E89F359187F2651E08F9D16FB13CDF3A566D

Go to forum: 3rd Party DriverPacks

124 Reply by TechDud

(5 replies, posted in 3rd Party DriverPacks)

DP_Bluetooth_MS-Misc_wnt5_x86-32_1408131.7z - 13.44 MB   343E081E0310F4DCCC9A903B33395CD877A37500

edit: link removed - updated below

Go to forum: 3rd Party DriverPacks

125 Reply by TechDud

(30 replies, posted in Software)

http://www.zdnet.com/want-windows-xp-sp … 000033030/
Had wondered why a few hundred copies of MassStorage had been downloaded since August.  That caught my eye.

Slipstreaming it seems staightforward.  There are a number of textmode bugfixes with SP4, from notes in the Topic.  The Windows XP SP4 security enhancements are a good addition as well, imho.

I do see that you had sucessfully tried DriverPacks [Nightlies] with a previous SP4 beta, about a year ago Chief.
Am hoping it has helped.  smile

Go to forum: Software