Latest working Winuae Version for XP 32bit (SSE1)?

[Toni Wilen]

Try 2.9/3.0 betas (urls in 2.9/3.0 beta thread) until you find the last working version. Perhaps it helps..

[Nova]

i checked this one on first page http://www.winuae.net/files/b/winuae_3010b1.zip without luck.

edit: ok, for your information, winuae_2820b4 is the last working version, after that the error occurs.

[Toni Wilen]

Compilation options have not changed between b4 and b5. Perhaps compiler update was installed or something.

[PeterK]

All WinUAE versions up to 3.0.0 are working here on my XP SP3 (P4 SSE3), latest betas not tested.

You could try to add an option to your boot.ini in case your PC has 2 GB or more RAM (some older WinUAE versions may need that:

/MAXMEM=2047

[Supamax]

Originally Posted by PeterK

You could try to add an option to your boot.ini in case your PC has 2 GB or more RAM (some older WinUAE versions may need that:

/MAXMEM=2047

All WinUAE versions run fine on my P4 HT 3 GHz, 3 GB RAM, PCI Express ATI Radeon HD 4670 1 GB RAM, Windows XP SP3.

So I really don't think that RAM > 2 GB is a problem.

[PeterK]

Ok, I don't even need this option myself nowadays, but many years ago I once had a problem with the 2 GB which was seen as a negative number. Sorry, I can't remember the configuration details anymore. That's why I said "you could try ..." and not "you have to ..." set that switch.

[Nova]

again, i am not an expert, tracking down the last working version is all i can do about it. i hoped it would be more of a help.

but i still believe it has something to do with a missing cpu feature or kind of a targeting problem. but as toni already pointed out, only sse1 is needed, so this can be excluded for sure i think.

[PeterK]

You could also try some tools to find missing resources like DLLs (or .Net framework v??):
http://www.showdep.com/index.old.html
http://www.dependencywalker.com

[Toni Wilen]

Missing DLL would show different error.

Does Event Viewer show any more details about the error?

[MetalliC]

there was known issue - original MSVC2010 can generate SSE2 opcodes with /arch:SSE, afair this was fixed in SP1, possible later VS releases have similar bugs too... almost no one cares today about non SSE2 CPUs.

[Nova]

Originally Posted by Toni Wilen

Does Event Viewer show any more details about the error?

no, unfortunately not.

anybody else with an athlon xp sse1 to test, if winuae_2820b4 is the last working version as a confirmation? because my machine is running fine without further problems.

[MetalliC]

ok, get to my old PC, here is where it crashes:

winuae_3010b1


winuae_3100b22


MOVLPD is SSE2 opcode, so it must be compiler issue.
I guess it can be avoided by disabling SSE usage at all on Code Generation page.

[Toni Wilen]

Can you see if it crashes in startup code or in some other dll? (I can upload matching pdb file if needed)

[MetalliC]

shown code is in exe



as I've said before - you can try to C++ - Code Generation - Enhanced Instruction Set - Not Set
at least this way it doesnt generated SSE1/2 anymore in the past versions of MSVC

[mark_k]

To help reproduce the problem it might be worth setting up an XP VM using Bochs. Being a full software emulator, as opposed to a virtualisation package like VMware or VirtualBox, you can set the emulated CPU to have any set of features, i.e. no SSE1/2/MMX/whatever.

[Nova]

@metallic: thanks for confirming & clearing things up, really appreciate helping me out

Originally Posted by MetalliC

almost no one cares today about non SSE2 CPUs.

out of couriosity i have tested more programs (reactivated this pc only recently) and there is quite some tools that do not work anymore (showing the same error). so for this reason you definitely have a point there unfortunately

i don't know so much about the technical backround, but i wonder why it can not be arranged like a switch: check processors features - then make use of what is avaiable at best (in this case only sse1).

by doing so, older cpus would not strictly be excluded.

[MetalliC]

Originally Posted by Nova

i don't know so much about the technical backround, but i wonder why it can not be arranged like a switch: check processors features - then make use of what is avaiable at best (in this case only sse1).

SSE and other SIMD extensions is all about speed, but if cpu features will be checked in runtime and then one of several code paths chosen - it kills speed, so...

out of topic: no-one cares about non SSE2-capable CPUs for a many years. I'm personally have some fights with ATI about 7 years ago - I have a BSOD using AthlonXP CPU and their's drivers, so I've found where and why exactly it happens, patched this error in drivers (very wrong CPU type detection) , described to ATI how it can/must be fixed - and nothing in result, well, because they dont care.
so I suppose owners of such old PCs have only choice to stick with old software versions. or upgrade.

[Toni Wilen]

I am not going to change any compilation settings until 3.1 is out (It is getting far too late). I may switch to SSE2 as minimum in following version because no one else has complained.

[Nova]

Originally Posted by Toni Wilen

I am not going to change any compilation settings until 3.1 is out (It is getting far too late). I may switch to SSE2 as minimum in following version because no one else has complained.

how many complains will change your mind then

is the gain of speed with sse2 as a minimum in winuae really that tremendous?

[Toni Wilen]

Originally Posted by Nova

how many complains will change your mind then

is the gain of speed with sse2 as a minimum in winuae really that tremendous?

Lets say that faster than 5% is better than supporting obsolete PC. In my opinion anything older than Intel Core (or matching AMD model) is totally obsolete today

We'll see what happens when future betas gets released..

(Assuming visual studio runs on your PC, you may be able to compile your own custom build, visual studio community version is free)