56.55 is out, don't dawdle get it now before it's cold !!

[mobilenvidia]

Thats right, it here, it even caught me off guard.

I was expecting 56.54 the highest Forceware I knew off, 56.52 and 56.53 exist also.

These drivers come from Gainward and are desktop based.

Anyway new goodies to play with, and now just right click on the desktop press 'Digital Display' and the control panel appears like magic. Finally nvidia has this sorted.

There are numerous wee changes in layout.

Don't just sit there gawking at the screen start downloading.

The Driver it self is hosted by me, so any probs in downloading let me know.

Download of INF and Driver just click link in my profile.

As always feedback encouraged.

Enjoy,

Pieter.

PS anybody that knows the fastest settings for Benchmarking let me know, as I have quite a performance drop, but then there a few new settings I havn't had a chance to play with.

[®®®]

just saw them at stationdriver. let's see how these work. A pity that they are not mobile.

[mobilenvidia]

Yeah, lets hope that 56.54 gets released soon.

BTW nice signature.

Pieter.

[®®®]

BTW nice signature.

:oops: :oops: :oops:

idea stolen from you, shame on me, but i had to HAVE this little image in my signature, too.

There are new files in this package: nvsysrot.dll. and nviewx.dll responsible for the nView CPL,

____

EDIT

they are not copied/used during installation on my machine.

Using a slightly modified (removed ALL tweaks) 20.03/56.55 results in a working combo with a new nView Desktop Manager Wizard with lots to play with when TVout or VGAout is hooked. AutoDetection works. Changing resolution on VGAout or TV works too.

Haven't played yet, but we have a new Profile Manager for lots of games, so if errors in OGL or whatever occur, have a play with that.

Nice driver with great hope to the upcoming mobile release.

benchmarks here: http://forums.laptopvideo2go.com/index.php?showtopic=194

[LSudlow]

Like Pieter, 56.55 gives me a performance drop, but it's not severe and probably isn't noticeable in real life. I do like some of the new interface features.

Driver............3DMark01.............3DMark03

53.03............6963.....................1335

53.04............6965.....................1332

53.06............6976.....................1333

53.30............6940.....................1335

56.55............6744.....................1306

Machine: Dell Inspirion 5150

BIOS: A31

CPU: 3.06 GHz Pentium 4M (Non HyperThreading)

RAM: 512MB

GPU: Nvidia FX Go5200 w/ 64MB RAM

OS: XP Pro

[mobilenvidia]

I must have a look at 56.55 properly now, I've been away.

And the new Domain has taken over most of my time.

Pieter.

[Raptor]

The new Forceware 56.55's seem to only show a significant performance boost with the GeForce4 cards.. I have already tried it myself and it rocks! Noticable FPS increase.. I love the new GUI and the Game profile page!

I was wondering if anybody else is not seeing the overclocking menu on Display Properties page.. I would really love to be able to use that auto-overclocking feature I've heard so much of... http://downloads.guru3d.com/download.php?det=737&56805

I will benchmark these drivers soon.. I just need to do a reformat to clean my system of all the stuff that has built up over time..

Raptor

[Guest]

Tried this driver too and suspend-resume works fine with this version now :)

[LSudlow]

I was wondering if anybody else is not seeing the overclocking menu on Display Properties page..

I have the overclocking page but I'm missing the OpenGL page.

Go figure.

[Guest PeteSL]

Loaded 56.55 with Pieter's inf on my Toshiba laptop with the 420 Go chipset. DARN! I was so hoping that they would fix the display detection bug but they didn't. The driver is still claiming that my display is a 1588x1200 nVidia default flat panel instead of the 1600x1200 Toshiba flat panel. Ah well, I guess I can keep on hoping.

[Teraphy]

The latest are 56.56 02/04/2004...

56.54 would also be a good release, but anything below that has issues.

[mobilenvidia]

Guys,

I do believe that the GF4 4x0go has the Performance page disabled.

A 440go is an overclocked 420.

And a 460go is an overclocked 440.

nVidia presumably turned of the OCing because of it.

There is no way of turning it on, unless someone has a BIOS hack to enable it.

Pieter.

[Tenstrum]

Has anyone tried this on the Toshiba laptops w/black bar issue? I really want to get my drivers updated....

:)

[Guest]

Hey all, I have a Dell Precision M50 with the crappy "won't-display-past-1280x1024" problem and the 56.55 with the modded .inf from the laptopvideo2go page works GREAT.

THANK YOU SO MUCH EVERYONE!!! I am SO much happier now. I wish I could tell you more detailed things but I'm afraid I'm not into overclocking, I just want to play the few games I get. I know nothing about clockspeeds, benchmarks to run, good numbers etc, I just know I'm at 1600x1200 with a full display properties control panel and 3d accel. I'd be happy to answer questions, but pls email me at nibelung001@yahoo.com. I won't be checking this forum.

THANKS AGAIN!!! YOU GUYS KICK arse!

