As I said before, if I am copying files that are hundreds of megabytes to RAM: using the Shell, I never have any issues unless I try and copy more than the RAM disk can take. At this point, the system will freeze. If I use the Workbench's drag'n'drop, it doesn't seem to like the same large files at all and will freeze during the copy.
Given that the copy function works okay in the Shell (ignoring the ran out of space freezing issue) and not with the Workbench to me points to an issue with the Workbench's copy function.
Kind regards,
Francis
Amiga 1200 with Apollo IceDrake Amiga 1222+ with RadeonRX 550
corto wrote:@Maijestro This is a known but that does not happen only on A1222. I understand your frustration ... I am trying to identify the problem in order to fix it or circumvent it (at least, if possible).
Thank you for confirming that it is not a hardware defect, because that was my biggest concern. If the problem is already known, I would like to see it fixed in the near future. I work a lot with the ram disk for quick file storage e.g. unpacking.
For the time being, I will probably not copy large files to the ram disk via drag&drop until the problem is solved.
Thanks again for your reply.
MacStudio ARM M1 Max Qemu//Pegasos2 AmigaOs4.1 FE / AmigaOne x5000/40 AmigaOs4.1 FE
The strange thing is that if I have in another Shell a "LIST SYS: ALL" and meanwhile I copy a file to ram several times with differnete names: "copy aamp21.lha ram:1" "copy aamp21.lha ram:2" "copy aamp21.lha ram:3" ...
when my system reaches ~900/1000 MB of ram filled, usb stack "goes off", my keyboard leds turns off and mouse optical goes off too.
But the LIST SYS ALL: still runs on that other Shell.
Given that the copy function works okay in the Shell (ignoring the ran out of space freezing issue) and not with the Workbench to me points to an issue with the Workbench's copy function.
You're probably using AsyncWB, since that seems to be the default for OS4. Just for kicks, you might try disabling it and trying the Workbench copy again.
corto wrote:Guys, you can also try to disable ExtMem with: SYS/Kickstart/ram-handler.kmod ExtMem=NO
Sweet! This worked for me on my A1222.
Kind regards,
Francis
UPDATE: This also fixes the issue of the system freezing when the RAM: disk becomes full. I now get the expected error requester stating that the RAM: disk is full.
Amiga 1200 with Apollo IceDrake Amiga 1222+ with RadeonRX 550
Yesterday, in my tests, I was pretty sure that even with ExtMem off, I had no requester preventing the copy if the available memory was not large enough.
corto wrote:Guys, you can also try to disable ExtMem with: SYS/Kickstart/ram-handler.kmod ExtMem=NO
Sweet! This worked for me on my A1222.
Kind regards,
Francis
UPDATE: This also fixes the issue of the system freezing when the RAM: disk becomes full. I now get the expected error requester stating that the RAM: disk is full.
Where do I have to enter it in the shell, or how did you do it?
MacStudio ARM M1 Max Qemu//Pegasos2 AmigaOs4.1 FE / AmigaOne x5000/40 AmigaOs4.1 FE
>At least 4 GB with software using ExtMem like ram-handler, maybe more on the 64 bit systems.
Sorry to butt in, but from what I understand: A1222 runs on a 2GB memory limitation The extra memory would be used just for the ram (I am leaving aside the technical subject of using ExtMem)
>At least 4 GB with software using ExtMem like ram-handler, maybe more on the 64 bit systems.
Sorry to butt in, but from what I understand: A1222 runs on a 2GB memory limitation The extra memory would be used just for the ram (I am leaving aside the technical subject of using ExtMem)
Does anything use memory above 2GB in AOS4 ?
AmigaOs4.1 has a limitation of 2GB Ram which not only affects the a1222, but all systems. That's how I understood it.
If a tool, game, program needs more than 2GB memory it has to access the ExMem function, but I don't know of anything that uses the ExMem function.
MacStudio ARM M1 Max Qemu//Pegasos2 AmigaOs4.1 FE / AmigaOne x5000/40 AmigaOs4.1 FE
@Maijestro As far as I understand the 2GB limitation comes from some pointers using a bit for something in AmigaOS (I don't remember the details but can be found by searching for it) that limits the otherwise 4GB 32bit addresses to 2GB only. Additionally the 32bit PPC machines had a memory map where the upper 2GB was reserved for PCI and system stuff like firmware ROM and supported only 2GB RAM so this wasn't a problem on those machines.
Removing the 2GB limit and allow 4GB would need changing the AmigaOS API to remove the used bit which would break code relying on that. Removing the 4GB limit would need AmigaOS to support 64bit and might break all 32bit code unless this would be handled by the OS in some clever way which is unlikely will ever happen with current development pace.
I have the same problem with my SAM460LE with 2Gb RAM. when copy more than 1 Gb of data to ram , mouse and keyboard die or system hang, really I don't know.
Sam460LE AmigaOS 4.1FE with 2 Gb ram and Radeon RX550 LowProfile.