Welcome, Guest. Please login or register.

Author Topic: Amiga One on Tour  (Read 5715 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: Amiga One on Tour
« on: May 10, 2002, 09:40:56 PM »
"the Amiga One " and not "an Amiga One" ??

Minor mistake or will their be no dev-boards before ?

(Leaving Alans prototype as the only Amiga One)

Just curious  :-o
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: Amiga One on Tour
« Reply #1 on: May 10, 2002, 09:49:52 PM »
Quote
Nit-picker... :-P  


No just curious !

So will they show a "dev-board" or Alans prototype, that
(according to many rumours) is just a relabeled TeronCX
with slower CPU, older southbridge and doesn't have the
A1-features like ethernet or sound ?

An answer to that question should be interesting.
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: Amiga One on Tour
« Reply #2 on: May 10, 2002, 09:56:25 PM »
@zacman
And some people say I make "simple" jokes....

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: Amiga One on Tour
« Reply #3 on: May 10, 2002, 10:01:14 PM »
@seer
Did you really take zacmans post seriously ?
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: Amiga One on Tour
« Reply #4 on: May 10, 2002, 10:40:23 PM »
Quote
It will be the developers version


Thats nice  :-)

Quote
hopefully with OS4 beta...


Veeeeeery unlikely  :-x

According to Bens posts on ann.lu :

Petunia isn't running on ExecSG atm (and still misses a lot of opcodes)
Intuition hasn't been recompiled and intregrated.
There are still some chipset-dependancies

Even if we assume he just poured some sand in our eyes, some things
would still be needed to run it on the A1:
"boot-file" (like vmlinux)
IDE-driver (for the VIA-southbridge)
KBD-driver
PCI/AGP-driver

And remember under 3 weeks...
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: Amiga One on Tour
« Reply #5 on: May 11, 2002, 09:41:55 AM »
@68040
What you suggested may count as a alpha-version but (IMHO)
a beta should atleast be able to start some user-SW.

Just take a look at the AROS-boot-floppy (if you got a x86) and
you will see what I would call a minimal beta.
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