PPC + Windows XP (?) problem

[Toni Wilen]

It probably should try lower amount (128M) first before aborting.

[amilo3438]

Originally Posted by Arnie

Just tried it on my XP setup and it works O.K so I'm not sure what the problem is for you.

Originally Posted by AnnaWu

Sorry, the info (screenshot included) is not informative for me.
Apart from the fact that I am not the only person with this problem.

Originally Posted by Arnie

It shows:

Windows XP SP3
Default BlizzardPPC
Booting from WB3.1
256mb fastmem.

Yeah, but you forgot that it also shows 3.25GB RAM! (in System Properties on your WinXP)

[Arnie]

Originally Posted by amilo3438

Yeah, but you forgot that it also shows 3.25GB RAM! (in System Properties on your WinXP)

Sorry, what's that got to do with anything?

[amilo3438]

Originally Posted by Arnie

Sorry, what's that got to do with anything?

See posts 16, 17, 18 on previous page!

[amilo3438]

Originally Posted by Toni Wilen

I also said it is not caused by amount of RAM but amount of address space. Anything more than 256M contiguous Amiga address space under XP can get unreliable. Perhaps something like "winuae.exe -maxmem 128" "fixes" it.

yes, if start with "winuae.exe -maxmem 128" it does not crash!

Hmm, but it also does not crash with "winuae.exe -maxmem 256" !? (tested winuae3200) ... and sysinfo reports 256mb of mem!

Edit:
It also does not crash with "winuae.exe -maxmem 512"! (strange - seems it only crash if started without using "-maxmem" parameter)

It seems as using with mem parameter it allocates needed memory ahead, before emu even starts, and that could be the reason why it does not crash, I guess.

So, starting the winuae3200 with "-maxmem 256" parameter the problem is gone! (It does not crash in "Quickstart A1200 Blizzard PPC" anymore)

I noticed I get in sysinfo 256mb also if use "-maxmem 128" parameter! (strange) (anyway, in both cases the PowerUP test passed!)

Edit2:
It works fine also after using "-maxmem 1" parameter! (super strange) (but if using "-maxmem 0" parameter it crashes!)

[Arnie]

Originally Posted by amilo3438

See posts 16, 17, 18 on previous page!

Originally Posted by Toni Wilen

I also said it is not caused by amount of RAM but amount of address space. Anything more than 256M contiguous Amiga address space under XP can get unreliable. Perhaps something like "winuae.exe -maxmem 128" "fixes" it.

Yes I read that but as Toni said it's not how much memory you have.

Have you tried increasing the PC's virtual memory?

I really don't know how you cope with XP on 1gb of memory, have you considered upgrading?

[amilo3438]

Originally Posted by Arnie

I really don't know how you cope with XP on 1gb of memory, have you considered upgrading?

(a long time ago when I upgraded from 512mb to 1GB)

Well, I do not complain, it works fine for my needs!

Ask Anna how she cope with XP on 512mb!?

[AnnaWu]

Originally Posted by Toni Wilen

It probably should try lower amount (128M) first before aborting.

Excellent idea, Toni