Re: GEOS file format, assembly, etc.

Tony Dean <tdean@lookout.mtt.it.uswc.uswest.com>

Mail folder: 1Q1994 Zoomer-List Archives
Next message: John D. Mitchell: "GEOS file format, assembly, etc."
Previous message: John D. Mitchell: "GEOS file format, assembly, etc."
In-reply-to: John D. Mitchell: "GEOS file format, assembly, etc."
Reply: John D. Mitchell: "GEOS file format, assembly, etc."

Errors-To: brian@grot.starconn.com
Date: Tue, 1 Feb 94 08:20 PST
Message-id: <199402011537.AA03349@lookout.ecte.uswc.uswest.com>
X-Comment: Zoomer PDA List
Originator: zoomer-list@grot.starconn.com
Errors-To: brian@grot.starconn.com
Reply-To: <zoomer-list@grot.starconn.com>
Sender: zoomer-list@grot.starconn.com
X-Listserv-Version: 5.5 -- Copyright (c) 1991/92, Anastasios Kotsikonas
From: Tony Dean <tdean@lookout.mtt.it.uswc.uswest.com>
To: Multiple recipients of list <zoomer-list@grot.starconn.com>
Subject: Re:  GEOS file format, assembly, etc.
Status: OR

> Everything you need to develop libraries and applications is in the current
> GEOS SDK BETA.  Geoworks has promised the documentation and what not for
> assembly language development at or prior to the v1.0 release of the SDK.

While it is certainly true that you can develop applications and
application level libraries, I found little support for systems
level development in the SDK. An example might be writing drivers and
a support library for an entirely new product or an unusual network
product. 

It appears to me that any systems level work must either be
provided by geoworks or in a DOS driver that GEOS can already
understand.

td