As said before.
All my codes are tested on Mac , also on Big Sur and all run.
I do not have a m1 but many will buy one.
And to use graphics commands on Mac carefully is nonsense.
It will probably be due to rosetta2.
I already linked the thread yesterday under "Mac".
This can be quite a problem.
These things can persist under VM for a very long time and usually have something to do with graphics.
Line
Re: Line
Thanks for that info, Shardik. It narrows the issue down to either M1 or Rosetta.Shardik wrote:...did the same test described above for Mojave on my Intel iMac 5K 2019 with MacOS 11.1 'Big Sur' and PB 5.73 x64 and it works like a charm.
Texas Instruments TI-99/4A Home Computer: the first home computer with a 16bit processor, crammed into an 8bit architecture. Great hardware - Poor design - Wonderful BASIC engine. And it could talk too! Please visit my YouTube Channel 
Re: Line
With Big Sur and on older Mac OS versions it works, that's nothing new.Saki wrote: There remains only the possibility that perhaps a VM is used which triggers the bug.
On m1 the Intel is emulated by rosetta2.
There is then not much left in itself
地球上の平和
-
spacebuddy
- Enthusiast

- Posts: 364
- Joined: Thu Jul 02, 2009 5:42 am
Re: Line
I had an update this morning for the Mac OS, now the code is working properly.
Still lots of bugs in M1 machines.
Hopefully Fred will make arm version work for Mac OS/X
Thanks All.
Still lots of bugs in M1 machines.
Hopefully Fred will make arm version work for Mac OS/X
Thanks All.
