Jump to content
LaptopVideo2Go Forums

1280x854 resolution install problems


®®®

Recommended Posts

reports of failed installation (4bit or 8bit problem, can't change resolution):

Affected models:

  • vprMatrix 185A5 (Only v45.84 works)
  • vprMatrix 200A
  • vprMatrix 220A5
  • Mitac 8060
  • Gericom

Affected GPU:

  • GF4 420 Go 32 MB, DEV_ID:0176 Subsys: SUBSYS_2201152D&REV_A3

known working drivers:

  • v52.16
  • v53.13

Affected members:

Threads:

DEMUS wrote:

Clean install, no video drivers beyond standard vga adapter that XP defaults with. Loaded the 66.93 with tweakless .inf (30.39) using the update driver option from the device manager.

after load the device is ready to use without restarting. At that point I can switch the settings to my 1280x856x32bit on my lcd display (main monitor) and everything is beautiful. If I click on the advanced button to check the nVidia pages I get an ugly flash and my screen instantly resets to the primary monitor having only 800x600x4bit and the secondary (external) having all the options.

If I don't click the advanced button and restart the laptop, from the welcome screen on the system has 4bit 800x600 as the only option and in display settings I can see that the secondary has all of the aditional options.

In either case there are no nvidia or nview option pages in the display settings advanced section.

-------------------

After trying with three different drivers, I have narrowed down the problem. After a driver loads, I can set the display at the correct resolution, check dxdiag and even sign into WoW. but if I load the cpanel, either by clicking the advanced button or restarting the laptop, then I can actually see the panel loading and I get an error message about the panel making changes to my settings. those changes are BAD...is there some way to tell the cpanel to knock that off? or just go in a reset the values to something that works again?

Okay so I did a little comparison of the [softwaredevicesettings] of the 3 infs that I mentioned earlier and the following is a little brief.

For OEM vs 52.16 (20.55)

OEM and 20.55 shares:

InstalledDisplayDrivers nv_disp

VgaCompatible 0

SoftEDIDS 1

OEM and 20.55 differs:

OEM:

VPEENABLE 0

All of the modes that NV17 supports (reference, horizontal, and vertical modes)

20.55:

VPEENABLE 1

HKR,, NV_Modes, %REG_MULTI_SZ%, "{*}S 320x200 320x240 400x300 480x360 512x384 640x400=1FFF;SHV 640x480 720x480 768x576 800x600 1024x768 1152x864 1280x720 1280x768 1280x800 1280x854 1280x960 1280x1024 1360x768 1366x768 1400x1050 1440x900 1600x900 1600x1000 1600x1024 1600x1200 1680x1050 1920x1200 1920x1440 2048x1536x8,16,32=1FFF"

OEM has(that 20.55 does not):

VPEENABLE 0

Mobile 3

UseSelectedDevice 1

RMMaintainDevs 1

DualViewMObile 1

PushBufferMemorySpace 2

DevSwitchSuppressMask 1

RMMaintainScaling 1

RMMaintainTVStandard 1

MapOSD3ToNV 3

EnableAGPFW 1

ReqAGPRate 4

"Attach.ToDesktop" 1

"DefaultSettings.BitsPerpel" 16

"DefaultSettings.XResolution" 800

"DefaultSettings.YResolution" 600

20.55 has (that OEM does not)

DFPAsDefaultMonitor 1

UseBestResolution 1

In the tweaks section:

Devices Connected 1

dynEngCtrlEnabled 2

EnableAGPSBA 0

Enable Win2kDualview 1

MultiFunctionsSupported 1

NvCplEnableHardwarePage 1

NvCplEnableRotatePage 1

NvCplEnableShowTemperatureSettings 1

PowerMizerEnable 1

RotateFlag 4

HKR,, DCBOverride0, %REG_BINARY%, 04,25,00,22,18,20,10,01,00,02,b8,88,00,00,00,02,01,01,b8,88,00,00,02,02,11,02,00

00,00,00,02,01,11,02,00,00,00,00,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff

ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff

ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff

ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,3f

3e,00,00,37,36,00,00,51,50,00,00,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff

ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff

ff,ff,ff,ff,ff,ff,ff,ff,ff

HKR,, DCBOverride1, %REG_BINARY%, 04,25,00,23,09,20,10,01,00,02,b8,88,00,00,00,02,01,01,b8,88,00,00,02,02,11,02,00

00,00,00,02,01,11,02,00,00,00,00,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff

ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff

ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff

ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,3f

3e,00,00,37,36,00,00,51,50,00,00,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff

ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff

ff,ff,ff,ff,ff,ff,ff,ff,ff

For OEM vs 30.47

OEM and 30.47 shares:

InstalledDisplayDeivers nv4_disp

UseBestResolution 1

VgaCompatible 0

EnableAGPFW 1

SoftEDIDs 1

MapOSD3ToNV 3

OEM and 30.47 differs:

OEM:

All of the modes that NV17 supports (reference, horizontal, and vertical modes)

20.55:

HKR,, NV_Modes, %REG_MULTI_SZ%, "{*}S 320x200 320x240 400x300 480x360 512x384 640x400=1FFF;SHV 640x480 720x480 768x576 800x600 1024x768 1152x864 1280x720 1280x768 1280x800 1280x854 1280x960 1280x1024 1360x768 1366x768 1400x1050 1440x900 1600x900 1600x1000 1600x1024 1600x1200 1680x1050 1920x1200 1920x1440 2048x1536x8,16,32=1FFF"

OEM has(that 30.47 does not):

VPEENABLE 0

Mobile 3

UseSelectedDevice 1

RMMaintainDevs 1

DualViewMObile 1

PushBufferMemorySpace 2

DevSwitchSuppressMask 1

RMMaintainScaling 1

RMMaintainTVStandard 1

ReqAGPRate 4

"Attach.ToDesktop" 1

"DefaultSettings.BitsPerpel" 16

"DefaultSettings.XResolution" 800

"DefaultSettings.YResolution" 600

30.47 has (that OEM does not)

Acceleration.Level 0

MultiFunctionSupported 1

NvCplEnableHardwarePage 1

OverlayMode2 0xF00050

OverlayMode3 0x10400001

OverlayMode4 0x3

RotateFlag 4

00000002RMColorSaturationBoost 0b,00,00,00

DesktopManager 0

DXVAEnable 4

Enable256Burst 1

Enable3Dnow 1

EnableALiAGP, 1

EnableIrongateSBA, 1

EnableMMX, 1

EnableSSE, 1

EnableSSE2, 1

EnableVia4x, 1

NvCplEnableHardwarePage, 0

Override1400x1050, 1

QuickTweak, 32

UseAliCompat, 01,00,00,00

UseAMDCompat, 01,00,00,00

UseCompressedModeFormat, 1

UseIntelCompat, 01,00,00,00

UseMicronCompat, 01,00,00,00

UseNvidiaCompat, 01,00,00,00

UseRccCompat, ,00,00,00

UseViaCompat, 01,00,00,00

VideoBusMasterMode, 00,00,00,00

All of the D3d and Opengl settings

Hopefully you can help me out with this....

I am also attaching all 3 of the inf that I used in this comparison. I took out the other stuff to make the file sizes smaller.

Best wishes,

Jim

Edited by ®®®
Link to comment
Share on other sites

  • 2 weeks later...

Hi, I'd like to know if there's any update regarding with making the latest drivers (v 6X.XX) working with vpr matrix 200/220 A5 models. I tried all the drivers above v53.03 and I'm stuck with 800x600 4bit mode when I reboot, and I have no idea how to fix that.

Thanks.

BTW I'm currently using 47.18 drivers. I'd really like to try out the latest drivers to see if it helps with the performance of CS:S.

Link to comment
Share on other sites

Michelangelo, in case you read that try set the MAPOSD3toNV value from 3 to 2 in the drivers greater than 6x.xx (all new ones) and of course use the latest mobile INF

I tried this suggestion for the 67.66 drivers and it didn't work. Still booted up with 800x600 4bit mode.

I'm trying to see if installing the vpr drivers first (ancient 30.82) then updating to 67.66 works. I don't think the MAPOSD3toNV value is the problem. The vpr driver inf has the value set to 3.

BTW I just upgraded to 52.16 drivers.

Link to comment
Share on other sites

Nothing I do seems to work. The drivers simply refuse to work.

BTW last time, I tried to use the nvidia drivers directly from nvidia website, and selected the Geforce4 MX 420 when I was installing it. It seems to work partly that way. I can just add the 1280x854 resolution with 60hz refresh rate via custom adding the resolution. The problem is with the dreaded standby problem and CS:S refuses to work. It just errors out, saying the resolution won't work or something, and it tries to go back to default, which doesn't work either.

I'm now using the 53.03 drivers. Anything above and the drivers (with your inf) refuses to work.

Link to comment
Share on other sites

What chipset use the vprMatrix? VIA?

Also what is the name of the original INF and what is the version again of your original driver preloaded on the vpr?

Also could all of you run the batch HERE so we know what LCD Displays and BIOS versions you have and then attach the log file.

Edited by ®®®
Link to comment
Share on other sites

The chipset used for vpr is ALi M1671.

the name of the original INF is I believe is NVQU.inf and the original driver preloaded is 30.82

I'll run the batch later.

Link to comment
Share on other sites

Have anybody of you tried those new 70s driver with the original NVQU.INF included (for example 71.40). Also it would really help if you post your SubSys and run the batch file in the thread mentioned above. :)

