376 Reply by TechDud

(7 replies, posted in Windows 7 Discussion)

Hello & welcome to the DriverPacks forum!     smile


In theory, it should only install drivers for hardware that exists on the machine you run Setup upon.

In reality, there can be some drivers that install on all hardware.
  This is rare though.
    Ordinarily, if you do not have the hardware, you cannot use the driver.
      Virtual environments can be an exception to this, which we don't officially support (IIRC).

  Great effort and care is taken to weed out these so-called "super-generics", such as ATi's PCIe driver, Matrox's Extio drivers (which have been fixed in new revisions of their drivers), or "The Three Amigos" associated with Marvell's SATA drivers (mv61xxmm, mv64xxmm, mvxxmm).

These afflicted NT5.x (previous to Vista).  I am uncertain if NT6.x (Vista and up) are affected.

Perhaps somebody else could speak to this.     hmm


Oh, that reminds me, i neglected to add the "¡Three Amigos!"  to my "Known Issues" List for NT5's DP_MassStorage.

Go to forum: Windows 7 Discussion

377 Reply by TechDud

(13 replies, posted in 3rd Party Vista / 7 DriverPacks)

Hello!     smile


The DriverPacks have been created and maintained by various members of the community.

I sincerely hope that you start such a pack.
No one person can hope to do all packs on their own.

If you do decide to start a new pack, start small.
  Start with what hardware you have on-hand from a primary chipmaker such as Broadcom or Realtek.
    It will make testing and verification much easier for you.

Be advised that only OEM links are used to gather such drivers.
  Do keep track of the links where you gather drivers, it adds further credibility.
    Think of it like noting your sources in a thesis.

Third-Party sites such as station-drivers, as good as they likely are, are indeed frowned upon here.
  It is for our audience that this is done.

Bluetooth might not be advised to be integrated into install media, yet rather installed post-Setup by SAD3.
  If i remember correctly, the MS Bluetooth stack need be installed first for at least NT5.
    It may be similar with NT6.x (Vista and up).

The utilities included for each chipmaker probably need entries in an associated "Bluetooth.Ini" file, to be processed by DPs_Fnshr within SAD3.
  There will be some trial and error there.

You will find that many here are very willing to lend assistance on any questions you will inevitably have.


Good luck, and happy hunting!

Go to forum: 3rd Party Vista / 7 DriverPacks

378 Reply by TechDud

(6 replies, posted in DriverPack WLAN)

Broadcom WLAN {DriverVer=09/26/2012, 6.30.59.81} already included in ..\Le\bcmwl5.inf

Is it not working?

  Noting that additional country support can be added by creating a registry file to contain entries in the [common.reg] section of the .Inf.  This maintains WHQL status by not requiring modification of the .Inf file.  This can ensure proper channel ranges if used properly.  If used improperly, it could be illegal in your jurisdiction, illegal for export, and/or potentially harmful to emergency service providers and/or medical equipment and others.  Therefore, i have not included such registry files.


Is there any interference from previous utilities in DP_WLANutils_wnt5_x86-32_1307252.7z?     hmm

  Also noting that the same utility from the package you linked is contained within ..\Le\BCMle081.exe
    There is one difference though.
      I have taken the liberty to update the VisualC package (2011 vs 2006).

Go to forum: DriverPack WLAN

379 Reply by TechDud

(6 replies, posted in DriverPack Chipset)

Why close it?  This is not yet resolved.
We may not be the only people to wonder about this.
  It is a good topic.  It should be moved to Chipset though.  Done.

Go to forum: DriverPack Chipset

380 Reply by TechDud

(12 replies, posted in Other)

During US Government and consequently NASA shutdown,
the Astronomy Picture of the Day can be viewed in English at the following link.
  If the date is still listed on that page as 2010, ignore this as the individual pages should read 2013 starting with October 1st.

http://asterisk.apod.com/library/APOD/A … irror.html

Alternate links and additional languages (also listed two posts above) can be found here.
Note that some links there are in English, such as those from Australia and Russia.

"Bal'shoye spaseeba."  "Da sveedaneeya."     smile

