[Please do not mail me a copy of your followup]

Simon Clubley <clubley@remove_me.eisner.decus.org-Earth.UFP> spake the secret code
<u144e7$2m92k$1@dont-email.me> thusly:

>On 2023-04-11, Richard <legalize+jeeves@mail.xmission.com> wrote:
>>
>> Nit: Not according to the standard. F90/F95 removed no features and only
>> "obsoleted" some features, which is why the compiler issued warnings
>> and not errors.
>
>So which version of Fortran outright removed Hollerith constants ?

FORTRAN 77, according to wikipenis:tm:
<https://en.wikipedia.org/wiki/Fortran#FORTRAN_77>
--
"The Direct3D Graphics Pipeline" free book <http://tinyurl.com/d3d-pipeline>
The Terminals Wiki <http://terminals-wiki.org>
The Computer Graphics Museum <http://computergraphicsmuseum.org>
Legalize Adulthood! (my blog) <http://legalizeadulthood.wordpress.com>

On 4/11/2023 12:57 PM, Richard wrote:
> Simon Clubley <clubley@remove_me.eisner.decus.org-Earth.UFP> spake the secret code
> <u13mpq$2kv9o$2@dont-email.me> thusly:
>> On 2023-04-10, Arne Vajhøj <arne@vajhoej.dk> wrote:
>>> $ fortran/stand=f95 bill
>>>
>>> program bill
>>> ^
>>> %F90-W-WARNING, Fixed form source is an obsolescent feature in Fortran 95.
>>> at line number 1 in file DISK2:[ARNE]bill.for;1
>>
>> These should all be -E- IMHO.
>
> Nit: Not according to the standard. F90/F95 removed no features and only
> "obsoleted" some features, which is why the compiler issued warnings
> and not errors.

F90 did not remove anything.

F95 did remove a few things (but VMS Fortran kept them).

Arne

On 4/11/2023 1:14 PM, Richard wrote:
> Simon Clubley <clubley@remove_me.eisner.decus.org-Earth.UFP> spake the secret code
> <u144e7$2m92k$1@dont-email.me> thusly:
>> On 2023-04-11, Richard <legalize+jeeves@mail.xmission.com> wrote:
>>>
>>> Nit: Not according to the standard. F90/F95 removed no features and only
>>> "obsoleted" some features, which is why the compiler issued warnings
>>> and not errors.
>>
>> So which version of Fortran outright removed Hollerith constants ?
>
> FORTRAN 77, according to wikipenis:tm:
> <https://en.wikipedia.org/wiki/Fortran#FORTRAN_77>

Yes.

But.

<quote>
APPENDIX_C:_HOLLERITH

The character data type was added to provide a
character data processing capability that is superior
to the Hollerith data capability that existed in ANSI
X3.9-1966.

The Hollerith data type has been deleted. For
processors that extend the standard by allowing
Hollerith data, the following rules for programs are
recommended:

....

C2. Hollerith_Constant

The form of a Hollerith constant is a nonzero,
unsigned, integer constant n_ followed by the letter H,
followed by a string of exactly n _ contiguous
characters. The string may consist of any characters
capable of representation in the processor. The string
of n_ characters is the Hollerith datum.

In a Hollerith constant, blanks are significant only in
the n_ characters following the letter H.

C3. Restrictions_on_Hollerith_Constants

A Hollerith constant may appear only in a DATA
statement and in the argument list of a CALL statement.
</quote>

VMS Fortran has always extended with this.

Arne

On 2023-04-11, Richard <legalize+jeeves@mail.xmission.com> wrote:
> [Please do not mail me a copy of your followup]
>
> Simon Clubley <clubley@remove_me.eisner.decus.org-Earth.UFP> spake the secret code
><u144e7$2m92k$1@dont-email.me> thusly:
>
>>On 2023-04-11, Richard <legalize+jeeves@mail.xmission.com> wrote:
>>>
>>> Nit: Not according to the standard. F90/F95 removed no features and only
>>> "obsoleted" some features, which is why the compiler issued warnings
>>> and not errors.
>>
>>So which version of Fortran outright removed Hollerith constants ?
>
> FORTRAN 77, according to wikipenis:tm:
><https://en.wikipedia.org/wiki/Fortran#FORTRAN_77>

FORTRAN 77 came before Fortran 95. :-)

(And Fortran 95 completed the removal of Hollerith constants.)

