patch9x issues, patchmem, etc on win9x

[cov3rt]

I am testing patch9x (jhrobotics) on a windows 95 osr 2.5 system with intel ich7-m chipset (dell latitude d820) with 4 GB ram. i was under the impression the patch9x would be roughly equivalent or better than patchmem from rloew, but unfortunately, it seems to be regressing in some areas. i specifically downloaded "patcher9x-0.9.91-boot.ima", used winimage to extract the contents, and only integrated the "patch9x.exe" + "CWSDPMI.exe" files in my custom 98SE boot disk iso burned to a cd, (patch9x needs to run from "a:" directory).

The author of patch9x mentioned that fixes from patchmem were largely integrated with patch9x ( not fully ) but most stuff implemented and to work on w95 as well, at least in the most recent release 0.9.91, which is the one i am using, however, i cannot set maxphyspage at 40000 or higher, where as in the past with patchmem, i was able to get up to at least 48000 without problem. "maxphyspage=39999" or lower does work ( roughly 922 MB ram ). minfilecache and maxfilecache were set to 52224 throughout testing with "maxphyspage=30000" to at least up to "maxphyspage=48000".

Additionally, i cannot run patchmem if patch9x already gets installed from beforehand which i do for install media ("c:\win95") in this case before running setup. i was thinking that maybe i could get the best of both worlds for combining the patches, but this doesn't appear to be possible. running "patchmem /m" says something about vmm32.vxd already being patched and vmm.vxd not found. i searched vmm.vxd in both my install media and c: drive and could not locate such file, only vmm32.vxd is present. 

 

Edited 22 hours ago by cov3rt

[SweetLow]

> maxphyspage=39999
JFYI, MaxPhysPage measured in hehadecimal numbers. So 40000h - 39999h is 26215h, not 1.

> patch9x would be roughly equivalent
> i cannot run patchmem if patch9x already gets installed
> i was thinking that maybe i could get the best of both worlds for combining the patches
You have to think twice. patch9x just includes patchmem, what else you are waiting?

>windows 95 osr 2.5
>i searched vmm.vxd
1. It's time to read patchmem manual. There is described which files installer tries to patch.
2. If I remember correctly USB supplement should install newer version of VMM.VXD to %windir\system\vmm32\ if you wish to see this working.

[cov3rt]

ok so i was able to get patchmem /m to work in a late update phase, because the vmm.vxd file became present. it mentioned something about skipping vmm32.vxd due to no backup?, but i was able to patch vmm.vxd at least. 

while i was able to now set maxphyspage higher to as much as 44796, i could not get vbemp driver to load unless using like 30000 ( with 44796, it just went to a black screen ), and even then, when i did reboot, upon reaching desktop, windows complained on not having enough memory, and to quit one or more programs, which i found very odd, because i dont remember if i ever encountered this problem in perhaps a decade of testing win9x stuff. i tried vbemp as low as 10000, min/maxfilecache to 52224, no change for the ms dos problem, but was fixed by changing back to the standard vga display adapter driver. 

also for example using the following in my config.sys ( tested at least with maxphyspage=30000 ) prevented booting to windows, mentioning that initializing error relating to memory, needing to quit one or more programs. "DEVICE=C:\WINDOWS\HIMEM.SYS /NUMHANDLES=62 /TESTMEM:OFF
DOS=HIGH,UMB
DEVICE=C:\WINDOWS\EMM386.EXE NOEMS", though the config.sys stuff i just referenced are more optional, i dont absolutely need them, it's more of a tweak. 

all in all, it seems to point to patch9x as the problem, and i haven't even tested patch9x on windows 98SE yet with or without patchmem, which i'd be doing soon. outside these things, other programs / functions were mostly ok, i was able to run for example hwinfo32 6.42, TaskInfo2002 v. 4.0.0.51, process explorer 8.52.