cov3rt

Some info on missing exports for gom player 2.1.43.5119 on a windows 95 osr 2.5 fully updated system: . gom.exe - user32.dll - - AnimateWindow, GetMonitorInfoA, MonitorFromRect . gomx.dll - d3d9.dll - Direct3DCreate9 . libavcodec.dll - kernel32.dll - InterlockedCompareExchange, InterlockedExchangeAdd . Mpeg2DecFilter.ax - kernel32.dll - IsDebuggerPresent. USER32.dll - ChangeDisplaySettingsExA, ChangeDisplaySettingsExW

I decided now to try to make Irfanview 4.44 work as an alternative, but faced many unexpected results, like no fully working autohotkey 1.0.48.5 / autoit 3.1.12.1 scripts, and almost half of the plugins in the package do not work. I did mention in my other thread on patch9x that i was able to work around the SSE2 instructions problem so it will at least open regular jpeg/jpg files, but there are still many things unresolved for my purpose of using the program. I do not plan on trying to make most of the non working ones work, i did several attempts with ghidra with chatgpt but was not able to get anything to work yet. My main focus is webp.dll which currently does not work. You can use some older versions for some of the plugins and they'll work, like jpeg2000.dll version 4.3.3.0, but a good remainder of plugins still do not work. Here is what's missing for unpacked webp.dll checked on a fully updated windows 95 osr 2.5 system: kernel32.dll missing exports ( implicitly dependent modules ): EncodePointer DecodePointer GetModuleHandleExW IsDebuggerPresent IsProcessorFeaturePresent SetFilePointerEx InitializeCriticalSectionAndSpinCount

For the ethernet, If you can, try to find a package that uses B57W9X for the inf with driver version 7.80. I had that working for "VEN_14E4&DEV_165D&SUBSYS_865D1028&REV_01" on 98SE.

