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.

As I don't have real more than 2TB NVMe drive still - QEMU NVMe 256TB drive checked and works.

No. S4OS is supported by Millenium only (and in OEM versions only AFAIK). 98 supports S4BIOS, but enabling this is not the OS task.

https://github.com/LordOfMice/Tools/blob/master/gpttsd.zip As GPTTSD is mostly generic TSD with 64-bit LBA support: User-defined partitions mount added by request from RayeR.

My friend. We are not in school and I am not teacher. It is your responsibility to understand correctly formulated statement.

Used where? You described only problem with install Windows 98 from CD. No mentions of attempt to boot from USB Drive for example. Do you understand what is boot floppy image and what its purpose in CD-ROM boot process? Your .ISO has UNTOUCHED floppy image. I assume it's time to read something, El Torito standard for example and to study some .ISO authoring/editing software.

Of course you will get error. You try to use unpatched himem.sys -> Unpatched himem.sys locates on boot floppy image of Windows 98 Install CD. Replace it there by patched version.

If you said about error in some software you had to describe exactly error in software, not behaviour of hardware. If you have error in himem.sys then take patched version (one of the two "preferred", of course) and just replace %windir%\HIMEM.SYS (or anywhere you want). >if you know whether "patcher9x" package includes all fixes from rloew's patchmem not all fixes, but all essential

It is normal for hardware with Always On A20 line, I assume it is obvious.

Hibernate support AFAIK. Yes for _PATCH_ itself. But you can use SATA.INF, of course, if you wish. I said about binaries and .INFs already above. I don't understand what did you ask. You can not use two .INFs simultaneously. You should select one of them for particular adapter.

>can any of your updated versions work on Windows 95 Osr 2.x? EHCI_506.PDR - probably: https://msfn.org/board/topic/187782-silicon-image-si680other-unsupported-pci-ide-controller-under-windows-95-osr-20/page/2/#findComment-1286966 I don't use any of windows 95 now. So check and tell us. >I was thinking i can use the updated ACHI.PDR Yes. > requiring also PATCHSATA No. This ESDI_506.PDR is prepatched standalone version (including enhanced version of PATCHSATA). You can use new .INF file too for "SATA" adapters: http://sweetlow.orgfree.com/download/WIN98SE_ATAPCIBM.ZIP but there is not strict dependency between binaries and .INFs. And "WIN98SE" in the name of file is just the source of original file, it should work on any Windows 9x. >but the specific version of ESDI_506.PDR becomes irrelevant when switching to AHCI mode and using the ACHI drivers Yes. ESDI_506.PDR and AHCI.PDR are completely independent (as the hardware they handle are independent). >Can users replace all updated files in your package into the original package of Rloew's files and use in the same way Yes. They can be used this way too. But not with RLoew's packages only. Anywhere you meet ESDI_506.PDR (of according OS, of course; Millenium ESDI_506.PDR has some additional features for example and is not recommended to be replaced) or AHCI.PDR just replace them with these patched versions.

http://sweetlow.orgfree.com/download/esdi_506.zip Fixes: 1. [TBP2.1 - BigHDD] Fixed - data underrun in the initialization procedure of PM Only drives. This resulted in slowdown on booting (sometimes significantly) and caused other problems. 2. [98SE] ATA devices are no longer considered to be in a stopped state (SpinDown) after initialization. 3. [98SE] The CMOS type of a PM Only drive on non-primary ATA channels when added after the boot stage is now consistent with that during boot. 4. [98SE] Fixed the setting of the I/O request call method in the drive initialization procedure. This did not affect functionality in the vast majority of cases, but has been improved nonetheless. Update is recommended due to point 1.

There is exact answer your question. Stan Mitchell, Inside the Windows 95 File System,1997

https://github.com/oerg866/win98-quickinstall/issues/22#issuecomment-4488077576 RLoew's Terabyte Plus 3.0 ESDI_506.PDR data corruption bug. Fix: http://sweetlow.orgfree.com/download/esdi_506_tbp3.zip

0. Use the newest versions of ESDI_506.DPR & AHCI.PDR too. 1. C:\WINDOWS\SYSTEM is not need, of course. 2. Literally few days ago when I solved problem of executing ATA commands (like setting PATA transfer mode for PATA device on SATA Host - PATA Device bridge) I made the dumper of IDENTIFY info without using smartvsd.vxd interface too, so for the first take: https://github.com/LordOfMice/Tools/blob/master/atainfo.zip unzip content and run DumpIDENTIFY.exe. You should get 3 .DAT files and no errors or warnings. 3. If success on step 2 then try to use SMARTInfo - this is the same thing as DumpIDENTIFY but with smartvsd.vxd interface using. You have to get IDENTIFY.DAT dumps too and no errors.