sandorski
No Lifer
..it ain't working anymore! :|
Proceed to end for simple request. 😉
[mini-Rant] Been having issues ever since starting to use WinXP 64 back in Oct. They were somewhat minor so I chose to ignore them, but yesterday I decided to try and fix them because I had an Idea! That idea consisted of removing my Audigy Gamer and trying the Onboard sound on my Dual SataII mobo.
So I shutdown, remove the Audigy, restart, enter BIOS, enable Onboard Audio, Save/Exit, wait for Windows to boot. WTH, monitor goes Black/Power Save halfway to Windows. After a few changes here and there that do nothing, I decide to pop my Windows CD in and do a Repair Install. That works to get into Windows with Audio working too, but resolution is at 640x480 so I attempt to change Resolution...screen goes Black! :|
I try many things, but eventually Boot into Safe Mode and remove my Video(9800Pro) from Hardware, which works and I get back into Windows. This time I check my Monitor and see that it's set to "Plug and Play Monitor", hmmm. So I go to Update Driver and it returns nothing. Goto NEC to download Inf and download the file "Mitsubishi_New" and proceed to get Windows to use that. Windows won't, saying that my Monitor is incompatible with that Inf. Ok, back to NEC, notice a link to a list of Win64 compatible monitors, check it out, Monitor "DiamondPlus 91" is not listed, WTF?
Here's the kicker, up until I tried all this my Monitor was properly recognized and using the proper Inf(NFL9905). 😱 Been so long I can't recall what/how I did it when first setting up my new system, I suspect though that I just used the individual NFL9905.Inf file I used in old WinXP and told WinXP64 to use despite possible incompatibilities??
So I try Google just for that individual file, get some results that send me back to NEC, no good. Another link wanted $7 for me to download, but WTF?[/mini-rant]
Simple request: Does anyone have an old NFL9905 Inf file or info where I can get one? Any other suggestions, fixes, kludges would be greatly appreciated. 🙂 Update: Found an old Driver, but it won't work either(same Windows message). It appears some kind of work around is necessary.
Proceed to end for simple request. 😉
[mini-Rant] Been having issues ever since starting to use WinXP 64 back in Oct. They were somewhat minor so I chose to ignore them, but yesterday I decided to try and fix them because I had an Idea! That idea consisted of removing my Audigy Gamer and trying the Onboard sound on my Dual SataII mobo.
So I shutdown, remove the Audigy, restart, enter BIOS, enable Onboard Audio, Save/Exit, wait for Windows to boot. WTH, monitor goes Black/Power Save halfway to Windows. After a few changes here and there that do nothing, I decide to pop my Windows CD in and do a Repair Install. That works to get into Windows with Audio working too, but resolution is at 640x480 so I attempt to change Resolution...screen goes Black! :|
I try many things, but eventually Boot into Safe Mode and remove my Video(9800Pro) from Hardware, which works and I get back into Windows. This time I check my Monitor and see that it's set to "Plug and Play Monitor", hmmm. So I go to Update Driver and it returns nothing. Goto NEC to download Inf and download the file "Mitsubishi_New" and proceed to get Windows to use that. Windows won't, saying that my Monitor is incompatible with that Inf. Ok, back to NEC, notice a link to a list of Win64 compatible monitors, check it out, Monitor "DiamondPlus 91" is not listed, WTF?
Here's the kicker, up until I tried all this my Monitor was properly recognized and using the proper Inf(NFL9905). 😱 Been so long I can't recall what/how I did it when first setting up my new system, I suspect though that I just used the individual NFL9905.Inf file I used in old WinXP and told WinXP64 to use despite possible incompatibilities??
So I try Google just for that individual file, get some results that send me back to NEC, no good. Another link wanted $7 for me to download, but WTF?[/mini-rant]
Simple request: Does anyone have an old NFL9905 Inf file or info where I can get one? Any other suggestions, fixes, kludges would be greatly appreciated. 🙂 Update: Found an old Driver, but it won't work either(same Windows message). It appears some kind of work around is necessary.
