Welcome, Guest. Please login or register.

Author Topic: App for OS4  (Read 8914 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Kronos

  • Resident blue troll
  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 4017
    • Show all replies
    • http://www.SteamDraw.de
Re: App for OS4
« on: April 15, 2003, 08:20:54 PM »
Häääääääh ???

Whats so special about a port of UAE ?

You just take the AOS-68k,WOS, or MOS-version (MOS should be
that best start) and force it through gcc.

Thats it !

O.k. maybe you were thinking about a JIT-version, but be advised:
Better forget that ....
1. Make an announcment.
2. Wait a while.
3. Check if it can actually be done.
4. Wait for someone else to do it.
5. Start working on it while giving out hillarious progress-reports.
6. Deny that you have ever announced it
7. Blame someone else
 

Offline Kronos

  • Resident blue troll
  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 4017
    • Show all replies
    • http://www.SteamDraw.de
Re: App for OS4
« Reply #1 on: April 15, 2003, 08:41:10 PM »
@alx
Now that sound like a really stupid idea .....


How much SW is outthere that requires OCS/AGA AND the power
of a CPU faster than UAE could provide ? And how many of those
would actually run on such a setup ?

And do you have even the slightest idea how much work it would
be to adapt UAE this way ?

Gigantic waste of resources for virtually no benefit, probraly
even worse something slowing the OS down and making it less
stable .......
1. Make an announcment.
2. Wait a while.
3. Check if it can actually be done.
4. Wait for someone else to do it.
5. Start working on it while giving out hillarious progress-reports.
6. Deny that you have ever announced it
7. Blame someone else
 

Offline Kronos

  • Resident blue troll
  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 4017
    • Show all replies
    • http://www.SteamDraw.de
Re: App for OS4
« Reply #2 on: April 15, 2003, 08:56:09 PM »
/me wonders how often he has to hear the word "sandboxed"
completly out of context .......

A 68k programm is an 68k programm and therefore it has now
idea on what kind (or if on any at all) of emulation it runs.

The only think that "not sandboexed" means is that both
protected and non-protected apps run on the same kernel in the
same mem-space nothing more. Also means that it is allways
possible for an unprotected app to damage the kernel.

Preventing that is the MAIN reason for using a sandox.


edit:

But to stop it here:
Better write replacements for the SW that won't run without
the chipset than trying to run it by force.
1. Make an announcment.
2. Wait a while.
3. Check if it can actually be done.
4. Wait for someone else to do it.
5. Start working on it while giving out hillarious progress-reports.
6. Deny that you have ever announced it
7. Blame someone else
 

Offline Kronos

  • Resident blue troll
  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 4017
    • Show all replies
    • http://www.SteamDraw.de
Re: App for OS4
« Reply #3 on: April 16, 2003, 06:27:20 AM »
/me is pissing on whom ??????


Just because I suggest looking forward (and writing new SW) instead
of backwards (and writing an AA-emu) makes me pissing on someone ?


Or is it because I corrected some urban myths about the benefits of
a "non-sandboxed" emu/OS ????


Oh well I can live with that .....

Back to the topic:
@tafka
What you should do really depends on the amount of time you are
able to invest. If you got really lots of it you should go for the big
"killer-app" like an audio or GFX programm.

If your time is limited you should look on free SW for a starting
point. For example, the Amiga-port of XFig called AmiFig has been
dicontinued some times ago and is available for free. Maybe you could
get the sources from the author. Or look at the masses of X11/KDE/GTK-SW
and choose one of those.

If you only got very little time and want fast results, port little
cli-tools and similar from Linux, write commodity-style-SW or
drivers for "odd" HW.

Lots of tasks outthere that don't require to beat a dead horse (OCS/AGA).



1. Make an announcment.
2. Wait a while.
3. Check if it can actually be done.
4. Wait for someone else to do it.
5. Start working on it while giving out hillarious progress-reports.
6. Deny that you have ever announced it
7. Blame someone else
 

Offline Kronos

  • Resident blue troll
  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 4017
    • Show all replies
    • http://www.SteamDraw.de
Re: App for OS4
« Reply #4 on: April 16, 2003, 12:07:41 PM »
@JoNty

And now guess where Zool would run better :

a) UAE-setup with "match A500-speed" (or was it an AGA-game ?).

b) Under ExecSG (did it allow multitasing ?) on Petunia ( = >060)
with a hacked_in_place chipset-emu.

My bets are 100:1 on a  :-D

Said the guy who can't wait for support of the Carweazle_3
Joystick-ports in UAE so he can finally play Lotus_I/II,
R-Type,Turrican, Wings of Death .......  ;-)
1. Make an announcment.
2. Wait a while.
3. Check if it can actually be done.
4. Wait for someone else to do it.
5. Start working on it while giving out hillarious progress-reports.
6. Deny that you have ever announced it
7. Blame someone else
 

Offline Kronos

  • Resident blue troll
  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 4017
    • Show all replies
    • http://www.SteamDraw.de
Re: App for OS4
« Reply #5 on: April 17, 2003, 03:17:53 PM »
Quote

JoNty wrote:

Likewise, in a window.


Why o why in a window ??
A 640x512 window would just fit 1/4 of my 18"LCD ......
Way to small  :-(

A seperate screen at say 800x600 (to allow overscan and so)
sounds perfect for me  :-D
1. Make an announcment.
2. Wait a while.
3. Check if it can actually be done.
4. Wait for someone else to do it.
5. Start working on it while giving out hillarious progress-reports.
6. Deny that you have ever announced it
7. Blame someone else