Back to Blog
Amigaos 4.0 Install Cd For Mac5/10/2021
In my opinion all serious single platform emulator coders do it because it is a great coding challenge to do something that was supposedly difficult or even impossible and make it as good as possible.Another text interview and another great guest Im very proud to have Toni Wilen as my guest The guy that makes for us WinUAE, even with PowerPC emulation.I dont remember which was my first contact with computers but my first computer was Spectravideo SVI 328 MK2 (I think it was 1985 when I got it, when I was 10 or 11 years old).
Next was Commodore C64 few years later and then second hand A1000 ( 1988 I guess). Only much later ( 2005 or so) I started buying other models for emulation compatibility comparison purposes. Today I practically only use my Amigas for compatibility testing. I learned 6510 assembly with C64 and 68k assembly and C (slightly later) after I got my first Amiga. Dice-C was small enough to work nicely with A1000 internal RAM expansion and 2 floppy drives. Your portfolio has such amazing and know programs like FileMaster and SysInfo. Amigaos 4.0 Cd Software For OurWhat was the inspiration for you to creat so good software for our computer. I dont know. I just did something I wanted to do and it needed to be something I want and can use without getting annoyed. I also rarely check or test competing programs because it would mean too easy way to add features that I would never use or need and they would only slowly rot away after being implemented. Did you expect it Did it influence somehow on your future work Now you are involved in WinUAE, how did you start this project. I dont remember how FileMaster started, it is has been far too long ago but I do remember how my UAE work started. It was time when it was common knowledge that AGA cant be emulated. Believe it or not Amiga community was and still is weird.). I learned how UAE worked and extended it with (basic) AGA support. When I started working with UAE, most of basic documented features were already implemented by Bernd Schmidt. Of course it was far from accurate A500 emulation (I dont think it was even the goal of UAE originally, just to get it working) but most system friendly software worked fine. Most common debugging method for me is to simply run programs (usually scene demos) that work incorrectly and debug what they do and then try to find out why does it work differently on real hardware. Usually it also means writing short test programs to minimize unknown variables. Also really big help was logic analyzer I bought long time ago, it allowed me to see exact DMA cycle sequences and all odd undocumented corner cases. Only documentation that would explain still unknown undocumented features would be Agnus schematics. Biggest unknown part is blitter internals, odd things happen when blitter channel enable bits are modified when blitter is active. Some demos accidentally forgot to wait for the blitter but work correctly only because blitter did something unexpected. For example blitter cycle sequence can change to something that never exists in normal operation). Internal cycle usage diagrams are not documented. No, official 68020030 documentation cycle-usage listings are useless for accurate emulation).
0 Comments
Read More
Leave a Reply. |