NVidia drivers 82.69

[LoneCrusader]

Not sure if this will help or not; I noticed your card is a PCI-E card. Try removing all references to VGARTD.VXD from the INF and remove this file from your system and registry. AGP GART drivers are not necessary for PCI-E devices and it may be interfering in this case...

[troydm]

Okey it seems I'm one step closer, I've limited my ram to 512mb and set refresh rate to 60hz (probably setting refresh rate did the trick) and now I can use 640x480 with 256 colors and Nvidia driver is loading correctly and I can see nvidia tray icon and see different settings, but going to any higher resolution or color bits causes windows to freeze.

Tried both using properties to set resolution and setting resolution from tray icon. Not sure if it's monitor related issue or a video adapter/driver one and unfortunately I don't have any other monitor to test in order to clarify what causes this issue. To me it seems to be an issue with how Generic PnP monitor driver handles modern Samsung 27" LCD PLN monitor which I'm using, my monitor supports 1920x1080 with 60hz refresh rate. I have it connected via VGA D-Sub cable. Didn't tried DVI-D one yet and I'm not sure if NVIDIA driver supports this type of connection or not.

Any suggestions what could be wrong?

Edited April 9, 2019 by troydm

[pangoomis]

NVIDIA driver for Windows 98 does support DVI-D. Try DVI then.

[truemaster]

hello im using pci-e geforce gainward 6800gs 512mb with driver 77.72 without problems in win98se. but i like to ask something is normal in the dxdiag the chip type and dac type to be n/a? in directx features the agp texture accelaration is disabled but i think thats normal since i use pci-e. also the hw id for this card is PCI\VEN_10DE&DEV_00C0&SYBSYS_080110B0&RE thanks in advance

[schwups]

Same here, so probably that's normal. (NV7800GT/ driver 82.16). Agp texture accelaration is certainly no PCIE feature and dxdiag from 2004 is older than these graphic cards. 
 

[schwups]

I tried to install R.Loews "NVIDIA GRAPHICS CARD SIZE PATCH" (PTCHNVSZ.zip) for a GF7950GT 512MB. I got "cannot open source file" on prompt "PATCHNVC NVCORE.BAK NVCORE.VXD". What am I doing wrong or does anyone have an idea?

[Drugwash]

Please make sure you followed the required steps precisely as mentioned in MANUAL.TXT, especially #8:
 

Quote

4. Boot to DOS or Safe Mode. Normal Mode probably will not work.
5. If in Safe Mode, open a DOS Box.
6. Go to the WINDOWS\SYSTEM Folder.
7. Copy the PATCHNVC.EXE from the Patch Package Folder to the WINDOWS\SYSTEM
   Folder.
8. Rename NVCORE.VXD to NVCORE.BAK
9. Run:
 
   PATCHNVC NVCORE.BAK NVCORE.VXD
 
   If you get an error, delete NVCORE.VXD, rename NVCORE.BAK back to
   NVCORE.VXD [...]

Can't think of anything else, sorry.

Edited August 17 by Drugwash
clarification

[schwups]

I hope you are doing well. I want to set the clock back a few years next and if that doesn't work I check it on another machine. Or is it possible, that the patch is broken?

[Drugwash]

I'm still alive, at least; dunno how well that is but it certainly could've been worse. My mother just passed away last month, and I'm about to get entangled in legal papers regarding the enheritance of her flat. Thank you for asking. Hope you're doing well too.

Theoretically anything is possible although if the archive were broken I suppose you would've received an error of some sort at unpack time.
As for the patch code itself - well, the documentation does mention your video card being somewhat newer than others and using certain different methods or whatever, so again theoretically it's possible for the code not to be perfect, reason why the author mentioned he should be contacted in case of failure. Unfortunately that is no longer possible now - may he rest in peace.

For what it's worth here's the checksums calculated now for the package I had here since five years ago:
 

