My AmiUpdate does not work

I preferred to open a new topic, rather than polluting the already long and sometimes irrelevant subject of the AmiUpdate update topic.

I installed version 2.54 which seemed to work fine yesterday. Today, I run another test and, when I execute AmiUpdate, I realize that the program generates an error whose origin I do not know.

The error message mentions an XML file that is badly formed. I haven't found any XML file that could concern AmiUpdate. Snoopy tracing doesn't help me either.

>See error log for AmiUpdate<

I reinstalled AmiUpdate 2.54, but nothing helped.

Perhaps someone can help me find the solution?

Sorry for my English, this is a google translation.

@Amiguy

You don't say which server you are connecting to when you get this error. I have tried all the ones I can think of, and no errors here.

Sorry...

Simon

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.

Thank you for your answers.

@Rigo
I don't think the servers are to blame. The problem must be local.

@abalaban
This is an interesting suggestion that I will check out as soon as possible.

If it's local, then there may be a possibility that your preferences may be screwed up.Have a look in ENVARC:sys/update.prefs, maybe something has corrupted the XML file...

Simon

@Rigo

It *has* to be the prefs file, i get the same error periodically from Notifications when there was a crash which resulted in a mangled ringhio.xml file

@Rigo and Raziel

It is in fact the update.prefs file that was in question.

I had huge problems with my AmigaOne X5000, particularly due to NGFS. So I took precautions that often saved my life, notably by saving my versions of operational Workbenches. This method allows me to compare future malfunctions.

This is the case for the update.prefs file, where we can notice that AmiUpdate does not tolerate labels containing accents ("Téléchargements").

>See the comparison between two update.prefs files<

After correction, Amiupdate works again without problems.

Thanks a lot for your help.

@Amiguy

Quote:
AmiUpdate uses an XML file for its preferences, and UTF-8 is the default encoding. Chances are that if you provide a path that contains local characters, AmiUpdate doesn't convert the given string to UTF-8 before writing the preferences file.

@trixie

I think that's what was fixed in the newly released update.library 53.20, judging by its releasenotes.

Best regards,

Niels

Thanks for your precisions. You are absolutely right about the UTF-8 encoding, improved with the new update.library.

But there are still areas for improvement...

My environment is well equipped with this new library.

My new version of update.library

However, when reading the produced XML file, it apparently does not take into account all the special characters. Thus, we can see that the character '/' is well transcribed, but not the characters 'é' and probably others.

>See my new update.prefs<

Despite the new update.library which should correct transcriptions of accented characters, not all characters are interpreted.

It is therefore impossible for the moment to freely use local terms to define reference directories.