exxos's Atari, Amiga & retro forum

This is how TOS 1.62 behaves:

Cyprian wrote: 09 May 2025 10:38 This is how TOS 1.62 behaves:

Damn.. talk about the mandela effect ! :roll:

EDIT:

Well at least it seems to do as I remember in TOS404!


I think MiNT "grey's out" the disabled windows ?

exxos wrote: 09 May 2025 10:44 Damn.. talk about the mandela effect ! :roll:

:lol:

exxos wrote: 09 May 2025 10:44 I think MiNT "grey's out" the disabled windows ?

I think it depends on the AES version: TOS AES, XaAES, MyAES, N.AES, Geneva AES, MagiC AES.

I think it depends on your flavour of EmuTOS. The 512k version with 3D effects and other AES3 features behaves as you're remembering.

BW

Just uploaded two new firmware revisions. These seem to fix the issue with the Winbond SDRAM.. It was on test all night again and wasn't any problems.

The firmware should also be tested with the alliance memory on previous builds to make sure nothing broke.. But I don't believe it should.. Technically the alliance memory would suffer from the same issues but never actually seem to...

AUTOBOOT (ACSI pin 10 wire emulated) is untested - It should allow drives like ultrasatan etc to boot without the ACSI pin 10 wire needing to be connected (that code has been working before)

EDIT:

Oddly the updated Winbond code isn't happy in TOS.. comes up XXXXXXXXXXX on TTram test. and yet it ran all night with EMUTOS.. :pullhair:

EDIT2:

Ok I think I know what I have done :roll:

Will upload new firmware later.

New firmware in the "usual place". Its had a tiny fix over "current3" to improve SDRAM access (which seemed that's what also broke WB RAM). So it *should* be fine with Alliance and winbond RAM now (needs testing)

ACSI autoboot is now put back in . Just tested ultrasatan and booted up (TOS206)

exxos wrote: 08 May 2025 12:55

coonsgm wrote: 08 May 2025 12:49 I can't wait to update mine! (Hopefully tonight I have time)

Slow and steady wins the race ;)


I need to change the PLD on the next revision board now.. Then do all the testing all over again :roll:

Replaced and soldered....now, where to find the latest working firmware?

exxos wrote: 08 May 2025 19:23 ..and as I spent 10 minutes trying to get rid of the "short" between 2 pins.. Feking flood fill !! Thats getting removed there next revision as well!!


Capture.PNG

What's the problem with those two grounds being connected?

Steve wrote: 09 May 2025 22:01 What's the problem with those two grounds being connected?

None other than it looks like a short!

I generated myself a bit of a discombobulation :stars:

STOS will boot up fine in EMUTOS from IDE.

It tries to load in TOS206 from IDE, but the STOS splash screen is corrupted and it seems to lock up.

If I load STOS from floppy, in TOS206, it works fine.

(ive recopied STOS from my floppy to D: but doesn't seem to help, it sometimes gets to the editor but locks up anyway)

I have Ultrasatan as my boot drive, but its loading HS11 from it, then it "losing" the drives and getting the drives from the IDE instead.

The copy I did from A: to D: seems to get to the editor, but the splash is a bit corrupted.

The copy I did from my PC to C: the splash is totally corrupted, but now getting to the editor and locking up..

So unplug the IDE:
Got ultrasatan only. Booted HD11 from US. Copied STOS from floppy to C: booted STOS and works fine also!

So it looks like for some unknown reason, STOS won't boot from properly from the IDE in TOS206, but will on EMUTOS. So...... ?????
:pullhair: :pullhair: :dizzy:


Oddly my ROM copy program now works with the IDE unplugged. So its like TOS206 + IDE = RAM corruption or some sort... :shrug:


EDIT:

Swapped multiple times.

IDE + EMUTOS + STOS works fine.

IDE + 206 + STOS does NOT work properly.

FLOPPY + 206 + STOS works fine.

What's the difference other than HD11 driver in TOS206 ?!