I am aware of some of that. I was actually comparing using the information in the combined kit release notes. It has information about how to determine the version of the included programs. Some have a command to do it, some have an address that needs to be examined with ODT.
With OS/8, the notion of a config files changes. You make changes and save them in the binary of the command, so a command binary can change. You learn this after doing a build with R BUILD and then realizing that you can't save your changes. I haven't figured out if there is a way to load a system head into BUILD. -chuck On Fri, Dec 9, 2016 at 7:13 PM, Vincent Slyngstad <[email protected]> wrote: > From: Charles Dickman: Friday, December 09, 2016 3:59 PM >> >> I have some DECtapes that are V3D and I have found some RX01 images >> from the V3D Combined Kit. The programs that are common to both are >> different versions, so V3D changed over time. > > > I know that .SV format saves some cruft along with the binary, so .SV files > can compare different even though they are effectively the same. > (I have some Perl code somewhere that will diff them in a way that helps > identify this problem. What happens is that the differences are all in the > "tails" where .BN format provides granularity not available in .SV format.) > > It is also possible to save a program after it's been run a few times, which > saves different values for the return addresses at the top of the > subroutines and such. > > Vince