Quoted from:  http://masterrussian.com/blbasic.shtml

Go to forum: Other

381 Reply by TechDud

(6 replies, posted in DriverPack Chipset)

Hey Ra!  How's your travels?

IIRC, that version of the driver was in the official Chipset release, a year ago.
========================================================
Does the driver within DP_Chipset in the folder ..\L\ interfere with the package you linked, cheche?

It does seem likely that the newer driver in DP_Chipset could remain after installation of that package you linked.

I obtained that from http://download.lenovo.com/pccbbs/mobiles/00ee25ww.exe.  It might work with your notebook, yet it may cause issues.  It does appear to be simply an updated version to include support for newer models.
If it does work, and you dare to try it (at your own risk, of course), the utility could be included for installation utilizing DPs_Fnshr.

There was an even newer driver withing DP_Misc, yet it was removed as it was WHQL'ed for 7_x64 and the PE Header of the executable indicated 64bit as well.  It's probably still in the official 3rd-party DP_Misc.  I was down for a while a year and a half ago because i made the mistake of installing an unrelated 64bit driver on my 32bit windows main machine.  It was a fabulous disaster, and i was unable to recover that install.

Go to forum: DriverPack Chipset

382 Reply by TechDud

(294 replies, posted in DriverPack Mass Storage)

Within the .Ini, any driver that specifies disableIfOS="w2k", skipIfOS="w2k", skipIfOS="w2k3", skipIfOS="w2k,w2k3" or undefined could be candidates.
Any entry that specifies skipIfOS="wxp" (including combinations) would probably be best avoided.

Go to forum: DriverPack Mass Storage

383 Reply by TechDud

(294 replies, posted in DriverPack Mass Storage)

Updated Asmedia SATA driver to v1.4.1.0.     smile

DP_MassStorage_wnt5_x86-32_1309231.7z - 9.45 MB   2d509a928e39b206eb276ea8570f4129925c40cf

* - edit: link removed - updated near last post in this topic

Go to forum: DriverPack Mass Storage

384 Reply by TechDud

(8 replies, posted in 3rd Party DriverPacks)

Added many models from HTC, LG, Motorola, Samsung, Sony-Ericsson, & ZTE.     smile

Most of these will require the KB fix listed in the first post of this topic.

DP_Phone_wnt5_x86-32_1309201.7z - 10.2 MB   bff36fed97650e374b284687c79dc90181083a48

* edit:  link removed - updated below

Go to forum: 3rd Party DriverPacks

385 Reply by TechDud

(75 replies, posted in DriverPack Chipset)

Rolled-back Intel USB drivers to stamp out the bugs.

Newer drivers that have no precedent have been archived in ..I\1_Original_Erroneous_IntelUSB_drivers.7z to prevent installation on Win2k.  The generic Windows driver will be installed instead.

All unofficial Chipset packs have likely suffered from this, since after the Officially released DP_Chipset_wnt5_x86-32_1209 (including DP_Chipset_wnt5_x86-32_1211b5.7z).

Thanks again to zawakened for confirming this issue!     smile


DP_Chipset_wnt5_x86-32_1309231.7z - 9.09 MB   8b152ccadba386d2c70c97695541f28b590bf2fc

edit:  link removed - updated near topic end

Go to forum: DriverPack Chipset

386 Reply by TechDud

(6 replies, posted in DriverPack Chipset)

Hello again!     smile

That is an older driver than what is contained in DP_Chipset.
  Does that not work for you?

Go to forum: DriverPack Chipset

387 Reply by TechDud

(294 replies, posted in DriverPack Mass Storage)

"how can I know which driver will work with XP sysprep masstorage, and which will not?"

I have zero familiarity with sysprep.     hmm

  One could conceivably use the "... IfOS=" variables in the MassStorage.Ini as a guide.
    The Security Catalogs would offer more info, as well as the .Inf files themselves.

Go to forum: DriverPack Mass Storage

388 Reply by TechDud

(294 replies, posted in DriverPack Mass Storage)

Here is where the offending BSOD may ultimately be from:

