tabank Posted June 15, 2004 Report Share Posted June 15, 2004 Currently, i'm using the original driver for GeForce4 440 Go that came with the laptop which is version 28.46. I has been trying to update it to a newer version. I tried 53.03 with 20.55 INF. I had the standby problem and also i couldn't get the native resolution of 1600x1200. The maximum resolution I can get with 53.03 is 1588x1200. The same thing happened with 52.16. With 46.90, the max resolution is 1440x900. Any suggestion of how to correct the resolution? Quote Link to comment Share on other sites More sharing options...
®®® Posted June 15, 2004 Report Share Posted June 15, 2004 Welcome to the forum tabank, currently there is some testing goin on behind the scene with some settings that might affect the BlackBar. We have to wait for a result though. The best suggestion for BlackBar affected Toshiba users was: USE 52.16. Can't understand why 52.16 still gives you a BlackBar... :) Have you tried one of the older INFs (<12.xx)? If not give it a try. Quote Link to comment Share on other sites More sharing options...
tabank Posted June 16, 2004 Author Report Share Posted June 16, 2004 Sorry for not being clear. I don't think that I have the black bar problem. My screen was perfectly filled. There were no black bars on my screen. (If that IS the black bar problem then I'm sorry...I'm new to this kind of things.) Anyway, it just that I couldn't get the resolution upto 1600x1200. Besides, the standby fix didn't really fix the problem for me. And, i just found out that i can no longer play FFXI. Quote Link to comment Share on other sites More sharing options...
mobilenvidia Posted June 16, 2004 Report Share Posted June 16, 2004 There are only 12 pixels missing out of 1600, so you might not notice a tiny black border. The 12 pixel problem (black bar) is a common Toshiba fault, there is something afoot in the way Toshiba handles the EDID (explained elsewhere). We are waiting the testing of some settings found in newer drivers. We hope to have a fix (although we have been for months now) very soon. So keep an eye on the forum, Pieter. Quote Link to comment Share on other sites More sharing options...
Guest Gialdy Posted June 17, 2004 Report Share Posted June 17, 2004 Who's testing the new settings? Could he need more help? I have sometime to play with settings and get this thing fix. Just give me a couple of the settings and I'll do some trial and error. Quote Link to comment Share on other sites More sharing options...
mobilenvidia Posted June 17, 2004 Report Share Posted June 17, 2004 Ministeve is da man, but alas his Lappy is getting repaired. Try putting this in the INF (under nvtweak section will do): HKR,, OverrideEdidFlags0, %REG_BINARY%, 51,F3,82,50,00,00,FF,FF,04,00,00,00,36,12,64,19,00,40,41,00,26,30,18,88,36,00,1ED7,10,00,00,18 Reinstall driver. This should hopefully overide the faulty EDID (fingers crossed) Pieter. Quote Link to comment Share on other sites More sharing options...
Guest hirokazu Posted June 17, 2004 Report Share Posted June 17, 2004 hi, i just installed 56.72 drivers on my Toshiba Satellite 5100 (not sure of the exact model, can't be bothered to check :) ) and it works great - anyhow, i've got the 12 missing pixels too and it annoys the hell out of me, its happened with previous drivers that i got off elsewhere too, which i eventually uninstalled. anyhow, i'll try that potential fix and get back to you guys, however, if it doesn't work, anything else to try, or would you rather us just wait till you guys have got it figured out? thanks. Quote Link to comment Share on other sites More sharing options...
Teraphy Posted June 17, 2004 Report Share Posted June 17, 2004 That registry key is only for a resolution of 1024x768 (missing 55 pixels). I have not looked at any other resolutions. For other resolutions I need the following: 1 bad EDID obtained from running the latest drivers (for comparison) 1 good EDID from 52.16 (or last known working driver) EDID can be found at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\DISPLAY 1 BIOS ROM for good measure unless it's either 4.17.00.41.C7 or 4.17.00.59.F9 since I have these two already. Quote Link to comment Share on other sites More sharing options...
Guest hirokazu Posted June 18, 2004 Report Share Posted June 18, 2004 the only driver i've tried that works is the one that the system came with, 28.46 (NVTS.inf). the EDID for device TOS5088 under that driver is: 00,ff,ff,ff,ff,ff,ff,00,51,f3,88,50,00,00,00,00,00,09,01,03,80,1f,\ 17,00,ca,a8,e0,99,57,4b,92,25,1c,50,54,00,21,09,81,80,a9,40,01,01,01,01,01,\ 01,01,01,01,01,01,01,48,3f,40,30,62,b0,32,40,40,c0,13,00,31,e5,10,00,00,18,\ 00,00,00,fc,00,54,4f,53,48,49,42,41,20,49,6e,74,65,0a,00,00,00,fc,00,72,6e,\ 61,6c,20,31,36,30,30,78,31,32,0a,00,00,00,fc,00,30,30,20,50,61,6e,65,6c,20,\ 20,20,20,0a,00,0c,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\ 00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\ 00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\ 00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\ 00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\ 00,00,00,00,00,00,00,00,00 i'll try get back to you ASAP on the non-working EDID from 56.72 (Pieter's INF 20.55) drivers, and i guess i'll give 56.12 a try to see if that will work too. sorta busy ATM, so i've rolled back to the default drivers for the time being. BIOS Version is 4.17.00.41.C5, no idea how to extract the BIOS ROM though. BTW another interesting thing of note that i only noticed recently is that with non-working driver version, not only is 12 horizontal pixels missing, the vertical resolution is also reported wrong - 1588x1400 when it should be 1600x1200. Quote Link to comment Share on other sites More sharing options...
Teraphy Posted June 18, 2004 Report Share Posted June 18, 2004 If things work out I'll fix up these lines. These are just for testing and should effect the EDID. To re-explain which line goes with which display: Removed -- they were wrong. hirokazu, the second line is for you. I would love to see your BIOS. You can google for NVIDIA BIOS Editor by Ray Adams or... I'm sorry Pieter for the following :) http://www.guru3d.com/xbios/ I *think* this is the main site/page? I recommend testing with a driver using an original NVTS.inf file (see 61.12 driver for example) with this key added under [nv_SoftwareDeviceSettings]. Also, try with Pieter's INF. Then if you could post the EDID that comes out of this display I'd be happy :) Thanks. Quote Link to comment Share on other sites More sharing options...
tabank Posted June 18, 2004 Author Report Share Posted June 18, 2004 Sorry for the late response. I had been batttling with the BetterInternet thingy. Anyway, I tried 52.16 with 9.6 INF. Everything was good; no black bar or standby problem. However, whenever I tested Direct3D using the DirectX Diagnostic Tool, it would say "You cancelled the test by pressing a button" or something like that... I'm currently using DirectX 9.0b. Quote Link to comment Share on other sites More sharing options...
Guest hirokazu Posted June 18, 2004 Report Share Posted June 18, 2004 Sorry for the late response. I had been batttling with the BetterInternet thingy. Anyway, I tried 52.16 with 9.6 INF. Everything was good; no black bar or standby problem. However, whenever I tested Direct3D using the DirectX Diagnostic Tool, it would say "You cancelled the test by pressing a button" or something like that... I'm currently using DirectX 9.0b. i get that about 75% of the time with the 56.72 drivers too. i'm not sure, but i think that may be related to the return to desktop problems that sometimes occur when you or a program changes the resolution (temporarily, not through the display properties), and you get booted back to the desktop... what's odd is that that happens to me with the default OEM drivers sometimes too, don't have a surefire way to fix it, but sometimes changes screen resolution in display properties and then changing back stops it from happening. --- anyway, i'll use that link to extract my bios, and i'll try the 52.16 drivers with the EDID override and see what happens. thanks for your help. EDIT: regarding the bios, i downloaded that xbios program, tried "read from memory", gave an error regarding PCIbus or smthing, so i go look for nvflash.exe, newest version i find is v4.46, try it in Command Prompt, similar error. so i bootup in pure DOS mode using a floppy, try nvflash to extract the bios rom again, no luck, says something about unsupported EEPROM, i'm thinking there's a newer version of nvflash i need, but that and testing drivers will have to wait for about a week or so, unfortunately. Quote Link to comment Share on other sites More sharing options...
®®® Posted June 18, 2004 Report Share Posted June 18, 2004 xbios (Ray Adams Vioe Bios Edxitor) is somehow not capable to identify some of the mobile GPUs. It seems that he has not added the PCI ids, therefore the programs does not recognize them. I also get the can't read from memory error message :) Concerning nvflash ( http://forums.laptopvideo2go.com/index.php?showtopic=766 ), go to the UTILIES section of the forum. A lot of usefull tools and apps hang around there. Give the newest nvflash (v5.xx) also a try, but don't be too optimistic. It doesn't even work with my GPUs so chances are low that it will work with yours...... Quote Link to comment Share on other sites More sharing options...
Guest Gialdy Posted June 19, 2004 Report Share Posted June 19, 2004 Sorry for the late response. I had been batttling with the BetterInternet thingy. Anyway, I tried 52.16 with 9.6 INF. Everything was good; no black bar or standby problem. However, whenever I tested Direct3D using the DirectX Diagnostic Tool, it would say "You cancelled the test by pressing a button" or something like that... I'm currently using DirectX 9.0b. I had the same problem and found a fix for it. The Nvidea desktop something is loadied up from the registry and stays in memory. That thing is the one make up the problems with the Direct X. To turn it off, go to MSconfig and look for the registry address that loads it. Then go to the registry and delete that line. Everything should work fine after that. PS Do a restore point if you are unsure of what your doing. 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.