Path: utzoo!utgpu!watmath!clyde!bellcore!rutgers!tut.cis.ohio-state.edu!unmvax!pprg.unm.edu!hc!lll-winken!netsys!ziggy!scotty
From: scotty@ziggy.UUCP (Scott Drysdale)
Newsgroups: comp.sys.hp
Subject: Re: Pre-formatted tapes for HP drives
Keywords: hp350 hp9000
Message-ID: <137@ziggy.UUCP>
Date: 9 Dec 88 04:39:33 GMT
References: <1074@statware.UUCP> <26038@teknowledge-vaxc.ARPA> <9055@bcsaic.UUCP>
Reply-To: scotty@ziggy.UUCP (Scott Drysdale)
Organization: Un*x Link,Frederick Md.
Lines: 32

we recently got a bunch of hp350 series 9000 workstations where i work.  they
are going to be used as edit/compile/link/emulate stations using the 64000
compatible emulator cage and the 186 emulator.  we previously (and still now,
unfortunately) used the 64000 for these functions - but it's obviously
terribly slow doing everything.  i started squirting source from the 64000
to the unix system tonight, and got some stuff compiled/assembled/linked.
some observations:
the compiler/assembler/linker seem to be the same brain-damaged ones as
the 64000's.  compiler makes putrid code and doesn't like to put initialized
structures in the "code" space, the linker takes the same painful input
file to direct it's work.  the assembler seems to have the same bugs as the
64000 assembler.
i haven't tried the emulation stuff yet - but so far it doesn't look good.
anyone know of any 3rd party compilers/assemblers/linkers that understand
segments the way intel intended (ie, groups, rel,rel,rel->linker->rel, etc)
and produce output that's usable by the emulator package, and run on the
350/9000?  it'd be nice to get something that's on par with microsoft c's
optimizations and ANSIness - anyone know of a way to convert microsoft
rel files to hp rel files?
also, anyone know of a decent text editor for the 350/9000?  vi doesn't quite
cut it, and the 64000-style editor is simply awful.  we're looking for something
that doesn't use the "anything you type will cause something to happen"
style of user interface (ie, vi, microemacs,...).  it'd also be really cool
if the editor knew how to use hp's windowing system and mouse.  the editor
must present in some form (status line?) the current state of the editor
(ie, let you know that it's in the middle of command xyz, or what your
next allowable keystrokes can be, etc).  if you've seen/used intel AEDIT,
that's a good example of what we're looking for.

thanks.

  --Scott Drysdale
Telecommunications Techniques Corp.