Atarieterno wrote:The same thing happens to me, but with my STe in ACSI mode. The copying files from the floppy disk drive to the card SD there is no problem (also I do not had problems when it was using a Megafile 60, therefore I do not believe that is "bad DMA"). When I try to backup large quantity of data, for example from a partition to other of the same SD, the information fails. I use the PPera's drivers.
Jookie wrote:I got some other reported issue on Falcon SCSI, I will have to look further into this one (and that one). It seems it works better on TT though...
Could you, please, run the CE_TSTHD.PRG (from config drive) on your Falcon when CE is connected, and let it transfer data for at least 500 MB? (maybe hour or so).
dhedberg wrote:Here's my report.
Ran CE_TESTHD.PRG on my Falcon030.
- 1.2GB with no errors.
- Quit the program and copied a 700MB file from my IDE drive to the CosmosEx SD card.
Ran CD_TESTHD.PRG on my C-Lab MKII.
- 800MB with no errors.
- Quit the program and copied a 700MB file from the CosmosEx shared drive to the CosmosEx SD card.
Why is the CD_TESTHD.PRG so slow? It took forever to read/write 1.2GB. It takes a 2 seconds to copy the 700MB file.
Ektus wrote:dhedberg wrote:Why is the CD_TESTHD.PRG so slow? It took forever to read/write 1.2GB. It takes a 2 seconds to copy the 700MB file.
The Falcon's SCSI bus is capable of transferring around 1.5 MB/s. Therefore, copying a 700MB file should take at least 8 to 10 Minutes! Same with transferring to/from a network drive or wherever, the SCSI is the limiting factor here.
Ektus wrote:I don't have a CosmosEx, but if the test programs show everything working and real operation produces errors, I'd look at the software side of things. Switch off the Falcon's CPU cache and try again?
1st1 wrote:Could it be the powersupply for the cosmosex device which is too weak?
Jookie wrote:Download this newer version of the HD interface test (which will be included in the next update), for now from my dropbox:
Run it on your Falcon, choose 'S' for simple error messages, pass the speed test, and then choose 'S' for stress test, and let it run as long as possible:
- if everything would go well, you should see only stars (asterisks) here - at least one full screen of them - then I would suspect something to be wrong here with the handling of SD card
dhedberg wrote:What termination resistor packs are you using on the CosmosEx? I measured them and they do not seem to be the standard SCSI 220/330 ohm resistor networks (200/330 ohm resistor packs are used internally in the Falcon as well). Could the termination of the CosmosEx be a problem?
Jookie wrote:Translated disks (using CE_DD) go through CE_DD.PRG, which does have retries implemented, so when the communication Atari vs CE fails, it retries again (or couple of times), and if that succeeds, then you have your data just fine, without corruption.
Raw disks - SD card and USB RAW drive - go through disk drivers like HDDRIVER or ICD Pro and through TOS, and they don't do the retries - if the communication of Atari vs CE fails, the data will not get read / written again and it's screwed.
Until the fixes are done, I know that there is an option in HDDRIVER to turn on verification after write, which does slow the speed to half (data is transfered twice), but at least it immediately reports that data got screwed.
Users browsing this forum: No registered users and 5 guests