Drugwash Posted August 20, 2024 Posted August 20, 2024 4 hours ago, schwups said: So far I thought upper and lower case doesn't matter. Theoretically it shouldn't, in normal operation. AFAIK Windows doesn't care about the filename case as Linux does, but I'm not 100% sure how this works in DOS mode. It's been quite a while since last tinkering with DOS and 9x, and my memory is failing rapidly. Besides that there is an admittedly slight possibility that the comparison code in the patch would be very strict. Long gone are the days when I would quickly disassemble the code to see how it works, so can't say anything for sure. But an all-caps filename would easily chuck this off the list. Well, that's about it, can't think of anything else. Hope you get to the bottom of it one way or another. Viel Glück!
deomsh Posted August 20, 2024 Posted August 20, 2024 I just tested the PATCHNVC.EXE on NVCORE.VXD renamed to NVCORE.BAK inside Virtual Box 7 in MS-DOS safe mode (no Windows installation). No errors. I found about 5 patched locations, seems to coincide with HEX-strings inside PATCHNVC.EXE. The last one for instance: If I repeat the proces with patched NVCORE.VXD renamed to NVCORE.BAK I get a message: I have no 512MB 7xxx NVIDIA card, so no testing possible FOR ME...
defuser Posted August 20, 2024 Posted August 20, 2024 I suspect that your problem may be related to the wrong file name. The patch works correctly, even if I execute it like this: D:\PTCHNVSZ>PATCHNVC 1 NVCORE.VXD or even so: D:\PTCHNVSZ>PATCHNVC 1 2 The driver versions that I successfully checked with this patch are 82.69, 81.98 and 77.72. I applied the patch to these files under Windows XP (From there, it's easy to immediately replace the driver files in the target system, so as not to do it under DOS). The patch worked correctly in all cases and there were no more 512MB issues with these fixed versions. Some time ago, I just tested all three versions with a 512MB card.
schwups Posted August 21, 2024 Posted August 21, 2024 I found my mistake. Setting the command path beforehand on system seems crucial. On 8/20/2024 at 11:07 AM, Drugwash said: - the command path (either in pure DOS mode or Safe mode DOS window) is set to [C:\]WINDOWS\SYSTEM; Until now I thought it doesn't matter and I could enter the entire path starting from the command path C:\, which apparently doesn't work in this case. In any case, the new file was created without comment and confirmation. Thanks to you all again.
deomsh Posted August 21, 2024 Posted August 21, 2024 Congratulations. But: according to step 6 of the manual you should have been in 'C:\WINDOWS\SYSTEM' already (or 'C:\%windir%\SYSTEM' in case of another WINDOWS-directory). So changing PATH shouldn't be needed.
Drugwash Posted August 21, 2024 Posted August 21, 2024 35 minutes ago, schwups said: Setting the command path beforehand on system seems crucial. There is this concept of working directory. In your case you launched the executable with a full path from a different directory than the one the executable lied in, and it worked for running the exe, but the working directory remained the one where you launched the command from. As the exe most likely works with relative paths it was looking for the source file NVCORE.BAK in the working directory, that is C:\ (or whatever the DOS path was in the command window), instead of C.\WINDOWS\SYSTEM, and obviously it couldn't find it there. :) Anyway, glad you finally figured it out. Good luck ahead!
schwups Posted August 22, 2024 Posted August 22, 2024 (edited) Completed with NVSIZE BIOS PATCH: Now DXDIAG gives 506MB VRAM. It has reduced available 32bit RAM by 512MB. 3008MB => 2496MB POST: 7104MB => 6592MB Edited August 22, 2024 by schwups 1
ruthan Posted January 14 Posted January 14 (edited) 6150 on Board on WIn98SE with patches failing.. I tried to modify - original 81.xx inf files and 82.69 abd 82.69 Maximus decimus tweaker drivers to make Geforce 6150 - Nforce430 on ECS MCP61PM-AM board working. i can install drivers fine. I but always hit classic Windows protection error wall, SIV is reporting that Video card is Nforce 405 (with this name its detected in Windows Xp), it should be 430, but it tried both same with forcing Geforce 6200 driver. Nvidia is not mentioned in original drivers.. In original i tried to add as NV30 same codename as Geforce 6200. I have some more modern board with Geforce 7050, when i expect the same result.. I wonder have someone even working nforce on board videocard like this in WIndows 9x.. My experience is that sometimes clean install can do such things, but more used machine is starting to hit Windows protection error, more and more. Edited January 15 by ruthan
defuser Posted January 14 Posted January 14 (edited) On 8/23/2024 at 2:38 AM, schwups said: Completed with NVSIZE BIOS PATCH: Now DXDIAG gives 506MB VRAM. It has reduced available 32bit RAM by 512MB. 3008MB => 2496MB POST: 7104MB => 6592MB Greetings. I have a video card with a similar design to yours and it looks like I will soon have to do the same procedure... Let me ask you, after the BIOS patch, do you have a normal exit from DOS (Back to WINDOWS) using the "Exit" command? This is a key issue that the NVCORE.VxD patch failed to address. More precisely, it was this patch that broke the exit from DOS, which was tested on the reference 128MB GeForce 5 video card, first with the original NVCORE.VxD, with which the exit from DOS worked fine, and then with the patched NVCORE.VxD, with which the exit from DOS stopped working, all other things being equal. And even fine-tuning MTRR did not give positive results in this issue (But it repeatedly increased the speed of 2D and page scrolling in browsers, as well as the performance of games under DOS). Therefore, there is only one hope left - a BIOS patch. Edited January 14 by defuser
SweetLow Posted January 15 Posted January 15 10 hours ago, defuser said: do you have a normal exit from DOS (Back to WINDOWS) using the "Exit" command? JFYI: schwups, OS:ME
schwups Posted January 15 Posted January 15 Indeed currently I have no Win98(SE) installation on a hard drive. On 1/14/2025 at 8:20 PM, defuser said: Greetings. I have a video card with a similar design to yours and it looks like I will soon have to do the same procedure... Let me ask you, after the BIOS patch, do you have a normal exit from DOS (Back to WINDOWS) using the "Exit" command? This is a key issue that the NVCORE.VxD patch failed to address. More precisely, it was this patch that broke the exit from DOS, which was tested on the reference 128MB GeForce 5 video card, first with the original NVCORE.VxD, with which the exit from DOS worked fine, and then with the patched NVCORE.VxD, with which the exit from DOS stopped working, all other things being equal. And even fine-tuning MTRR did not give positive results in this issue (But it repeatedly increased the speed of 2D and page scrolling in browsers, as well as the performance of games under DOS). Therefore, there is only one hope left - a BIOS patch. I checked it on ME. It's probably just as it should be in the case of the DOS Box here. The box closes using the "Exit" command. But you changed the description of the problem. So maybe now you mean "Real DOS". 1
defuser Posted January 16 Posted January 16 14 hours ago, schwups said: Indeed currently I have no Win98(SE) installation on a hard drive. I checked it on ME. It's probably just as it should be in the case of the DOS Box here. The box closes using the "Exit" command. But you changed the description of the problem. So maybe now you mean "Real DOS". Yes, I'm sorry, I was too quick to ask. This, of course, was about getting out of real DOS...
defuser Posted January 18 Posted January 18 In general, I flashed this patched BIOS and after that it booted up immediately in XP without any problems, the memory in the system became 512MB less. But in Windows 98, it loaded only in 640x480@16 colors. In Device Manager, it says "This device cannot find any free Memory Range resources to use (Code 12.)". And if you set resources manually in safe mode, it already writes the following "This device is either not present, not working properly, or does not have all the drivers installed. (Code 24.)". Then I updated the driver to version 82.69 and now it always writes " Protection Error. You need to restart your computer". What I've already tried: - add SPLIT8MB in AUTOEXEC.BAT - limit memory to a safe 2GB (as well as up to 512MB) - apply PATCHMEM /A /C: 128 / M /P - delete EMM386.EXE - register EMMExclude=A000-FFFF in SYSTEM.INI Technical information: NVIDIA Quadro FX 4500 [DISPLAY] ** DEVICE: PCI\VEN_10DE&DEV_009D&SUBSYS_032210DE&REV_A1\000800 ** DRIVER: DISPLAY\0001 ** MFG: NVIDIA ** HARDWAREID: PCI\VEN_10DE&DEV_009D&SUBSYS_032210DE&REV_A1 PCI\VEN_10DE&DEV_009D&SUBSYS_032210DE PCI\VEN_10DE&DEV_009D&REV_A1&CC_0300 PCI\VEN_10DE&DEV_009D&CC_030000 PCI\VEN_10DE&DEV_009D&CC_0300 ** COMPATIBLEIDS: PCI\VEN_10DE&DEV_009D&REV_A1 PCI\VEN_10DE&DEV_009D PCI\VEN_10DE&CC_030000 PCI\VEN_10DE&CC_0300 PCI\VEN_10DE PCI\CC_030000 PCI\CC_0300 ** Registry.MatchingDeviceId: PCI\VEN_10DE&DEV_009D ** Registry.Inf: NVAGP.INF:[NV30] ** CLASSGUID: {4d36e968-e325-11ce-bfc1-08002be10318} ** CLASS: DISPLAY ** CAPABILITIES: 00000014 ** Registry.ProviderName: NVIDIA ** Registry.DriverDate: 5-28-2023 ** Registry.DevLoader: *vdd ** Devnode Status: 18006EA6 ** Problem: Devnode Problem = 0000000Ch (NORMAL_CONFLICT) ** Tree Level: 3 MTRRcap Register: 000000FE 0000000000000D0A Variable MTRR Count: 10 Fixed MTRR Supported: TRUE Write-combining (WC) Memory Type Supported: TRUE SMM Memory Range Registers (SMRR) Supported: TRUE MTRRdefType Register: 000002FF 0000000000000C00 Default Cache Type: 00h Uncacheable MTRR Enabled: TRUE Fixed MTRR Enabled: TRUE Reported Processor Physical Address Size (bits): 39 Variable MTRRs - Base, Mask and Decription: 00000200 0000000000000006 0000007E00000800 8G @ 0 / WB 00000202 0000000200000006 0000007FE0000800 512M @ 8G / WB 00000204 0000000220000006 0000007FF0000800 256M @ 8G 512M / WB 00000206 0000000230000006 0000007FF8000800 128M @ 8G 768M / WB 00000208 0000000238000006 0000007FFC000800 64M @ 8G 896M / WB 0000020A 000000023C000006 0000007FFE000800 32M @ 8G 960M / WB 0000020C 00000000C0000000 0000007FC0000800 1G @ 3G / UC 0000020E 0000000000000000 0000000000000000 Not used 00000210 0000000000000000 0000000000000000 Not used 00000212 0000000000000000 0000000000000000 Not used Has anyone ever encountered something like this? While I would not like to roll back the BIOS back, but first try to fix everything that is already there. Any ideas?
SweetLow Posted January 18 Posted January 18 1 hour ago, defuser said: 0000020C 00000000C0000000 0000007FC0000800 1G @ 3G / UC Looks like BIOS reserved 512M for this card as 256M card usually takes 768M of address space on PCI-E systems. But show any (good) DOS PCI dumper info for this card to know it exactly.
defuser Posted January 18 Posted January 18 11 minutes ago, SweetLow said: Looks like BIOS reserved 512M for this card as 256M card usually takes 768M of address space on PCI-E systems. But show any (good) DOS PCI dumper info for this card to know it exactly. Vendor 10DEh NVIDIA Corporation Device 009Dh G70GL [Quadro FX 4500] Command 0007h (I/O Access, Memory Access, BusMaster) Status 0010h (Has Capabilities List, Fast Timing) Revision A1h, Header Type 00h, Bus Latency Timer 00h Self test 00h (Self test not supported) Cache line size 64 Bytes (16 DWords) PCI Class Display, type VGA Subsystem ID 032210DEh Unknown Subsystem Vendor 10DEh NVIDIA Corporation Address 0 is a Memory Address (anywhere in 0-4Gb) : F6000000h Address 1 is a Memory Address (anywhere in 64-bit space, Prefetchable) : C0000000h Address 3 is a Memory Address (anywhere in 64-bit space) : F5000000h Address 5 is an I/O Port : 0000E000h System IRQ 11, INT# A Expansion ROM of 0Kb decoded by this card (Currently disabled) New Capabilities List Present: Power Management Capability, Version 1.1 Does not support low power State D1 or D2 Does not support PME# signalling Current Power State : D0 (Device operational, no power saving) Message Signalled Interrupt Capability MSI is disabled MSI function can generate 64-bit addresses PCI Express Capability, Version 1 Device/Port Type : PCI Express Endpoint Device Unsupported Request Severity is Non-Fatal Non-Fatal Error Detected Unsupported Request Detected Maximum Link speed : 2.5Gb/s Maximum Link Width : x16 Link Port Number : 0 Common Clock Configuration In Use Current Link speed : 2.5Gb/s Current Link Width : x8 Conventional Memory: INT 12h Memory below 1M: 635 KB (00000000 - 0009EC00 : 0009EC00) Extended Memory: INT 15h, AH=88h Memory above 1M: 0 KB INT 15h, AX=E801h Free between 1M and 16M: 0 KB Free above 16M: 0 KB Configured between 1M and 16M: 15360 KB (00100000 - 01000000 : 00F00000) Configured above 16M: 2812928 KB (01000000 - ACB00000 : ABB00000) INT 15h, EAX=0000E820h 0000000000000000 - 000000000009EC00 : 000000000009EC00 1 (Available) 000000000009EC00 - 00000000000A0000 : 0000000000001400 2 (Reserved) 00000000000E0000 - 0000000000100000 : 0000000000020000 2 (Reserved) 0000000000100000 - 0000000020000000 : 000000001FF00000 1 (Available) 0000000020000000 - 00000000ACBF9000 : 000000008CBF9000 2 (Reserved) 00000000ACBF9000 - 00000000ACC00000 : 0000000000007000 4 (ACPI NVS) 00000000ACC00000 - 00000000AD6B2000 : 0000000000AB2000 2 (Reserved) 00000000AD6B2000 - 00000000AD95C000 : 00000000002AA000 2 (Reserved) 00000000AD95C000 - 00000000BD038000 : 000000000F6DC000 2 (Reserved) 00000000BD038000 - 00000000BE024000 : 0000000000FEC000 2 (Reserved) 00000000BE024000 - 00000000BE038000 : 0000000000014000 3 (ACPI Reclaim) 00000000BE038000 - 00000000BE18B000 : 0000000000153000 4 (ACPI NVS) 00000000BE18B000 - 00000000BF7FF000 : 0000000001674000 2 (Reserved) 00000000BF7FF000 - 00000000BF800000 : 0000000000001000 2 (Reserved) 00000000F8000000 - 00000000FC000000 : 0000000004000000 2 (Reserved) 00000000FEC00000 - 00000000FEC01000 : 0000000000001000 2 (Reserved) 00000000FED00000 - 00000000FED04000 : 0000000000004000 2 (Reserved) 00000000FED1C000 - 00000000FED20000 : 0000000000004000 2 (Reserved) 00000000FEE00000 - 00000000FEE01000 : 0000000000001000 2 (Reserved) 00000000FF000000 - 0000000100000000 : 0000000001000000 2 (Reserved) 0000000100000000 - 000000023E000000 : 000000013E000000 1 (Available) Available: Bytes KiB MiB GiB TiB Below 4GiB: 536472576 523899 511.6 0.5 0.0 Above 4GiB: 5335154688 5210112 5088.0 5.0 0.0 Total: 5871627264 5734011 5599.6 5.5 0.0
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now