Copper Merge on 68k?

Samurai_Crow · 371

Samurai_Crow

  • Newbie
  • *
    • Posts: 48
    • Karma: +0/-0
  • Hobby coder
on: October 27, 2018, 07:26:48 PM
If I were to try to replace MrgCop() with a compatibility breaking implementation at another slot in Graphics.library so that a backward compatibility kludge could be left in its place like OldOpenLibrary() did in Kickstart 1.2, what offset should I use to avoid breaking compatibility with OS 3.x codes?  Should I start yet another library with limited utility outside the 68k Amiga models?  Is there another way like a .resource or .device that would be more appropriate?



wawa

  • Senior Member
  • ****
    • Posts: 252
    • Karma: +1/-0
Reply #1 on: October 31, 2018, 09:41:16 PM
id think asl toni directly. i doubt he is or wants to be a member here or whatever new forum, for that matter.



Samurai_Crow

  • Newbie
  • *
    • Posts: 48
    • Karma: +0/-0
  • Hobby coder
Reply #2 on: November 01, 2018, 07:55:11 PM
@Wawa
When Toni was still working on the Kickstart replacement bounty, I did ask him.  He said that he wasn't interested in a revival of the Amiga platform but just a legal way to use his emulator without paying for a ROM image.

The more I think about it, a modular set of libraries to replace Graphics.library might be a better approach and Copper.library might not be such a bad idea if it were made backward compatible to AmigaOS 3.



wawa

  • Senior Member
  • ****
    • Posts: 252
    • Karma: +1/-0
Reply #3 on: November 01, 2018, 11:05:40 PM
Quote
He said that he wasn't interested in a revival of the Amiga platform but just a legal way to use his emulator without paying for a ROM image.
toni has his own motivations, and certainly this stance is reasonable. i guess i would read it like, "go ahead and try, i dont care". but i dont know if your idea is right or wrong. you would have to discuss it with others.