I posted this question on the HP OpenVMS forums but I should probably have posted here since it involves the interaction of FreeAXP/PuTTy and Windows:
I have succeeded in installing openVMS 8.4 in FreeAXP. I now have a file named 'openvms_alpha_8_4_update500.zip' on my Windows 7 laptop. This zip file contains 'VMS84A_UPDATE-V0500.ZIPEXE' and 'VMS84A_PCSI_V0200.ZIPEXE'
How do I go about applying these updates? I believe that I have to load my OS CD and choose the upgrade option, but then how do I get these .ZIP files into OpenVMS via Putty so that the upgrade can take place?
Apparently i don't need the OS CD Upgrade option - it's a question of transferring the ZIPEXE files into OpenVMS from Windows and running the ZIPEXEs.
I tried cut'n'paste but this did not seem to work. Advice appreciated.
Bruce: I think I have configured TCPIP in OpenVMS by using the 'Automatic Configuration of TCP/IP Services Using DHCP Client'.
So assuming TCP/IP is set up in OpenVMS, my next question is how to transfer the files from my Windows laptop. I have FreeAXP/PuTTy running on the Windows laptop - I'm not clear on how I would set up a link between Windows and FreeAXP to do the transfer.
Sorry these are noob questions - I've never done this sort of thing before
Use something like Filezilla to FTP files between Windows and VMS. This is straight forward assuming you have two NICs on the FreeAXP host system and have turned off all Windows services on the NIC assigned to FreeAXP.
Bruce: I'm afraid this is all too difficult for me. I can assign 2 NICs in FreeAXP using thepci11 and pci12 tabs. After that I'm stumped.
I used 127.0.0.1 as the host address, added the system username and password and port 9000. I get a "connection established, waiting for welcome message..."
There is a "Response :"<.. garbage..> (B Virtual serial0)"
then "Error: could not connect to server"
I have chosen the option to force UTF-8 as the character set (as Autodetect gives a message "Invalid character sequence received...select Force UTF-8 ..."
The fact that I got "(B Virtual serial0)" seems reasonably optimistic but where I go from here I have no idea.
You don't have TCP/IP configured correctly or you don't have a DCHP server handing out addresses. Run TCPIP$CONFIG.COM. If you don't understand what the configuration procedure is asking for, it is time to hit the books.
malmberg June 26 2018 https://www.openvmshobbyi st.com/forum/viewthread.p hp?forum_id=10&thread_id= 2363
bhamakripa June 24 2018 I am trying OpenVMS via SIMH. Need to get OS binaries for v7.3. Registered here but don't have any membership number yet which is needed to get license. Pls suggest what to do. I hardly know anyth
basilh June 05 2018 Any other forum members in Perth, Australia?
malmberg March 24 2018 Probably. More people hang out on the comp.os.vms newsgroup.
vaxpert March 23 2018 I have a PE42A and other Alpha system stuff for sale. I'm in So California. Any interest out there?
goodbyespy February 27 2018 To Prohorenko. Please, visit group OpenVMS in the ok.ru
peteherrera February 24 2018 How much does it cost to buy a complete OpenVMS hardcopy documentation set of the latest version
prohorenko February 17 2018 Please help to obtain the license on OpenVMS
malmberg December 12 2017 HPE only makes the most current version of OpenVMS Alpha / IA64 /VAX available to hobbyists. When I had access to the Alliance 1 program it was the same. No public downloads are allowed by HPE.
nmbonao December 08 2017 Is anybody knows OpenVMS 8.2 version downloadable version? or CD copy? Thank you very much
aarommes December 02 2017 Bitcoin and Blockchain enthusiasts ( plus distributed computing ) please connec / reply: http://www.openvmshobbyis t.com/forum/viewthread.ph p?forum_id=130&thread_id= 2991
malmberg September 10 2017 https://sourceforge.net/p /vms-ports/wiki/VMSInstal lation/ For the most part just use VMS 6.1 media instead of 7.3. But why run the older release?
DoeveR August 07 2017 Where can I find the write up on running VMS 6.1 using the simh emulator?
Bart March 20 2017 Happy to have found my password again!