DP_MassStorage_wnt5_x86-32_1209:  DriverPack_MassStorage_wnt5_x86-32.ini

ms_1_tag="iastor7"
ms_1_sysFile="iastor7.sys"

DP_MassStorage_wnt5_x86-32_1309031:  DriverPack_MassStorage_wnt5_x86-32.ini

ms_1_tag="iastor9"
ms_1_sysFile="iastor.sys"

Both approaches add an iastor?.sy_ file into i386, yet the latter has no requirement for a separate iastor?.sys file in the DriverPack.

Edit the .Ini and copy the file, then rename it to "iastor9.sys" and recompress.
That may end the BSOD, unless the quotes in the previous post are indeed at issue.


  That's my theory and i'm sticking to it.     wink

Go to forum: DriverPack Mass Storage

389 Reply by TechDud

(75 replies, posted in DriverPack Chipset)

Editing the .Inf files is OK except for the fact that it will break WHQL/WHCK signing.
This could have the undesired effect of having the built-in OS drivers installed instead for at least older chipsets.
It is also possible that the drivers in the I\2k folder are installed instead where the HWID's match.

There is also the fact that some Intel USB drivers have registry entries that are not present in the newer driver revisions.

zawakened wrote:
TechDud wrote:

I look forward to crediting you in the changelog.

"It's not necessary, really!"

I appreciate contributions from others and would find it an err on my part to not at least ask if it is OK to give credit where credit is due.  If you do not want to be credited, that is OK too.

May i have your permission to credit you in the changelog?

Go to forum: DriverPack Chipset

390 Reply by TechDud

(294 replies, posted in DriverPack Mass Storage)

IIRC, somebody else had a similar issue, yet it worked on a real system.
It was a different HWID though.
Ah, here's the relevant thread:  http://forum.driverpacks.net/viewtopic. … 978#p51978

mr_smartepants wrote:

"Testing within a VM will always have pitfalls with drivers because the hardware is not always presented to the virtual environment in the correct way.
One way to isolate the VM as the source of the problem is to try your build on a live-metal machine using a spare HDD (all other HDD disconnected).
If it works on live-metal but crashes in VM then you know the source of the problem.

In my opinion, VMware is a much better VM than VirtualBox.  I used to use VB exclusively but eventually moved to VMware for speed/compatibility."

cdob wrote:

"Newer iastor driver version failed in the past, appearantly Intel dosn't support a VirtualBox device officially."
http://www.msfn.org/board/topic/107504- … d-drivers/

Chipset for "better SATA compatibility"?  Probably no.
  Tis for other "assorted good & plenty" associated with CPU/NB/SB.

Go to forum: DriverPack Mass Storage

391 Reply by TechDud

(75 replies, posted in DriverPack Chipset)

Thank you for confirmation of this bug!
I look forward to crediting you in the changelog.     smile

"It's strange that Intel didn't fix that till now v9.4 of Chipset Installation Utility"

Not from what i've seen.  The bugs are still present, although rearranged somewhat.
I downloaded v9.4.4.1006 and there is no change from previous versions.

Intel even notes in their changelog that they have "fixed" this.  Sad, eh?

Intel wrote:

"Issues Resolved in 9.4.4.1006

ID    Description
1    Updated sections names; Fixed errors in USB INF files; Various string fixes."

It would seem that the usb files need be rolled back to those which were originally in DP_Chipset_wnt5_x86-32_1209.  Had to include those older files, or Win2k USB 2.0 wouldn't work!

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.


Sadly, i cannot find an OEM link for v9.4.4.1006.  It is only available on Station-drivers, and that is a "no-go" for inclusion of drivers for newer hardware.  C'est la vie!  Maybe they will finally get it right with v9.5.0.1069!

Tried an unsafe search of Intel, and that didn't help.
  Ref:  https://encrypted.google.com/search?q=s … p;filter=0

Go to forum: DriverPack Chipset

392 Reply by TechDud

(7 replies, posted in DriverPack Sound)

The NT6 (Vista/7/8.x) Audio forum section is here --> http://forum.driverpacks.net/viewforum.php?id=36

