DOSEMU for AmigaOne/AmigaOS 4.0

[bloodline]

Hammer wrote:
@bloodline

(Just recalling) In general terms, the SDL is dependant on host OS’s 2D acceleration support...(correct me IF I'm wrong, since I haven't touch SDL for a while).

Yes indeed, it basicly uses the best possible graphics system availiable on the Host OS.
I'm a very new convert to SDL, it was only when I decided to start a project I wanted to build on a few Windoze machines, but plan to run on a Linux machine, did I really see how good it was!!! :-o

[Hammer]

bloodline wrote:

Yes indeed, it basicly uses the best possible graphics system availiable on the Host OS.

SDL is quite useful for application programming . But, what about system programming?

Have you asked what was the requirements of Fatman’s VESA based project?

[fatman2021]

I’m working on a new video game. This video game will only use C/C++ for what its good at, i.e. small code, looping, etc. I’m going to write my own graphics library in both x86 and PowerPC Assembly. I don’t want to use anyone else’s c libraries because I do not like tying myself down to some else’s code and the bugs within their libraries. If I could get away with it, I would like to package my game with some type of free x86 emulator with FreeDos running over it or a Dos emulator with my game running over it. And one more thing, yes I know that x86 and PowerPC assembly are nothing alike.

[Mr_Capehill]

Sounds like a lot hassle to me. I wouldn't want to install some emulation environments onto my Amiga to run an Amiga game!

I understand that you want some speed, but I think you should write the game first and optimize then. And please, at least give SDL a chance before crushing it. ;-)

And if you want to write a game for the new Amiga, why wouldn't you do it in a system frienly way? We are still suffering because of lots of old software were written to bang hardware directly.

[Rogue]

VBE is MS-DOS only. You can't use it on anything else, since for starters it is written in x86 assembly. Secondly, it is entirely non-portable, since it depends on the int10 mechanism, and you can't even use it under Linux x86 or Windows.

[trgse]

too bad that Amiga-SDL as it is today won't work on Amiga OS 4.0

[bloodline]

trgse wrote:
too bad that Amiga-SDL as it is today won't work on Amiga OS 4.0

I'm not aware of anything that runs on AmigaOS4  :-D

Sorry couldn't resist,  Seriously though, it really wouldn't take long to port SDL from the current AmigaOS 3.1 to AmigaOS 4 (once AOS4 is actually available to the general public).

The AROS port didn't take long to get working... and that was done as a hobby!!! Though it still needs a bit of work.  :-P

[Rogue]

trgse wrote:
too bad that Amiga-SDL as it is today won't work on Amiga OS 4.0

SDL will run on OS 4.

[Rogue]

I'm not aware of anything that runs on AmigaOS4  :-D

Well, I am.

Sorry couldn't resist :-)

[jd997uk]

@Rogue

Well, I am.

OH, YEAH? What would you know?
I mean, you'd have to be involved in the writing of OS4 to know something like that.   ;-)  :-D  :-D  :-D

Sorry, couldn't resist!  :-P

-john

[bloodline]

Rogue wrote:

I'm not aware of anything that runs on AmigaOS4  :-D

Well, I am.

Sorry couldn't resist :-)

Hahhahhahaha!
Yes, sorry about that, I didn't mean that as a nasty jibe.

The main point of my post was that porting SDL to OS4 should be really easy from the current SDL Amiga port. (Providing OS4 has the same API as 3.1) :-)

[falemagn]

VBE is MS-DOS only.

While it's true that the BIOS extension is DOS-specific, the that's not the only way to access VESA functionalities. Moreover, once the screen is set up, you only have to access the framebuffer, and hat works regardless of whether you used the int interface or not.

[Rogue]

falemagn wrote:

While it's true that the BIOS extension is DOS-specific, the that's not the only way to access VESA functionalities.

How else would you do it except with the INT10? Sure you could call it directly, but I am not aware of any other API.

Moreover, once the screen is set up, you only have to access the framebuffer, and hat works regardless of whether you used the int interface or not.

Framebuffer access doesn't have anything to do with VESA, and is equally possible on, say, the Amiga, by locking the bitmap. However, when you have a color-mapped framebuffer then you might need to change the palette, and that is entirely un-portable, as is the rest of the VESA bios.

If you don't want to use SDL or similar, I propose going for a very slim abstraction layer, something that sets the display mode, sets a color palette entry, swaps front- and backbuffer. That's about it, unless you want to bring in user interaction (mouse/keyboard), in which case you'd better off using SDL again, since that isn't covered by VBE either  :-D

[Rogue]

jd997uk wrote:

OH, YEAH? What would you know?
I mean, you'd have to be involved in the writing of OS4 to know something like that.   ;-)  :-D  :-D  :-D
-john

Yeah, well, you got me ;-)

[Rogue]

bloodline wrote:

Hahhahhahaha!
Yes, sorry about that, I didn't mean that as a nasty jibe.

I didn't take it as such. Note the ";-)"

The main point of my post was that porting SDL to OS4 should be really easy from the current SDL Amiga port. (Providing OS4 has the same API as 3.1) :-)

Yes, you can compile an OS 3.1 program for OS 4, with a few possible things that needs to be fixed - mostly opening libraries if not done in the startup code, and a few things like interrupt handlers that have changed slightly (you wouldn't want to pass parameters to a PPC function in 68k registers, especially if the 68k is disabled  ;-) )

To the best of my knowledge, someone from the team is already working on porting SDL to OS4.

[bloodline]

Rogue wrote:

bloodline wrote:

Hahhahhahaha!
Yes, sorry about that, I didn't mean that as a nasty jibe.

I didn't take it as such. Note the ";-)"

The main point of my post was that porting SDL to OS4 should be really easy from the current SDL Amiga port. (Providing OS4 has the same API as 3.1) :-)

Yes, you can compile an OS 3.1 program for OS 4, with a few possible things that needs to be fixed - mostly opening libraries if not done in the startup code, and a few things like interrupt handlers that have changed slightly (you wouldn't want to pass parameters to a PPC function in 68k registers, especially if the 68k is disabled  ;-) )

To the best of my knowledge, someone from the team is already working on porting SDL to OS4.

Good, I'm glad you didn't take offence, I don't want any bad feeling between our respective groups  ;-)

I would be surpised if you were not porting SDL, it would make your lives much easier when porting games to other alternative platforms, like Mac, Linux and um... AROS  :-D