Overview Features Instructions Performance Forum Downloads Products OrderV4 Reseller Contact

Welcome to the Apollo Forum

This forum is for people interested in the APOLLO CPU.
Please read the forum usage manual.
VISIT APOLLO IRC CHANNEL



All TopicsNewsPerformanceGamesDemosApolloVampireAROSWorkbenchATARIReleases
Information about the Apollo CPU and FPU.

GOLD2x and Trackdisk Issue

Will 'Akiko' G.

Posts 9
31 Jan 2018 11:14


I don't know if this is the right subforum for this, so don't delete it, just move it to the right one, please.

I noticed a very strange issue with a V500V2+ and the trackdisk device.

Well, first the setup:
Amiga 500+ with an additional 1 MiB card, a Chinon FB-357A HD drive and the Vampire. Amiga OS3.1 with MUI, MWB and PFS3 (the aio handler version) and nothing else.

The issue:
Everytime I try to write back an ADF file to the internal drive, to an external DD drive or to RAD I get NDOS disks most of the time or sometimes disks with some heavy checksum errors. It doesn't matter if I use adf2disk, adf-blitzer or the fine tracksaver. If I write the ADF files to the disk with another Amiga (also a FB-357A) I get perfectly working disks. If switch the Vampire for a Viper 520 I also can produce perfectly working disks with the Amiga 500. Even using the format command sometimes produces non-working disks. It doesn't matter if I turn caches off or booting without startup-sequence. I also checked this with GOLD2 and GOLD2.5, same result.

So are there any known issues with the Vmapire 500 and the trackdisk.device?


Gunnar von Boehn
(Apollo Team Member)
Posts 4553
31 Jan 2018 12:06


AFAIK this works flawless with GOLD 2.7


Will 'Akiko' G.

Posts 9
31 Jan 2018 12:26


Can someone reproduce this? It drives me crazy. How do you get beta access?


Roy Gillotti

Posts 381
31 Jan 2018 13:30


Will 'Akiko' G. wrote:

  Can someone reproduce this? It drives me crazy. How do you get beta access?
 

  Have to be on the development team, or be a lucky youtube reviewer with connections with the development team. Or just wait a little longer until it's released.


Simo Koivukoski
(Apollo Team Member)
Posts 530
04 Feb 2018 18:03


Sorry, I couldn't reproduce this issue with the Gold V2.5 core. A couple of things that come to mind are that is your PSU strong enough and have you set your MaxTransfer to 0x1FE00. Did you copy your source ADF-file back to the another system and made a CRC check for it that it is not corrupted? (your RAD-drive problem indicates it)

Tested with V500V2+ / Chinon FB-357A HD drive / Amiga OS3.1


Will 'Akiko' G.

Posts 9
05 Feb 2018 10:25


Simo Koivukoski wrote:

Sorry, I couldn't reproduce this issue with the Gold V2.5 core. A couple of things that come to mind are that is your PSU strong enough and have you set your MaxTransfer to 0x1FE00. Did you copy your source ADF-file back to the another system and made a CRC check for it that it is not corrupted? (your RAD-drive problem indicates it)
 
Tested with V500V2+ / Chinon FB-357A HD drive / Amiga OS3.1

Thank you for looking into this. I've a selfmade powersupply delivering about 80w, this one works perfectly. I also use the proper 0x1FE00 MaxTransfer value. I actually had to go for a 0xFFFFFFFC mask and a 0xFE00 MaxTransfer (you know < 64KiB). That worked in the end. Maybe the flash memory is a bit weird.


Steve Ferrell

Posts 378
06 Feb 2018 01:01


Will 'Akiko' G. wrote:

I don't know if this is the right subforum for this, so don't delete it, just move it to the right one, please.
 
  I noticed a very strange issue with a V500V2+ and the trackdisk device.
 
  Well, first the setup:
  Amiga 500+ with an additional 1 MiB card, a Chinon FB-357A HD drive and the Vampire. Amiga OS3.1 with MUI, MWB and PFS3 (the aio handler version) and nothing else.
 
  The issue:
  Everytime I try to write back an ADF file to the internal drive, to an external DD drive or to RAD I get NDOS disks most of the time or sometimes disks with some heavy checksum errors. It doesn't matter if I use adf2disk, adf-blitzer or the fine tracksaver. If I write the ADF files to the disk with another Amiga (also a FB-357A) I get perfectly working disks. If switch the Vampire for a Viper 520 I also can produce perfectly working disks with the Amiga 500. Even using the format command sometimes produces non-working disks. It doesn't matter if I turn caches off or booting without startup-sequence. I also checked this with GOLD2 and GOLD2.5, same result.
 
  So are there any known issues with the Vmapire 500 and the trackdisk.device?

Sounds like a head alignment issue to me.



Will 'Akiko' G.

Posts 9
06 Feb 2018 07:50


Steve Ferrell wrote:

  Sounds like a head alignment issue to me.

What the ... did you even read my post? How does a swap of the accelerator make a head alignment issue go away? Furthermore, can you explain me how a head alignment issue of a RAD drive looks like? *facepalm* Did you notice that I already wrote how I got rid of the issue?

posts 8