On Thu, 13 Nov 1997, Magnus Kollberg wrote:
> Has anyone tried this? I tried some old automation compilations.... with
> various results. Isn't there a way to set STe compatibel "bus" or something
> as well? Maybe a small program to set it could make it work even better.
It's quite easy the control the bus-mode:
$FF8007|byte |Falcon Bus Control BIT 5 . . 2 . 0|R/W (F030)
| |STe Bus Emulation (0 - on) ---------------' | ||
| |Blitter (0 - 8mhz, 1 - 16mhz) ------------------' ||
| |68030 (0 - 8mhz, 1 - 16mhz) ------------------------'|
> > Dolmen doesn't exist, and will probably never see the light of day.
> > Buy MagiC, or even better N.AES :-) MiNT+N.AES is *the* TOS-compatible
> > OS on the Afterburner, it has everything MagiC has and much more.
>
> Hohohohohhh.... so what does MiNT have that MagiC doesn't? Don't dig up the
> old MiNT net argument as we have got STiNG for both which is esier and
> almost as good.
Hehe, I knew this would provoke Magnus ;-) Seriously, for my use MagiC
is virtually unusable: It doesn't have a decent filesystem, and while
it has a pretty good TCP/IP-stack (STinG) it doesn't have any usable
internet-clients at all. They're all very unstable and unreliable,
even the most basic MiNT-utilities like elm (e-mail) or plain ftp are
miles ahead in terms of speed, reliability and features.
And for STinG being easier than MiNTnet; I got MiNTnet up and running
in a few minutes, and I have used it without problems for almost two
years now. After over a week with experimentation STinG still doesn't
work under MagiC here (TCP-related)...
A serious argument for using N.AES and not MagiC is compatibility.
One thing is that MagiC has serious problems on some Falcons, but
apart from that MagiC does *not* comply to the AES 4.0/4.1 standard as
defined by Atari in MultiTOS and used in N.AES, Geneva and oAESis (if
it ever gets finished).
/*
** Jo Even Skarstein
http://www.stud.ntnu.no/~josk/
**
** beer - maria mckee - atari falcon - babylon 5
*/
Received on to. nov. 13 1997 - 12:55:16 CET