Please start a new topic there and post any further info or questions there.

Sadly though, if you are not using DriverPacks, it makes it difficult to assist.

Have you tried SAD3 to install Audio x64 v11.11?

Go to forum: DriverPack Sound

393 Reply by TechDud

(294 replies, posted in DriverPack Mass Storage)

Cheque cashing policy @ local supermarket:

"To err is human, to forgive $30."     lol

Some of the greatest discoveries in science have been made by accident!

As adults, it is sometimes impossible to foresee the value of play.  We tend to ignore it.
At least it helps form new pathways in our "plastic" brains, hopefully denying dementia, etc.
=================================================================

"If installing it on VirtaulBox with the SATA option then i get a BSOD and with "DP_MassStorage_wnt5_x86-32_1209" i don't get a BSOD"...

What do you mean by "SATA option"?


If and when you have a spare SATA drive, give installation a try on "real iron".
Am venturing to complete changes to DP_Phone.  (ETA a couple of days)
There will be a new DP_Chipset by then to fix errors with Intel uHCI drivers.
=======================================================
That delay for startup has been present since early July, if i remember correctly.
I haven't been able to isolate it.  There may be a restart involved, or the effect of one.

Any assistance that leads to a solution gets credited in the changelog.     smile

Go to forum: DriverPack Mass Storage

394 Reply by TechDud

(294 replies, posted in DriverPack Mass Storage)

Awesome screen captures!  How did you do that?

STOP $7A:

MS wrote:

"The KERNEL_DATA_INPAGE_ERROR bug check has a value of 0x0000007A. This bug check indicates that the requested page of kernel data from the paging file could not be read into memory. "
...
"0xC000000E, or STATUS_NO_SUCH_DEVICE, indicates a hardware failure or an incorrect drive configuration. Check your cables and check the drive with the diagnostic utility available from your drive manufacturer. If you are using older PATA (IDE) drives, this status code can indicate an incorrect master/subordinate drive configuration."
...
"Another common cause of this error message is defective hardware or failing RAM.

A virus infection can also cause this bug check."

     Quoted from: http://msdn.microsoft.com/en-us/library … 85%29.aspx

I have also seen allegations that a faulty P/S can cause such issues.


First off, remove and/or disable any unnecessary items such as cellular phones, hubs, cardreaders, cameras, portable hard drives, etc.
Use an integration (preferably on a DVD RW so as not to end up with a stack of discs) containing only DP_Chipset_wnt5_x86-32_1308271.7z, DP_MassStorage_wnt5_x86-32_1308271.7z & DP_Misc_wnt5_x86-32_1308272.7z

Double-check that the source you use is unmodified and otherwise "virgin".


Now, if your confidence in the HDD is less than 100%, one could run the drive manufacturer's tools to do an advanced test of the drive.  Likewise, if your confidence in the RAM is not 100%, MemTest could be executed to be certain; beware that it will likely output much more heat than normal usage.

If those are not of issue, one could ensure that the system has the latest BIOS/uEFI installed.  Just beware that improper updates can 'brick' your hardware.  A battery may be required if this is a portable.


If you still experience a BSOD, when does it occur?
  Also link to the driver download page for your Toshiba, please.
    Either way, i have a cunning plan, and an update for DP_Phone which now includes your Sony-Erricson (et al).

Go to forum: DriverPack Mass Storage

395 Reply by TechDud

(294 replies, posted in DriverPack Mass Storage)

Curious; were you attempting to install from CD/DVD, USB-stick, or USB-CD/DVD?
Also wondering what the specific BSOD code is.

Go to forum: DriverPack Mass Storage

396 Reply by TechDud

(7 replies, posted in DriverPack Sound)

Hello and welcome to the forum!     smile

That may be because this solution is for NT5.  Please start a new topic in the NT6 section of this forum.
Doesn't HP have support for their audio solution?

Also, are you integrating DriverPacks or attempting to install post-Setup with SAD3?

Go to forum: DriverPack Sound

397 Reply by TechDud

(294 replies, posted in DriverPack Mass Storage)

