®®® Posted September 21, 2004 Report Share Posted September 21, 2004 :: UPDATES 2004-NOV-10: repacked driver v66.10 so it now includes the Original DELL release AND the WindowsUpdate release in one package.The 7zipped driver archive has increased only by 3MB :) 2004-NOV-07: our member Ulysse ( :P ) found v66.10 WHQL at WindowsUpdate with an additional generic INF, which supports all mobile GPUs (except GF2 Go) 2004-OCT-10: added v66.12 :: DETAILS v66.10 mobile driver for 2K.XP, filedate 19.08.2004, released 20.09.2004 MultiLanguage, Setup included, with WHQL certification released by DELL for 5150/5160 (GF FX 5200), vA07 :) to our member "citrixcl" for letting us know about this release now also available at WindowsUpdate v66.12 mobile driver for 2K.XP, filedate 01.09.2004, released 12.10.2004 MultiLanguage, Setup included, with WHQL certification released by TOSHiBA for FX Go5700 (Qosmio G15 & F15) :: OPEN ISSUES :: ISSUES RESOLVED Blank screen at LCD panel after resume from S3 with LCD+VGA extend mode and extended VGA is primary. Blank screen after resume S4 with Samsung Panel. :: OPINION [*by LSudlow] Dell Inspiron 5150 owners have had a LONG wait for official drivers from Dell. With the release of 66.10, Dell has made a huge leap up from (if I remember correctly) the 45.xx series, and has combined support for the newly discontinued Inspiron 5150 and its replacement the 5160. I'm a big fan of the 66.xx series. These drivers are fast, with good compatibility and full support for Windows XP Service Pack 2 and DirectX 9c. 66.10's benchmarks are pretty consistent with 66.31 and 66.32, and it has the advantage of being an official mobile driver. If you want the latest, or already have 66.31/66.32 running well, there's no reason to install 66.10. But if you haven't yet upgraded to the 66 series and prefer the safety of an official mobile driver, 66.10 is your ticket. :: BENCHMARKS [*by LSudlow] Driver..|..3DMark01..|..3DMark03..|..3DMark05 53.03...|....6963....|....1335 53.04...|....6965....|....1332 53.06...|....6976....|....1333 53.30...|....6940....|....1335 53.81...|....6943....|....1337 54.01...|....6833....|....1307 56.55...|....6744....|....1306 56.56...|....6731....|....1304 56.64...|....6661....|....1277 56.72...|....6822....|....1308 56.82...|....6591....|....1271 58.21...|....6803....|....1308 60.60...|....6536....|....1190 60.72...|....6826....|....1253 60.80...|....6484....|....1186 61.11...|....6446....|....1186 61.12...|....6639....|....1215 61.21...|....6620....|....1213 61.40...|....6697....|....1269 61.80...|....6702....|....1271 62.01...|....6896....|....1308 62.11...|....6897....|....1308 62.20...|....6890....|....1307 65.62...|....6776....|....1301 65.73...|....6806....|....1307 65.90...|....6806....|....1308 66.00...|....FAIL....|....1309 66.10...|....6779....|....1307 66.31...|....6782....|....1308 66.32...|....6782....|....1305....|.....189 66.51...|....6796....|....1304....|.....202 66.70...|....FAIL....|....FAIL....|.....FAIL 66.72...|....FAIL....|....FAIL....|.....FAIL 66.74...|....6839....|....1322....|.....196 66.77...|....6823....|....1321....|.....197 66.81...|....6847....|....1321....|.....191 66.93...|....6836....|....1320....|.....187 67.50...|....6830....|....1320....|.....195 70.41...|....6740....|....1296....|.....191 NOTE: I use a home-grown inf (especially modded & tweaked for DELL's Inspiron 5150 and 5160), which can be found HERE. Pieter's version may perform quite differently. :: DOWNLOAD & This and all other drivers available at LaptopVideo2Go are 7-zipped and come as a self-extracting archive for your convenience. We take care that your download time/traffic is minimized by compressing the driver in an optimized way. The method we had developed first is a service that you'll only find here proper working. filesize 14.164.697 bytes | included both the DELL and WINDOWS UPDATE release filesize 10.992.075 bytes Pieter's mobile INF modified for v66.10 Pieter's mobile INF modified for v66.12 Larry's DELL 5150/5160 optimized INF :: INTENDED CARDS FROM ORIGINAL INF v66.10 DELL INF: see attached INF v66.10 generic WindowsUpdate INF: see attached INF HERE *new* v66.12: see attached INF HERE v66.10 NVDM.INF: NVIDIA_NV34.DEV_0324.1 = "NVIDIA GeForce FX Go5200"NVIDIA_NV34.DEV_0324.3 = "NVIDIA GeForce FX Go5200 " v66.12 NVTS.INF: NVIDIA_NV36.DEV_0348.1 = "NVIDIA GeForce FX Go5700"NVIDIA_NV36.DEV_0348.2 = "NVIDIA GeForce FX Go5700 " Original_v66.10_INF.zip ( 4.79k ) Number of downloads: 86 Quote Link to comment Share on other sites More sharing options...
fame Posted September 22, 2004 Report Share Posted September 22, 2004 did someone test the driver? is it better then the 65.73? Quote Link to comment Share on other sites More sharing options...
Bill Posted September 23, 2004 Report Share Posted September 23, 2004 I am about to test this driver I think, I know Larry benchmarked it already with his INF. I am hoping this driver will remember my digital vibrance setting apon start up as well as clone mode being on or off.(on start up as well) The 66.31 driver seems to forget that stuff. (as Pieter would say, "It won't stay?" "Hit Control+Alt+S+T+A+Y :) ") That was a reference to a joke from a while back, I wonder if anyone will get it. Bill Quote Link to comment Share on other sites More sharing options...
Guest Just Lou Posted September 24, 2004 Report Share Posted September 24, 2004 Dell finally did its job. They released a 66.10 for the 5150 with blankscreen fixes!http://tinyurl.com/6nkde Release Title Video: nVidia GeForce FX Go5200, Driver, Windows XP, Multi Language, Inspiron 5150, 5160, v.6.14.10.6610, A07 File Name R84389.EXE (19 MB) File Date 09/20/2004 File Format Hard-Drive Nvidia GeForce FX Go5200 Video Driver. Fixes: Blank screen at LCD panel after resume from S3 with LCD+VGA extend mode and extended VGA is primary. Blank screen after resume S4 with Samsung Panel. Larry will you mod this baby and keep that TVout workin buddy! Just so everyone knows. This driver does nothing to fix the "blank screen". It still happend just as often as it did with any other driver. :) Quote Link to comment Share on other sites More sharing options...
®®® Posted September 24, 2004 Author Report Share Posted September 24, 2004 Just Lou, at least give us some details why on YOUR laptop it doesn't work. Quote Link to comment Share on other sites More sharing options...
Guest sax007blau Posted September 24, 2004 Report Share Posted September 24, 2004 @dontknow hi, you ask just lou about details of the blank screen. because I have the same problems I will give some more details. I meen with blank screen that after start the desktop first appears but then the screen gets black for about 1 second, after that the desktop appears again and everything works normally. I also get this black screen if I got I'd like to go into the menu (right mouse click on desktop and then NVIDIA settings). These are the only problems with the newer (5x.xx und 6x.xx) driver but I don't like this blank screen at the beginning. That's why I use for more than 1 year the 44.68. This is the only driver I don't get a blank screen. By the way: I'm reader from this forum from the beginning. I solved many problems. Great work, thanks. Greetings from switzerland sax007blau _________________________________________ Dell Inspiron 8200, P4 @ 2 GHz, 512 MB RAM, 15" UXGA 1600x1200, GeForce4 440 Go 64M, Windows XP Pro SP2 Quote Link to comment Share on other sites More sharing options...
LSudlow Posted September 24, 2004 Report Share Posted September 24, 2004 Guys, that "blank screen" (Some people call it a flicker. I call it a blink.) has been with us through all the 5x.xx and 6x.xx drivers and isn't likely to go away. We're not precisely sure what's happening, but it's built into the drivers. The driver is either testing for connected devices, setting the clock speed, or both. nVidia did have a beta driver a couple of months ago that had no blink (or flicker or blank) but it was full of bugs and we've never seen its successor. So the blink at startup will be with us for a while. It's annoying, but it's not harmful and eventually you get used to it. The blink (or blank or fllicker) when you open the nVidia Control Panel is caused by the Coolbits switch that enables the overclocking page. If you don't overclock, find the coolbits line in the INF and set it to 0, and the (flicker/blink/blank) will be gone. Or you can use Regedit to go directly to HKLM\Software\nVidia Corporation\Global\NVTweak and edit the coolbits switch right there. Quote Link to comment Share on other sites More sharing options...
®®® Posted September 24, 2004 Author Report Share Posted September 24, 2004 Thanks Larry. Quote Link to comment Share on other sites More sharing options...
Guest citrixcl Posted September 25, 2004 Report Share Posted September 25, 2004 i kind of like the blink... it makes people go ooh what was that... i say oh nothing just setting the computer over into overclocked mode. woo wee Quote Link to comment Share on other sites More sharing options...
Guest Just Lou Posted September 25, 2004 Report Share Posted September 25, 2004 Guys, that "blank screen" (Some people call it a flicker. I call it a blink.) has been with us through all the 5x.xx and 6x.xx drivers and isn't likely to go away. We're not precisely sure what's happening, but it's built into the drivers. The driver is either testing for connected devices, setting the clock speed, or both. nVidia did have a beta driver a couple of months ago that had no blink (or flicker or blank) but it was full of bugs and we've never seen its successor. So the blink at startup will be with us for a while. It's annoying, but it's not harmful and eventually you get used to it.The blink (or blank or fllicker) when you open the nVidia Control Panel is caused by the Coolbits switch that enables the overclocking page. If you don't overclock, find the coolbits line in the INF and set it to 0, and the (flicker/blink/blank) will be gone. Or you can use Regedit to go directly to HKLM\Software\nVidia Corporation\Global\NVTweak and edit the coolbits switch right there. "Flicker"? It is not a "flicker." It is a blank screen upon return from standby. The only way to get the screen back is to go back into standby mode and resume again, or power the system back on. Dell said this driver would fix the problem, but it doesn't. Quote Link to comment Share on other sites More sharing options...
LSudlow Posted September 25, 2004 Report Share Posted September 25, 2004 Sorry 'bout that. I was responding to the "...the screen gets black for about 1 second..." description. You've clearly got something worse. Quote Link to comment Share on other sites More sharing options...
Bill Posted September 26, 2004 Report Share Posted September 26, 2004 (edited) Since no one here has commented on this driver (as in how fast they run, what bugs they have, ect) I will say that after trying them, they run kinda slow for me, and these drivers don't remember when I set clone mode or not, but they do remember my digital vibrance settings. I would rather reccomend the 66.31 or 66.32 driver. Bill //edit: moved&merged Edited September 26, 2004 by dontknow Quote Link to comment Share on other sites More sharing options...
®®® Posted September 26, 2004 Author Report Share Posted September 26, 2004 It is a blank screen upon return from standby. The only way to get the screen back is to go back into standby mode and resume again, or power the system back on. Dell said this driver would fix the problem, but it doesn't. Just Lou, the one thing i can do for you to bring some light into your issue is repeating myself: We need details. I can guess that you have some kind of Toshiba... If so, then we can help you. Quote Link to comment Share on other sites More sharing options...
Guest Guest Posted September 26, 2004 Report Share Posted September 26, 2004 It is a blank screen upon return from standby. The only way to get the screen back is to go back into standby mode and resume again, or power the system back on. Dell said this driver would fix the problem, but it doesn't. Just Lou, the one thing i can do for you to bring some light into your issue is repeating myself: We need details. I can guess that you have some kind of Toshiba... If so, then we can help you. "Toshiba"? No, I have a Dell 5150. The problem is quite common, and happens about 25% of the time when resumming from standby. The system come back on, but then the screen goes blank. If I put the system back in standby, and resume again, it usually comes back on the second try. There are a few threads about this on the "Dell' forums. Quote Link to comment Share on other sites More sharing options...
®®® Posted September 26, 2004 Author Report Share Posted September 26, 2004 Oh, you have a DELL. And a DELL 5150. Here we go. I guessed wrong somehow :) Possibilties were: ACER, HP/COMPAQ, SONY, GERICOM, ASUS, even an Alienware or Liebermann 17'' Gold something or FUJITSU, BENQ, PowerPro or what i saw yesterday: a TTX VX+ As you don't have a Toshiba (MAPOS3toNV set to 2 , when standby issues) and you got Larry's DELL, then we still have a solution for you. Use Larry's INF over HERE, which is optimized for DELL's 5150/5160. :) Quote Link to comment Share on other sites More sharing options...
Guest Just Lou Posted September 26, 2004 Report Share Posted September 26, 2004 Oh, you have a DELL. And a DELL 5150. Here we go. I guessed wrong somehow :) Possibilties were: ACER, HP/COMPAQ, SONY, GERICOM, ASUS, even an Alienware or Liebermann 17'' Gold something or FUJITSU, BENQ, PowerPro or what i saw yesterday: a TTX VX+ As you don't have a Toshiba (MAPOS3toNV set to 2 , when standby issues) and you got Larry's DELL, then we still have a solution for you. Use Larry's INF over HERE, which is optimized for DELL's 5150/5160. :) Silly me for ASSuming people would know I have a Dell 5150, in a thread about a Dell 5150 driver. :P ...I've tried Larry's inf's with earlier drivers, and it did not fix the problem. With so many drivers not fixing it, I'm pretty sure it's a hardware or firmware issue. Quote Link to comment Share on other sites More sharing options...
mobilenvidia Posted September 26, 2004 Report Share Posted September 26, 2004 Just Lou, Try one of these settings in the [Mobile_tweaks] section of my INFs. HKR,, ModesetBlankDelay, %REG_DWORD%, 0x00000096 HKR,, ModesetBlankDelay, %REG_DWORD%, 1 HKR,, ModesetBlankDelay, %REG_DWORD%, 150 HKR,, ModesetBlankDelay, %REG_DWORD%, 200 The GPU might be switching on too fast for the Inverter. Quote Link to comment Share on other sites More sharing options...
Guest Just Lou Posted September 26, 2004 Report Share Posted September 26, 2004 Just Lou,Try one of these settings in the [Mobile_tweaks] section of my INFs. HKR,, ModesetBlankDelay, %REG_DWORD%, 0x00000096 HKR,, ModesetBlankDelay, %REG_DWORD%, 1 HKR,, ModesetBlankDelay, %REG_DWORD%, 150 HKR,, ModesetBlankDelay, %REG_DWORD%, 200 The GPU might be switching on too fast for the Inverter. I will try it. Thanks Quote Link to comment Share on other sites More sharing options...
Guest verbal Posted September 26, 2004 Report Share Posted September 26, 2004 Lou, I'm having the same blink problem. Did you try one of those recommended settings in the INF? Quote Link to comment Share on other sites More sharing options...
Guest Just Lou Posted September 27, 2004 Report Share Posted September 27, 2004 Lou, I'm having the same blink problem. Did you try one of those recommended settings in the INF? No. I'm stuck in Florida right now, and won't be able to try it until later this week. Quote Link to comment Share on other sites More sharing options...
Guest Swiss007 Posted September 30, 2004 Report Share Posted September 30, 2004 Pieter, thanks for the INF file. The driver works fine with my Inspiron 8100 Geforce2go 1400x1050. No problems after hibernate as before with Dell's 44.82. :) Regards Swiss007 Quote Link to comment Share on other sites More sharing options...
®®® Posted October 13, 2004 Author Report Share Posted October 13, 2004 Original v66.12 OEM Toshiba INF for FX Go5700 Original_v66.12_NVTS.INF.zip ( 4.78k ) Number of downloads: 23 Quote Link to comment Share on other sites More sharing options...
®®® Posted October 15, 2004 Author Report Share Posted October 15, 2004 (edited) Teraphy, besides Pieter also i noticed that the 66.12 INF is different to 66.10. 1. There is the file NVTSEXT.DLL (a skin customization module). Here is one reference in the INF: HKR,, NVCplGfxLib, %REG_SZ%, "nvtsext.dll" I wonder what could be skinned here. This file started to be present with the release of v65.90 , EXCEPT it isn't present in v66.10 DELL driver and in v66.00. 2. Conexant TV-out decoder? HKR,, CX875.HD480i.0720x0480.flickerfilter, %REG_DWORD%, 4 HKR,, CX25875.HD480i.0720x0480.flickerfilter, %REG_DWORD%, 4 3. OverrideEDIDFlags is used! [OverrideEdidFlags_TP2_NV36_AddReg] HKR,, OverrideEdidFlags0, %REG_BINARY%, 51,F3,8B,50,00,00,ff,ff,04,00,00,00,6C,12,70,0A,D0,B0,20,E0,11,10,10,48,13,00,4b cf,10,00,00,18 HKR,, OverrideEdidFlags1, %REG_BINARY%, 51,F3,8B,50,00,00,ff,ff,04,00,00,00,26,02,3b,80 HKR,, OverrideEdidFlags2, %REG_BINARY%, 51,F3,8A,50,00,00,ff,ff,04,00,00,00,6C,12,70,0A,D0,B0,20,E0,11,10,10,48,13,00,4b cf,10,00,00,18 HKR,, OverrideEdidFlags3, %REG_BINARY%, 51,F3,8A,50,00,00,ff,ff,04,00,00,00,26,02,3b,80 [OverrideEdidFlags_TP3_NV36_AddReg] HKR,, OverrideEdidFlags0, %REG_BINARY%, 51,F3,8A,50,00,00,ff,ff,04,00,00,00,6C,12,70,0A,D0,B0,20,E0,11,10,10,48,13,00,4b cf,10,00,00,18 HKR,, OverrideEdidFlags1, %REG_BINARY%, 51,F3,8A,50,00,00,ff,ff,04,00,00,00,26,02,3b,80 4. Pieter this has to be corrected in INF 30.34a: nvwddi.dll was moved from [nv.Panel] to [nv.nViewPanel] in 66.12 [nv.nViewPanel] nvwddi.dll in 66.10 [nv.Panel] nvcpl.dll nvmctray.dll nvwddi.dll Edited October 15, 2004 by dontknow Quote Link to comment Share on other sites More sharing options...
mobilenvidia Posted October 15, 2004 Report Share Posted October 15, 2004 4. Pieter this has to be corrected in INF 30.34a:nvwddi.dll in 66.12 [nv.nViewPanel]nvwddi.dll in 66.10 [nv.Panel] nvcpl.dll nvmctray.dll nvwddi.dll This has been corrected in 30.34a, to what it is now. v30.35 will have this sorted automaticly from now on. This INF is diferent to others it changed some sections. 66.12: [nv4_EventLog_Inst]AddReg = nv4_EventLog_AddReg[nv4_EventLog_AddReg] HKR,, EventMessageFile, 0x00020000, "%SystemRoot%\System32\IoLogMsg.dll;%SystemRoot%\System32\drivers\nv4_mini.sys" HKR,, TypesSupported, 0x00010001, 7 [nv4_Generic_Service_AddReg] HKR, Video, Service, %REG_SZ%, nv [nv_NVSVC_Inst] DisplayName = %NVSVC.name% Description = %NVSVC.desc% ServiceType = 16 ; SERVICE_WIN32_OWN_PROCESS StartType = 2 ; SERVICE_AUTO_START ErrorControl = 1 ; SERVICE_ERROR_NORMAL ServiceBinary = %11%\nvsvc32.exe all other drivers: [nv4_Generic_Service_Inst]ServiceType = 1 ; SERVICE_KERNEL_DRIVERStartType = 1 ; SERVICE_SYSTEM_START ErrorControl = 0 ; SERVICE_ERROR_IGNORE LoadOrderGroup = Video ServiceBinary = %12%\nv4_mini.sys AddReg = nv4_Generic_Service_AddReg [nv4_EventLog_Inst] AddReg = nv4_EventLog_AddReg [nv4_EventLog_AddReg] HKR,, EventMessageFile, 0x00020000, "%SystemRoot%\System32\IoLogMsg.dll;%SystemRoot%\System32\drivers\nv4_mini.sys" HKR,, TypesSupported, 0x00010001, 7 [nv4_Generic_Service_AddReg] HKR, Video, Service, %REG_SZ%, nv [nv_NVSVC_Inst] DisplayName = %NVSVC.name% Description = %NVSVC.desc% ServiceType = 16 ; SERVICE_WIN32_OWN_PROCESS StartType = 2 ; SERVICE_AUTO_START ErrorControl = 1 ; SERVICE_ERROR_NORMAL ServiceBinary = %11%\nvsvc32.exe This caused me no amount of grief in trying to work out what was going on. Got it sorted and then it became 30.34a Quote Link to comment Share on other sites More sharing options...
®®® Posted October 15, 2004 Author Report Share Posted October 15, 2004 Pieter, search for nvNviewPanel in 30.34a you'll find only one reference: [DestinationDirs] nv.nViewPanel = 11 because this one is missing: [nv.nViewPanel] nvwddi.dll Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.