And can somebody pls attach the full original 30.82 INF

Link to comment
Share on other sites

According the log file the LCD Display is not recognized properly i would say. It just installs a generic NVD0300 display, which was also the case in the BlackBar issue @ some TOSHiBA's. So maybe another EDID override would help here? We need to wait for the EDID experts here.

(I added the Subsys which is also mention in the original INF of 30.82.)

Link to comment
Share on other sites

I tried the 70's drivers with the NVQU.inf file and it still gave me a 800x600 4bit mode when rebooted.

Link to comment
Share on other sites

From the log file it appears to only install the NVD0300. If the BIOS contains good information for the display then this isn't a problem. I'd have to view the BIOS to see what it has for info.

I wouldn't put it past an EDID change to fix this issue.

Link to comment
Share on other sites

Guest jimnyuen

Thanks to all forl the help with this issue!!

Teraphy, do you need anything from our us in order for you to review the bios info? If you do can you also make sure you provide the instruction on how to obtain the information you seek!!

Again thanks for helping!!

Jim

Sorry for got to login b4 posting...

Link to comment
Share on other sites

  • 3 weeks later...

:)

Could someone run the attached program to grab the BIOS and post BIOS.ROM please?

And run the second one from a command prompt :

\> lv2goedid > edid.txt

Please and thank you :) I apologize for not keeping up on this thread.

