Tfx Aga?

[apex]

Originally Posted by jotd

No need to discuss the pros and cons of whdload to people who aren't interested. Lesson learned.
So only answering to tell you "you're welcome".

Damian use WinUAE, I am using real hardware and I see only advantages using WHDLoad. Please just ignore this discussion and go on with the WHDload version. Thank you very much.

[DamienD]

Originally Posted by apex

Damian use WinUAE, I am using real hardware and I see only advantages using WHDLoad.

Whether someone uses real hardware or emulates makes no difference...

The 3 x game EXEs work on either.

[apex]

It make sense, because I cannot cut down my OS easily. To run normal HD games, I have to use my A1200/030. To run the big games I have to use my A1200/60, removing patches and other stuff or I use WHDLoad, then I have no problems.
From the perspective using real hardware, WHDLoad makes absolutely sense. ;-)

[Angus]

I appreciate it must be jolly good fun, running round implying people are thick, and talking about rocket science.



This is what you were saying in April. You were wrong then too.

Originally Posted by DamienD

Have you even ever installed the native version of TFX?

It runs fine on:

(a) TFX_020 BETA exec (requires FPU)
(b) TFX_030 BETA exec (requires FPU)
(c) TFX_040 BETA exec (requires 68040/060 CPU)

[jotd]

indeed those beta ersions are broken beyond repair except for the 020 if you hack the exe so data hunk is in chipmem.

no answer from Charlie either... sad

[DaveTaylor]

The 020 beta exe is from the end of 1997. It's the latest touch of the original coder. All other working exes are from early 1995.
Good that you made it running, JOTD.

See screenshot here.

http://eab.abime.net/showpost.php?p=362737&postcount=43

By the way, the whole thread is old, but interesting.

[jotd]

020 beta is 571008 bytes, it's the latest version we have, and is also using 68881 FPU routines.

Which means that if I can fix FPU instructions so they use 68040/060 FPU emulation this could be the fastest version around on real machines.

Today this latest executable only runs on 68020/030+FPU and not on 68040/68060. No 68040 version has been made. The so called 040 beta version (599152 bytes) doesn't use the FPU at all. Maybe it uses 68040 instructions, but I'm not sure. Besides it's from 1995 as well. Not really useful except for me because the executable has symbols.

On WinUAE it runs on 68040/060 because by default unimplemented FPU instructions are transparently emulated (but you have to force the FPU attnflags bit, this can be done using 68040.library/oxypatcher whatever or removing the check, but winuae does the job, not oxypatcher (oxypatcher does a terrible job on that game: it just makes computations fail)

[Angus]

Does Cyberpatcher perform any better, Jean-Francois?

By the way, if I remember correctly at one point Charlie had access to somebody's 040, but later on he was doing his best to make the 040 code work without having one to test it on. I don't think he ever had access to an 060.

[jotd]

Didn't test cyberpatcher TBH, and I don't think I will. Even if it works I don't think I can use the result anyway.

I have math source code I can plug into the FPU version, will do that.

[dlfrsilver]

Originally Posted by jotd

indeed those beta ersions are broken beyond repair except for the 020 if you hack the exe so data hunk is in chipmem.

no answer from Charlie either... sad

there : https://www.linkedin.com/in/charlie-wallace-281143/

[jotd]

contacting people you don't know on linked in requires pro account. Asking the man to be part of his network just to ask something is bound to fail. I've already tried that with Sean Griffiths and got no answer.

[jotd]

holy crap! I adapted the motorola FPSP code, compiled it, ran it in background, and ran the FPU program on a 68040 setup, no unimplemented instructions emulated.

And it bloody WORKED!

So now here comes the easy part. I need your inputs. 68040 and 68060 users on real machines.

What I'd like to do is a blind test so people aren't influenced by the setup

So, basically, I'm going to create an amiga shell that runs TFX with various configurations. Your task shall you accept it will be to test those configs with the same level of detail and tell me which one is the best (without looking inside the script so you don't know which setup it is).

I'm going to provide the set of executables and the "fpsp" emulation code + slave so you can just upgrade and test easily.

Note: Winuae users can help if they want, but they'll have to untick the "unimplemented FPU instruction" box, else that will be cheating since WinUAE does the job.

[Angus]

Wow, sounds cool, Jean-Francois. Nice work! :-)

[jotd]

Tested on 68060 doesn't seem to work yet, but I think it may work on properly configured systems.

[pipper]

What is FPSP and how does it work?

[alexh]

Originally Posted by pipper

What is FPSP and how does it work?

https://android.googlesource.com/ker...sp060/fpsp.doc

[Angus]

Originally Posted by alexh

https://android.googlesource.com/ker...sp060/fpsp.doc

Yeah.................... but what IS it?!


Floating Point Simulation Program?

[jotd]

something like that yes.

FLOATING-POINT SOFTWARE PACKAGE

software-emulate the unimplemented exceptions, but use the implemented exceptions. Won't work on a 68040 or 060 without FPU at all.

[tolkien]

Dont know what happends in my a1260. The normal EXE works but whdload version fails to starts with a black screen and I have to reboot.

I'll go trying future versions but I think this is a good job anyway.

[jotd]

are you using the "auto" config in whdload? Strange. works on 060 with the nofpu exe ("TFX") on my setup, fails on FPU (for the moment hehe)