sysV 2.0 vs 3.1 compatibility?

Robert C. White Jr. rwhite at nusdhub.UUCP
Sat Dec 17 12:14:24 AEST 1988


in article <718 at auspex.UUCP>, guy at auspex.UUCP (Guy Harris) says:
> If, in fact, you're trying to run this program on your host machine
> (3B2?), not on the 5620, that's your problem; "dmdcc" presumably
> generates an executable image for the 5620, and that may well not be set
> up to be executable under UNIX.

I missed the first part of this but ....

If you have an executable for a dmd terminal (I use a 630, not a 
5620) you have to "jx <program> <arg1> <arg2> ..." the program to
make the computer download it into the terminal and start it running
there.

I am not shure about the half-and-half programs that end up running
executables on both machines.

I know you get the "Killed" message if you make a 630 image executable
and try to run it on a 3B2.  The processors and data spaces are totally
different.

Rob.



More information about the Comp.lang.c mailing list