Welcome, Guest. Please login or register.

Author Topic: fxSCAN 4.02 with native x86-support (Amithlon)  (Read 2904 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: fxSCAN 4.02 with native x86-support (Amithlon)
« on: July 22, 2002, 09:36:20 PM »
Seems the old 100%-PPC-fanatic-statement
"noone will ever write SW for AOS-x86"
has been proven wrong  :-D

And now we only need Amithlon_2.0 with USB(scanner)-support  :-(
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: fxSCAN 4.02 with native x86-support (Amithlon)
« Reply #1 on: July 22, 2002, 10:18:54 PM »
Quote
Who said that?


A lot of people at amiga-news.de and on ann.lu.




Put up or shut up  :-P
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: fxSCAN 4.02 with native x86-support (Amithlon)
« Reply #2 on: July 22, 2002, 10:54:31 PM »
Quote
Mind you, there are people on ANN still complaining that the Amithlon support stifles PPC and AmigaOS4 development, and that it should be abandoned in favour of the latter.


Sounds just like the people who declared Amithlon useless because
Pegasos/OS4/A1/MOS would be out in just a few weeks .....

BtW: That was in September   ;-)
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