I see, thanks. I haven't run it from an icon, so I didn't see the requester. The crash at exit is a regression though, as it doesn't happen on ABIv0 nightlies or distros from a few years ago.
@ncafferkey fixed a number of network drivers to work on 64-bit: intelpro100, nvidianet, prism2, realtek8180, rtl8029, etherlink3 as well as made a general fix to AROSTCP.
Thanks deadwood, given the many improvements, and the many software programs converted to 64-bit, I have recreated a new build for the next version of AROS One 64 v11.
Everything seems to be going well and quickly. I noticed that you have eliminated the ‘defective’ TAR command.
I would say that AROS One 64 has improved considerably. As soon as a fix for Mplayer, TAR and maybe some missing Datatypes is available, AROS One v1.1 will be ready for distribution.
Regarding AROS ABIv0, will there still be Core updates, or should we consider the 32-bit chapter closed?
Regarding AROS ABIv0, will there still be Core updates, or should we consider the 32-bit chapter closed?
This depends on whether there will be people still using 32-bit version. From what I'm seeing on the forums, everyone is switching to 64-bit version (which is good). If there is a demand for it, I will make an update to 32-bit core sometime in Q4 this year.
@ncafferkey fixed a number of network drivers to work on 64-bit: intelpro100, nvidianet, prism2, realtek8180, rtl8029, etherlink3 as well as made a general fix to AROSTCP.
deadwood Every now and then, when I copy data with Dopus4 64Bit v11, a Guru appears. It's very annoying because it almost always appears suddenly, often when copying to FAT 32 devices.
Once, after the Guru appeared, it even invalidated my SFS Hardfile (which had never happened before)!
I will need more information TBH. On your screen shot you are copying from disk to pendrive, both being SFS I guess. Each time this happens please take a screnshot from the requester with "More.." clicked if possible and note what was the source (which device: ahci, ata, usbscsi, which file system) and same for destination. If after 3-4 instance of this problem we can see some pattern I can start looking for cause.
Unfortunately, this occasionally occurs when copying to other devices, likely due to a previously executed file or corrupted memory. As soon as it happens again, I will try to attach the Guru. In many cases, it does not allow me to use ‘More.’
Regarding AROS ABIv0, will there still be Core updates, or should we consider the 32-bit chapter closed?
This depends on whether there will be people still using 32-bit version. From what I'm seeing on the forums, everyone is switching to 64-bit version (which is good). If there is a demand for it, I will make an update to 32-bit core sometime in Q4 this year.
The biggest thing which would hold me to 32 bit would be Hollywood; is there still a thought there'll be an wrapper/emulator to allow it to run on 64 bit?
Yes, there is but it will be first targetted/debugged for at applications that people actually use. If you can list 10 most critical Hollywood applications you use together with links where to download them, it would be a good starting point for working on the emulator somewhere later this year.
(1) The Hollywood compiler itself
(2) Hollywood Designer
(3) LilCalendar (in 32 bit AROSONE distro)
(4) HollyPaint (in 32 bit AROSONE distro)
After that I have a set of education-specific applications what I've written; I suppose they might be of some use to someone else so next week I'll be on a break from work and I'll get them into a format suitabe for uploading to the AROS archives.
Ok. I'll most likely start with smaller things things. The compiler and designer will be much more challanging, for one because they are commercial packages.
@deadwood - I will need more information TBH. On your screen shot you are copying from disk to pendrive, both being SFS I guess. Each time this happens please take a screnshot from the requester with "More.." clicked if possible and note what was the source (which device: ahci, ata, usbscsi, which file system) and same for destination. If after 3-4 instance of this problem we can see some pattern I can start looking for cause.
Success again (see second screenshot), I copied ‘copy As’ from the shared folder to the Tar file, restarted, repeated the copy and no guru appeared, as mentioned, this happens occasionally when copying from any path!
Ok, these two screen shots show different errors. Are you able to cause any of that copy errors with linux hosted AROS or does it only happen on native?
@ncafferkey fixed a number of network drivers to work on 64-bit: intelpro100, nvidianet, prism2, realtek8180, rtl8029, etherlink3 as well as made a general fix to AROSTCP.
Regarding ISOs found on build.axrt.org/development please don't use them to fully update your existing "stable" installations.
These are development builds which are untested. These build are good for standalone testing, that is buring them on CD or pendrive and testing how they work, but they are not good for updating you main/everyday installations. Also sometimes, like in above post, developers might indicate to take specified compoments from specified build when they asses it is safe to do so, however this does not mean the whole build is valid to update your "stable" instalation.
Going forward I will try to release an official, tested and certified update package every 1-2 months so that you can refresh you "stable" installations with latest changes.
You can view all discussion threads in this forum. You cannot start a new discussion thread in this forum. You cannot reply in this discussion thread. You cannot start on a poll in this forum. You cannot upload attachments in this forum. You cannot download attachments in this forum.
AMIGASYSTEMDistro Maintainer