Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!lll-lcc!styx!ptsfa!ihnp4!occrsh!occrsh.ATT.COM!gorgo.UUCP!authorplaceholder
From: authorplaceholder@gorgo.UUCP.UUCP
Newsgroups: comp.sys.att
Subject: Re: Binary incompatibility on SysV R2.1
Message-ID: <58300008@gorgo.UUCP>
Date: Sun, 26-Apr-87 17:57:00 EDT
Article-I.D.: gorgo.58300008
Posted: Sun Apr 26 17:57:00 1987
Date-Received: Wed, 29-Apr-87 06:05:06 EDT
References: <9300002@bradley>
Lines: 27
Nf-ID: #R:bradley:9300002:gorgo.UUCP:58300008:000:1147
Nf-From: gorgo.UUCP!bsteve    Apr 26 16:57:00 1987


John Lengeling in comp.sys.att writes:

>I have a 3B2/300 running System V Release 2.1 and while
>trying to run some commercial programs (filePro 16/Crystalwriter), I get 
>the following error:
>
>	foo: cannot execute
>...
>What does the F_BM32RST flag do and is there a way to convert the binary to
>get it to run?  We are going to upgrade our machine(s) to release 3 
>this summer, will this problem also exist when I upgrade to 3.[01]

The problem will persist with SVR3.1. However you may be able to get the old
binaries to run on a model 310... The upgrade to the 310 involves a system
board swap out and I think costs about $2500...

The crux of the problem was that compiled binaries were promised to run
across 2 releases. Release 1.0 binaries would run on release 2.0. Release 2.1
was a provisional step between 2.0 and release 3. However, I have found that
most old binaries still run on the 310,400,600 and the 3B15... I have a 300
and my old cshell binary ceased to run when I upgraded to release 3.0, but
would still run under 2.1 and 3.1 on a 310 or 400.

  Hope this helps,
   Steve Blasingame (Oklahoma City)
   ihnp4!gorgo!bsteve