How do the non-i/o functions work?

mikro · 03 November 2011, 13:24

Hello,

I hope this is a right place to ask, I'm curious about one thing. I understand the concept of WHDLoad, how it replaces disk access, fixes cache stuff etc but I can't understand how the other functions work when the OS is disabled.

FAQ/doc mentions memory allocation or disk access or some synchro functions (which can be NOP-ed) but what about the rest? Timers, palette setting, sound playback? I believe Amiga programmers have been very disciplined when it comes to system programming (i.e. not accessing hardware directly but calling OS functions instead) so ... how does this work in WHDLoad when no OS is present?

Every slave makes its own palette setting routines and replace the calls in the original binary? If so, what does this routine do? I can't believe it accesses HW directly, esp. when it is supposed to work on variety of AmigaOS flavors...

Can someone explain? Thanks in advance!

S0ulA55a551n · 03 November 2011, 13:50

Nearly all games on the Amiga disable the OS and bang the hardware directly

StingRay · 03 November 2011, 14:21

Quote:

Originally Posted by mikro

Timers, palette setting, sound playback?

Almost all games have their own custom routines for these tasks.

Quote:

Originally Posted by mikro

how does this work in WHDLoad when no OS is present?

If the game uses only a few system routines you can emulate them, i.e. recode them without using the OS. If there are lots of OS routines used, WHDLoad has its own "KickEmu" routines which emulate the OS.

mikro · 03 November 2011, 14:33

Ah, that's interesting. In Atari world, that's normal thing but since I've seen source code of some recent Amiga demos, I thought it's common practice for games since the beginning. Thanks for explanation!

03 November 2011, 13:24	#1
mikro Registered User Join Date: Oct 2007 Location: Bratislava / Slovakia Posts: 34	How do the non-i/o functions work? Hello, I hope this is a right place to ask, I'm curious about one thing. I understand the concept of WHDLoad, how it replaces disk access, fixes cache stuff etc but I can't understand how the other functions work when the OS is disabled. FAQ/doc mentions memory allocation or disk access or some synchro functions (which can be NOP-ed) but what about the rest? Timers, palette setting, sound playback? I believe Amiga programmers have been very disciplined when it comes to system programming (i.e. not accessing hardware directly but calling OS functions instead) so ... how does this work in WHDLoad when no OS is present? Every slave makes its own palette setting routines and replace the calls in the original binary? If so, what does this routine do? I can't believe it accesses HW directly, esp. when it is supposed to work on variety of AmigaOS flavors... Can someone explain? Thanks in advance!

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Replacing OS4 functions for OS3.x	arti	Coders. C/C++	25	17 December 2018 16:03
Memwatch functions in Action Replay III don't work in WinUAE	Galahad/FLT	support.WinUAE	12	11 May 2014 13:42
functions benchmark	wawa	Coders. System	2	15 April 2013 18:55
Lost F key Functions on WINuae startup	breadbaker	support.WinUAE	8	06 December 2005 20:09
CD32 blue button functions differently	oldpx	support.WinUAE	6	09 August 2004 13:43

03 November 2011, 13:50	#2
S0ulA55a551n Registered User Join Date: Nov 2010 Location: South Wales Age: 47 Posts: 944	Nearly all games on the Amiga disable the OS and bang the hardware directly

03 November 2011, 14:33	#4
mikro Registered User Join Date: Oct 2007 Location: Bratislava / Slovakia Posts: 34	Ah, that's interesting. In Atari world, that's normal thing but since I've seen source code of some recent Amiga demos, I thought it's common practice for games since the beginning. Thanks for explanation!

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)