Atari + gotek + MAPROM floppy corruption

[exxos]

My first run of my TF536, plus my new gotek with flashfloppy (first run also) and first run of @agranlund MAPROM

I created a image in steem as below..

Capture.JPG

The H4 rockets with TOS206 when it boots MAPROM, but I tried to load YAART by @czietz it just quits back to desktop.

Though when I view the contents of the floppy on my H4, I just get the same corruption ?!

IMG_5396.JPG

I tried saving desktop but the file vanishes after I reboot.

So no idea whats going on with any of this :)

EDIT:

Files show up fine without the TF536 fitted.. So will try booting without MAPROM on the TF536 next.

EDIT2:

Floppy contents seem OK without without MAPROM loaded :shrug:

[PhilC]

not tried using Tos2.06 with Maprom but have noticed that floppy doesn't work on one of my H4s when using the TF536 but remove it and put a 68k back in and its fine not sure if its related to the 1.44mb gal etc,?

Could it be related to the 68mb ttRam incorrect identification?

[exxos]

not tried using Tos2.06 with Maprom but have noticed that floppy doesn't work on one of my H4s when using the TF536 but remove it and put a 68k back in and its fine not sure if its related to the 1.44mb gal etc,?

Floppy contents seem OK without without MAPROM loaded.. It only seems to corrupt the AUTO folder names, but YAART won't load so must be corrupted as well.

[PhilC]

@exxos ok ill test without maprom running tomorrow and will confirm.

[exxos]

@exxos ok ill test without maprom running tomorrow and will confirm.

Seems repeatable. Floppy seems fine, run MAPROM from desktop, then I get the corrupted file names again.

[PhilC]

@terriblefire this sounds similar to what was happening to me, could it be related to ram ?

[exxos]

One thing I don't get though.. if MAPROM is remapping ROM to fast-ram, and the 030 MMU is remapping to ROM space, then wouldn't this conflict with the actual TOS206 decoding board ?

[PhilC]

@exxos i had windered about all that but then gave up on it before it gave me a headache but yes you are right, all the decoder board is doing is making a 256k boot rom work. @agranlund did a minimal EmuTOS boot that let you remap a rom from a file into ram etc.

[exxos]

@exxos i had windered about all that but then gave up on it before it gave me a headache but yes you are right, all the decoder board is doing is making a 256k boot rom work. @agranlund did a minimal EmuTOS boot that let you remap a rom from a file into ram etc.

hmmm, if thats the case my TOS206 board will need a register to turn it off which would have to be done by MAPROM once its copied ROM to fast-ram :roll:

[stephen_usher]

The ROM decode will only be affecting physical addresses on the address bus and have no effect upon the logical addressing used by the CPU via the MMU. The logical addresses never leave the chip.