Yesterday I updated my AmiUpdate from 2.49. It did not work because I had a lingering update library in my libs: multi assigns chain. Once removed and rebooted everything went fine.

You need to check that the backup program understands and respects AmigaOS links otherwise you may get into troubles especially regarding the shared objects from AmigaOS 4

@khayoz

Yes an updated webkit would be really cool. Nowadays, more and more websites became unreadable with our current version of Odyssey. This makes me sad to not even be able to read my emails through the webmail of my isp anymore.

I have just finished reading the second volume and I really enjoyed the read. I did not know quite a number of details and I found it very interesting.
Now I wonder if there is/will be an hard cover of the volume three. I really want to read it, but I would prefer a physical version rather than the ebook version.

@abalaban

Ok as promised I did some research on my hard-drive and I found out that in fact back in the time I only extracted the few files I needed from the libgphoto and libgphoto_port in order to get working the particular camera driver I was interested in. Far from a complete port!
I cloned the github repo and it needs really more work than I can afford to spend currently on an Amiga project. I am sorry for the false hope :-/
It does not sem to require to much exotic dependencies we do not have yet. But it may need some work to make the dynamic loading to work if our libdl isn't up for the job.

A long time ago, it was at the age of my A1XE with prerelease 2 or so, when I was playing with usb driver for a digital camera and VHI I did a port of this library.
It probably changed quite a lot since I did it but I may have a look this weekend.

If the script for auto-installing is correctly written and makes use of the proper way to update *all* files on the file system (do not remember the name of the dedicated shell command atm) then you should be able to browse all your installs in the rollback utility and find the one that updated both libs, rollback this one and AmiUpdate will offer you the ability to download again the package.

As Joerg said libc.a should not be in the same update as newlib because they are targeted to different audiences: users VS developers. There is different situations where mixing won't work, you named one, but what about when I install the update as a simple user (so no SDK installed, hence no place to install the libc.a) but later on I learn how to code and install the SDK?
I advise making two updates one for newlib and one for libc.a the second requiring a given version of newlib (can be described in AmiUpdate database)
BTW AmiUpdate also checks using filesystem dates as a last resort.

@elfpipe

Don't know if this may make any difference but maybe your Kickstart/ram-handler.kmod may not have the 'read' attributes set?
Another idea: may it be possible that you have several kickstart and you somehow messed up with them? Ending up with mixing incompatible versions? On this last one please add asked by Colin provide version numbers of the listed kmod.

@elfpipe

Quote:

I did port updated smartmontools but it cannot work with internal sata from X5000 and A1222 because it was decided to abstract them using vsata.device in an incompatible way. I seem to remember some information may be retrieved using a custom tool but I cannot remember it's name right now and am going to leave for work,maybe something like idetool or something like that.

@kas1e
Yes I think only an Arexx port could allow such feature

Hi Kas1e,

I don't think that this is possible right now. And I don't think that Filer instances knows the order they were started.

@LiveForIt

I did the same using TCP: instead of AUX: thus leaving the serial for debug purpose

@kas1e

Because this is not possible right now does not mean that this will always be the case.

Hi Kas1e,

I'm afraid that there is currently no possibility to select source/destination state of a lister via tooltip or command line argument.
I guess you are trying to mimic a Dopus 4 style filemanager with a dual lister setup.
IMHO this would be very restrictive compared to the current ability to have multiple listers where anyone can be the destination of all the others at anytime.

As LiveForIt told nothing you can do unless you are a programmer and have access to the source code. I just want to correct what he told about the function goal: this is not a function to look for a string inside another string but a function to find the first file or directory matching a given name pattern see https://wiki.amigaos.net/amiga/autodocs/dos.doc.txt.

Otherwise there are other ftp servers for AmigaOS 4 still supported for example a-ftp-server or ftpd (by others and me) which are free or ZitaFTPserver (by Hans) which is commercial, see available options on os4depot.net http://www.os4depot.net/index.php?fun ... se&cat=network/server/ftp

I probably miss something but for what reason would you want to FreeMem() memory allocated with AllocVec()?
Internally AllocMem() probably defaults to AllocVec() but it may also perform different things prior this.
So my advise would be always match allocation methods with appropriate freeing one, and you would always be on the safe side.

@SinanSam460

We had a nice private party with Huno two weeks ago and he was working on this code. What I can say is that he worked hard during the three days to polish rendering and all was done natively on his X5000 he was not cross compiling at all... this may be relevant to your problem I don't know??

@kas1e

To me your problem is stack related: the code is trashing the stack somewhere and depending on the dependency to the stack of the functions you are calling then it may or may not crash. On the other end as soon as you are calling printf then you are realigning it and everything got back on track.
The worst is that printf itself is often the culprit of such stack trashing: for example you are passing too much or too few parameters compared to the format string or you are passing wrong type (eg. a 64 bit parameter while only consuming 32 bits).

Edit: fix typo in seconds white of my answer

@kas1e

Thank you I had difficulties with the installers (I have the first CD batch with read errors, which for some reason was not apparent on my 1200 PPC back in time but seems to be really a showstopper now under AmigaOS 4...). Then I managed to completely mess my system with rtgmaster and all. I thought PPC version will be easier to run but now I have a grimreaper which only bring me a black screen if ignored.
I will try the 68k version again, not sure if I installed both 1.2 patches. I will check, thank you.

Ps: I think the 32bit screen problem is exactly the same problem you mention for the PPC version: it could not find the correct screen resolution.

@Nuder_Try

Did you managed to get this sorted?