Simon.

--
Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP
Walking destinations on a map are further away than they appear.

On 2023-04-11, Scott Dorsey <kludge@panix.com> wrote:
> Simon Clubley <clubley@remove_me.eisner.decus.org-Earth.UFP> wrote:
>>On 2023-04-11, Richard <legalize+jeeves@mail.xmission.com> wrote:
>>>
>>> Nit: Not according to the standard. F90/F95 removed no features and only
>>> "obsoleted" some features, which is why the compiler issued warnings
>>> and not errors.
>>
>>So which version of Fortran outright removed Hollerith constants ?
>
> Wait, hollerith fields were removed?

Yes. They now live in the same place as K&R function definitions. :-)

Simon.

--
Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP
Walking destinations on a map are further away than they appear.

On 4/11/2023 5:47 PM, Scott Dorsey wrote:
> bill <bill.gunshannon@gmail.com> wrote:
>> On 4/10/2023 7:09 PM, Scott Dorsey wrote:
>>>
>>> Some of the stuff added in the layers after fortran90 have been
>>> messy, like pointers. Engineers shouldn't be allowed to touch
>>> pointers.
>>
>> There are many things engineers should not be allowed to touch.
>> Another would be writing business applications in Fortran. But
>> that's probably a story for another time. :-)
>
> I can understand how folks like quants who want to do real math might
> want to be using fortran for business applications. Unfortunately it
> doesn't have money types, but you can always use integer and do some
> fancy stuff to add the decimal point.

Not all business involves money. Inventory, people, educational
data, etc. But even without the money Fortran is not really the
right language for the job.

bill

On 2023-04-12, bill <bill.gunshannon@gmail.com> wrote:
> On 4/11/2023 5:47 PM, Scott Dorsey wrote:
>> bill <bill.gunshannon@gmail.com> wrote:
>>> On 4/10/2023 7:09 PM, Scott Dorsey wrote:
>>>>
>>>> Some of the stuff added in the layers after fortran90 have been
>>>> messy, like pointers. Engineers shouldn't be allowed to touch
>>>> pointers.
>>>
>>> There are many things engineers should not be allowed to touch.
>>> Another would be writing business applications in Fortran. But
>>> that's probably a story for another time. :-)
>>
>> I can understand how folks like quants who want to do real math might
>> want to be using fortran for business applications. Unfortunately it
>> doesn't have money types, but you can always use integer and do some
>> fancy stuff to add the decimal point.
>
> Not all business involves money. Inventory, people, educational
> data, etc. But even without the money Fortran is not really the
> right language for the job.
>

Agreed.

You need COBOL, DIBOL, or another language with decimal data types
in order to do business applications. If, in 2023, you try writing
a business application using floating point numbers, you don't
understand the requirements for such applications.

Simon.

--
Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP
Walking destinations on a map are further away than they appear.

>
> We got basic, c, c++, and Fortran. We are still waiting for pascal
> compiler. I still need pascal to compile my pascal programs.
>
>
> _______________________________________________
> Info-vax mailing list
> Info-vax@rbnsn.com
> http://rbnsn.com/mailman/listinfo/info-vax_rbnsn.com
>

On 4/12/2023 8:31 AM, Timothy Stark wrote:
>> We got basic, c, c++, and Fortran. We are still waiting for pascal
>> compiler. I still need pascal to compile my pascal programs.

It will show up. It has been promised.

I believe the expected order of arrival is: Cobol, Pascal, Basic.

Arne

On 4/12/2023 8:18 AM, Simon Clubley wrote:
> On 2023-04-12, bill <bill.gunshannon@gmail.com> wrote:
>> On 4/11/2023 5:47 PM, Scott Dorsey wrote:
>>> bill <bill.gunshannon@gmail.com> wrote:
>>>> On 4/10/2023 7:09 PM, Scott Dorsey wrote:
>>>>>
>>>>> Some of the stuff added in the layers after fortran90 have been
>>>>> messy, like pointers. Engineers shouldn't be allowed to touch
>>>>> pointers.
>>>>
>>>> There are many things engineers should not be allowed to touch.
>>>> Another would be writing business applications in Fortran. But
>>>> that's probably a story for another time. :-)
>>>
>>> I can understand how folks like quants who want to do real math might
>>> want to be using fortran for business applications. Unfortunately it
>>> doesn't have money types, but you can always use integer and do some
>>> fancy stuff to add the decimal point.
>>
>> Not all business involves money. Inventory, people, educational
>> data, etc. But even without the money Fortran is not really the
>> right language for the job.
>>
>
> Agreed.
>
> You need COBOL, DIBOL, or another language with decimal data types
> in order to do business applications. If, in 2023, you try writing
> a business application using floating point numbers, you don't
> understand the requirements for such applications.

