MERCURY127

yes, but u must see at least [000D76BB] Loading Vxd = vkd [000D76BB] LoadSuccess = vkd [000D76BB] SYSCRITINIT = VMM [000D76BB] SYSCRITINITSUCCESS = VMM in bootlog, as indication start prot mode... after Loading Vxd / LoadSuccess (hich is real mode part) will appear SYSCRITINIT / SYSCRITINITSUCCESS and DEVICEINIT / DEVICEINITSUCCESS for each vxd, and after [000D76BC] DEVICEINIT = CONFIGMG begin processing of device tree.

i know. but it is better do not pack anyway - more flexible and easy troubleshooting,

And... What about step-by-step loading? F8 - s-b-s, enter win, and try. Also, what if try real debugger, for example SoftIce? ;D

Just remove or rename vpp or vpd.vxd from vmm32 folder and check if success. It will work, only if ur vmm32.vxd really empty and Not contain these vpp/vpd.

vmouse and vmd is mouse related. check ur mouse. vflatd is linear framebuffer related, are u sure, thar ur vc have this feature? anyway, this files can be deleted for test purposes. my suggestions: 0) vmm32 is container: dos part - realmode starter (real vmm32.vxd), fyrst protected mode part - vmm vxd, main windows module (preboundled with vmm32.vxd, but its possible cut off in real vmm.vxd file), all other vxds, added in container on install procedure. if u see that must ur vxds succefully loaded - so obviuosly, that VMM work good. then u can replece ur system vmm32.vxd to extracted vmm..vxd from ur distr, and place all other vxds from ur distr to system\vmm32 folder. after this, u can start windows with win /d:m command and look, which part make problems.... but before it i suggest u check all ur hadrware, especially memory.

i think, u need Ram Limitation Patch. try trial form rloew sites.

Disable all devices, which can disable in bios. Then try clean install.

9x allow use only one cpu for all - system and programs. When i try soft play some 100 mbits/sec 4k file, i see 70% busy all 8 cpu my 4ghz 3770 - 4 physical + ht. So i think, one core even newest 9900 at 5 ghz not allow u play 4k. also 9x not allow ur player use avx/avx2, but all sse/2/3/4 - can.

i have exactly this problem on my pcie Radeon X600 (some powercolor oem) on VGA connection. my monitor is benq bl2411, 1920x1200. monitor wrongly detected as 1920x1440. when i try set res 1920x1200 - i get vertical panning... but if i use DVI - then 1920x1200 work good. but mon anyway detected as 1920x1440. 98SE, Catalyst 6.2 or 5.9 - no diffs.

try use himem with /machine:at key, or xmgr instead himem (with adding string for xmgr into ios.ini). by default original himem often use very slow internal procedures w/o /machine:at key

last result (after using /m switch, or limiting of memory other methods): - vfat bsod now gone; - driver now is loaded successfully, w/o any errors; - Odyssey see wifi card, provided by driver; - but after scanning, list of networks remain empty. :( i think, it is all. THE END. but u can try this method (patching sys for vid/pid) with other (not so new) ralink pci cards.

i not sure that it work now. my system now wont boot, i have bsod with VFAT error, instaed normal boot wiith code 10 yesterday. so, if anyone interesting, here is my patched RT28609X.SYS: 9A904 -> 01 06 00 00 - first devid (now 60 53) - dword, 9A908 -> 81 06 00 00 - sec devid - dword, 9A90C -> 14 18 00 00 - realtek vid - dword. so u can write here own device for testing ur wifi cards. 2860.zip

No, this is not end. It's devids white list in driver. I replace one value 01h 06h to 60 53 and now... have vfat error... So i understand, me need new rlp with /m option?

Code 10 :( My card is PCI\VEN_1814&DEV_5360

OK, thanks, i check all tomorrow...

It's can work? Someone try so?

https://www.sumatrapdfreader.org/free-pdf-reader.html work on 9x with kex and gdiplus.dll.

No, sure, its not appear on regular SE. i think, it that SE havent so many infs as IF (110 in current 2018-test3) in distr folder:..

MSBATCH.INF DevicePath=1 cause MSGSRV32 error at 16 minute installation (when begin search pnp devices). Not 98SE, but 98IF (based on SE) detlog content: end of setuplog:

solved. D:\IF1808>fc /b SUWIN.0 SUWIN.EXE Сравнение файлов SUWIN.0 и SUWIN.EXE 0001F46E: 75 EB 0001F4CA: 74 EB WARNING: possible obvious side effects...

I not think that installer use fdisk for write mbr...

yes, i think about this... many times. but these three files is 16 bit NE files (win3x binaries). it is very hard to patch... many code segments. many data segments. far calls. also in win3x world is usual thing - do DOS calls for disk operations. its real hacker's nighmare...

no problems... MBR.zip

once - easily. three times - a little annoying. seventeen times - would kill...

it is PROBLEM, if u need 98 only for sporadic experiments... for sample, after her MBR intrusion was not load Win7, even if 7 installed on other physical disk.