I'm still working on these programs but they work fine for me :P

lv2gobios.exe

lv2goedid.exe

Edited by Teraphy
Link to comment
Share on other sites

Grabbing the EDID didn't work. Which is fine since the BIOS is actually OK. NVD0300 is producing valid timing.

My alternative recommendation is to add/test these lines:

HKR,, DevSwitchSuppressMask,       %REG_DWORD%,    5

HKR,, RMMaintainDevs,              %REG_DWORD%,    1
HKR,, UseHWSelectedDevice,     %REG_DWORD%,    1

I can't guaranty this will work... but these keys are in the original (nvqu.inf) and deal with the display and might affect the issues you describe.

Link to comment
Share on other sites

I'm not sure where to add those lines, but I added under [nv_SoftwareDeviceSettings] and tried the 67.66 drivers. Still no luck.

Link to comment
Share on other sites

Guest Viper50BMG

Hi, I'm new to the forum here, but I'm suffering from a similar problem on my VPR 200a5. For me, it goes to a completely black screen when I reboot after I upgrade the drivers. I then hear the "thok" type sound (most likely notifing me that I'm running in a very low resolution). I can reboot into VGA mode and rollback, but if I lose a stable rollback point (like trying a different driver without rolling back immediately after a failed attempt) I have to completely "restore" windows to it's shipped state to get device manager to recognize my Geforce as anything other that a basic VGA card. Strange... Anyhow, if anyone manages to come up with any other ideas for compatability with modern forceware that would be excellent. Let me know if I can help in any way.

Link to comment
Share on other sites

Guest FunkMonkey

Thanks for all your help so far Teraphy but I have the same problem as solgae above. I'm fairly new to this kind of thing and don't know where to inset the code that you mentioned. If you could post a simple guide saying which file to put that code in, and where in that file that would be really helpful.

Link to comment
Share on other sites

solgae placed it in the correct location. I'm at a loss for the time being until I think of the next step...

Link to comment
Share on other sites

  • 1 month later...
Guest BumBum

Hello,

well I have a few problems with the current 71.84 driver.

After install I had the "4bit and can't change resolution" problem wich I solved

easily by deactivating the checkbox "Fade out modes, which are not supported by this monitor".

Everything seems to be ok, except the fact that my refresh rate is now 54 or 55 Hz ???

There is no other option.

I wrote this also in the german part of this forum and ®®® said this should not harm my LCD Panel but should not have LCD's a refresh rate of 60 Hz ??

Link to comment
Share on other sites

  • 1 month later...
Guest jeff coloma

i've got a vprmatrix 185A5 with the same issues everyone has noted. the last working drivers are 53.13. last tried 71.84 with the added lines from teraphy within the .inf file. same results, unable to change resolution. doubt we'll ever get a workable driver. but i did try what bumbum did. i unchecked the hide unusable resolutions option.

just like bumbum, i'm limited to a 54 or 55 Mhz refresh rate, but the normal display is usable. i can use any resolution and color depth safely up to 1280x854 (default res). BUT... direct3d is unusable. if i run any app or game that uses direct3d, i get some error message about directx. ran the directx diag program to find out what was going on. directx 7 calls work fine. directx 8 and 9 calls fail due to the inability to find a compatible resolution.

if there are any settings or bios dumps or anything that i can pass along to the community, i'd be glad to helpl. i hate feeling being left in the dust.

Link to comment
Share on other sites

  • 2 weeks later...
Guest J. Hommowun

Hello everyone. I also have a vprMatrix laptop (220A5, I believe), and have had similar difficulties upgrading drivers. The information about unhiding the non-displayable modes finally gave me a way to upgrade successfully. I am currently running the latest version of the Omega Drivers (www.omegadrivers.net - which is also in the links section from this site); I do not know if this workaround will work for all drivers listed on this site, however - I seem to recall trouble with step 6 prior to attempting the Omega Drivers. Here's what I did:

Step 1 - Uninstall old drivers (may not be absolutely necessary, but avoids cross-contamination, so why not do it?). In my case, I used a combination of the Windows Add/Remove Programs Control Panel Item and DriverCleaner3 (which program unfortunately does not include its source site in its info files, but I'm sure it can be googled easily enough).

Step 2 - Run the Omega Driver install file. IMPORTANT: This must be run in a normal boot (normal with 'Enable VGA' is fine). If the file is run in Safe Mode, Windows will detect the Graphics Card as a generic VGA device and the following steps will not be possible. Never fear, though... if you did accidentally install the Omega Driver in Safe Mode, you can just run the (Re)Install Omega Drivers link from your Start Menu the next time you boot in Normal Mode. After installing, you obviously need to reboot.

Step 3 - You should now have the ever-so-famliar 640x480x4 color mode logon screen. Log on, and open the Display Properties (right-click on the desktop and hit 'Properties' or go through the Control Panel). On the Settings tab, click 'Advanced,' then click the 'Monitor' tab. Uncheck the 'Hide modes that this monitor cannot display ' box as described earlier in this thread. Click 'Ok' to accept and return to the Settings tab.

Step 4 - Set your display size to 1280x854 and your Color Depth to 32 bit (these options should be available now). You should now be running in 1280x854x32 with a 54 Hz refresh rate.

Step 5 - Now that you're actually back in good size and color, click the 'Advanced' button again and you should find that a tab for 'GeForce4 420 Go 32M' has been added to the list. Click on that tab to bring up the Graphics Card specific menu.

Step 6 - Near the bottom of the menu at left, you should find an option for 'Screen Resolutions and Refresh Rates.' Click this to open that submenu. At the bottom of this page, you'll see a box for 'Custom Resolutions and Refresh Rates.' Click the 'Add' Button. In the menu that appears, change the refresh rate to 60 Hz. Repeat this step for any resolutions you wish to run in and any color depths (i.e., to run in 800x600x32 and 800x600x16, you need to perform this step twice). NOTE: I recall that trying this on 70's drivers from this site yielded a "Cannot add custom resolution' error, but it works with the Omega Drivers.

Step 7 - After adding the resolutions you wish to use above, click on the 'Monitor' tab (its up near the 'GeForce4 420 Go 32M' tab that you're still on, remember). Set the default refresh rate to 60 Hz. This should work now, since you've configured the 'custom' resolutions with the 60 Hz rate (if you've tried it before, you know you only had 54 Hz and 55 Hz available). You should now be in 1280x854x32 at 60 Hz refresh. Hooray!

Step 8 - If you've gotten this far, you can re-enable the 'Hide modes this monitor cannot display' (conveniently located on this same tab) to clean up the large number of resolutions on the 'Settings' tab that you cannot use. You will now only see and be able to use the resolutions you've set up to use the 60 Hz refresh rate.

That's it, you're done. This set up has been working fine with both DirectX 9.0c and OpenGL. With the settings tweaking to maximum performance, I've gotten significant reduction in loading times and near elimination of frame skipping in the Sims 2 (my current graphic guzzler of choice); and let's face it, with a card so low-scale compared to current models as the old 420 Go, every bit of performance gain is a plus.

Hope this helps out, and if anyone figures out how to get the custom resolution feature to function using non-Omega drivers, I'd be very interested to hear about it.

Link to comment
Share on other sites

Guest J. Hommowun

Oh, I almost forgot to mention - at a couple points during this process you may receive an error message from Windows saying something to the effect that the current driver was designed for an older version of Windows and cannot be used, the system was started using generic VGA drivers, etc., etc. Just hit okay and ignore it; once you've finished 'reminding' the computer that it can display at 60 Hz you won't get this error anymore.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...