jumper

Don't use a launcher. Don't use custom installers.

Try again focussing on MC and Java. Explain "custom installer". You're making this this problem too complex by adding Mesa and multiple MC launchers. Use just the basic versions of MC (ver ?) and Java (ver ?). Confirm that each is working by itself before combining them.

Which part of your install process. Lwjgl32.dll might not exist. What happened when you deleted lwjgl64.dll? Please summarize your complete install process as you actually did it.

Using for what which part?

I haven't watched the video, but it looks like you installed on a 64-bit machine and are trying to transplant it onto Win9x. Install onto 32-bit machine. If you can't start over, delete lwjgl64.dll. If you get a file missing error, copy lwjgl32.dll to lwjgl64.dll.

AI (or a child).

Maybe. Error details?

Good use of Ktree.11 and the log file. But remember: Kexstubs is a tool, not a solution. Without seeing the full definitions file, I suspect you're pushing Kexstubs too hard, resulting in a buffer overrun. Likely cause: unsorted definitions greatly reducing how many can be correctly handled. Thanks for the report and clear documentation. I will look into this further.

I've been using RamDisk98 for decades. Versions up through about 3 included source code, but I've never been able to locate any of those. If @jaclaz could find one, that would be the source to use and I'd be in for modifying it. We could reduce the memory footprint to only hold the tables, not the data clusters, then read/write the data from/to the image on disk on-demand.

fc /b original patched1 > patch1 fc /b original patched2 > patch2 Then view patch1 and patch2 side-by-side and check for overlapping addresses.

Use FC/B to compare the original with each of the patched files. If there is no overlap in the patches, I have a little utility that can combine the three files.

Just an app restart should be needed. That will reload all Kexstubs modules and reread their config files. If you are using my VBS scripts to change the logging state, they need to be updated to support new module names. Sort of related: I might be able to modify the Kex module loader to support custom load addresses. Then Kstub05.dll could just request an alternate load address in its config file instead of needing to be rebased. Also, work is still on-going at a slow pace. Most of the requests since the last release are now implemented. I just need to back out some new features that are not yet ready, but holding up the release of the new bases/n files.

Much too high? It's not an I/O port.

Try rloew's usb mass storage driver, USB.

What is "it"? Please translate the error text into (readable) English.

Are you saying that disabling legacy USB support in the BIOS fixed the problem for Fdisk and HxD?

What locale/language of Win95? Please name one URL. Installing fonts locally can be hard, but has always worked.

Win98 installations support multiple hardware configurations. Is there a way to select pre-launch which will be used?

What OS are each of you running it on? What is the problem URL? The traditional solutions are: disabling custom/web fonts; installing required fonts locally.

I recommend getting something simple to work first, even if the thumb drive is in compatibility mode. Then add Smartdrv. Fat16+DriveSpace and ram disks are other options. I've been thinking for over a decade about running 98se from a thumb drive and have lots of ideas.

You are using a tool other than fdisk to create the two partitions. Have you tried deleting the current partitions, using fdisk to recreate the first, then the other tool to recreate the second?

Again,

Mentioned, but never explained. So what is it?

What is:

Actually working more than ever. It tells you exactly what it could fix if you had ApiLog running in the background instead of just letting the load fail silently. Looking at the log files now.