recent Ringhio Server error at start up

get this window at every boot after last full AmiUpdate..anyone else get this before I start 'rolling back'?

'CHARSETCONVERT: Zero length FROM file "ram:tmp.txt"
'C:Charsetconvert failed returncode 20'

Yes, it comes from the former version of DirMeUp (a new one and a new demo are available).

I had to edit envarc:Sys/ringhio.appsprefs.xml and delete the ligne about DirMeUp to get rid of this message.

Glames has found that a character not supported by Ringhio had been used.

What character was used ?

And btw I strongly advice to do not edit the xml file but use instead the Prefs/Notification editor and the Delete button.

m3x : yeh, I know we must NOT touche this file but I found this error really annoying (and I had forgetted about the preferencs, shame on me ).

Glames could answer your question.

I think he would say "underscore _" character

@m3x

I got a similar error the other day, due to a strange ringhio.appsprefs.xml entry :


The strange thing is that there were multiple copies of it (5-10). Trying to delete all the entries using Prefs/Notifications, it freezed on the second attempt, unable to delete further entries or save/exit the program.
Starting Prefs/Notifications without SS, poped up DSI error. Increasing the stack size didn`t change a thing.

SW: OS4.1FE.U1

{edit}
a 1046 characters long string edit, to fit page layout.
Maybe this is the culprit for the Notifications freeze/crash?
{/edit}

I had this error after I installed WBexplorer.
You can read my comment about it.

I have that error few days ago too, but then it disappear somehow. Probably after i replace original one, with Enhancer's one. But i not sure, sorry.

I tried WBExplorer too, just before the problem appeared!
Now it seems resolved, after editing out one by one the strange entries with garbled characters (reset->delete just one entry->save->reset->delete next one , and so on).

The "CHARSETCONVERT: Zero length FROM file "ram:tmp.txt".
C:Charsetconvert failed returncode 20" error message is attributed probably to strange behaviour of the running programs, forcing multiple or strange string entries to Notifications/Ringhio server.
The baffling thing to me is that theses entries crashed the Prefs/Notifications when I tried to delete them (string lenght related crash?)

I got this error too now, 'thanks' to Workbench Explorer. I have a suspicion it may be something to do with it supplying a Null pointer for it's description, because it says "(null)" but all other Ringhio apps without a description just say they have no description.

My description is not blank:



This is how I submit messages:



Why do I and my 3 beta testers not get this error?

I deleted the entry in Prefs->Notifications, changed to this:

REGAPP_Description, "Test",

It works.

REGAPP_Description, "A better way to brwose drawers",

Does not work. (null)
When open Notifications window I get the error message.
But not when just "Test"

@mritter0

Maybe your localised string is getting freed before application.library has finished with it?

I Unregister the app before closing Locale.

See my edit above.

Error: A better way to browse drawers
Works: A better way browse drawer

Error: I like to ride bikes
Works: I like ride bikes

Error: Welcome To The Jungle
Works: Welcome The Jungle

Error: to
Works: too


Seeing a pattern here......

@mritter0

even if you "put" such string between quotes (or single quotes)?

TO is an argument in charsetconvert.

Maybe RinghioServer when creating TMP.TXT does it in a funny way that "confuses" (the cat!) charsetconvert :-/

@jabirulo
Interesting idea! For the sake of discussion, here's CharsetConvert's arguments:
FROM/A,FROMCHARSET/A,TO,TOCHARSET,EOL/K

It sounds plausible that RinghioServer might not use quotes for the FROM argument...

@mritter0
Why not try using the following string, as a possible work-around:
"\"A better way to browse drawers\""

Using the extra quotes does work!

So then it is an error in the Ringhio server, not WEx.

Someone needs to pass this info along to the developers. I am surprised that no one else has used the word 'to' in their description.

@mritter0
I submit BZ for , so if max will fix it it will be in some of updates in the Enhancer.

But even so, you (mritter0) had better use the workaround of double-quoting the message in WEx, because you cannot rely on everybody to have the Enhancer Pack, and the bug is not likely to be fixed in the Ringhio version accompanying AmigaOS.

Best regards,

Niels