GR 80000004 C:Charsetconvert after System power-up

[redfox]

Sunday morning Jan 13, 2013 I updated several available system files using AmiUpdate. All seemed to be ok afterward. I powered off my system as usual when I finished my session. Did not power up again until evening.

First power-up of the evening ....
Guru Meditation: 80000004
Task 0x6b892060 ("C:Charsetconvert")

Rebooted machine and it came up ok.

I have recorded this twice before
August 2, 2011
March 30, 2012

Since it has happened so rarely, I cannot pinpoint any fault. Will see if it occurs again in the near future.

---
redfox
MicroA1-C with 750GX CPU
AmigaOS 4.1 Update 6

[chris]

Sunday morning Jan 13, 2013 I updated several available system files using AmiUpdate. All seemed to be ok afterward. I powered off my system as usual when I finished my session. Did not power up again until evening.

First power-up of the evening ....
Guru Meditation: 80000004
Task 0x6b892060 ("C:Charsetconvert")

Rebooted machine and it came up ok.

I have recorded this twice before
August 2, 2011
March 30, 2012

Since it has happened so rarely, I cannot pinpoint any fault. Will see if it occurs again in the near future.

---
redfox
MicroA1-C with 750GX CPU
AmigaOS 4.1 Update 6

That's interesting that you're on a µA1. Mikey_C had loads of problems with OS4 crashing at the point WB shows up - we reduced the core voltage (two places as we didn't have any jumpers to hand) and it worked more reliably after that.

[ZeroG]

@redfox
BTW: Why do you run charsetconvert (a tool to convert the charset of a textfile) in your startup-sequence, user-startup or WBStartup?

[redfox]

@ZeroG

I cannot see Charsetconvert anywhere in my startup-sequence or user-startup or WBStartup.

I have never added it to any of these scripts.

--
redfox

[Belxjander]

I have also seen this... in refreshing my entire workbench startup config when installing update 5 it has gone away

I had the impression it was part of somethings startup but was unable to narrow down exactly what


I have not seen the error since and now have update 6 installed