Dear Atari Community!


We are happy to announce a new public release of EmuTOS:

EmuTOS 0.9.3 -- February 26, 2014



INTRODUCTION

EmuTOS is a single-user single-tasking operating system for the 32-bit Atari
computers, clones and emulators. It can be used as a replacement for the TOS
images typically needed today for using emulators and can also run on some
real hardware, like the Atari STe, Falcon and the FireBee. It can even run
on non-Atari hardware such as Amiga and ColdFire Evaluation Boards.
All the source code is open and free, licensed under the GNU General Public
License (GPL).



SPECIAL NOTES FOR RELEASE 0.9.3

This release is almost identical to the 0.9.2 one.
Only emutos-aranym has been updated to fix a regression with IDE disk images.

CHANGES SINCE RELEASE 0.9.1

Major changes:
- Added most Line-A functions.
- Added support for poweroff on the FireBee.
- Added support for SD/MMC Cards on FireBee, including hot swap.
- Improved IDE and CompactFlash support.
- Added support for the FireBee external 2"1/2 IDE connector.
- Improved ACSI support (including SCSI via converter).
- Fixed compatibility with fVDI (including aranym.sys).

Other changes:
- Fixed intermittent problems booting emutos-ram.
- Improved determination of disk capacity & blocksize.
- Improved detection of FAT12 / FAT16 / FAT32 partitions.
- Improved media change detection.
- Improved XHDI support.
- Handle all valid DOS FAT end-of-chain markers.
- Speed up a few VDI functions.
- Fixed AES PATH environment variable and shel_find().
- Fixed AES shel_find()/rsrc_load() search order, like TOS3/TOS4.
- Fixed AES sh_ldapp() application directory.
- Fixed AES appl_trecord() & appl_tplay().

Have a look at changelog.txt for more detailed information.



DESCRIPTION

EmuTOS is basically made up of the following:

- The BIOS, which is the basic input output system
- The XBIOS, which provides the interface to the hardware
- The BDOS, which are the high level OS routines, often known as GEMDOS
- The VDI, the virtual device interface, i.e. the screen driver
- The AES, the application environment services or window manager
- The desktop, which is the graphical shell to the user
- EmuCON2, the command-line interpreter

The BIOS and XBIOS code is our own development. It is written from
scratch and implements all relevant TOS 1.0 Bios & XBIOS functionality,
and a bit more, e.g. hard disk access. See doc/status.txt for details.

The GEMDOS part is based on Digital Research's GEMDOS sources, which were
made available under GPL license in 1999 by Caldera.

The graphical parts like VDI and AES are now more or less fully
implemented up to TOS v1.04 level. They work in all the graphics modes
of the original Atari ST, with some extensions. For example, systems with
VIDEL support 256 colours and 640x480 screen resolution. Some emulators
can patch EmuTOS to work with much bigger screen resolutions.

The desktop is somewhat better than the original one, but not as nice as
the one in TOS 2 or higher. It is still quite usable, and of course you are
always free to use a more advanced desktop replacement like TeraDesk.

EmuCON2 is a basic but useful command-line interpreter, written from scratch
by Roger Burrows in 2013.

Since EmuTOS just implements TOS functionality, you might want to use
MiNT on top of it in order to run more modern software. EmuTOS is not
an alternative to MiNT, but it's the only free base OS to boot MiNT.



EMULATION AND FUTURE PLATFORM

EmuTOS and MiNT cooperate well. Both can utilize Native Features
(NatFeats) interface for emulators:
    http://wiki.aranym.org/natfeats/proposal

EmuTOS uses this new standard interface for all the relevant native
functions supported by an emulator on which it's running. This interface
proxies the calls to the underlying host OS so that these features don't
need to be emulated. This is both faster and can provide features that
would be infeasible on a real machine. It may allow using modern graphics
cards, provide fast native filesystem access and enable you to use
networking with all bells and whistles - and many other things you might
not have even dreamed of.

The ARAnyM emulator has the most extensive support for NatFeats.
The Hatari emulator supports the basic NatFeats facilities.



HARDWARE

Making EmuTOS run natively on a new hardware platform is more or less just
a question of driver support for EmuTOS. The same for MiNT, if you'd like
to have it running on top of EmuTOS.

This is the currently supported Atari hardware:

- CPU support for m68000, m68010, m68020, m68030, m68040, m68060, ColdFire V4e
- FPU detected
- 68030 MMU and cache
- Memory controller (both ST and Falcon)
- Monitor type detection (mono, RGB or VGA)
- DMA controller
- WD 1772 / AJAX Floppy disk controller (write track not tested)
- MFP
- PSG
- ST shifter
- STe shifter
- VIDEL
- ACIAs, IKBD protocol, mouse
- MegaST Real-Time Clock (set clock not tested)
- NVRAM (including RTC)
- Blitter (Blitmode() just returns HW status)
- Microwire
- SCC
- IDE
- ACSI
- The Native Features interface to some degree

Currently unsupported hardware features:
- DSP
- MFP #2
- TT 256-colour palette

EmuTOS is also available on some non-Atari hardware:
- Amiga (WinUAE, Amiga 1000, Amiga 1200 with Blizzard 1260)
- ColdFire Evaluation Boards (M5484LITE, M5485EVB)



AVAILABILITY

The EmuTOS home page is:

    http://emutos.sourceforge.net/

The project home is on SourceForge:

    http://sourceforge.net/projects/emutos/

The latest releases can be downloaded from:

    http://sourceforge.net/projects/emutos/files/emutos/

Development snapshots allow you to test the current development progress:

    http://sourceforge.net/projects/emutos/files/snapshots/

The latest sources are always available from our CVS server at:

    http://sourceforge.net/p/emutos/code/

If you are just curious or would like to help us develop this nice little
OS, you are invited to subscribe to our mailing list for developers at:

    https://lists.sourceforge.net/lists/listinfo/emutos-devel


We hope that you like EmuTOS. If you have any suggestions or comments, we
always appreciate to hear the good and also the bad things about it.


The EmuTOS development team.

-- 
Originally written by Martin Doering
http://emutos.sourceforge.net/
