Welcome, Guest. Please login or register.

Author Topic: P96 and CyberGraphX Emulation  (Read 2471 times)

Description:

0 Members and 2 Guests are viewing this topic.

Offline my_pc_is_amigaTopic starter

P96 and CyberGraphX Emulation
« on: October 31, 2019, 06:32:13 AM »
This is probably a very basic question but for the CyberGraphX emulation in P96, does it allow CyberGraphX only-aware software to run?    I think there is some software that says only CyberGraphX support and not sure if possible to run on P96 system.
 

Offline SamuraiCrow

  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 2281
  • Country: us
  • Gender: Male
    • Show only replies by SamuraiCrow
Re: P96 and CyberGraphX Emulation
« Reply #1 on: October 31, 2019, 07:11:58 AM »
P96 is CGX 3 compatible.  It is not CGX 4 compatible.
 

Offline slaapliedje

  • Lifetime Member
  • Hero Member
  • *****
  • Join Date: Oct 2010
  • Posts: 843
  • Country: 00
  • Thanked: 1 times
    • Show only replies by slaapliedje
Re: P96 and CyberGraphX Emulation
« Reply #2 on: November 01, 2019, 05:05:44 AM »
Any reason this couldn't be added, now that there is the new owner of P96?
A4000D: Mediator 4000Di; Voodoo 3, ZorRAM 128MB, 10/100mb Ethernet, Spider 2. Cyberstorm PPC 060/50 604e/420.
 

Offline SamuraiCrow

  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 2281
  • Country: us
  • Gender: Male
    • Show only replies by SamuraiCrow
Re: P96 and CyberGraphX Emulation
« Reply #3 on: November 01, 2019, 08:01:59 AM »
Any reason this couldn't be added, now that there is the new owner of P96?
The reason is that capabilities have been added by both parties already in a mutually incompatible way.  The jump table entries of anything beyond CGX3 correspond to different functions.
 

guest11527

  • Guest
Re: P96 and CyberGraphX Emulation
« Reply #4 on: November 01, 2019, 09:07:52 AM »
The reason is that capabilities have been added by both parties already in a mutually incompatible way.  The jump table entries of anything beyond CGX3 correspond to different functions.
The cybergraphics.library created by P96 is a "fake" library - it does not contain P96 specific API calls. The P96 public callable interface is in the Picasso96API.library. Both libraries jump into the rtg.library, which is the actual implementation. Thus, there is an additional layer of indirection between the implementation and the corresponding call-ins.

This said, what exactly is missing?