Nvefdxp Sys Nvidia Driver For Mac

Hi there TheDave and all others ho read this thread, First of all, i'd like to thank you very much!! I can imagine you spent a good amount of time testing and trying drivers to reach theese guides. Now, I have a DV6650BR and i had some trouble to install all devices: - First, i fallowed TheDave's guide. I got almost everything going, except the Ethernet card, 1394 net adapter and the webcam.

1. Nvefdxp Sys Nvidia Driver For Mac Download

People are following CBT more than any download nvefdxp.sys nvidia driver. You adobe distiller 9 free software download download nvefdxp.sys nvidia driver.

For the webcam, i fallowed a guide found in HP website, that installs Windows XP KB899271-v4, that works for my 1.3 MP webcam. For the ethernet, i tried the INF edits and the driver pack from this thread's page 16, but got no success. I managed to install it using a nForce 630a driver, just as DarkTemplar. I still have the 1394 net adapter problem. So, can anyone help-me?

Also, i noticed that audio quality is really poor.: ( Do you guys notice and problem with audio quality as well? PS: I'm not a native english speaker, so sorry for bad writting. TheDave and others, awesome work! No more POS Vista for us. I thought my machine had a bad system board because it would freeze when watching a video or simply using MS Word.

Well, turns out Vista was the problem. I'm glad I didn't send the laptop to HP. Anyways, I managed to install the audio and ethernet drivers succesfully. For the audio, I used the drivers provided on post #2. If you are having audio problems, use those drivers and follow the instructions properly. When I first installed the drivers, the volume couldn't be increased or decreased using the speaker icon in the task bar.

The volume would just stay at the same level. I realized I didn't follow the instructions carefully. After modding the two INF files (of the audio driver), the audio works properly. Make sure you check the hardware IDs of the audio driver and modd the INF files properly. As for the ethernet driver, it gave me some trouble the first time I installed the driver. When the installation was almost completed, the computer randomlly restarted.

Then the computer wouldn't boot to Windows, it would give me a blue screen. Well, then my next move was Safe Mode, which didn't help at all. By some reason, when I restarted the computer and run it in 'normal mode,' the system booted just fine. But of course, the ethernet wasn't still working.

So downloaded the Nforce 16.08 driver: And I used the ethernet driver from it. Driver needs to be MODDED. Use the instructions provided by TheDave on post #2. I'm still have an 'unknown device' listed in the device manager and the bluetooth is still not working. Please let me know if you got any of these two working.

HUGE Thanks to TheDave for this info to dump Vista and go back to Xp - for an Upgraded user experience. Tech support at HP was absolutely worthless for this. Got my HP dv2740se running with your instructions on page one, just for my chipset. It is the same chipset nForce 560.

Other drivers are at HP Website now, that will get you connected to Internet and make quick-launch buttons work. Then I went to Windows Update and most everything else, including audio, was taken care of via the M$ downloads. I have a 100% clean Device Manager now, and video and disk access is now 30% to 50% than when Vista was constipating everything. For those of you curious, the dv6645us (and maybe even the dv2610us too) has the following hardware makes/models, and could use the suggested drivers: NVidia MoBo chipset: nForce 560 (CPU-Z states it is the exact MoBo model: Quanta 30CF) Used file: directly from Nvidia. Once extracted, installed, inf edits were then made & updated for just the SMBus & Ethernet drivers.

INF EDITS: This is where things get much more difficult if you don't know what you are doing, or just aren't comfortable doing them. This can also be somewhat dangerous I guess, and will actually let you install any driver for any piece of hardware. Just because windows will actually let you install (any) driver, doesn't mean the device will actually work though. You should be confident when picking your drivers and making these edits.

Nvefdxp Sys Nvidia Driver For Mac Download

Since I was using the real NVidia drivers for the chipset that was identified by the CPU-Z utility, I was pretty confident with this driver choice. After the Nforce drivers run through their install process, it usually leave the drivers uncompressed in a directory on your C: drive (probably C: NVIDIA something) SMBus inf edit: I opened up the SMBus nvsmbus.inf file, and saw a large list of Hardware ID's under the NVIDIASYS section.

I copied and pasted the last line of this section, and changed it to read:%PCI VEN10de&DEV01b4.DeviceDesc% = AMDNODRV, PCI VEN10DE&DEV0542 The way I came up with the new last four digit #'s, was to go into device manager, double-click on the unknown device 'SMBus.' , click on the 'Details' tab, and scrolled through the first 3 options. I found that under the 'Compatible Ids' area, a very similar id existed, and I just needed to change the last 4 (3 really) digits of the new line I had just made to 0524 (from 0446). Now I just saved the inf with the updated info, went back to the 'Driver' tab on the unknown device, and clicked 'Update Driver'. When needed, I pointed the procedure to the right place (c: nvidia 12.15 smbus ), it found the right driver, and I would reboot if needed. Now since the device did not come up with a red X in device manager, I would say that it is working correctly. Ethernet inf edit: To get this driver loaded, I edited two inf files: Ethernet nvnetbus.inf & Ethernet nvenetfd.inf For the first file (nvnetbus.inf), I went through, and found the Standard section of the file, and added this line:%nvnetbus.DeviceDesc%=nvnetBusDevice, PCI VEN10DE&DEV054C Again, I knew to change the last 4 digits of the line to 054c since it was listed as the Hardware id in the device manager for the unknown Ethernet device.

For the second file (nvenetfd.inf): I browsed through it, and saw that I would need to copy & edit the appropriate line under each of these three sections ControlFlags, Nvidia, Nvidia.NTx86.5.1. With the end of each new line under each of those 3 sections, the line would need to be changed to 054c as well. Now I just saved the inf file(s) with the updated info, went into to the 'Driver' tab on the unknown device, and clicked 'Update Driver'. When needed, I pointed the procedure to the right place (c: nvidia 12.15 ethernet ), it found the right driver, and I would reboot if needed. Now since the device did not come up with a red X in device manager, I would assume that it is working correctly. Since I was able to, I plugged in an ethernet cable to my little home network, and the device worked great (100 Mbit FD even!).

This concludes the first inf edit tips for the needed MoBo drivers. Next inf edits will be for the audio devices & modem.

Wireless 802.11b/g nic: Broadcom 4311BG 5 in 1 Card reader: Ricoh 5 in 1 (For this, I was able to just use the 5 in 1 Ricoh drivers meant from another pc:.) Video device: nVidia GeForce 7150M / nForce 630M I used driver 156.72 from Note: (12-4-07) It was brought to my attention that the drivers at my original link (above) no longer has the drivers available. I zipped up my copy I still have, and have made them available to download from here: Bluetooth device: Broadcom for HP. Uses the WIDCOMM stack though, can be obtained form HP: Newer Version (5.1): Older Version (4.0): Keyboard hard (quick launch) buttons:. HP links broken, see 3rd note below a little ways. I'm still messing with this, but I have found this much so far.

Install the HP Quick Launch Button drivers: This should get the device listed right in device manager. To get the 'on screen' volume controls to show up on XP Pro, I read downloaded, and installed the MS IntelliType (6.1) drivers for the 'MultiMedia Keyboard' (when asked) from Microsoft at this url: 1st NOTE: As a side note to this 'on screen' volume display.

The regular HP one just started working after a couple days, and I am unable to tell what got this working. I don't know if maybe the Microsoft DOT NET framework I installed actually got it working or not (this is the only thing I can think of).

So I have uninstalled the MS IntelliType driver for now. 2nd NOTE: After messing around with this a few more times, I downloaded, and installed (separately) the quicklink button drivers: 5.2, 6.0, 6.1, 6.2, & 6.3. 6.2 was what I found originally had found, and linked to up above. However, it does not function 100% (nor do any of those versions). However, the most important item to me was the on screen volume indicator. And it did not work right away in any version, except v6.1.

So if you don't care about the 'dvd' & 'Q' button as I don't, and just want the on screen volume indicator as I did, you can download and install v6.1 of those drivers here: 3rd NOTE: Apparently HP is too dumb to just add a link to the above linked pages telling people to get the critical update, and they are too lazy to just make a new version of this software with the critical update included. DO NOT Forget to download and install the critical update that HP thinks is sooo important. I have uploaded the files for your enjoyment.

Quick Link Buttons v6.3 (latest): Quick Link Buttons v6.1: After you download and install EITHER one of these files, be sure to install the HP CRITICAL UPDATE from here: Again, The reason I post both version, is I know some people only like the latest versions of stuff, but I post the other (older) one because I found it to work better, and actually display the on-screen volume right after installing. One (major) downside to the older version though, when it displays the on-screen volume level, it (temporarily) steels the window focus while the OSD is displayed. HD Audio & Modem (Both Conexant) setup: 3 Steps to this part of the setup. 1) Download & Install the (UAA) Universal Audio Architecture drivers: 2) Download, and unzip the audio driver file: Under the Conexant section of the wis30B2a.inf file, I added the following hardware id:%HdAudioFunctionDriver.Waikiki5047.DeviceDesc% = HdAudModel,HDAUDIO FUNC01&VEN14F1&DEV5045&SUBSYS103C30CF This solved one of the 'unknown devices' under device manager. After going to the device properties in device manager, and manually going through the 'Upgrade drivers' process, and pointing that procedure to the correct directory where you updated the inf file to have the correct hardware id. 3) Download, and unzip the modem driver file: Under the ControlFlags section of the WinXP SprtHD5m.inf file, I added the following hardware id: ExcludeFromSelect= HDAUDIO FUNC02&VEN14F1&DEV5045&SUBSYS103C30CF AND under the HSFMODEM section of the WinXP SprtHD5m.inf file, I added the following hardware id:%HSFModem% = ModemX, HDAUDIO FUNC02&VEN14F1&DEV5045&SUBSYS103C30CF After editing the inf file, go through the same 'upgrade driver' process, be sure you point to the correct directory manually if you have to. This should solve the remaining 'unknown device' issue.

