feipoa wrote on 2025-04-17, 08:03:

I've not run into this problem. I suggest sharing a screenshot.

You also may want to try the Evergreen utility to set the registers and the IBM 5x86 utility. There's also a Free5x86 utility packaged in the original post.

Really strange, I'm stuck.

Try a different CPU, try a different motherboard model, and try the Evergreen utility.

feipoa wrote on 2025-04-17, 09:27:

Try a different CPU, try a different motherboard model, and try the Evergreen utility.

Tried 2 different cpus, 2 different mobos. That I've run it before. Maybe the file is the problem.

OK, I think there was a currupted file issue on my disk. Changed the file and solved. How can I make it work from autoexec.bat? It doesn't work.

Hello again,

I finally got the ti486sxlc2 running on my scamp board. All fine. I’m using all the suggested parameters from page 1. Till today:

What changed:
- replaced gd5428 with gd5434

Result:
- win95 not booting. Error message while still in text mode „general protection fault“ something like that as I have to translate it. System then shuts down „you can now turn off your pc“

What I tried:
- disabling the cache by -e- (while all other options remain) resolved the issue and windows boots. Problem is that I cannot reactivate it while under windows. The cyrix command line tool won’t work while in windows

What’s further strange:
- when I loaded win95 then start msdos mode, run the cyrix -e and all the others (-cd -x -A….) and then exit back to windows it‘s working! I tested it three times. That won’t go into my head as exiting dos mode shouldn’t be so much different to a normal windows restart.

Any ideas?
Regards

I could solve the problem:
You have to start windows 95 using win /d:x

Seems Windows runs into issues when checking rom addresses for available memory. Or better said: the diamond seems to use unusual address spaces I would assume

You also could not boot Windows 95 the usual route if you used? cyrix -r -m-

What does win /D:x do?
According to Google AI:

1/D:X: This switch is used to specify a DOS environment or a specific DOS program. In this case, X represents a placeholder for the specific DOS program you want to run, or the DOS environment you want to enter. 

What are you typing in place of x?

No. It did not boot using the standard parameters. As windows would exit back from dos mode fine I assumed it has to be something to do with the way windows act only! while booting and not while exiting from dos mode. Thus i tried that parameter.

That’s what it does:

X excludes the adapter area from the memory range in which Windows searches for free memory. Corresponds to the SYSTEM.INI entry: EMMExclude=A000-FFFF

Thus you see x is not a variable. It is /d:x

Ps: I am sure I could further limit the address range not-to-be-scanned further with the system.ini command. Maybe I will try that. Maybe not 😀