即使我能够获得UNIX媒体，是否还需在某些地方获得旧的UNIX发行版？

我相信那里肯定有很多老兵躺在那里的旧媒体。
在我上一份工作中，我们在HP-UX工作站上运行了许多许可证。
VEE 5.0是最后一个支持的版本。
我们能够获取程序文件，只需在Wintel盒子上运行它们。
但是我们用测试结果创建的数据文件完全是另一个故事。
他们遭遇了经典的英特尔/摩托罗拉不同意见，即哪个字节首先出现。
人物很好。
Real64s需要移动所有8个字节。
同样是32​​s和16s。你的Windows许可证密钥可能对Unix代码无效。
我在安捷伦打开了一个案例，因为我的公司有许多运行VEE 8.0代码的测试站。
我们现在没有时间升级所有这些。
但我是公司的新手，需要许可证。
即使我购买了9.2的全新许可证，安捷伦也不允许我在8.0上进行开发。
安捷伦称，它已过时且不受支持。
所以我现在不知道该怎么做。
有人需要告知安捷伦制造业的真实情况。
使用新版本的工具进行验证和验证，仅仅是因为您需要进行一组简单的更改，这不是资源明智的选择。
这并不像我想要安慰安捷伦！
我付了新的许可证才能成为有效的用户。无论如何，你应该能够找到能够为你提供Unix东西的人。
但它可能不适用于你的SPARC.Good Luck，保罗



     以下为原文

  I am sure that there must be many veterans out there who have the old media lying around. 

In my last job, we ran many licenses on HP-UX workstations.  VEE 5.0 was the last supported version.  We were able to take the program files and simply run them on Wintel boxes.  But the data files that we created with our test results were another story altogether.  They suffered from the classic Intel/Motorola difference of opinion of which byte came first.  Characters were fine.  Real64s needed all 8 bytes moved.  32s and 16s likewise.

Your license key for Windows is probably not valid for the Unix code.  I openned a case with Agilent because my company has many test stations running VEE 8.0 code.  We do not have time to upgrade all of them now.  But I am new to the company and need a license.  Even though I have purchased a full, new license for 9.2, Agilent will not allow me to do development on 8.0.  It is obsolete and not supported according to Agilent.  So I do not know what to do right now.  Someone needs to inform Agilent about what really goes on in the manufacturing world.  Validation and verification with a new version of tools, just because you need to make a simple set of changes, is not a resource wise choice.  And it is not like I am trying to sponge off Agilent!  I paid for a new license to become a valid user.

Anyway, you should be able to find someone who can get you the Unix stuff.  But it may not work on your SPARC.

Good Luck,

Paul

到达一些退伍军人是我发布到这个论坛的目的之一 - 但到目前为止没有运气。
对于我的一小段代码，字节顺序不是问题，因为我可以交换ASCII数据。
在VEE主页上，VEE 3.21版本被列为可用于SPARC / Solaris平台的最后一个版本。关于过时策略，这似乎与大多数公司相同。
看一下测试设备，例如
HP和Tek因其坚实的仪器和出色的支持（例如服务手册的形式）而获得了良好的声誉。
对于这样的仪器而言，这对于消费类产品来说更为重要，而且很遗憾，大多数大公司都放弃了这种支持方式......对于VEE8.0 / 9.2的最佳情况......



     以下为原文

  Reaching some of the veterans was one of the purposes of my posting
to this forum - but no luck so far.

For my small pieces of code, endianness would not be an issue since
it is OK for me to exchange ASCII data. On the VEE homepage
the VEE 3.21 version is listed as the last one to be available for the
SPARC/Solaris platform.

Regarding the obsolescence policy this seems to be commonplace
with most companies. Looking at test equipment, e.g. HP and Tek got such
a good reputation because of their solid instruments and the excellent
support (in form of service manuals for example). For such instruments
this is more important then for consumer products and it is a shame, that
most major companies dropped this way of support...

The very best for your case with VEE8.0/9.2...