well I still see people having that same issues that I had. so those incompabilities is not solved yet.
If they really appear on the newest core release, then you should report those issues. And, if you want to make a good job while you are at it, try whether the same problem appears if you run the suspect code on WinUAE with 040-jit setting. This is because most reported incompatibility are just coding bugs where the software cannot deal with a CPU that is way faster than the programmer expected. The highest-ranking probability of such coding flaws is where coders start a blitjob without checking whether the preceding one has been finished already because they assume that whatever the CPU is doing in parallel will keep the CPU busy long enough for the preceding blitjob do end in time.
and I constantly hear that it is "MORE COMPATIBLE" when it doesn't behave like any 68k. so how can it be more compatible?
for me Compatible = Behaves like THAT product..
So either the Apollo-Team is stupid or lying. Hey, wait, there is a third option: you are applying a definition of the word "compatible" that obviously cannot be the same one as used by the Apollo-Team. Obviously it would be impossible to behave more like something than the very thing itself, right? So if you keep pondering this for a second it should become apparent that it means that it does not behave like an 060 because it does not bork when it sees e.g. a 64bit multiplication. It does better, it just executes the instruction.
Amnyway. you are right. 060 cards is getting insanly expensive.. and I am doing whatever I can to solve that. but the thing is. the vampirecards are soon approaching that very same pricetag...
How is 300EUR approaching anything? Yes, other versions with more capable hardware might cost more. Do you think this "trend" deducted from two distinct points will continue if alternative 080-based accelerators will hit the market?
Anyway my point is still: IF they want people to use their core. DO listen to more people.
There is no Vampire that has not been sold. And, frankly put, the input to be expected is none that we couldn't come up with ourselves: make it compatible. Sure, but this takes work and work takes time. It is as simple as that. In the a1k thread Gunnar pointed out that he can do the compatible MMU now but this would mean changing priorities. If somebody believes that more money can be made with an accelerator that has a compatible MMU, this somebody would have to fund the development. Right now the AGA reimplementation seems to be much more important because there are many times as many people wanting a stand-alone Amiga or an AGA upgrade for their OCS/ECS hardware than people that cannot do without the legacy-compatible MMU.
I am very often to demoparties etc. I talk to coders etc and I still have to fine ONE democoder remotly interested in doing something. as it breaks the bonderys of why they even care about the amiga.
Why would anyone want to cater a market with a new CPU that doesn't want to have any restrictions removed? I understand that some people find it interesting to code for an unexpanded A500. At the upper end of this pretty much the same people find it interesting to code for an A1200 with an 060/50. Well, so be it. Even availability of 75 MHz 060 didn't change the latter. This clearly isn't the market for a new CPU.