Built-In WebCam: It should just work in XP (w/SP2) in windows explorer. However, there are reports of some issues with 3rd party apps. I was able to install this utility from HP: I did have to manually start the installed exe file from program files hp webcam hp webcam xp32 VimicroCam.exe. That little utility did seem to work ok though, and it even recorded a test vid w/audio once config'd some. You can also check out this thread: And see if the drivers listed in there work for you. I have no idea, as I have not tested them with this model laptop, so good luck.

AMD Processor Drivers: Apparently there are better drivers for the CPU itself. These drivers are suppose to have better handling of the dynamic CPU clock speed, and thus saving you battery life, which is very important. I didn't do any test of this theory, but it make sense from a logic stand point. Anyways, you can visit the AMD website here: Once that page is up, look for a title called (toward the bottom of the page): AMD Athlon™ 64 X2 Dual Core Processor Driver for Windows XP and Windows Server 2003 (x86 and x64) After you found that, download, and install the driver, you should reboot if asked. Maybe more later.

I have read on alot of pages, and googled for days now and tried LOTS of drivers, but I am stuck. I have installed XP Pro x64 on on my HP and I got the wireless network up and running but not: Ethernet, Video and sound. I would love any assistans I could get!

Posted:, 10:40 PM Lets make sure you have the SLD created correctly. Are these missing files, listed as file resources in their respective components? Do you have a repository setup in the SLD? And is the component(s) related to their respective repositories? Did you get any errors when you built the image i.e. 'File Note Found'?

