atarixle

Never ment to be harassing. I love to see the GUI having progress. What I mainly ment was that the limitations in hardware have to be implemented in software (use relocatable code only, instead of an MMU in hardware; ...). Those occupy memory, and main memory is limited. Multitasking might run well but how much memory is left for applications? You could put it into The Cart or comparable memory-monstrouse products, or reload as much as possible from RAM-Disk or storage on the parallel-port. But still all the active code has to fit into less than 64k main memory. The framework for the Window-Management and GUI widgets is eating up memory too ... ok this is what you save when the app itself does not need to have this implemented separately. And the last thing is time. You are one of the most genious programmer who writes the official firmware for other products. You said that time is missing. Contrary I also said that once the GUI framework is ready, writing apps itself should be doable relatively quickly.

The thing is, it is a final and well received product with even some commercial success. This is why I mentioned it at all (again). FJCs GUI is indeed impressive, but I highly guess that it wont come any further just because of the limitations the Atari has. The goal of having Multi-Tasking on the 6502 is set too high. It is indeed impressive to see, that coders can do it, but without the help of some hardware, like the 68000 and the x86 has, it is doomed to stuck in demo mode.

GEOS itself has been ported ...

Once the GUI framework is written, the rest should be done quickly. Programs that really could use a mouse-GUI were a file-manager (just to be able to unload the GUI and run everything already existing), a font-editor (pixels faster than joystick, but not as precise as with keyboard), graphics-8-paint (because Graphics 15 has enough paint-programs), simple texteditor (for editing some config files from within the GUI, something BOSS-X still lags of because I didn't make it to write anything like a simple text-editor in Turbo-BASIC). For serious work we could use a GUI-version of The Last Word, plus running a music-player in the background.

Wait, the tiny one is one of my BOSS-X - Fonts. It's name is "MACSMALL.FNT'. Oops. I was inspired to re-create this pixel-by-pixel. The Chicago-Font, I first saw on Atari-Related screenshots (perhaps MagicMac-screenshots), so I named my 8x8 sized recreation "ATARIST.FNT".

16 files at once, needs 4 pages when having 64 files max, quite ok scrollspeed even in Turbo-BASIC.

I sent back the new mobile because of many other reasons (it didn't find all phone numbers in search, broke up mobile connections, asked me for the unlock code several times ...). It was crappy but it was fast as heck compared to my now 5 years old reliable mobile phone.

Ok, now I got 3 Emulators on my Android: Droid800 and Colleen got the same problem: as soon as pick a folder too close to the root (e.g. /storage/emulated) I get stuck and cannot pick another folder. I have to delete all files from this installation to run a freshly installed, untouched instance of the emulator. Atari800-SDL does not escape from its own files-folder (only files/, files/data/ and files/savestates/ is visitable but empty). All emulators worked fine on my older mobile phones, but the newest one I got me recently, running Android 13 btw, does bring these errors. Guess I will have to try Atari800 in RetroArch, or Kodi if needed. But that's a little too bloated IMO.

A big Thank for the new version!

Intel produced 32 bit CPUs until the late '00 years, may be even longer. The R60e I got is a 2006 or 2007 Intel Core Duo E. I am interested in Retrogaming on its low-res 4:3 screen (1024x768). I bought my 32 bit Acer Aspire One 10" as brandnew in 2010.

Wow I never had thought of this but I tried out enabling the Jaguar BIOS. This makes the sound appear. Strangely it worked in Windows without activating this checkbox. Thanks for all your help, may be this helps you too. This issue is solved for me. (may be I can add a solved tag to the toppic)

At least the MATE mixer says that virtualjaguar has sound and it is up to the max. Still can't hear anything but a crack noise when starting.

The binary is 64 bit only. I will test drive it on my PC, but it is off the boundaries of my 4:3 screen-sized Thinkpad capabilities.

This will be the next thing I check out. For now, on debian 11 64, virtualjaguar has no sound too, so I wont test debian 12 64 and debian 11 32 now. Now I need to run to the dentist. Later!

I am so stupid and forgetful ... why don't I try this myself, when I got a bunch of computers here running debian 11 32 / 64 and debian 12 64 bit ... but watching my computers do the update to the latest point-release I guess I wont check this out before finnishing this post.