Newsgroups: comp.sys.transputer
From: stocker-dg@salem.ge.com (David Stocker)
Subject: Re: C004 configuring, Rspy and D7405A toolset.
Organization: GE Industrial Systems
Date: 15 Mar 1997 18:54:44 GMT
Mime-Version: 1.0
Content-Type: Text/Plain; charset=US-ASCII
Message-ID: <5ger9k$lg4$1@tammy.gemis.ge.com>

In article <fe8jEBA4jTJz0A$6@oxim.demon.co.uk>, markb@oxim.demon.co.uk 
says...
>One of the problems with D7405A is that it is not clear how you go about
>configuring the C004 on the b008 boards (PC environment obviously). We
>used to use ncs, but ncs just refuses to run with all of the environment
>set up for the D7405A toolset.

I agree totally.  IMHO, the new ASERVER system in Windows environment is more 
trouble than it's worth!

>I have been told that with the new toolset, it is the responsibility of
>the rspy program to set up the c004, but I cant find any documentation
>on how to do that.

Agreed!

>My next point has already been raised in this group, but not resolved.
>that is the problem that the iserver service window dows not appear to
>support ansi/bansi codes, so that functions like ss.goto.xy produce
>visible garbage, rather than perform their function. Is this iserver
>console window supposed to support ansi/bansi? or are we supposed to set
>ITERM to a special Windows iserver console window .itm file?

I have a similar question -- it seems that the D7404A toolset (OCCAM) and 
D7141A toolset (C) now only support the B004 and B008 cards -- no third party 
link interface boards are supported.  So how are we supposed to use these 
toolsets when SGS-Thompson is no longer supplying these boards?!  Lucky for 
me that the "old" iserver still works, so that I can actually use the third 
party link interface boards that I already had (except for the point 
mentioned above...)  But of course I can't use the debugger, since it's 
windows based...

Has anyone used D7405A/D7414A with third-party link interface boards?  I'd 
love to hear how you did it...

Dave Stocker
stocker-dg@salem.ge.com


