calculating problem with may 2019 BII

[chelim78]

Dear Mr. Regensburg
I downloaded Basilisk II 1.0, SDL2 port (may 4th 2019) in replacement of BII 2014 which works perfectly. Unfortunately when using Foxpro with this new BII, Foxpro says that 1 + 1 = 0 and so on, and I'm afraid I cant use 32 bit 2014 BII anymore with the next mac OS, as Apple says. Could you help me once more ?

[Ronald P. Regensburg]

You can still run BasiliskIIGUI.
In Memory/Misc. tab set CPU Type to 68030 (without FPU) and save the change.

Does that solve the issue?

[chelim78]

Yes ! Wonderful ! Thanks a lot !

[kanjitalk755]

I have tried to fix the FPU issue of BasiliskII.
I think you can now specify 68040.
Can anyone try the latest source?

https://github.com/kanjitalk755/macemu

[chelim78]

Do you mean I should try 68040 with FPU ? 68040 without FPU does not calculate.

[adespoton]

Odd; 68040 has an FPU built-in, so there should be no situation where someone has an 040 without FPU. This means either we've got a setting for a fictional configuration, or 68040 with no fpu still attempts FPU, making it a misleading configuration.

[Ronald P. Regensburg]

In the GUI there is no separate CPU setting "68040 with FPU" there is only "68040" and that is always with FPU. Choosing "68040" will write to the prefs file

Code: Select all

cpu 4
fpu true

Do you mean I should try 68040 with FPU ? 68040 without FPU does not calculate.

The current BasiliskII builds have a FPU bug. kanjitalk755 may have solved that issue. You will have to wait till someone builds a new BasiliskII from the latest kanjitalk755 source. I will probably do that later this week. Then you can try if setting CPU to 68040 with that build will work with correct calculations in FoxPro.

[Jorpho]

I didn't know this was a thing. Would the SoftFPU extension be an option? (Googling around, I can't seem to find if it's available for download anywhere.)

[adespoton]

I've tried SoftFPU with BII, to mixed results. PowerFPU works on SheepShaver, but does absolutely nothing.

So, using 68030 and SoftFPU *might* work; it's worth a try. It'll be slower, but probably not noticeably so.

[chelim78]

Two more bugs using Foxpro under may 2019 BII with 68030 without FPU :
- sometimes, when pasting (command-C) a txt file, BII quits suddenly (no error message)
- sometimes when I press the key "a" it prints "A" and so on. I discovered that his can be fixed by pressing a few times on shift key… it's very odd.
I have never encountered such problems within the last 20 years

[Ronald P. Regensburg]

- sometimes, when pasting (command-C) a txt file, BII quits suddenly (no error message)

Make sure that in the GUI app in Memory/Misc tab "Ignore Illegal Memory Accesses" is checked.

- sometimes when I press the key "a" it prints "A" and so on. I discovered that his can be fixed by pressing a few times on shift key… it's very odd.

There is a known issue with CapsLock in the newer builds of BasiliskII and SheepShaver. If BasiliskII (or SheepShaver) is launched while CapsLock is active, typed text will not correctly reflect the CapsLock status. One more press on the CapsLock key will correct the issue. Could that be the issue that you encountered?

[chelim78]

- sometimes, when pasting (command-C) a txt file, BII quits suddenly (no error message)

Make sure that in the GUI app in Memory/Misc tab "Ignore Illegal Memory Accesses" is checked.

(Sorry, it was a Cmd-C copy bug, so there was no paste at all with that bug !)
No, "Ignore Illegal Memory Accesses" was not checked. I've just checked it and now I wait and see...

- If BasiliskII (or SheepShaver) is launched while CapsLock is active, typed text will not correctly reflect the CapsLock status. One more press on the CapsLock key will correct the issue. Could that be the issue that you encountered?

I never launch BII with CapsLock on. Anyway, one more press on CapsLock key does fix the issue.

[Ronald P. Regensburg]

You can help us by testing if kanjitalk755 did indeed solve the FPU bug in BasiliskII.

