exxos's Atari, Amiga & retro forum

Oh, and Frontier doesn't seem to be a good test of stability. Even with all these issues on the machine it's running perfectly in fast RAM with the cache turned on.

Switching over to PAK/3 TOS 3.06 I actually see a Bus Error when things crash! i.e. when Genbench crashed in the small vdi text test with data corruption. Only later does the system lock up this time. Otherwise it behaves in the same way as TOS 2.06 (except the Color XCONTROL sets the pallet strangely, obviously thinking that the machine is a TT).

P.S.
OK, even with the cache off under PAK/3 TOS 3.06 GB6 crashes in the small text section. (Again, Frontier works flawlessly and looks a lot smooth than under 2.06.)

This is good... more of PP's disk converted games run under PAK/3 TOS than under 2.06. It seems that his loader detects the machine as a TT and follows the TT code path, with the 68030 compatibility stuff.

stephen_usher wrote: 24 Nov 2020 22:10 This is good... more of PP's disk converted games run under PAK/3 TOS than under 2.06. It seems that his loader detects the machine as a TT and follows the TT code path, with the 68030 compatibility stuff.

Good to know that that will work on the TF536

So, changing the socket on my board changed nothing. The only other thing to try is changing the socket on the motherboard.

I only ever get problems when running in Fast-RAM, but that could possibly be pushing the main RAM faster? I don't know.

I've just reprogrammed the Xilinx chip and.....

SUCCESS!!!!!!

I have a working TF536! (Or at least FASTRAM works without crashing the machine. I've yet to try other tests.)

:yay: :girldance: :cheers:

@stephen_usher that's really bizarre but not the first time I've seen that.

Very good news indeed

One step forward, one step back.

PAK/3 now gets this far and then freezes:
Last week's snapshot of EmuTOS boots but crashes after a while and now it's destroyed the C: drive on the UltraSATAN. I knew I should have backed up the SD card.

P.S. Does anyone know of a good filesystem checker/fixer?
P.P.S. It was the filesystem screwed up by EmuTOS causing PAK/3 to crash.

I managed to get CHKDSK3 to look at the partition and it's royally screwed.

I see some filename and directory name corruption I've only ever seen on a floppy when there's been a DMA issue. The first couple of characters are very wrong, as in some extra bits set. I've never seen it on an ACSI device before.

Bother CHKDSK3 broke things even more.

I did an "Analyse FAT" and it came up with a dialog saying that FAT1 and FAT2 differed and aske which to use, to I clicked on Cancel... and then it overwrote the second FAT and used the first one anyway! That's broken, as it shouldn't have touched the disk at all.