One thing that does catch my eye is your inclusion of the DP_CPU pack which is obsoleted by the newest DP_Chipset.

Also, the "Intel(R) USB 3.0 eXtensible Host Controller" should be set to legacy or USB 2.0 in your BIOS/uEFI.  Intel's USB 3.0 is not compatible with NT5.  If you cannot switch, a dummy driver (nul op) will be installed with DP_Chipset.

In addition, I would include DP_Graphics_B_wnt5_x86-32_1307261 & DP_Misc_wnt5_x86-32_1308272.

within PantUSB3.inf, Intel wrote:

"; **           FileName: PantUSB3.inf                                           **
; **           Abstract: Null driver for Intel(R) USB 3.0 devices               **
; **        Last Update: July 25, 2013 (Version 9.3.0 Build 1029)               **"

Before you do anything, please state the type of media you are attempting to install from and the $ code for the BSOD.

Thank you for bringing this to my attention.

Go to forum: DriverPack Mass Storage

398 Topic by TechDud

(2 replies, posted in Other)

Gearing up to learn python, for mathematical and statistical functions.

One source i remember was the inadvertently censored book from the author's web site.  http://forum.driverpacks.net/viewtopic. … 380#p49380

Free new edition PDF --> http://python-ebook.blogspot.co.uk/2013 … lable.html

Can anyone please provide any basic instruction including or excluding what may be in that book, "Python Programming, 2nd Edition"?

I need somewhat of a "reorientation" after a 25+ year absence of programming, excepting the last 6 months or so.
  Had some basic experience with 6809E (1MHz) assembler, MS-Disk-Extended-BASIC and TurboPascal on 6805. 

Windows 1.0 just was beyond my grasp then via the Coco3.

Surprisingly, there is an update to the "Coco" legacy with an emulator known as "Coco4", where an addon I/O board will update the old CoCo3 hardware.

Quote:
                  "CoCo 4   Making the Computer Personal Again!"

Amazing!  I didn't imagine working with that type of pre-x86 hardware would ever be within reach.
I wonder if any Aluminium electrolytic capacitor replacements would be advisable along with any in-built opto-isolators and  surge-arrestors?
Servicing heat-sinks and possible Voltage Regulator upgrades could cut power consumption somewhat.

Things should work a little faster now.  That is, excepting the floppy drives!     smile

Go to forum: Other

399 Reply by TechDud

(20 replies, posted in DriverPack Mass Storage)

[off-topic]
This is probably not what killed your beloved pet.
I could not help but think of you though, OverFlow.

http://www.ohio.com/news/still-no-defin … s-1.426574
thanks to xdrfox; originally posted here --> http://optimalprediction.com/wp/general … ment-15928

This was another post which very strongly reminded me,
yet i needed to wait to post a link to this eyewitness comment, out of respect.
I know not what region mairs is from.

http://enenews.com/water-with-pieces-of … ent-377118

I post, not to spread fear, but to spread knowledge.
Knowledge can dispel fear.
  If this knowledge can prevent or help recognize and treat illness,
    it may dispel further suffering, loss and subsequent fear.
[/off-topic]

Go to forum: DriverPack Mass Storage

400 Reply by TechDud

(7 replies, posted in DriverPack Mass Storage)

Hello and greetings!     smile
Thank you for joining the forum.

0) First and foremost.  Ensure you have a valid license for XP.
1) use latest Chipset & MassStorage, and integrate with DPs_BASE into unmodified XP disc, copied to a folder
2) burn a new disc
3) At the initial VAIO screen, press the F2 key.
4) in your BIOS, set USB 3.0 to legacy (USB 2.0)
5) turn off "Secure Boot" (if available)

If that doesn't work, please post your DPs_BASE log.

Note:  Intel RST v11.2.0.1006 is utilized for Textmode in MassStorage, Sony supplies v11.0.0.1032
     also noting that the Sony Wireless State Device Driver (*SNYA008) is not included for NT5
              (it is for 8_64bit)


Novus Ordo?  What "new order"?  There is nothing new under the sun.

Go to forum: DriverPack Mass Storage