Get this BasiliskII build created from the current kanjitalk755/macemu source:
https://www.emaculation.com/basilisk/Ba ... 191016.zip
and check if calculations in FoxPro are now correct also with setting CPU 68040.

[Adam P]

Odd; 68040 has an FPU built-in, so there should be no situation where someone has an 040 without FPU. This means either we've got a setting for a fictional configuration, or 68040 with no fpu still attempts FPU, making it a misleading configuration.

There were Macs shipped with a 68LC040. My Performa 636 had that CPU, along with its F-line instruction bug that interfered with FPU emulation.

A proper Mac emulator with 68LC040 support would handle type-4 exception vectors.... which would require a bit of emulation code. Likewise, 68030 emulation needs to generate a proper illegal instruction vectors for SoftwareFPU to work (along with everything else SoftFPU needs).

[chelim78]

Get this BasiliskII build created from the current kanjitalk755/macemu source:
https://www.emaculation.com/basilisk/Ba ... 191016.zip
and check if calculations in FoxPro are now correct also with setting CPU 68040.

with 68040 without FPU calculating is now perfect
I tried copying-pasting a whole txt file succesfully
but typing lowers and uppers remains confusing

[Ronald P. Regensburg]

with 68040 without FPU calculating is now perfect

As explained above, this setting is in fact 68040 with FPU . The GUI names the selection simply '68040', because 68040 is considered to be always with FPU.

So, the FPU bug in BasiliskII is indeed solved. I will post this build later in the BasiliskII downloads topic.

but typing lowers and uppers remains confusing

Apart from the issue that occurs when BasiliskII is launched with CapsLock active, I do not see this problem. Does this happen only in FoxPro or also in other applications, like SimpleText?

[chelim78]

NO SHIFT TYPES LIKE THIS
holding shift types like this
SHIFT LOCK TYPES LIKE THIS

pressing once more on shift or shift lock does not change anything
so I have to type lowers with just one hand

[chelim78]

I have no keyboard poblem apart from BII
keyboard viewer always shows correctly

[Ronald P. Regensburg]

You are right, something is wrong. As long as you do not touch the CapsLock key, everything should work as expected. After using the CapsLock key, CapsLock cannot be released in BasiliskII. The issue is also present in a recent earlier build, shortly before the FPU issue was solved. The problem is not present in my May 2019 SDL2 build. I will ask kanjitalk755 to have a look.

Edit: The issue is also present in SheepShaver in the 11 October build by emendelson, but not in the 6 October build by emendelson. The most recent builds are built with SDL2 2.0.10, the older builds are built with SDL2 2.0.9.

(Just a thought: There was an issue with CapsLock that was solved by a workaround in the BasiliskII / SheepShaver source. Maybe the issue is solved in SDL2 2.0.10 with the result that now the workaround causes the problem.)

[chelim78]

As lauching anew macos didnot change anything I went back to 32 bit BII with 68040 CPU. No calculating problem, no keyboard problem, everything is all right for the moment, untill macos accepts this 32 bit app...

[Ronald P. Regensburg]

I made a new build of current kanjitalk755/macemu source, again with SDL2 2.0.9. It does not have the CapsLock issues with SDL2 2.0.10 and it still solves the previous FPU issue:

https://www.emaculation.com/basilisk/Ba ... 191018.zip

[chelim78]

Thank you, I'll test it in a while.

[chelim78]

This last build seems to be perfect !

[kanjitalk755]

I have fixed the capslock issue in case using SDL2.0.10.
Older SDL frameworks can no longer be used.

[chelim78]

Doing cmd-C remains a russian roulette. Sometimes it works, sometimes BII crashes.

Is there something wrong in BIIGUI ?
- memory/misc :
macos rame size : 256
mac model : quadra 900 (mcos 8.x)
CPU : 68040
Rom file : performa
Don't use CPU when idle : enabled
ignore illegal memory accesses : enabled
- JIT compiler : not enabled
no translation cache

I have saved last two apple crash reports.