MD5:  751d90ff7c651ea2d56c9d38644adcd3 *PTCHNVSZ.zip
SHA-1:  7d4b9940f59a51fdbb030225c6f53907b04d6017 *PTCHNVSZ.zip
MD5:
75e52e901928486098222b482d25371b *CWSDPMI.EXE
006ae40ed6efe8b3a8bbc0b4f7812ac6 *NVCHECK.EXE
5bcd26079eb14f601bbb67051ddcda61 *NVFLASH.EXE
4923ec18e90cac112407bae512842b76 *NVSIZE.EXE
77a4a4bd08f7e8a9da85a351a69c8514 *PATCHNVC.EXE
0b1a3003498b9f1e9c3d1ba372a59ff0 *PATCHOPT.EXE
1f756cc0108f0455ecd112059e5820f6 *PTCHNVSZ.EXE
a7d52d595a285a7c4f0f6eabdb0cdc1c *FIXEOI.VXD
f3fb4a63171dca8e3ee42e26c3d27dd4 *TESTEOI.VXD
SHA-1:
c10c8d48bc201f2d62b59c2c23c59864777abcfb *CWSDPMI.EXE
321adf12b2c60dd67cc4cf7b3c702cac7aaea67f *NVCHECK.EXE
bb7ecc13d68710cd183d06ddb40caa9e0b12e9db *NVFLASH.EXE
277ffbd8c887ff384ecfbc78f5579c7ea7a5b1d7 *NVSIZE.EXE
4f22262aa2319c6f5e14a8f62deb0ed8961e4f27 *PATCHNVC.EXE
f539192da5da4d6e3072e066a9248af4acbec243 *PATCHOPT.EXE
027e319484f093d73174ccd176ea8426a1669c17 *PTCHNVSZ.EXE
c274a9f2d59a0ed351ffc0d6c0e0e497f7b9878e *FIXEOI.VXD
0ad0ee47ab532c0081f5970e876f027faf95124b *TESTEOI.VXD

Personally I don't believe the patch would contain a "time bomb" as it's called considering it originally was a one-time payment commercial software. But since it is easy to set back time - albeit risky with regard to other registered commercial applications that may get confused - I guess you could try that too as a last resort.

Either way good luck!

[schwups]

My condolences. I wish you the necessary strength. My Mother still lives and is 91 years old. First I only compared MD5 of PTCHNVSZ.zip and PATCHNVC.EXE. These are the same. NVCheck and NVSize work. Thanks for sharing.

[schwups]

Yes, probably no time bomb. I also just set the clock back 5 years - to no avail.

[Drugwash]

Sorry I couldn't help more.
Thank you for your condolences. Many healthy and happy years ahead to you and the family!

[Goodmaneuver]

On 8/18/2024 at 2:26 AM, schwups said:

"cannot open source file"

Might try copying source file to "C" temp location and try, this will eliminate a hard drive error and sometimes this is necessary when installing. Is zip extractor having the trouble? If so, try other zips if not already then extract using a different method or OS.

[Drugwash]

Something in Goodmaneuver's reply above made me think of a few details that may be of importance. Make sure that:

- the NVCORE.BAK file (which should be the original NVCORE.VXD renamed by you) has no read-only and/or hidden attribute; if so remove attributes;
- the filename case is exactly as required, i.e. not NVCORE.bak/nvcore.bak/nvcore.BAK or any other variations thereof;
- the patcher executable PATCHNVC.EXE lies in the same folder as NVCORE.BAK ([C:\]WINDOWS\SYSTEM);
- the command path (either in pure DOS mode or Safe mode DOS window) is set to [C:\]WINDOWS\SYSTEM;

As I understand it the file NVCORE.BAK would be the source file while NVCORE.VXD would be the destination - that is, the final, patched file. If the patcher cannot open that file it could be either if it doesn't exist at the required location; has hidden attribute; it cannot be written to (read-only attribute); filename comparison is case-sensitive and doesn't match the requirement; code sequence(s) in the source file don't match what the patcher is expecting. Wish the error message would be more verbose.
For the latter case - code mismatch - there is nothing to be done, unfortunately, as the patch author isn't around anymore to analyze the code and modify the patcher. Only chance would be for you to try a different version of the video driver, as I seem to recall there were at least a couple of them available years ago. But best would be to perform a binary comparison of the same NVCORE.VXD between the currently installed driver and any other package variants, to avoid the hassle of installation in case those files are binary identical.

[schwups]

Thanks to you both. 

There is no "read only" and the ShutdownPatcher patches the file.

So far I thought upper and lower case doesn't matter.

I'll check everything else.

Edited August 20 by schwups