[mobilenvidia]

You are most welcome.

I'm glad this is finally sorted for M50's and I presume i8200's as well.

Spread the word.

This hasn't happened since 42.57 !

Enjoy,

Pieter.

[mobilenvidia]

Just uploaded v 20.04 of my INFs with the following DLLs added:

nvsysrot.dll

nviewx.dll

hpqvdisp.dll (don't know what it does but it's there)

Install 56.55 with the setup.exe program so that nview installs properly.

Enjoy,

Pieter.

[Guest PeteSL]

Pieter,

Any chance of getting the 56.54 inf that had all of the Toshiba settings in it? I would like to try and see if I can get full 1600x1200 display (maybe they have something special in it for the Toshiba 1600x1200 display.

Thanks.

[Guest]

Argh!

Just tried the new drivers on my Dell D800 GeForce 4200 and I still have the standby issue :)

The screen seems to "melt" when going to standby and on resuming, I think the computer works, but all I get is a black screen... I've tried all the tips on this forum. The only drivers that work for me are the 44.68

Anyone have any other ideas I could try?

Thanks in advance,

Beugnet2

[luxojr]

Yep, man...

we still have standby issue, me too with a Quadro4 700 GoGL. As you say the notebook works everything works, the only thing that doesn't wake up from the standby mode are the light lamps inside the LCD PANEL. Infact if you look carefully, under good light condition, u can see the windows desktop.

That's what i know, hope this help.

Nice day, LuxoJr

[®®®]

peteSL, Guest, LuxoJr,

try adding the following settings from your original OEM inf to the 20.04 inf under

[nv_SoftwareDeviceSettings]

for PeteSL:

HKR,, DevSwitchSuppressMask, %REG_DWORD%, 3

HKR,, DisableTVClockInversion, %REG_DWORD%, 1

HKR,, DualViewMobile, %REG_DWORD%, 1

HKR,, DualviewPolicyID, %REG_DWORD%, 1

HKR,, HotkeyPrimaryDevScheme, %REG_DWORD%, 1

HKR,, HotKeyUseOSResolution, %REG_DWORD%, 1

HKR,, IgnoreHWSelectedDeviceInSpanningMode,%REG_DWORD%,1

HKR,, Mobile, %REG_DWORD%, 2

HKR,, ModesetBlankDelay, %REG_DWORD%, 150

HKR,, NV11MLFNT, %REG_DWORD%, 1

HKR,, OverlayMode3, %REG_BINARY%, 01,00,00,00

HKR,, Override1400x1050, %REG_DWORD%, 1

HKR,, OverrideMonitorPower, %REG_DWORD%, 1

HKR,, PanScanSelection, %REG_DWORD%, 1

HKR,, PowerSaverHsyncOn, %REG_DWORD%, 1

HKR,, PushBufferMemorySpace, %REG_DWORD%, 2

HKR,, SoftEDIDs %REG_DWORD%, 0

HKR,, UseGDIRefreshRate, %REG_DWORD%, 1

HKR,, UseHWSelectedDevice, %REG_DWORD%, 1

for guest:

HKR,, CH7009.default.flickerfilter, %REG_DWORD%, 3

HKR,, DetectedDevsCacheTime, %REG_DWORD%, 0x1194

HKR,, DevSwitchSuppressMask, %REG_DWORD%, 1

HKR,, DFPAsDefaultMonitor, %REG_DWORD%, 1

HKR,, DualViewHotKeyPolicy, %REG_DWORD%, 1

HKR,, DualViewMobile, %REG_DWORD%, 2

HKR,, DualviewPolicyID, %REG_DWORD%, 2

HKR,, dynEngCtrlEnabled, %REG_DWORD%, 2

HKR,, EnableAGPSBA, %REG_DWORD%, 0

HKR,, EnablePersistenceStorage, %REG_DWORD%, 1

HKR,, EnumerateTVAsACPIDevice, %REG_DWORD%, 1

HKR,, ExternalSSDeviceRestore, %REG_DWORD%, 1

HKR,, HotKeyUseOSResolution, %REG_DWORD%, 2

HKR,, InstalledDisplayDrivers, %REG_MULTI_SZ%, nv4_disp

HKR,, LidBehavior, %REG_DWORD%, 0x11

HKR,, MapOSD3ToNV, %REG_DWORD%, 3

HKR,, ModesetBlankDelay, %REG_DWORD%, 1

HKR,, MVNumKeys, %REG_DWORD%, 0

HKR,, NV11MLFNT, %REG_DWORD%, 2

HKR,, OverlayMode2, %REG_BINARY%, 52,00,10,00

HKR,, OverlayMode3, %REG_BINARY%, 00,00,00,00

HKR,, PanScanSelection, %REG_DWORD%, 0

HKR,, PMMCLOCKClone, %REG_DWORD%, 0xbebebe00

HKR,, RMMaintainDevs, %REG_DWORD%, 1

