search

khval / NallePuh

Paula audio and CIAA/CIAB emulation for AmigaOS
GNU General Public License v2.0
4 stars 0 forks source link

Support for misc.resource #38

Open samo790 opened 10 months ago

samo790 commented 10 months ago

Some old 68k programs/games require misc.resource For example the RTG version in development of AlienBreed3D 2 TKG I wonder if it's possible to try to support it in the future

Hypexed commented 10 months ago

So this is like the CIA resource. The misc resource arbitrates access to serial and parallel hardware. So programs can bang the hardware in a friendly way. I wonder what an RTG game and therefore assumed OS friendly game wants to bang serial or parallel ports for? Simple enough without emulating the hardware in question.

samo790 commented 10 months ago

Well the original game wasn't RTG.. I guess the use of the misc.resource was a reminiscent of the original code... I guess soon or later they will get rid of this, but until they will not, maybe would be cool to try supporting it.. just i dont know if it could be possible via NallePUH or if its scope was that :-)

khval commented 10 months ago

Because I only know of one game that needs it, and that game is now open source, I don’t see a major need for it. But if you can produce a list of games or programs where misc.resource is required to work, I might consider it. AlienBreed3D 2 TKG has a menu that won’t work with NallePuh anyway, and it needs to be replaced. Maybe it can be salvaged, but probably not worth the effort to make it look exactly the same. Right now, it’s not a priority.

tor. 16. nov. 2023 kl. 12:48 skrev samo79 @.***>:

Well the original game wasn't RTG.. I guess the use of the misc.resource was a reminiscent of the original code... I guess soon or later they will get rid of this, but until they will not, maybe would be cool to try supporting it.. just i dont know if it could be possible via NallePUH or if its scope was that :-)

khval commented 10 months ago

@Hypexed The device API kind of slow, and can be an issue where you are waiting for char in serial buffer and get stuck, skipping the device API, you have interrupt trigger when serial buffer is full, so you wont need to wait for incoming data.

the only thing I wonder about is how this negotiated with the OS. Does OS assume full access until the hardware is captured or is some how swapped out.