exxos's Atari, Amiga & retro forum

TF534 on A1000
Motherboard Rev: ? w/ daughterboard
CPU: 030 @ 40mhz
FPU: Yes
Fit with Relocator: Yes
Relocator: EzdineG (gerbers here)
AmigaOS: 3.1.4 w/ bestwb 1.1; also 3.1 / classicwb

This post is confirmation that the TF534 works correctly with the Amiga 1000. Tested thoroughly for weeks now using the relocator above. Machine would not post with Kickstart 1.3, possibly due to RAM autoconfig, but works fine >= 3.1.

Thanks for this update,
right, will not work under 1.3 for two reasons:
1. Zorro lll isn't working under KS 1.3
2. No scsi.device in rom

Have question about Amiga 1000 and TF534
If I swap kick for 3.1 TF534 I'll be working on A1000 without any mods ?

8 Bit Dreams wrote: 07 Jul 2019 01:44 Thanks for this update,
right, will not work under 1.3 for two reasons:
1. Zorro lll isn't working under KS 1.3
2. No scsi.device in rom

Yeah it should still post... just no ram or ide drive..

@EzdineG was the kick1.3 soft kicked? I think the soft kick bootstrapper has incompatibilities with 030 cpu?

terriblefire wrote: 28 Jun 2020 21:51 Yeah it should still post... just no ram or ide drive..

@EzdineG was the kick1.3 soft kicked? I think the soft kick bootstrapper has incompatibilities with 030 cpu?

No, this was using the hardware mod allowing the use of a physical ROM. 1.3 would get stuck after the first color change before the workbench hand appeared.

Without the mod, both TF530/534 would crash at the bootstrapper as you describe above.

EzdineG wrote: 28 Jun 2020 23:17

terriblefire wrote: 28 Jun 2020 21:51 Yeah it should still post... just no ram or ide drive..

@EzdineG was the kick1.3 soft kicked? I think the soft kick bootstrapper has incompatibilities with 030 cpu?

No, this was using the hardware mod allowing the use of a physical ROM. 1.3 would get stuck after the first color change before the workbench hand appeared.

Without the mod, both TF530/534 would crash at the bootstrapper as you describe above.

Is that an A1000 specific 1.3? If so i'd try an A500 one just for a laugh.

It was the A500/2000 common 1.3.

That said...

It is possible I was attempting to boot with a version that had the scsi.device hacked in, because I did have that setup booting with the TF530’s IDE.

If you need confirmation, I can try it with a 1.3 masked ROM.

EzdineG wrote: 28 Jun 2020 23:25 It was the A500/2000 common 1.3.

That said...

It is possible I was attempting to boot with a version that had the scsi.device hacked in, because I did have that setup booting with the TF530’s IDE.

If you need confirmation, I can try it with a 1.3 masked ROM.

Its just useful to know if that rom will boot with 030.

terriblefire wrote: 28 Jun 2020 23:29

EzdineG wrote: 28 Jun 2020 23:25 It was the A500/2000 common 1.3.

That said...

It is possible I was attempting to boot with a version that had the scsi.device hacked in, because I did have that setup booting with the TF530’s IDE.

If you need confirmation, I can try it with a 1.3 masked ROM.

Its just useful to know if that rom will boot with 030.

I can confirm it does.

Before the 534, I used 1.3 on the 1000 with the TF530 just fine (even got IDE to work later with the hacked scsi.device ROM.)

EzdineG wrote: 28 Jun 2020 23:32

terriblefire wrote: 28 Jun 2020 23:29

Its just useful to know if that rom will boot with 030.

I can confirm it does.

Before the 534, I used 1.3 on the 1000 with the TF530 just fine (even got IDE to work later with the hacked scsi.device ROM.)

Ok good to know. I have one of your ROM boards built for my A1000 but its actually sitting in my H4 at the moment.