[Info-vax] clock problems with OpenVMS x86 on VirtualBox

[bill]

On 5/8/2023 9:14 AM, Arne Vajhøj wrote:
> 
> 
> If you mean a true emulator then I don't see the point - there are
> plenty of such products available from third parties. If anyone need
> one, then they buy one. No need for VSI to do anything.

I guess I'm just to subtle.  I certainly didn't mean for VSI to re-
invent the wheel yet again.  I meant that they should [ick up one of 
these existing emulators (SIMH for the VAX) do a port for VMS (if
it doesn't already exist) and then bundle them with VMS-x86_64.
IMHO a reasonable alternative to the VEST idea.  I am sure any VAX
emulation will be faster than the fastest hardware VAX ever built.
Alpha, I couldn't say.

> 
> (VSI would also have a small problem supplying a VMS version for
> a VAX simulator)

Well, once things smooth out keeping these VAX customers on VMS might
just be the incentive they need to do a VSI VAX Version.  I am pretty
sure they have said in the past that they have the license to do this
but just didn't see a business case.

> 
> If you mean something like VEST or AEST (which is a translation not
> an emulation) - it would probably be called IEST to follow naming
> convention, then my guess is that if VSI were DEC/HP size, then they
> would have created such a beast, but they are not. VSI is a smaller
> company and they have to prioritize. IEST with the possibility to
> also process images that has already been through AEST and
> possible VEST would be a lot of work. So they decided not to do it.

I see it as an alternative.  And, I expect a much more reliable one.
I have never run anything VESTed or AESTed but I can see a lot of ways
that could go wrong.  I think even more so with the new architecture.

bill