exxos's Atari, Amiga & retro forum

dad664npc wrote: 22 Aug 2023 14:17 The problem I had copying your folders on to sd card was MACOS. I can copy them with a virtual Windows machine.
So am now deleting.... every now and again I am seeing "Can not delete folder <xxxxx>" so hit SKIP, then that is followed with a "Can not delete file A..", then hit SKIP again to continue on its merry way (three occurrences so far with 20000 files to go :shock: )

Very odd that you get the error box. I have never seen that, It just outright crashes at random :shrug:

But what driver are you using ? Also you have blitter enabled ? Using TOS206 ?

Ok, so I tried with my MSTE configured as 8Mhz with my CosmosEx and HDDriver 11.

And boom:


4 bombs and no more deletions going on, but mouse pointer remained active.

BTW I didn't see any file/folder name corruption until I ran it a 2nd time with the remains of same folder after a reboot:


It's now down to 640 folders and about 6300 files, but it isn't bothered at all by the corrupt folder names. I'll report back if it finishes ok.

It makes me wonder if it's a memory problem, not enough resources to contain the list of files/folders it wants to delete. Since it had 2376 folders left when it crashed first time, that's why I continued after a reboot to see if it would run to completion.

rubber_jonnie wrote: 22 Aug 2023 14:32 It's now down to 640 folders and about 6300 files, but it isn't bothered at all by the corrupt folder names. I'll report back if it finishes ok.

It makes me wonder if it's a memory problem, not enough resources to contain the list of files/folders it wants to delete. Since it had 2376 folders left when it crashed first time, that's why I continued after a reboot to see if it would run to completion.

Odd you also see some random corrupted names also. It suggests a corrupted sector read.. but on now 4 machines with 4 drives... If it is a hardware problem, then every Atari has a fundamental flaw in its DMA system.

I did wonder if it's simply not able to allocate a large enough buffer for it all the files or something. But again, it seems to work with TOS1.62 and PP driver. So I don't get it :(

Ironically ICD would not let me delete more than about 500 files in one go. So maybe that is a clue. :shrug:

exxos wrote: 22 Aug 2023 14:29

dad664npc wrote: 22 Aug 2023 14:17 The problem I had copying your folders on to sd card was MACOS. I can copy them with a virtual Windows machine.
So am now deleting.... every now and again I am seeing "Can not delete folder <xxxxx>" so hit SKIP, then that is followed with a "Can not delete file A..", then hit SKIP again to continue on its merry way (three occurrences so far with 20000 files to go :shock: )

Very odd that you get the error box. I have never seen that, It just outright crashes at random :shrug:

But what driver are you using ? Also you have blitter enabled ? Using TOS206 ?

STe with TOS2.06 + HDDriver 11.13 - Unsure about blitter - think its enabled but can't confirm until deletion completes.
Interesting fact - I'm seeingg the following every 1000 files

exxos wrote: 22 Aug 2023 14:36

rubber_jonnie wrote: 22 Aug 2023 14:32 It's now down to 640 folders and about 6300 files, but it isn't bothered at all by the corrupt folder names. I'll report back if it finishes ok.

It makes me wonder if it's a memory problem, not enough resources to contain the list of files/folders it wants to delete. Since it had 2376 folders left when it crashed first time, that's why I continued after a reboot to see if it would run to completion.

Odd you also see some random corrupted names also. It suggests a corrupted sector read.. but on now 4 machines with 4 drives... If it is a hardware problem, then every Atari has a fundamental flaw in its DMA system.

I did wonder if it's simply not able to allocate a large enough buffer for it all the files or something. But again, it seems to work with TOS1.62 and PP driver. So I don't get it :(

Ironically ICD would not let me delete more than about 500 files in one go. So maybe that is a clue. :shrug:

So after I rebooted and restarted the folder delete, it completed with no further issues. It had however reverted to 16Mhz, so I will try the whole thing again at 16Mhz as my firt test was at 8Mhz.

rubber_jonnie wrote: 22 Aug 2023 14:45 So after I rebooted and restarted the folder delete, it completed with no further issues. It had however reverted to 16Mhz, so I will try the whole thing again at 16Mhz as my first test was at 8Mhz.

8MHz and 16Mhz By itself could yield some useful info as well I guess.

dad664npc wrote: 22 Aug 2023 14:42 STe with TOS2.06 + HDDriver 11.13 - Unsure about blitter - think its enabled but can't confirm until deletion completes.
Interesting fact - I'm seeing the following every 1000 files

Hmmm.. . when I first started testing it didn't seem to matter if the blitter was enabled or not. But it was repeatable this week that it would only ever fail when the blitter was enabled.

I have not specifically counted any amount of files deleted, so that could be useful info.. mostly seems to have been random but I guess I can check more thoroughly!

exxos wrote: 22 Aug 2023 14:48 I have not specifically counted any amount of files deleted, so that could be useful info.. mostly seems to have been random but I guess I can check more thoroughly!

The test folder deleted cleanly so I'm just copying it over again to test at 16Mhz.

So:
1656 - 630 = 1026
2736 - 1028 = 1708

1026 + 1708 = 2734 total files and folders deleted before the crash. So doesn't seem any logical number in the total amount deleted. I will try a second time to see if anything looks common....

exxos wrote: 22 Aug 2023 14:46

rubber_jonnie wrote: 22 Aug 2023 14:45 So after I rebooted and restarted the folder delete, it completed with no further issues. It had however reverted to 16Mhz, so I will try the whole thing again at 16Mhz as my first test was at 8Mhz.

8MHz and 16Mhz By itself could yield some useful info as well I guess.

16Mhz failed at EXACTLY the same point. 2376 folders left and 23510 files left.

I'm going to try to finish it again, but this time at 8Mhz, since last time it finished fine at 16.