You obviously missed the first line of my comment. And, while not
all business needs decimal data types there are business applications
that will require floating point. The problem with engineers writing
business applications is not just language choice but their inability
to even understand the problem.

bill

On 4/12/2023 8:42 AM, Arne Vajhøj wrote:
> On 4/12/2023 8:18 AM, Simon Clubley wrote:
>> On 2023-04-12, bill <bill.gunshannon@gmail.com> wrote:
>>> On 4/11/2023 5:47 PM, Scott Dorsey wrote:
>>>> bill  <bill.gunshannon@gmail.com> wrote:
>>>>> On 4/10/2023 7:09 PM, Scott Dorsey wrote:
>>>>>>
>>>>>> Some of the stuff added in the layers after fortran90 have been
>>>>>> messy, like pointers.  Engineers shouldn't be allowed to touch
>>>>>> pointers.
>>>>>
>>>>> There are many things engineers should  not be allowed to touch.
>>>>> Another would be writing business applications in Fortran.  But
>>>>> that's probably a story for another time.  :-)
>>>>
>>>> I can understand how folks like quants who want to do real math might
>>>> want to be using fortran for business applications.  Unfortunately it
>>>> doesn't have money types, but you can always use integer and do some
>>>> fancy stuff to add the decimal point.
>>>
>>> Not all business involves money.  Inventory, people, educational
>>> data, etc.  But even without the money Fortran is not really the
>>> right language for the job.
>>
>> Agreed.
>>
>> You need COBOL, DIBOL, or another language with decimal data types
>> in order to do business applications. If, in 2023, you try writing
>> a business application using floating point numbers, you don't
>> understand the requirements for such applications.
>
> Note that the issue is sort of a last century issue.
>
> Fortran and C are exceptions today.
>
> Most of the "newer" (as in post 1990!) languages support decimals:
> - JVM languages - Java, Kotlin, Scala, Groovy
> - .NET languages - C#, VB.NET, F#
> - Delphi
> - Python
> - PHP (primitive but there)
> etc.
>

Newer does not necessarily mean better.

bill

On 4/12/2023 8:18 AM, Simon Clubley wrote:
> On 2023-04-12, bill <bill.gunshannon@gmail.com> wrote:
>> On 4/11/2023 5:47 PM, Scott Dorsey wrote:
>>> bill <bill.gunshannon@gmail.com> wrote:
>>>> On 4/10/2023 7:09 PM, Scott Dorsey wrote:
>>>>>
>>>>> Some of the stuff added in the layers after fortran90 have been
>>>>> messy, like pointers. Engineers shouldn't be allowed to touch
>>>>> pointers.
>>>>
>>>> There are many things engineers should not be allowed to touch.
>>>> Another would be writing business applications in Fortran. But
>>>> that's probably a story for another time. :-)
>>>
>>> I can understand how folks like quants who want to do real math might
>>> want to be using fortran for business applications. Unfortunately it
>>> doesn't have money types, but you can always use integer and do some
>>> fancy stuff to add the decimal point.
>>
>> Not all business involves money. Inventory, people, educational
>> data, etc. But even without the money Fortran is not really the
>> right language for the job.
>
> Agreed.
>
> You need COBOL, DIBOL, or another language with decimal data types
> in order to do business applications. If, in 2023, you try writing
> a business application using floating point numbers, you don't
> understand the requirements for such applications.

Note that the issue is sort of a last century issue.

Fortran and C are exceptions today.

Most of the "newer" (as in post 1990!) languages support decimals:
- JVM languages - Java, Kotlin, Scala, Groovy
- .NET languages - C#, VB.NET, F#
- Delphi
- Python
- PHP (primitive but there)
etc.

I am sure there are plenty of C++ libraries with an Amount class
with decimal data and full operator overloading support.

Arne

On Tue, 2023-04-04 at 00:22 +0100, Chris Townley wrote:
> > I applied for the Alpha licence last year. Can't wait for my e-
> > mail!
>
> Not that I can do anything until AMD is support is added, which they
> say
> will be in V9.2-1
>
> I went to the CLP registration page, but the X-86 option is still
> disabled. Also haven't had any emails

