Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!seismo!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: net.micro,net.micro.att
Subject: Re: 5620 Emulator for AT&T PC 6300?
Message-ID: <2307@brl-smoke.ARPA>
Date: Wed, 2-Apr-86 10:20:29 EST
Article-I.D.: brl-smok.2307
Posted: Wed Apr  2 10:20:29 1986
Date-Received: Sat, 5-Apr-86 08:31:15 EST
References: <733@bonnie.UUCP> <2024@brl-smoke.ARPA> <747@houxu.UUCP>
Reply-To: gwyn@brl.ARPA
Organization: Ballistic Research Lab (BRL)
Lines: 24
Xref: watmath net.micro:14236 net.micro.att:1068

In article <747@houxu.UUCP> jhv@houxu.UUCP (James Van Ornum) writes:
>I think Doug Gwyn missed the point of the AT&T 5620 emulator request.

No.  I think you missed the point of my response.

>First, it would be useful to have the terminal end of "layers" running on an
>AT&T PC 6300, even if each window were a full screen, just because of the
>advantages of "layers" for some activities.  Surely the 6300 can handle that.

Probably, with a modest amount of work.  One would have to figure out
what to do about the difference in coordinate systems.

>Second, there are some graphics programs, such as cip, where it is easier to
>draw the desired figures than it is to write "pic" descriptions.  Surely the
>6300 could provide a useful interface to "cip". 

Not without a replacement for the downloaded interactive code, it couldn't.

>None of this requires emulating the cpu chip in the 5620, just reproducing
>some of the capability, as seen by the user, of the 5620.

If the 6300 doesn't emulate the 5620 (WE32001 instructions, etc.),
then one would need virtually ALL of the 5620's capability replicated,
in order to be able to rebuild the downloaded code for the 6300.