Two Amiga related software projects that i want to make.

[Piru]

@balrogsoft

UAE is C.

To be frank, you're facing an impossible task if you're going to figure out Amiga emulation all by yourself.

[Piru]

@balrogsoft

Yes, UAE is C and WinUAE is C++, but i must to code in C++ with Visual Studio and Symbian SDK.

I just won't believe that. Not being able to use C would be just insane and suicidal.

And i don't need to figure how Amiga emulation work, as i said, i have two Amiga hardware books, and a 68000 reference book.

I don't want to be rude, but is is just insane.

You will NEVER be able to write amiga emulation just with "two Amiga hardware books, and a 68000 reference book".

And i can use UAE code to find and solve specific problems

Even when using UAE for reference (unless if you end up copying UAE pretty much as-is, in which case your app is GPL) you're into several years of work at least.

but i don't want to port directly UAE, because as i said my C++ knowledge is limited, i used more Java and other languages.

But UAE is not C++, it's C. Even WinUAE is mostly C.

[Piru]

Denis (who made a FPGA implementation of an A500) said that he had three Amiga books that have 90% of information need to implement Custom chips, i think that is a high percent of information to start the project, but i will not able to do, why?

IMO that 90% is hugely overestimated (or misquoted). I'd say it's 10% or less of the information needed. The manuals explain how the hardware works, not how it's implemented. Even though you'd replicate every documented functionality 100%, it would still not work correctly. How everything relates to each other, what is undocumented or abused in various games, demos and apps, and figuring out how to get everything work right is the 90+%.

I post this topic to request information and help

The best you can get is UAE source.

the only one thing that i got are critics

And rightly so. Amiga emulation is just too much work to do from 0.

suicidal.

That comment was about Symbian, not you.

[Piru]

@balrogsoft
Amiga is a very complex system compared to many game consoles and other seemingly similar systems (say: Atari). The reason is the custom chips, and their complexity. The chips are interconnected with each other, and for example you can trigger various operations from within another (for example: copperlist can be used to control blitter, which in turn can generate new copperlist, etc).

Emulating all this in software is very hard, esp if you want the emulation to function properly even with the games, demos and apps that use the chipset's full potential (various tricks and hacks, undocumented and often unintended behaviour of the hardware, but found to be useful for generating various cool effects). Actual CPU emulation is trivial in comparision, you can write cpu emu in couple of days.

Proof of the complexity of the task is UAE: It took years and years to get it to even function relatively usable level, and still the emulation is improved and fixed in every release.

So, while I give full credit to Dennis for is great work on the Minimig project, I still have to wonder if the project would have ever existed without UAE/Fellow... My understanding is that these have been invaluable help for him. To quote Dennis:

A lot of the work I did was indeed some form of calculated guessing. Days of reading through the hardware reference manual and trying to find the out the logic behind things. Also, because Winuae and Winfellow already exist, I have the luxury of being able to look how they did it when I'm stuck. (which I did on some occasions)

Still, what Dennis has done is something I had very hard time believing at first. I was very sceptical.

So I guess I could be just plain wrong, maybe it's not that hard. Or maybe it is, and Dennis just kicks serious behind. I guess you should ask Dennis directly what he thinks about feasibility of your project and ignore me. :-)