My boat finally came in. The email just arrived!
--
Tactical Nuclear Kittens

On 13/04/2023 23:12, Single Stage to Orbit wrote:
> On Tue, 2023-04-04 at 00:22 +0100, Chris Townley wrote:
>>> I applied for the Alpha licence last year. Can't wait for my e-
>>> mail!
>>
>> Not that I can do anything until AMD is support is added, which they
>> say
>> will be in V9.2-1
>>
>> I went to the CLP registration page, but the X-86 option is still
>> disabled. Also haven't had any emails
>
> My boat finally came in. The email just arrived!

So did mine, except they say we are all enrolled, but they are
restricted who can download it. It will be rolled out over e next three
months.

Pretty pointless announcement

--
Chris

On Friday, April 14, 2023 at 1:25:32 AM UTC+2, Chris Townley wrote:
> On 13/04/2023 23:12, Single Stage to Orbit wrote:
> > On Tue, 2023-04-04 at 00:22 +0100, Chris Townley wrote:
> >>> I applied for the Alpha licence last year. Can't wait for my e-
> >>> mail!
> >>
> >> Not that I can do anything until AMD is support is added, which they
> >> say
> >> will be in V9.2-1
> >>
> >> I went to the CLP registration page, but the X-86 option is still
> >> disabled. Also haven't had any emails
> >
> > My boat finally came in. The email just arrived!
> So did mine, except they say we are all enrolled, but they are
> restricted who can download it. It will be rolled out over e next three
> months.
>
> Pretty pointless announcement
>
> --
> Chris
Hi All,
I received the email yesterday as well. I went to sp.vmssoftware.com (VSI service platform).
There you need to login with your email and password.
Enter the email address you received the announcement email on,
then click "forgot password" and bob is your uncle!
You will receive a reset link, enter the new password, login again and there you are.
Goto to tab "packages", there you should see the program you were registered/licensed to in the HP days. If you select " only accessible" you will see the x86 vms software packages.

Hope this helps!

Cheers,
Sjoerd

On 2023-04-14, Sjoerd van Leersum <s.van.leersum@xs4all.nl> wrote:
> Hi All,
> I received the email yesterday as well. I went to sp.vmssoftware.com (VSI service platform).
> There you need to login with your email and password.
> Enter the email address you received the announcement email on,
> then click "forgot password" and bob is your uncle!
> You will receive a reset link, enter the new password, login again and there you are.
> Goto to tab "packages", there you should see the program you were registered/licensed to in the HP days. If you select " only accessible" you will see the x86 vms software packages.
>

Ouch. Based on the email contents, I wonder if they were expecting people
to do that and if they will now stop that way in...

Simon.

--
Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP
Walking destinations on a map are further away than they appear.

On 2023-04-13, Chris Townley <news@cct-net.co.uk> wrote:
> On 13/04/2023 23:12, Single Stage to Orbit wrote:
>> On Tue, 2023-04-04 at 00:22 +0100, Chris Townley wrote:
>>>> I applied for the Alpha licence last year. Can't wait for my e-
>>>> mail!
>>>
>>> Not that I can do anything until AMD is support is added, which they
>>> say
>>> will be in V9.2-1
>>>
>>> I went to the CLP registration page, but the X-86 option is still
>>> disabled. Also haven't had any emails
>>
>> My boat finally came in. The email just arrived!
>
> So did mine, except they say we are all enrolled, but they are
> restricted who can download it. It will be rolled out over e next three
> months.
>
> Pretty pointless announcement
>

