WinUAE 1.5.1 beta series

[cosmicfrog]

now with winuae_1510b7 Z ram set to 1 gig chip 4 meg on xp64 with 2 gig mem

[Toni Wilen]

Originally Posted by cosmicfrog

now with winuae_1510b7 Z ram set to 1 gig chip 4 meg on xp64 with 2 gig mem

43-187: NATMEM: 1280M area failed to allocate, err=8 (Z3=1024M,RTG=4M)
43-187: NATMEM: retrying 1..
43-187: NATMEM: 1024M area failed to allocate, err=8 (Z3=768M,RTG=4M)
43-187: NATMEM: retrying 2..
43-187: NATMEM: 896M area failed to allocate, err=8 (Z3=640M,RTG=4M)
43-187: NATMEM: retrying 3..

// MessageId: ERROR_NOT_ENOUGH_MEMORY
//
// MessageText:
//
// Not enough storage is available to process this command.
//
#define ERROR_NOT_ENOUGH_MEMORY 8L // dderror

For some reason Windows refuses to reserve that much memory. Not a WinUAE problem.

[cosmicfrog]

ok load the 1gig config get 512 in WB
restart winuae move mem from 512 to 768
now wb has 396 mem and slider now on 384 in winuae
task manger says i have around 1.4-1.5G free

[TCD]

Originally Posted by Toni Wilen

Most likely Windows limitation (64-bit Windows is usually needed to get more memory) 512M Z3 really means 512M+256M+<possible RTG RAM> contiguous address space needed.

It's most likely that your memory is fragmented. So maybe a memory cleanup tool or a simple reboot could solve this problem

[cosmicfrog]

yep just do a clean reset to eliminate that
got any suggestions for monitoring fragmented mem

[Toni Wilen]

Originally Posted by cosmicfrog

ok load the 1gig config get 512 in WB
restart winuae move mem from 512 to 768
now wb has 396 mem and slider now on 384 in winuae
task manger says i have around 1.4-1.5G free

It is not about free memory but failing to reserve huge contiguous virtual address space (~1.3G needed to get 1G Z3)

64-bit Windows should always have at least 1.5G of virtual address space free (per process address space, not system wide) Perhaps you have some utility, patch, hack, stupid driver or perhaps even virus scanner that hooks to WinUAE and does something weird.

[cosmicfrog]

was on abime.net earlier and other ppl have had same prob but its worth a try
off to disable everything that starts up

edit
no difference still the same oh well

[amiga]

Originally Posted by cosmicfrog

ok load the 1gig config get 512 in WB
restart winuae move mem from 512 to 768
now wb has 396 mem and slider now on 384 in winuae
task manger says i have around 1.4-1.5G free

LESSON OF THE DAY:

1 gig RAM is absolutely pointless on the Amiga; stick with 64meg or less !!

[cosmicfrog]

That may or may not be true but as the slider lets me choose up to 1.5 gig and i only get 512 in wb I think your comment should have been posetd some where else

( sorry I had to reply toni)

[Toni Wilen]

I said in changelogs that >=1G is pointless (but fun!) and may not be compatible with most Windows/hardware setups.

[Ed Cruse]

Originally Posted by Toni Wilen

I said in changelogs that >=1G is pointless (but fun!) and may not be compatible with most Windows/hardware setups.

This message was not meant as a reply to your message Toni, I hit the wrong button.

That much ram is not pointless, normally I run with 64megs but I do have a program that allocates 512megs of contiguous ram. I rarely use more then 10megs but it sure is nice to have a lot more when it's needed.

[Toni Wilen]

http://www.winuae.net/files/b/winuae_1510rc1.zip

RC1 (few days or not):

- clear RTG screen when switching to different RTG mode
- d9dx9_36.dll set to delay load, winuae now runs without recent DX redistributable installed as long as D3D filter(s) aren't used
- shaders moved to plugins\filtershaders\direct3d (perhaps opengl shaders will be implemented someday..)
- pixel shader filter on the fly change crashes fixed (I hope)
- adf was not updated if disk write DMA was aborted (Cadaver save)

