jumper

Subst causes Windows to use DOS compatibility mode. That was okay for my aging 98se box for many years.

Shell32.dll has corruption in the Import tables. First entry, so probably the fault of UPX or other compression.

Perhaps. Please provide a document and code sample.

I'm still having trouble getting changes applied to the pif, like W98 is buffering a la ini files. But did finally get CoE to set 10h at 63h.

It's just where it should be in the 386 section. Follow the 16-bit chain of headers to find the 386 section. Chain starts at 171h as legacy section header actually follows its data. Header struct (size 22d/16h): Char [16d/10h] - szSectionName Word Next, dataOffset, dataLength You have an extra 16h+6h in your section calculation. Maybe an extra 286 section that mine (98 and ME) don't have? (Sorry, can't post files from pc now.)

1B0h in my pif tests on 98: Fc/b y.pif z.pif Will try again on ME. Update: Close on Exit is 01h at 1B0h on 98 and ME, so !Suggest must be 04h at same on both.

Try profiling it in Dependency Walker for clues as to which module is causing it to abend.

You're running in full-screen and don't want to be interrupted by Windows, so for best performance you should be in MS-DOS mode. 1. Don't dismiss the dialog! Run the wizard to create a new shortcut. 2. Use the other tabs to set better options. 3. Install a program that will click the buttons for you. 4. Use a different VM to run the more challenging DOS programs.

Means at least 3 ( >= 3 ).

Or after 12/31/2107. All other dates get wrapped into that range. This is correct for FAT partitions.

Patching the import table is easy.

Thanks. My cd's aren't at hand, and extra folders didn't get copied to disk....

But you just called it a: And was your first response about FE or SE?

No, mine doesn't. Not even as an option. And he's asking about ME, not 98.

Not an Aspire One. Please edit title to remove the "one". 1996 is too early. The mmx is probably an upgrade. Could also be socket 5. What markings/labels are on the mainboard and largest support chips (the chipset)? And on the current ram A close-up photo would help.

I'm thinking edo simms, maybe 2x32MB. Why? If you have one, tell us what you see: Cpu socket, chipset, ram slots, etc.

Installer bugs with known workarounds are low priority.

Ddhelp.exe is the DirectDraw preloader. Don't rename it, disable its preload with Msconfig. It will then load when needed. Systray.exe is the poorly named Powrprof launcher. Deselect Show on Taskbar in Power Meter. Mdgx recommends U891711. Search msfn.org for extensive discussion. I haven't tried any of them.

I don't know driver patching.

Agreed. I have plans to support wildcards on both types of KnownDLLs, for example: API-MS-Win-Core-* = Kernel32.dll

Ddhelp and systray are also optional. The KB should not still be running after installation. The other five I have.

Core.ini version (on first line) should be 4.5.2016.24 or later. Kexstubs (k*stub*) should only be used in the experimental modes, not BASE or DCFG1. Use (or clone) BASE_NSB instead.

Also, if you network the machines together, Win7 can probably share the internet connection with older systems.

Check the 64-bit change log. That developmental build might have been 64-bit specific.

Actually, it looks like google.ru is popping up that dialog, so don't go to that site.