Search options (Page 16 of 64)

2013-10-06 05:03:32

Hello!

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!

2013-10-02 13:30:02

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?

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

2013-10-02 13:06:50

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.

2013-10-02 12:52:16

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."
Quoted from: http://masterrussian.com/blbasic.shtml

2013-09-25 05:57:29

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.

2013-09-25 05:34:03

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.

2013-09-24 15:30:50

Updated Asmedia SATA driver to v1.4.1.0.

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

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

2013-09-24 15:28:10

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

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

2013-09-24 15:24:47

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!

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

edit: link removed - updated near topic end

2013-09-24 13:43:33

Hello again!

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

2013-09-24 06:57:21

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

I have zero familiarity with sysprep.

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.

2013-09-23 14:01:57

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.

2013-09-23 13:44:08

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?

2013-09-23 09:30:31

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.

2013-09-23 08:45:47

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

"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

2013-09-23 08:41:20

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?

2013-09-23 08:29:21

Cheque cashing policy @ local supermarket:

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

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.

2013-09-22 10:03:53

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

2013-09-21 09:57:53

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

2013-09-21 09:54:36

Hello and welcome to the forum!

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?

2013-09-20 09:21:47

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.

2013-09-12 12:57:45

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!

2013-09-10 19:03:51

[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]

2013-09-10 17:13:42

Hello and greetings!
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.

2013-09-08 17:55:16

mr_smartepants was very generous with his time by regularly updating these packs for more than a couple of years, up until about a year ago.
Unfortunately, his time was constrained by certain "RL" factors and was unable to continue.
In the current climate of economic depression few really can afford to invest the large amounts time required to do a competent and comprehensive job like he did.
Putting food on the table takes precedence (hopefully uncontaminated).

Also, a large percentage of people have focused on tablets and those stuporing "smart"phones.
Greed and self-interest may have also been factors, loosely akin to "Tragedy of the Commons".

Still waiting to hear back from anybody concerning a possible NT6 driverpack collaboration.
It's almost been a month since the following was posted, with no reply.

"Why not inquire to bigfoot, what may need be done?
Is it not better to work in collaboration than it is to stumble about in competition?
A collaboration would allow for more participation from others, if agreed by bigfoot.
Let us not step upon his toes.
Remember the etimology of the acronym "T.E.A.M."
That is, "Together Everyone Achieves More"!"
quoted from: http://forum.driverpacks.net/viewtopic. … 643#p52643

Unfortunately, it seems that my potential participation may be incredibly difficult, as my time becomes further constrained.

Yet i digress.

bigfoot has some updated NT6 x64 packs available in that section of this forum.

If you are looking for NT5 drivers, check each NT5 subheading for updated driverpacks.
For example: DriverPacks.net Forum --> DriverPack Chipset --> [Nightlies] DP_Chipset_wnt5_x86-32_1304-1308 - Public

Babyboy made updated DP_Graphics NT5 driver updates possible via his generous donation of time and fearless dedication in testing potential updates. To him and especially mr_smartepants, OverFlow and Bâshrat the Sneaky, i owe a great debt of gratitude.
Without any one of those aforementioned people, progress would have been impossible.

"Smile! It can confuse certain biometrics."

Search options (Page 16 of 64)

Posts found [ 376 to 400 of 1,599 ]

376 Reply by TechDud 2013-10-06 05:03:32