Thanks for the referencing to SSE2, i got some help from chatgpt to make a patched i_view32.exe which now loads jpeg/jpg files without error ( redirects to MMX i believe instead of SSE2 for the problematic path, though i've only done limited testing. ), also working that previously didnt is .crw file. i removed vtf.dll from the plugins as it was the one causing the "isdebuggerpresent" problem when trying to check installed plugins. i may not patch that file because it's not really that important, more of a niche plugin anyways. will update more later on other stuff. Also im gonna attach the patched i_view32.exe for use on irfanview 4.44 on windows 9x ( windows 95 osr 2.5 or newer ), should be up for at least a few days to download. https://limewire.com/d/Rfwr7#NECTyRfjXh

Some other info below for config.sys profiles, also mem /c /p showed 10.8 KB of UMB and 600 KB of conventional memory free when using specifically the emm386.exe ram auto option below, the no good indicator means windows could not boot, it gave the insufficient memory message during boot. this is for testing with patch9x 0.9.91 + fix95cpu v3.0 and rloew's "patchmem /m" all installed from beforehand using maxphyspage=44796 and minfilecache/maxfilecache=52224. the NOEMS option doesn't work with patch9x apparently.: full config.sys sample "DEVICE=C:\WINDOWS\HIMEM.SYS /NUMHANDLES=62 /TESTMEM:OFF DOS=HIGH,UMB DEVICE=C:\WINDOWS\EMM386.EXE RAM AUTO ", last line substitutes below: DEVICE=C:\WINDOWS\EMM386.EXE NOEMS FRAME=NONE - NO GOOD DEVICE=C:\WINDOWS\EMM386.EXE NOEMS NOVCPI - NO GOOD DEVICE=C:\WINDOWS\EMM386.EXE RAM HIGHSCAN - GOOD DEVICE=C:\WINDOWS\EMM386.EXE RAM - GOOD DEVICE=C:\WINDOWS\EMM386.EXE RAM 1024 - GOOD DEVICE=C:\WINDOWS\EMM386.EXE RAM 2048 - GOOD DEVICE=C:\WINDOWS\EMM386.EXE RAM AUTO - GOOD

Thanks jumper, but im already past that point, your method could be a potential workaround for specific cases. I'm at a point where the system.ini settings probably aren't as relevant as so much trying to figure out what could be the culprit to the misc. problems i was having, like ms dos prompt in windows not being able to launch with vbemp driver, etc. It could be that patch9x + fix95cpu v.3.0 + patchmem just dont do well together. i think i can uninstall patchmem to see if that might help with specific problems, but honestly, at this point, im really just trying to get specific programs to work, for example, irfanview 4.38 / 4.44 both have major problems and i cant get keyman6-2-183-0 to launch it's keyman application, mentioning kernel32.dll missing export to isdebuggerpresent, ( keyman32.dll and keyman.exe were culprits as viewed by dependency walker ). also the same missing export kernel32.dll isdebuggerpresent was mentioned by irfanview 4.44 when trying to select the installed plugins menu, and it happens when using the full plugins for 4.38 as well. both irfanview versions fail for loading any jpg file / about page, giving precisely the same error. i really wanted to get at least 4.32 or newer to work of irfanview, because of the webp plugin for example. bmp files work without problem, i tested both without any plugins, but they still fail with jpg files, even using the thumbnail mode to browse a directory with jpg files crashes the system. here is the error specifically from irfanview 4.38: I_VIEW32 executed an invalid instruction in module I_VIEW32.EXE at 0157:004dceb0. Registers: EAX=00010001 CS=0157 EIP=004dceb0 EFLGS=00210202 EBX=007fd538 SS=015f ESP=007dbd78 EBP=007dbe40 ECX=00800930 DS=015f ESI=00800930 FS=3017 EDX=007fd190 ES=015f EDI=00000000 GS=2b7e Bytes at CS:EIP: 66 0f 6f 06 66 0f 6f 4e 20 66 0f d5 02 66 0f d5 Stack dump: 00000000 007fc990 007f4320 007dc0f0 007f4962 000013f6 00000000 0000000e 00000011 007f4320 bff713ee 00000157 bff78913 00000801 007dbdf0 000ee524

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.

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.

I was able to figure out the main issue after chatgpt referenced boot image related stuff. essentially it was not using the actual modified stuff, because i wasn't providing the .img/.ima base file from beforehand when creating the boot media via the software i was using. i know you did mention about this earlier, but i didn't understand what that meant exactly in my context. for those starting with just the 98SE boot disk iso, you'll need winimage + ultraiso and / or anyburn, but if you already have a stock 98SE boot image in .img form, then all you need is ultraiso i believe. i had chatgpt write a short guide on this, but i'm also providing the boot disk in .ima form already + my modified 98SE boot disk iso already made as attachments for some time so people can download and use / test, though i haven't been able to test the iso one's actual functionality, because i only have unsupported systems at the moment that are incompatible, like "hp 14-dq0054dx" using an external usb optical drive, shows as no fixed drive present, AHCI not loaded, etc. the boot disk doesn't support NTFS. It is essentially stock 98SE boot disk + CTMOUSE, AHCICDA.SYS, HimemX2, JEMM386.EXE, UIDE.SYS, modified autoexec.bat/config.sys/setramd.bat. https://limewire.com/d/Dq2t6#JQjSz1GzN9 SHORT VERSION for creating bootable el torito cd iso using extracted modified files injected into ultraiso + stock 98SE boot disk .ima file: CLEAN SHORT METHOD (what you want) You already have: - Stock Win98SE boot .IMG (good boot sector) - Modified boot files (CONFIG.SYS / AUTOEXEC.BAT / drivers) - ISO content (WIN98 folder / CAB files etc.) STEP 1: Open the .IMG in WinImage and make sure your modified CONFIG.SYS and AUTOEXEC.BAT are inside it. Save the .IMG. STEP 2: Open UltraISO. STEP 3: File -> New -> Data CD/DVD Image STEP 4: Drag and drop the Windows 98 CD files into the ISO project: - WIN98 folder - CAB files - SETUP.EXE (if present) STEP 5: Bootable -> Load Boot File Select your modified Win98SE boot .IMG STEP 6: File -> Save As Choose: Standard ISO (*.iso)

I burned the 98SE boot disk iso onto a cd and booted it via internal optical drive ( sata in ide mode ) on the Hp probook 6460b. I have used this method on other computers without problem, of course, almost all of them were much older ( usually no newer than ich6 ) and usually the connection was pure ide, not sata in ide mode.

No, i used various combinations in your "a20alwon" package, all of them produced the same messages i mentioned earlier. these were all with usb legacy checked in bios, and fast boot = off. i also re-tested your "2_1_PREFERRED" method with usb legacy unchecked, but no change. To isolate this better, can you perhaps upload an already made modified ms dos 7.1 boot disk iso for me to test so i can check whether i'm doing something wrong or not? I attached my original 98SE boot disk below ( expires in 1 week ). https://limewire.com/d/ow9JG#U7khgdkRPI

i thought i gave enough information. i dont know what else to do that would be feasible for me, but let me post some more info. as i was discussing back to chatgpt. they specifically mentioned to remove "umb" from the config.sys for the 98SE boot disk iso burned to cd, booted it on hp probook 6460b - selected - start computer with cd rom support, then: error - unable to control a20 line! xms driver not installed. loads a couple cd dos drivers, then ram drive - extended memory manager not present. warning - the high memory area (hma) is not available. additional low memory (below 640 KB) will be used instead. windows 98 startup disk could not create a temporary driver for the diagnostic tools. this may be because this computer has less than the minimum required extended memory. path not found - :\command.com, :\extract.exe, :\readme.txt, bad command or file name, the diagnostic tools were successfully loaded to drive . file not found. ------------------------------------------------------------------------------------------------------------------------------------------- i tried various combinations below in config.sys DEVICE=HIMEMX2.EXE /MAX=256M /METHOD:ALWAYSON /VERBOSE - didn't work with "umb" omitted from config.sys or device=HIMEMX2.EXE /MAX=256M /METHOD:PORT92 /VERBOSE - didn't work with "umb" omitted from config.sys or device=HIMEMX2.EXE /MAX=256M /METHOD:BIOS /VERBOSE - didn't work with "umb" omitted from config.sys an example file of config.sys i used: [menu] menuitem=CD, Start computer with CD-ROM support. menuitem=NOCD, Start computer without CD-ROM support. menuitem=HELP, View the Help file. menudefault=CD,30 menucolor=7,0 [CD] device=HIMEMX2.EXE /MAX=256M /METHOD:BIOS /VERBOSE device=oakcdrom.sys /D:mscd001 device=btdosm.sys device=flashpt.sys device=btcdrom.sys /D:mscd001 device=aspi2dos.sys device=aspi8dos.sys device=aspi4dos.sys device=aspi8u2.sys device=aspicd.sys /D:mscd001 [NOCD] device=HIMEMX2.EXE /MAX=256M /METHOD:BIOS /VERBOSE [HELP] device=HIMEMX2.EXE /MAX=256M /METHOD:BIOS /VERBOSE [COMMON] files=40 buffers=40 dos=high stacks=9,256 device=ramdrive.sys /E 2048 lastdrive=z ------------------------------------------------------------------------------------------------------------ i also used xmgr.sys with the following in config.sys: [menu] menuitem=CD, Start computer with CD-ROM support. menuitem=NOCD, Start computer without CD-ROM support. menuitem=HELP, View the Help file. menudefault=CD,30 menucolor=7,0 [CD] device=XMGR.SYS /R device=oakcdrom.sys /D:mscd001 device=btdosm.sys device=flashpt.sys device=btcdrom.sys /D:mscd001 device=aspi2dos.sys device=aspi8dos.sys device=aspi4dos.sys device=aspi8u2.sys device=aspicd.sys /D:mscd001 [NOCD] device=XMGR.SYS /R [HELP] device=XMGR.SYS /R [COMMON] files=40 buffers=40 dos=high stacks=9,256 device=ramdrive.sys /E 2048 lastdrive=z ------------------------------------------------------------------------------------------------------------------------

ok but also XMS driver could not be loaded / command.com, etc. is that normal too? btw, this isn't same topic but i was wondering if you know whether "patcher9x" package includes all fixes from rloew's patchmem, or does one need to install patchmem before patcher9x in certain situations. patcher9x notes does reference certain portions of adding patchmem, but im not sure if that means everything from it - https://github.com/JHRobotics/patcher9x

Maybe i don't know how to use this package, but i've tried various different methods / options by integrating it with a ms dos 7.1 boot disk ( used poweriso to make replace any files, and click save ), but i always get the unable to control A20 line. I even tested alternative sources like himemx.exe, himemx2.exe, and xmgr.sys ( also renamed as himem.sys ), but all produced the same problems. I am testing on hp probook 6460b laptop. bios is set to IDE mode. also tested with or without usb legacy enabled, currently enabled, no difference. The only other setting that i think could have any effect is the "fast boot" option in bios, currently it is unchecked. the boot disk is of iso form, booting from optical drive ( cd-rw disc ). Installed memory is 4 GB.

Thanks, this helps tremendously, I see that your updated inf from "WIN98SE_ATAPCIBM.ZIP" matches what the original sata.inf from TBPLUS package provides, but also adds some extra device descriptions, so i am using that version renamed to SATA.INF in the TBPLUS package. Since you say the updated ESDI_506.PDR is a prepatched standalone / enhanced version of PATCHSATA, does that mean PATCHSATA is no longer required, since your updated esdi_506.pdr already does what patchsata does but better? Also is the situation similar to windows 95? Lastly, if keeping PATCHSATA, can i also use the older sata.inf with the updated SATA.INF ( renamed one ).