Path: utzoo!utgpu!attcan!uunet!portal!atari!apratt
From: apratt@atari.UUCP (Allan Pratt)
Newsgroups: comp.sys.atari.st
Subject: Re: mx2v230 (in comp.binaries/sources.atari.st)
Keywords: Atari ST Networks
Message-ID: <1293@atari.UUCP>
Date: 5 Jan 89 22:24:59 GMT
References: <5860@saturn.ucsc.edu> <1280@atari.UUCP> <471@bdt.UUCP> <116@infbsgr.infbs>
Reply-To: apratt@atari.UUCP (Allan Pratt)
Organization: Atari (US) Corporation, Sunnyvale, California
Lines: 24

In article <116@infbsgr.infbs> hafer@infbsgr.UUCP (Udo Hafermann) writes:
> The user's computer gains network access by loading a resident program
> which redirects TOS requests for network drives.  All TOS calls are
> supported; BIOS calls for network drives are not possible (and
> protection mechanisms therfore cannot be by- passed).  A few new TOS
> calls for internal network purposes have been added.  Network access can
> be dynamically de-installed. 

Your terminology confuses me.  In Atari parlance,

	AES + VDI + GEMDOS + BIOS + XBIOS = TOS

Therefore saying "All TOS calls are supported" but "BIOS calls are
not possible" doesn't make sense.

If you mean GEMDOS where you say TOS, it makes more sense, and it will
work.  The reason I said networks can't work is that GEMDOS will cache
sectors which might then change on the media, without GEMDOS knowing
that its cached sectors are out of date.  If you reimplement GEMDOS
it'll work fine.

============================================
Opinions expressed above do not necessarily	-- Allan Pratt, Atari Corp.
reflect those of Atari Corp. or anyone else.	  ...ames!atari!apratt