Re: Bluetooth pack for win7 (& other OS' - see Post 8 by josywong) (13 replies, posted in 3rd Party Vista / 7 DriverPacks)

377 Reply by TechDud 2013-10-02 13:30:02

Re: [REQ] Broadcom 43142 Wireless LAN Lenovo B590 (6 replies, posted in DriverPack WLAN)

378 Reply by TechDud 2013-10-02 13:06:50

Re: [REG] Lenovo Energy Management Driver (6 replies, posted in DriverPack Chipset)

379 Reply by TechDud 2013-10-02 12:52:16

Re: "Satellite-Debris"; misc news (12 replies, posted in Other)

380 Reply by TechDud 2013-09-25 05:57:29

Re: [REG] Lenovo Energy Management Driver (6 replies, posted in DriverPack Chipset)

381 Reply by TechDud 2013-09-25 05:34:03

Re: [Nightlies] DP_MassStorage_wnt5_x86-32_1304-1412 - Public (294 replies, posted in DriverPack Mass Storage)

382 Reply by TechDud 2013-09-24 15:30:50

Re: [Nightlies] DP_MassStorage_wnt5_x86-32_1304-1412 - Public (294 replies, posted in DriverPack Mass Storage)

383 Reply by TechDud 2013-09-24 15:28:10

Re: [Nightlies] DP_Phone-Mobile_wnt5_x86-32_1307-1409 - Public (8 replies, posted in 3rd Party DriverPacks)

384 Reply by TechDud 2013-09-24 15:24:47

Re: [Nightlies] DP_Chipset_wnt5_x86-32_1304-1501 - Public (75 replies, posted in DriverPack Chipset)

385 Reply by TechDud 2013-09-24 13:43:33

Re: [REG] Lenovo Energy Management Driver (6 replies, posted in DriverPack Chipset)

386 Reply by TechDud 2013-09-24 06:57:21

Re: [Nightlies] DP_MassStorage_wnt5_x86-32_1304-1412 - Public (294 replies, posted in DriverPack Mass Storage)

387 Reply by TechDud 2013-09-23 14:01:57

Re: [Nightlies] DP_MassStorage_wnt5_x86-32_1304-1412 - Public (294 replies, posted in DriverPack Mass Storage)

388 Reply by TechDud 2013-09-23 13:44:08

Re: [Nightlies] DP_Chipset_wnt5_x86-32_1304-1501 - Public (75 replies, posted in DriverPack Chipset)

389 Reply by TechDud 2013-09-23 09:30:31

Re: [Nightlies] DP_MassStorage_wnt5_x86-32_1304-1412 - Public (294 replies, posted in DriverPack Mass Storage)

390 Reply by TechDud 2013-09-23 08:45:47

Re: [Nightlies] DP_Chipset_wnt5_x86-32_1304-1501 - Public (75 replies, posted in DriverPack Chipset)

391 Reply by TechDud 2013-09-23 08:41:20

Re: [IMPL] HP 8540w IDT High Definition Audio Codec (7 replies, posted in DriverPack Sound)

392 Reply by TechDud 2013-09-23 08:29:21

Re: [Nightlies] DP_MassStorage_wnt5_x86-32_1304-1412 - Public (294 replies, posted in DriverPack Mass Storage)

393 Reply by TechDud 2013-09-22 10:03:53

Re: [Nightlies] DP_MassStorage_wnt5_x86-32_1304-1412 - Public (294 replies, posted in DriverPack Mass Storage)

394 Reply by TechDud 2013-09-21 09:57:53

Re: [Nightlies] DP_MassStorage_wnt5_x86-32_1304-1412 - Public (294 replies, posted in DriverPack Mass Storage)

395 Reply by TechDud 2013-09-21 09:54:36

Re: [IMPL] HP 8540w IDT High Definition Audio Codec (7 replies, posted in DriverPack Sound)

396 Reply by TechDud 2013-09-20 09:21:47

Re: [Nightlies] DP_MassStorage_wnt5_x86-32_1304-1412 - Public (294 replies, posted in DriverPack Mass Storage)

397 Topic by TechDud 2013-09-12 12:57:45

Topic: Learning Python programming language, thanks to Cody Jackson, et al! (2 replies, posted in Other)

398 Reply by TechDud 2013-09-10 19:03:51

Re: [REQ] Include USB3 Massstorage driver for XP? (20 replies, posted in DriverPack Mass Storage)

399 Reply by TechDud 2013-09-10 17:13:42

Re: i need your help not encounter the drivers sata ahci for xp! (7 replies, posted in DriverPack Mass Storage)

400 Reply by TechDud 2013-09-08 17:55:16

Re: New OS discussion forums added (12 replies, posted in News)

Posts found [ 376 to 400 of 1,599 ]