Search options (Page 33 of 64)

Audio add-on card, or USB audio as alternatives?  If the driver doesn't exist yet, what can i do other than to wait on it to be publicly released.  I tend to think that a modified driver .Inf file may not be enough here.  What can one do other than to gather a bunch of driver "candidates" and installing them manually (as opposed to Automatically).  Use Explorer to search the *.inf files for your HWid VEN_14F1&DEV_50A1 for any candidates already in DP's.

  Perhaps another OEM has already released it; with or without your specific HWid included.
That is truly the "game"; finding relevant drivers!

If you do manage to find a working driver, don't forget to request us to add it to the DriverPacks.
If i find a candidate for you, i will not hesitate to post it here.

PS:  I wonder if your BIOS is up-to-date.  If you are unfamiliar with this procedure and it's risks, skip it.

PPS:    I do see that Fujitsu has an [ H] package WHQL'ed for XP for it's D3171-A mainboard, so XP support is possibly as "easy" as a separate .inf file specifying your HW to be installed manually; yet of course it is either up to MS or the OEM to release a driver.  It could even already be on their FTP, for all i know.  Probably best to find another [G] package, athough i'm no expert on Conexant audio.
They note to install KB888111 before installing a driver, though.  I thought that was already included in SP3, though minus two obsolete files. 

PPS:  You wouldn't be using HDMI, by any chance, eh?

The HWid's are most important at this point.  System Model# and Manufacturer of the unit(s) with those issues is helpful to find a recommended driver to compare with.

If you get a chance to make note of chip markings (such as: during maintenance-cleaning &/or repair); i often recommend taking the extra 2 minutes, should opportunity permit.

That utility is linked in either of mr_smartepants', OverFlow's, or my signature, at the bottom of the post.

I won't be able to respond for about 20 hours from now, so perhaps someone else "in-the-know" will be able to assist; just-in-case ([off-topic]i miss that old tractor[/off-topic]).

Well having that service running seems to be the largest issue, as this would leave many with an error added to the Event Log every reboot.

[lark]Think of "those guys" that phone people, claiming to be from Microsoft with important invalid license information, pointing people to run the Event Viewer.  They would indeed have a field day with that one, i gather, if they were still active.[/lark]

At any rate, that doesn't seem to pass the test of whether it is a net benefit for the majority of users that are without Fresco or VIAlabs USB 3.0 Host Controller/Hubs.  I can't even begin to think the implications security-wise; extending support in textmode could allow a wide variety of input devices (etc.), though - so that may be desirable as a 3rd-party RVMi addon.    That way, Fresco/VIA could end up as a 3rd-Party DriverPack, for those with such HW.

What does this MS pack even do under PE (with or without Fresco/VIAlabs)?  There are some yet unasked questions concerning any of these USB 3.0 drivers.  Ultimate Boot, etc...???  There should be some basic testing.

Whatever the final solution, there is no sense rushing it out the door, until it passes some basic testing.  That is the whole point of DriversPacks.  Without testing, things like that nV driver, version 19x.xx or something, that shut off most boards' cooling fans, and well... that was indeed bad.  Didn't end up in DP's, though, iirc.

I'm still stuck on discs at the moment, so every time i try this i'm looking at a 3hr turnaround, so i'm on hold on this for a while.

"RL" prevails.

PS:  Have you thought about joining the testing team?

Comments? 

That appears to have been manufactured within the 20th week of 2012, so it is likely a new mask.
Please post your HWid's, as this is possibly noted as a new "... &REV_xxxx".

Try a linux live CD (such as linuxMint, or Knoppix, etc.) to confirm .

Wait a moment;  did you say that you want to deploy Win7?
  If so, this Topic is posted in the wrong area of this forum.
Shouldn't you be using the DriverPacks for NT6 (and the appropriate tools)
if you want to deploy Win7?

"mostly harmless"

Those recurring errors (noted in EventViewer) seem to direct one to include KMDF in the source.
Forcing people to include this in their sources (including editing setupreg.hiv) is a non-starter.
These errors recur even when limited by HWid (as last post - see .ini) and no Fresco/VIA HW is present.

No, it BlueScreens.  see --> http://forum.driverpacks.net/viewtopic. … 615#p49615

What does it say upon the audio chip itself?

Another clue, perhaps, is contained in the .Inf file from the dell driver for your model.

If dell declined to release an XP driver for this hardware, it may never be released.
Other manufacturers may have released an XP driver, although that is increasingly unlikely.

Have you considered virtualization as a solution?

one important tidbit concerning Driver Signing.  If it's just a modded .Inf that is at issue:

I realized over half-way through responding to that post that i was merely responding to a bot.
Then i remembered that some readers here are on the opposite half of the computer-savvy bell-curve.
I responded for them.

PS:  I thought it was <ctrl>F8.

update_win2k.inf & update_srv2k3.inf for Win2k & Server2k3 respectively.

They are not supported for either Fresco or ViaLabs officially AFAIK, though they may be seen as WHQL in Server2k3.

after you do an install, add DEVMGR_SHOW_NONPRESENT_DEVICES=1 to your Environmental Variables (from CtrlPanel/System/Advanced) then close it.  Run devmgmt.msc, select "show hidden devices" & check for mvxxmm, mv61xxmm, & mv64xxmm in the Non-Plug&Play section.  They install on every DP-Integrated install.  They're "mostly-harmless".  With the addition of Fresco & Via, this might add wdf01000 to that list, even on systems with no USB 3.0.  This is what inspired me to make the 2k & 2k3 .Inf files unavailable to setup; just-in-case.

If you are into experimenting, here is a link to a (very) beta DP_MassStorage, including the first driver on your list.
http://forum.driverpacks.net/viewtopic. … 688#p49688 

Perhaps it would be best to roll this driver back to one from a previous DP.
I erred, as this driver is specifically WHQL'ed for Win7.

{DriverVer = 10/05/2012, 6.6.0.0} WHQL'ed for 2000, XP, Win2k3_x86, & xp64
here --> http://www.silabs.com/Support%20Documen … indows.zip 

The installer format has been changed to DPInst & is so much easier to extract now simply with an archival program such as 7-zip (et al).  No "IsXunpack.exe" required. 

Actually, that first driver you linked to IS WHQL'ed for w2k, Server2k3, & Server2k8 (32 bit).

um.. that last driver link contains hpcisss2.sys (W2k3) , not HpCISSm2.sys (for XP), though.
Unfortunately in this case, no Win2k3 WHQL signature was included.  However; the executable is indeed digitally signed.

Edit:  That driver already exists in DP_MassStorage_wnt5_x86-32_1209\D\M\C4

Unfortunately it also removes support for:

The latest update i see for the B400I controller & WHQL'ed for W2k3 is {DriverVer=01/07/2009, 6.14.0.32}
here --> http://h20000.www2.hp.com/bizsupport/Te … Id=3346452