Got that email as well. :-(

Sometimes I wonder if the VSI funders are keeping VSI around as a
tax writeoff because VSI management keep finding new ways to screw up
the VMS marketplace. :-(

VSI has just had an excellent writeup in The Register, and instead of
moving full steam ahead in response to that and giving a wide range of
people access to x86-64 VMS, so they can play with it, VSI turn around
and say we will gradually allow access over a 3 _month_ period. :-( WTF ???

Oh, and according to that email, you are not allowed to contact them
other than through the community forum, and if you do, your responses
will be initially ignored and your access eventually blocked.

So what is someone who finds a vulnerability in all this new code expected
to do ? Just post in the forum and hope no one does something bad with it ?
Contacting VSI privately, and via the customer portal which they don't
want you to use, is exactly the kind of way security issues should be
reported - securely in private and via a formal mechanism.

Simon.

--
Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP
Walking destinations on a map are further away than they appear.

On 14/04/2023 10:52, Sjoerd van Leersum wrote:
> On Friday, April 14, 2023 at 1:25:32 AM UTC+2, Chris Townley wrote:
>> On 13/04/2023 23:12, Single Stage to Orbit wrote:
>>> On Tue, 2023-04-04 at 00:22 +0100, Chris Townley wrote:
>>>>> I applied for the Alpha licence last year. Can't wait for my e-
>>>>> mail!
>>>>
>>>> Not that I can do anything until AMD is support is added, which they
>>>> say
>>>> will be in V9.2-1
>>>>
>>>> I went to the CLP registration page, but the X-86 option is still
>>>> disabled. Also haven't had any emails
>>>
>>> My boat finally came in. The email just arrived!
>> So did mine, except they say we are all enrolled, but they are
>> restricted who can download it. It will be rolled out over e next three
>> months.
>>
>> Pretty pointless announcement
>>
>> --
>> Chris
> Hi All,
> I received the email yesterday as well. I went to sp.vmssoftware.com (VSI service platform).
> There you need to login with your email and password.
> Enter the email address you received the announcement email on,
> then click "forgot password" and bob is your uncle!
> You will receive a reset link, enter the new password, login again and there you are.
> Goto to tab "packages", there you should see the program you were registered/licensed to in the HP days. If you select " only accessible" you will see the x86 vms software packages.
>
> Hope this helps!
>
> Cheers,
> Sjoerd

Thanks for that, but seems I don't need it - just received the access
letter!

Will get it downloading while I try to work out to set up KVM/QEMU

--
Chris

Yeah. I got access letter from VMS software inc. today too.

I had a problem with DHCP settings. I did applied static IP addresses instead so that my Verizon G3100 assigned new machines with new internal static IP addresses.
When DHCP bugs is fixed, I will changed settings back to DHCP in future..

I successfully installed OpenVMS x86 with VirtualBox under Windows 11. I set a bridged network adapter to ethernet driver like Killer E2500 driver and was now able access the Internet and HECnet outside. With other drivers, it did not work. There is no Jnet software available for x86 version so that I have to develop NJE driver from scratch or FujiNet to access BITNET network or IBM mainframes.

I installed C, C++ and Fortran compilers so far. I am waiting for Pascal, Cobol and Basic right now.

I found OpenVMS E9.2-1 install guide manual according to access letter email. It said that E9.2-1 now supports AMD processor. I will try it on my UDOO Bolt SBC board.

I moved TSVMSA to TSVMSB for VAX version and assigned TSVMSA to x86 version on HECnet network. I will not need TSVMST anymore.
I removed Multinet and TCPware from old VAX version and installed TCPIP software.

Is that possible to get Multinet and TCPware with VSI hobbyist paks? I am waiting for Process, Inc for porting their TCP/IP software to x86 version.

Tim

On 4/14/2023 5:47 PM, fsword007@gmail.com wrote:
> Yeah. I got access letter from VMS software inc. today too.
>
> I had a problem with DHCP settings. I did applied static IP addresses instead so that my Verizon G3100 assigned new machines with new internal static IP addresses.
> When DHCP bugs is fixed, I will changed settings back to DHCP in future..
>
> I successfully installed OpenVMS x86 with VirtualBox under Windows 11. I set a bridged network adapter to ethernet driver like Killer E2500 driver and was now able access the Internet and HECnet outside. With other drivers, it did not work. There is no Jnet software available for x86 version so that I have to develop NJE driver from scratch or FujiNet to access BITNET network or IBM mainframes.
>
> I installed C, C++ and Fortran compilers so far. I am waiting for Pascal, Cobol and Basic right now.
>
> I found OpenVMS E9.2-1 install guide manual according to access letter email. It said that E9.2-1 now supports AMD processor. I will try it on my UDOO Bolt SBC board.
>
> I moved TSVMSA to TSVMSB for VAX version and assigned TSVMSA to x86 version on HECnet network. I will not need TSVMST anymore.
> I removed Multinet and TCPware from old VAX version and installed TCPIP software.
>
> Is that possible to get Multinet and TCPware with VSI hobbyist paks? I am waiting for Process, Inc for porting their TCP/IP software to x86 version.
>

I thought they announced they were retiring?

bill

On Fri, 2023-04-14 at 02:52 -0700, Sjoerd van Leersum wrote:
> I received the email yesterday as well. I went to sp.vmssoftware.com
> (VSI service platform).
> There you need to login with your email and password.
> Enter the email address you received the announcement email on,
> then click "forgot password" and bob is your uncle!
> You will receive a reset link, enter the new password, login again
> and there you are.
> Goto to tab "packages", there you should see the program you were
> registered/licensed to in the HP days. If you select " only
> accessible"  you will see the x86 vms software packages.

Thanks for that. I think you also need a licence for it. It's probably
easy to download and install it and prepare it for when your licence
comes through.
--
Tactical Nuclear Kittens

On 4/14/2023 8:37 AM, Simon Clubley wrote:
> VSI has just had an excellent writeup in The Register, and instead of
> moving full steam ahead in response to that and giving a wide range of
> people access to x86-64 VMS, so they can play with it, VSI turn around
> and say we will gradually allow access over a 3 _month_ period. :-( WTF ???

It would be nice if that happened a bit faster.

1000 people at 100 per day is just 10 days.

> Oh, and according to that email, you are not allowed to contact them
> other than through the community forum, and if you do, your responses
> will be initially ignored and your access eventually blocked.

They don't want their support channel for paying customers blocked
by 500 hobbyists having problems with their PC or their VM software
or their network or whatever.

I think that is both reasonable and standard for community licenses.

> So what is someone who finds a vulnerability in all this new code expected
> to do ? Just post in the forum and hope no one does something bad with it ?
> Contacting VSI privately, and via the customer portal which they don't
> want you to use, is exactly the kind of way security issues should be
> reported - securely in private and via a formal mechanism.

VSI should have an official channel for reporting security
vulnerabilities.

But if not then those finding the vulnerabilities would
need to find a path.

One option is to use the other channels and assume VSI does
distinguish between "There is a remote code execution vulnerability
in product XYZ" report and "When I try to install VMS in VM ABC on
laptop FooBar I get error message XXXXXX" reports.

Another option would be to post in the community forum "Hi VSI - I think
I found a serious security vulnerability - please email me to get
details.".

I suspect that it is easier to get hold of VSI than to find a
serious security vulnerability.

Arne

Simon Clubley <clubley@remove_me.eisner.decus.org-Earth.UFP> wrote:
>
>Oh, and according to that email, you are not allowed to contact them
>other than through the community forum, and if you do, your responses
>will be initially ignored and your access eventually blocked.

A number of vendors do that these days. We make a big effort not to
ever buy from them. Ubiquiti is a typical offender; the inability to
talk to anyone at the company (even in sales) means we don't buy from
them. I can't believe anyone ever thought it was a good idea.
--scott

--
"C'est un Nagra. C'est suisse, et tres, tres precis."

In article <u0uqbn$1nef1$1@dont-email.me>,
Chris Townley <news@cct-net.co.uk> wrote:
>Can anyone suggest what sort of cheap server/workstation I could get to
>run this? All my modern systems are AMD
>
>I have looked at various DL380p Gen 8, but the cpus seen too old

This is a good question... and nobody is answering it. Has anyone had
experience running on the Gen 8 machines?

We won't buy the Gen 9 machines because of the disk controllers locking
out non-HP disks, so we are buying Dell servers now. Still have plenty
of HP Gen 6, 7, and 8 servers in use though.
--scott
--
"C'est un Nagra. C'est suisse, et tres, tres precis."

On 4/15/2023 8:40 AM, Scott Dorsey wrote:
> In article <u0uqbn$1nef1$1@dont-email.me>,
> Chris Townley <news@cct-net.co.uk> wrote:
>> Can anyone suggest what sort of cheap server/workstation I could get to
>> run this? All my modern systems are AMD
>>
>> I have looked at various DL380p Gen 8, but the cpus seen too old
>
> This is a good question... and nobody is answering it. Has anyone had
> experience running on the Gen 8 machines?

Robert Brooks and others (I think) have in past times stated repeatedly that a Gen 9 or later HP Proliant will be required for bare metal. Since the CPU characteristics are usually propagated through by the VM hypervisor, that would seem to mean that VM Hosts must be Gen 9 or higher as well, but I'm just guessing at that..

John H. Reinhardt