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

[Johnny Billquist]

On 2023-05-09 20:18, Chris Townley wrote:
> On 09/05/2023 17:10, bill wrote:
>> On 5/9/2023 11:52 AM, Dave Froble wrote:
>>> On 5/9/2023 8:52 AM, Johnny Billquist wrote:
>>>> On 2023-05-09 01:39, Robert A. Brooks wrote:
>>>>> On 5/8/2023 6:32 PM, terry-... at glaver.org wrote:
>>>>>
>>>>>> If you just mean running a complete VAX/VMS environment, since
>>>>>> x86-64 VMS already runs under a hypervisor it would probably be
>>>>>> better to just run vanilla SIMH as another VM. If VSI ever releases
>>>>>> a "cluster compatibility kit" for VAX/VMS, it could even be a poten-
>>>>>> tially-supported cluster environment.
>>>>>
>>>>> I can say with a staggeringly high level of confidence that
>>>>> VSI will *never* release anything for the VAX.
>>>>>
>>>>> As I've said before, we have the rights to release
>>>>> a VSI-built version of VAX/VMS, but we won't.
>>>>
>>>> Fully understood and understandable.
>>>>
>>>> But there is a whole lot of people who wish VSI would just 
>>>> re-release V7.3 with
>>>> a VSI stamp on it, so it could be handled for hobbyists.
>>>>
>>>> But I understand that even that is probably too much work to be 
>>>> worth it.
>>>> Extremely little return on any work done.
>>>>
>>>>   Johnny
>>>>
>>>
>>> I can guess that perhaps the biggest technical reason is the lack of 
>>> old VAX hardware to test against.  A few edits and firing up the 
>>> build procedure might be possible.  But on what HW do you run the 
>>> build procedure?
>>>
>>
>> SIMH...   :-)
>>
>> bill
>>
> 
> Maybe they haven't got a licence PAK?

I assume this was a joke. Because the point was that if they built a new 
version, they would be the ones generating the PAK...

   Johnny