HKR,, RmMaintainScaling, %REG_DWORD%, 1

HKR,, RMMaintainTVStandard, %REG_DWORD%, 1

HKR,, RotateFlag, %REG_DWORD%, 4

HKR,, SBIOSHandlesHotkeyInhibit, %REG_DWORD%, 1

HKR,, SoftEDIDs, %REG_DWORD%, 1

HKR,, UseCVTReducedBlanking, %REG_DWORD%, 0x80000020

HKR,, UseHWSelectedDevice, %REG_DWORD%, 1

HKR,, UseSingleSurfaceSemaphore, %REG_DWORD%, 1

and for LuxoJr:

HKR,, CH7019.default.flickerfilter, %REG_DWORD%, 3

HKR,, DevSwitchSuppressMask, %REG_DWORD%, 1

HKR,, DFPAsDefaultMonitor, %REG_DWORD%, 1

HKR,, DualViewHotKeyPolicy, %REG_DWORD%, 1

HKR,, DualViewMobile, %REG_DWORD%, 2

HKR,, DualviewPolicyID, %REG_DWORD%, 2

HKR,, dynEngCtrlEnabled, %REG_DWORD%, 2

HKR,, EnableAGPSBA, %REG_DWORD%, 0

HKR,, EnablePersistenceStorage, %REG_DWORD%, 0

HKR,, EnumerateTVAsACPIDevice, %REG_DWORD%, 1

HKR,, HotKeyUseOSResolution, %REG_DWORD%, 0

HKR,, LidBehavior, %REG_DWORD%, 5

HKR,, MapOSD3ToNV, %REG_DWORD%, 3

HKR,, ModesetBlankDelay, %REG_DWORD%, 1

HKR,, MVNumKeys, %REG_DWORD%, 0

HKR,, NV11MLFNT, %REG_DWORD%, 2

HKR,, OverlayMode2, %REG_BINARY%, 52,00,10,00

HKR,, OverlayMode3, %REG_BINARY%, 00,00,00,00

HKR,, PanScanSelection, %REG_DWORD%, 0

HKR,, RMMaintainDevs, %REG_DWORD%, 1

HKR,, RmMaintainScaling, %REG_DWORD%, 1

HKR,, RMMaintainTVStandard, %REG_DWORD%, 1

HKR,, RotateFlag, %REG_DWORD%, 0

HKR,, SBIOSHandlesHotkeyInhibit, %REG_DWORD%, 1

HKR,, SoftEDIDs, %REG_DWORD%, 1

HKR,, UseBestResolution, %REG_DWORD%, 1

HKR,, UseCVTReducedBlanking, %REG_DWORD%, 0x80000020

HKR,, UseHWSelectedDevice, %REG_DWORD%, 1

HKR,, UseSingleSurfaceSemaphore, %REG_DWORD%, 1

HKR,, WidePanelBehavior, %REG_DWORD%, 0

You can check these settings and compare them with your original OEM inf and then add them to Pieters 200.04 inf. Give it a try :wink:

[Guest [mouta]]

Hello all, i'm new here, i download the drivers from Pieter site, i have one question, i already sent him a mail but got no answer... why the new Inf's doesn't have the support to GeForce 4 488 Go? It's my video card, i would love to trya forceware just to see if it's better than a Detonator, i installed the 53.03 from StarStorm and they were good but i got som graphical issues in games like PES3 and Dead to Rights, can you tell me wjy Pieter removed the GeForce 4 488 Go and if it's just a matter of copy the line from the other inf's? Thanks in advance and please Pieter don't forget my video card in the next Inf. :)

[mobilenvidia]

Mouta,

Whoops :oops: , by accident I removed a line I shouldn't have, it's been fixed (v20.05).

488go is back in business.

As for E-mail, I have nothing from you anywhere, best to stick to Forum.

I keep an eye on here regulary.

Enjoy,

Pieter

[Guest [mouta]]

Mouta,

Whoops  :oops: , by accident I removed a line I shouldn't have, it's been fixed (v20.05).

488go is back in business.

As for E-mail, I have nothing from you anywhere, best to stick to Forum.

I keep an eye on here regulary.

Enjoy,

Pieter

Thanks, i thaught my video card had something wrong, glad to see it was a mistake. :) Keep up the good work Pieter. The e-mail must not arrived... dunno, do you think i should use this forceware instead of the Detonators? And about the 56.54 are they really mobile forceware? Will they be released?

[Guest]

dontknow,

Tried your tip, still doesnt fix the Suspend mode. Funny how the screen seems to "melt" when it goes out though :)

Beugnet2

[Guest PeteSL]

I had already tried those settings, unfortunately. Those are what are in my original OEM inf (and I reset SoftEIDEs to 0 at the same time) so I gave that a shot. This I was hopeful that maybe they might actually be testing with the Toshiba's since it was indicated that the definitions were in the 56.54 inf file. Ah well. Guess I'll just have to stare at that blank space on the right.

Thanks.