Hyperion Entertainment Message Boards

develin wrote:And there are some missed strings in the Swedish translation that might be good to know about, some in the new context menu and I also found that there was one in the new shell menu.

Thanks for your report, I'll file a bug for the translations and look into it.

I had an idea of creating a form of legacy applications/games wrapper that launches a program and registers with application.library. This could then for instance enable the game mode, but also supply application.library functionality using some ARexxing or so.

Shouldn't be too complicated.

Yeah, it might get confusing. I won't post anymore here, but rather in the ticket.
I haven't done anymore yet: busy with work and stuff, and now there's a power failure at home.

So. 1. I had the memory module reseated. I booted it up, which went ok. Time: 11:31 2. I had no network, since my network cable wasn't connected, so I connected it and did a "reboot fast sync", and just left it running. Time 11:35 3. I return a few hours later (13:23) and found the screen ...

How much ram do you have?
Try reseating RAM.

I have 2GB in one module. I reseated it during my first round in this thread, and have now done so again.

Now it started up ok, I've not had it powered on for a few days. We'll see what happens.

The memtester is the program linked above. It's started from CLI, so I don't think it is the CFE MemTester. The log would be okay if it wasn't repeating itself, but now it either fails to give any output at all, or just repeats these lines over and over: the log : [HELO][DRAM]SDRAM: ECC off, Non-ECC...

I hear what you say, and can agree. I do however have no other clue than a faulty memory. Given that the black screen freeze is what happened even when I didn't run memtester, it seems likely that memtester rather than being directly responsible, triggered the error by doing its "memory stuff&q...

Well, I don't really know what to try. I have to do something. I do feel it seems unlikely that the memory should be faulty, but given that the log indicates something memory related, and it just frooze after running memtester. It's almost as if the memory fails when in use...? [HELO][DRAM]SDRAM: EC...

I suggest you grab memtester off Depot & run it overnight to test your memory. We had one other user with a flakey system & memtester found one bad memory stick, he replaced it & fixed. Memtester takes a long time to check memory, so run it overnight, you only need 1 pass to check it/th...

Does it ever complete?

Looking quickly at the code, it seems to be a loop dependent on the variable "c". Is that ever changed in the loop? I. I couldn't spot where it's changed.

Given that there isn't a lot of code, it'd be fairly easy to debug it. I'm thinking you have an infinite loop.