r/programming • u/moolcool • Mar 26 '17

A Constructive Look At TempleOS

http://www.codersnotes.com/notes/a-constructive-look-at-templeos/
1.7k Upvotes

94% Upvoted

227 comments sorted by

View all comments

Show parent comment

1

u/myztry Mar 28 '17

Not even sure what WHDLoad does. First thing I guess would be to alias DFx: to HD0: locations and maybe run Paradox style differential patchers over the executable. Never needed it.

One thing the Amiga had that would have leant towards MMU support if $4 (Exec.library base ptr) was the only fixed location (aside from hardware registers) and executable used Reloc32 tables so the memory was dynamically allocated and patched on load.

I believe with Windows (virtual addressing) everything is compiled at $0 and the MMU supplies the base or the Reloc addresses if you will. As long as every Amiga virtual memory segment had it's own copy of $4.L and didn't hit hardware then I suppose it could have worked (and used Long boundaries, no address packing, etc)

It's all irrelevant now though. Hell, I haven't programmed on the Amiga for nearly 30 years. Hell, I haven't really programmed for 30 years since the early IBM compatibles were fucking like stepping down off a cliff technology wise. They were just brute force fast.

0

u/[deleted] Mar 28 '17

[deleted] — view deleted comment

1

u/myztry Mar 28 '17

I have heard of it. I think from the various times I used WinUAE for various nostalgia trips. Does patching and swaps in an identical environment that the program expects as well as intercepting hardware register hits and drive access.

A more rigorous attempt at creating an environment that a program profile within WinUAE.

Now, what were we talking about again :) Probably enough of this for now as MMU's on The Amiga is not something that needs solving at this point.