Error while copying bigger files to USB stick and shared drive

[atari66]

Hello

recently acquired a CosmoEX, using latest firmware and TOS 1.04 (German). With a bare installation (aka only loading the driver directly from CosmosEX) as well as in a situation where HDDriver (free trial version) is loaded some files (notably those larger than 140.000 bytes) I get the error message

'"Diese Laufwerk hat nicht gen"ugend Speicherplatz' - aka .not enough space on this drive'

this happens both with USB and shared network drive. Smaller files copy without issue.

sizes of files not working in bytes:

151870
144748
156324
344182
60299 (extremely strange, some larger files worked)

any ideas
thanks

[Jookie]

Hello,

you mention that you have the latest firmware, so does your main app report version: 2017-01-03 ?
Did you update just now? Did you wait a little and then turn it off and on after that update?
You have Raspberry Pi 3 installed, or some older one?
How do you power the device? Internal PSU of Atari, or external PSU? What rating (V, A) has the external PSU if used?

Jookie

[atari66]

WOW - that is a turnaround time (working in IT myself )!

the CosmosEX is brand new, got it only a few weeks ago
RPi version: a02082
Rasperry Pi 3, model b, rev 1.12
external USB UPS, 2A rated
ACSI connection

updated - so I must have been a few days out - and the error went away, at least when working with a fresh booted CosmosEX
will now do a complete copy of all files again to see if error happens again

thanks!

[atari66]

second try successful - all 570 files copied without error

thanks again and happy new year

[Jookie]

WOW - that is a turnaround time (working in IT myself )!
the CosmosEX is brand new, got it only a few weeks ago
updated - so I must have been a few days out - and the error went away, at least when working with a fresh booted CosmosEX

Yeah, this Raspberry Pi 3 compatibility thing got solved 5 days ago, so that update was necessary It was linux configuration issue, they (Raspbian) switch the RPi core frequency up and down, depending on the system load, and the trouble was that this core frequency was also used for generating SPI clock, which was wrong because of that core frequency going up. So now the core frequency is fixed to 250 MHz, the SPI works fine (the instruction (arm) frequency still toggles between 600 MHz and 1200 MHz depending on the load).

second try successful - all 570 files copied without error
thanks again and happy new year

Great, you're welcome, and same to you
Jookie