Re: TF536 on the ST
Posted: 12 Aug 2020 20:30
Hmmmm i'll try out a standard ST here but i've had no issues.. I need to get a swapped cable first though.
We welcome retro users & hardware gurus alike! Come and join the party :)
https://www.exxosforum.co.uk/forum/
Might be an idea to run it past PP - maybe its an issue with the 030 in general?Umberto1st wrote: 12 Aug 2020 20:16 PP's Hard disk driver is incompatible with the TF536 and TOS 2.06.I can partition but reads and writes are all corrupted. I have tried on multiple machines with the same result. I think its time to set the TF536 to the side for a while and get onto repairing my Falcon. I don't have any hair left to pull out. Hoping these issues can be worked, since it is a nicely designed booster.
Like i say it works for me fine. But PP is not really "friends" with us here on the exxos forum anymore.GadgetUK164 wrote: 12 Aug 2020 23:14 Might be an idea to run it past PP - maybe its an issue with the 030 in general?
Doesn't he tailor the driver for the actual system? So it might not be fair to expect a driver for a standard ST to work properly on the TF536 (or a Falcon or TT even)...I know HD Driver is more of a 'one solution for all systems'...GadgetUK164 wrote: 12 Aug 2020 23:14 Might be an idea to run it past PP - maybe its an issue with the 030 in general?
I have tried on two machines. Since I just purchased his driver, I'll give Peter a more detailed description of my system. I remember him railing on atariage, about this forum and certain individuals, so I probably will not mention this forum when I make my request. I'm not excluding the possibility that it could be my board. My solders are good, confirmed with a high power microscope. All my 030's are good. CPLD's program fine and it passes the ram test on diagrom. It could be a 030 problem with Peters Driver, since it has similar problems on the TF534. I cant make a definite conclusion on that without further testing. I still feel that it is a firmware issue in terms of autoboot on 2.06. I'm not sure I fully understand how you are bypassing HDINT in your firmware. I know that HDINT passed though the MFP. There is certainly an issue on how the TF536 handles the DMA. It's odd since the FDC works just fine with the DMA. Would it be possible to release a version that is dependent on a tethered INT. I know you probably busy with life as I am, so if you can it would be great. I'm putting this to the side and focusing on my Falcon(bad combel). I would love to get the Mega working with the TF536, since I have owned it for 35 years.terriblefire wrote: 12 Aug 2020 23:24Like i say it works for me fine. But PP is not really "friends" with us here on the exxos forum anymore.GadgetUK164 wrote: 12 Aug 2020 23:14 Might be an idea to run it past PP - maybe its an issue with the 030 in general?
Odd, haven't had any floppy problems. Do you have any pullups on the dma data bus?PhilC wrote: 13 Aug 2020 08:22 Just to add further feedback, I've not been able to get tos2.06 autobooting with the image from on this thread but EmuTOS boots fine.
I also wanted to add that I've been having floppy issues as well. Both my Mega ST and H4 won't boot or format a floppy at all unless I take out the HD upgrades. So far they seen to work with DD disks. Ill do more testing with this now the Megas floppy drive is fixed.
I dont have HD upgrades in.PhilC wrote: 13 Aug 2020 08:22 I also wanted to add that I've been having floppy issues as well. Both my Mega ST and H4 won't boot or format a floppy at all unless I take out the HD upgrades. So far they seen to work with DD disks. Ill do more testing with this now the Megas floppy drive is fixed.