Thinking to change to the dark side (blue)

[Kronos]

@red

"PreOrdering" was never a problem, prepaying is  :-D

There is surely no problem to pre-order at most of Genesi's distributors, as long as they don't ask any upfront money.

PrePaying is something I never did, and never will do.

[Kronos]

@Jose

No, the Peg does have no USB2 onboard, only 1.1.

But it has FW, a actually working onboard-audio, and in the case of the
Peg2 it also has DDR-RAM (yes that makes a difference in real life)
and a 1GBit-ethernet.

Both A1 and Peg have AGP-slots hacked out of somesort of PCI-bus
(PCI-66,PCI-X, or whatever, I have lost count  :-o ). The only difference
is that the A1/Peg1 has this hack intregrated into the NB while the Peg2
uses some extra circuits for it.

Sure it may be AGPx1 vs. x2 on spec, but the Articia just isn't capable
of substaining a bandwidth high enough to even reach x1 over a longer
perios, negating all added performace it might get from x2. And even
most of todays PC-games won't run noticeably slower when you just reduce the AGP-factor. When do you expect to see such games in
Amiga-land ? 2010, sounds realistic ..... :-(  :-D  :-P

[Kronos]

@Van_M

How many OS4-only apps are there ? (or better will be)

AudioEvolution, some gameports from Hyperion, and ?

Don't see that someone from the MOS-team would waste lots of time for that.

[Kronos]

@Van_M

It doesn't matter how many apps there will be for OS4, but how many
that are ONLY available for OS4, and sofar the ones I listed are the
only ones announced that way (not counting small SW-tools and suchlike).

It is certainly better to invest that time in something looking forward.

[Kronos]

A few notes:

There are several problems preventing MP on AOS:

Lots of OS-structures that need to be directly written to (and lots of SW
that does it on sructures that do have a "save" API), and allmost all
structures are open for reading.

Message-ports, those are used for Intuition, Arexx and other purposes.
2 Tasks that interact via these can't be protected against each other.

Problem that allmost all apps interact wiith these with the kernel ....

BOOPSI  :-o  there is just no way for the DOS-loader to see where the app
ends, and where custom-classes defined in the same file start. And there
is no way to know if both parts may share global variables.

Lots of OS-functions to expect the app to pass a pointer to data, which
might not be copied to OS-memory.

None of these can be changed without having some sort of box (and remember
those are bad, real bad :-P ), and none of them could be just recompiled
to an new APi without some major changes in the app code.

Thats why R.S. decided from start that there had to be provisions for
a clean cut.