SweetLow

Or limit XMS memory to 512M or use RLoew's PATCHMEM. And "MaxPhysPage setting in system.ini" is bad idea. P.S. It is pinned topic...

You should not remove but RELOCATE this item from old to new addresses: BF800000 - BFFFFFFF

It is not enough good tool in THIS area: Base Addresses: (0) D0000008 = mem base=D0000000 len=128M prefetchable (1) 0000C001 = I/O base=0000C000 len=256 (2) E5000000 = mem base=E5000000 len=64K CardBus: 00000000 ExpansionROM: 00000000 (128K,disabled)

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.

JFYI: schwups, OS:ME

Check and try to find something not included in my collection Probably no. But you can ask him here or on old-games or on ru-board, of course. Unofficial stuff has one unsolvable problem - it depends too hard on taste of maker of the pack (and third party software he/she is trying to run on his/her hardware). As good example touched above - the valuable third party updates for real modern hardware are not needed at all after you narrowed your request to using inside VM.

AFAIK on VMs the only thing you really need on modern hardware is TLB ivalidation patch for 98/ME plus speed patch for 95/98. All in one place - https://github.com/JHRobotics/patcher9x Literally nothing to talk.

For pure Windows 98SE Rus & Eng I maintain collection of raw QFE and some other updates with descriptions. And look at the BolenB sets for integration into distribution media. But it primarily depends on your hardware, of course.

I run 98 SE on Acer Aspire V3-571G and HP 250 G7 (84A6). Without some functionality, of course, but OTOH without errors.

Thank to @defuser testing: http://sweetlow.orgfree.com/download/a20alwon.zip 1. Fixed bug of simultaneous using /TESTMEM:ON and /A20CONTROL:OFF. Memory testing procedure relied on the state after /A20CONTROL:ON execution. 2. The code for the /A20CONTROL:OFF patch is made more generic and yet at the same time simplified. 3. Added 3+2+1 variant of patch. 4. The difference of variants -1 and 3 from /A20CONTROL:OFF on the hardware with the A20 Line Always On mentioned.

Intel Core2 Duo. The modern system built ... 15 years ago.

There are MANY protection errors possible in Windows 9x on modern hardware. It is far better to give exact message. SATA on modern laptop? Are you joking?

No, it is working as expected - XMS state is exactly equal to the state of real hardware. Always On to be precise. Ok, hardware is functioning as described above.

2_1 - as readme states. And it's the best till it's working, of course. Which of variants? You have to test 2 variants: 1. Original HIMEM.SYS (NOT in package). 2. 1_PS_2 Without any options except /v. And better with DOS=LOW in CONFIG.SYS (or without DOS too).

--> Real A20 Line: Enabled always and --> PS/2 A20 Line: Disabled --> PS/2 A20 Line: Enabled i.e. switchable. It is usual behaviour of middle time hardware (Intel chipsets from 5* to 9* for example) But the source of >Windows protection error. You need to restart your computer. on patched PS/2 handler is unknown.

It's pretty easy to reproduce such condition: SYSTEM.INI:[BOOT] drivers=mmsystem.dll power.drv if delete mmsystem.dll from drivers list you will get exactly this. So try to check this option and validity of mmsystem.dll P.S. And the second parameter: SYSTEM.INI:[DRIVERS] wave=mmsystem.dll

Definitely some problem exists with PS/2 handler. What is the result on unpatched (original) HIMEM.SYS? And to check more precisely it is better to run himem in verbose mode: device=himem.sys /v http://sweetlow.orgfree.com/download/a20speed.zip The modern version of this kind of software.

1. Instead of trying to setup RLoew SATA patch you probably need to setup something like "Legacy" or "Compatible" for chipset ATA Controller in BIOS. 2. Why is this thread in THIS subforum?

Or just use boot menu "Command Prompt Only" item what I suggested few posts above. But no luck.

Why did you use plural noun? I'm alone. Yes, I slightly confused too. Now even AI bots can follow the thread of a conversation better...

1. You didn't answer my previous question is BIOS handling your USB drive. It's crucial for direction of debugging. 2. https://github.com/LordOfMice/Tools/blob/master/rmmremove.zip http://sweetlow.orgfree.com/download/usb20_win9x.zip

Ok, MS-RAMDRIVE is bad case. But there are two other names treated as RAM Drives - RDV and VDISK. And as they are shorter than 11 characters - any name RDV* or VDISK* are treated as RAM Drives too... Yes in general, but IDK such software for XP.

Two fixes, I suppose now. Every one should help, but using both even better.

Do not delete anything. Set the name you wish from begin of "MS-RAMDRIVE" and add spaces to get string with 11 characters (exactly the "MS-RAMDRIVE" and DOS file record name length). I.e. replace "MS-RAMDRIVE" to "RAMDRIVE ".

No. Try to search yourself and don't forget that VMM32.VXD is actually packed collection of system VXDs