[Marcuz]

oki...
last beta tested briefly, on the very same configuration up here in this thread (picasso mode with whdload games, so to test the display changes).

windowed mode seems to work fine, but:

1) filter modes do stretch the screen in different ways when fullscreen and when windowed; that's noticeable when you simply switch the display mode.

i've noticed it with the basic ones only so far > d3d, null filter; it may be even with OpenGL, but with less drastic stretching. only i could not confirm it because when on OpenGL fullscreen, the GUI would not appear when called.

this bring me to point 2: both direct 3D and openGL on fullscreen are very unstable, particularly when calling the GUI: either Winuae hangs or it keeps going on in background (you hear the audio goin') but the screen turns black.

i need to test it more and i will provide you more detail, this evening, but if you have some particular thing you would like i try, well now you know it

One more thing:

some filter seems not to work (i have not tested them all, but, for instance PAL, bilinear) and they get back to the last filter used. PAL works if i load the built in exemple, but the settings appear to be not significantly different from the ones i was using myself. then, if i try to chang the filter, winuae hangs. this happens both fullscreen and windowed.

[Toni Wilen]

Originally Posted by marco pedrana

this bring me to point 2: both direct 3D and openGL on fullscreen are very unstable, particularly when calling the GUI: either Winuae hangs or it keeps going on in background (you hear the audio goin') but the screen turns black.

There has been no changes to opengl filters so i am not sure if this is winuae problem or your pc problem

[Marcuz]

so...

1) i confirm the OpenGL misdemeanor: try a quickconfig A1200, select the openGL filter and turn fullscreen: if you call the GUI it doesn't appear or it is hidden.

2) in the same quickconfig, the D3D works;
if then i choose bilinear or PAL filter in windowed mode, it gets ignored and it reverts to D3D.
if i'm in fullscreen mode, Winuae crashes with this error:
CreateDevice failed 80004005 S=1 F=0000 C=4005 (16389) ()

do you need the logs (it's very easy to test on vanilla A1200) ?

edit: sorry , i read late your last message, i'll check that too (i reinstalled Vista, as consequence of the HD crash)

[Marcuz]

ok, you are right: tested with Winuae 1.5: OpenGL is my problem (damn! what could it be? any idea? the drivers i use are the same as the last installation, only Vista is 32BIT instead 64BIT version)

OpenGL: to bring - occasionally -the GUI in front, you have to switch to windows, do something else, then click on the winuae tab, and the gui will be in front when you gets back.

Pal and bilinear filters are broken in this beta though

[Toni Wilen]

Originally Posted by marco pedrana

ok, you are right: tested with Winuae 1.5: OpenGL is my problem (damn! what could it be? any idea? the drivers i use are the same as the last installation, only Vista is 32BIT instead 64BIT version)

Pal and bilinear filters are broken though

What is bilinear filter?

[Marcuz]

i don't know: it is in the list of filters in the new menu. i tested that because all the Sai, Scale, G, Lanzclos (whatever) seemed to work (i've tested almost all), and that was so solitary that i tested it first.

gotta say though, that for "seemed to work" i just mean that they do not revert to other filter and that they don't cause crashes. as for any particular difference between them... well i don't see any.

i'm sorry to notice that people ask for that features for years and then don't bother even to test them, not even at a glance (this is the second time in 2 months)

[Toni Wilen]

Originally Posted by marco pedrana

i don't know: it is in the list of filters in the new menu. i tested that because all the Sai (whatever) seemed to work

bilinear.fx you mean? then check the log as said in changelog

[Marcuz]

uhm do you mean this post:
http://eab.abime.net/showpost.php?p=...&postcount=172
?

i attach the 2 logs, i don't understand what it mean for practical use this bit:

- d9dx9_36.dll set to delay load, winuae now runs without recent DX redistributable installed as long as D3D filter(s) aren't used

however, as long as i don't use those filters, everything else is ok