aww, you're planning to use AoM 0.5 on that configuration? that's going to be... a problem. Your problem might even be related to that, how is your swap space usage during that dump processing? Might AoM be running out of memory?

exp wrote:
...
aww, you're planning to use AoM 0.5 on that configuration? that's going to be... a problem. Your problem might even be related to that, how is your swap space usage during that dump processing? Might AoM be running out of memory?

BYe!
EXP

Ah. Pretty bad. I *do* have very little memory, but I didn't think it would affect anything other than performance. But functionality?
I'll try elsewhere (better configuration) when I get the chance. That moment might be a few weeks away, though. Are there any other ideas? Or a way to use the dump I've already downloaded?

Apparently it takes 4+ hours to parse the dump file with 256mb ram I'd guess it's not actually done...... I would strongly advise you to not try aom.5 on a computer with less than 350mb ram, 512mb is strongly recommended if you want other stuff running.

When aom.6 arrives in 2019 though you might be interested in checking it out again, until then try out webaom.

PetriW wrote:Apparently it takes 4+ hours to parse the dump file with 256mb ram I'd guess it's not actually done...... I would strongly advise you to not try aom.5 on a computer with less than 350mb ram, 512mb is strongly recommended if you want other stuff running.

When aom.6 arrives in 2019 though you might be interested in checking it out again, until then try out webaom.

~^v^v !!!! ^v^v~
Wouldn't have guessed. That window (decrypting/unpacking or whatever) just wasn't there anymore the next time I looked (after 30 minutes), so I thought it was done. Also, there wasn't even any message about increasing size of pagefile.

WebAOM won't do, I just need to browse, *offline*, and don't care about mylist or hashing. Also, by 2019 I'm planning on having a classic/neurocomputer hybrid, so other compatibility issues are bound to pop up. I really dislike delphi.

Anyway, although the bug temains, I got the explanation I needed. Thank You.

Just fyi the quality/speed/ram usage of aom.5 has nothing whatsoever to do with delphi...

Most people who dislike delphi don't really know anything about it, I've heard some pretty weird things (like it being an interpreted language... wtf!).

Oh, and I don't see a reason for why aom.5 would not work on 128mb ram if you have enough virtual memory, but you'd need a freaking lot of that. (500mb+ to be somewhat safe) As it'd be the dump parsing which would get the out of memory error the only place it might be written is in the log, there won't be an error window.

Just fyi the quality/speed/ram usage of aom.5 has nothing whatsoever to do with delphi...

I meant lack of stability, and missing libraries. I've had many problems with stability of delphi apps, though I might have just been unlucky (not to mention unskilled). Also, I dislike programming in delphi & pascal, but that's just my personal preference. Let's not discuss it.

As for memory, I do realize what would be needed if it was done in java.