Regards, Sean Liming / Book Author - XP Embedded Advanced, XP Embedded Supplemental Toolkit 'Graham Dunn' wrote in message news:CbSdnbltLfAUUwLbnZ2dnUVZr23nZ2d@golden.net. I've componentized drivers for nforce MCP (SMB, ethernet), but I'm being prompted for the location of several files (the ethernet inf and sys) during the FBA run. As this is a USB-only system, and the USB drivers haven't loaded yet, it makes it tricky to answer the prompts. Does anyone have any suggestions or directions to alternate nforce sld samples? ThanksGraham. Posted:, 03:00 PM Sean Liming (MVP) wrote: Lets make sure you have the SLD created correctly. Are these missing files, listed as file resources in their respective components?

Do you have a repository setup in the SLD? And is the component(s) related to their respective repositories?

Did you get any errors when you built the image i.e. 'File Note Found'? Build complete, elapsed time: 205.11 seconds, estimated run-time image size: 961.23MB / 1,335.04MB (compressed/uncompressed) No errors and 5 warnings SLD is available at The error that's popping up is: 'The file 'nvefdxp.sys' on NVIDIA nForce Networking Controller Driver Disk 1 is needed' Thanks, Graham.

Posted:, 04:13 PM The nvefdxp.sys is being placed in%11% ( windows system32) where it should be placed in%12% ( windows system32 drivers). Try changing the file location to%12% and see what happens. Regards, Sean Liming / Book Author - XP Embedded Advanced, XP Embedded Supplemental Toolkit 'Graham Dunn' wrote in message news:ffmdnRWtEfiAUz3bnZ2dnUVZhKdnZ2d@golden.net. Sean Liming (MVP) wrote: Lets make sure you have the SLD created correctly. Are these missing files, listed as file resources in their respective components?

Yes 2. Do you have a repository setup in the SLD? And is the component(s) related to their respective repositories? Yes 3. Did you get any errors when you built the image i.e. 'File Note Found'? Build complete, elapsed time: 205.11 seconds, estimated run-time image size: 961.23MB / 1,335.04MB (compressed/uncompressed) No errors and 5 warnings SLD is available at The error that's popping up is: 'The file 'nvefdxp.sys' on NVIDIA nForce Networking Controller Driver Disk 1 is needed' ThanksGraham.