Hello all. I have an HP DL380 G4 server running Windows 2003 Server Std SP2 and Pathworks v7.4. Recently we have been getting system crashes during certain network operations and it's possible that it may be Pathworks related. I am guessing that maybe Pathworks does not play nicely with some new windows network patch. The system has been stable for almost three years with the same configuration. Since it has been stable, I haven't played with Pathworks since I originally installed it in 2006. I did have issues with the install because Pathworks messes up HP network teaming. To resolve this I put in a PCI NIC with only the Pathworks software bound to it. This software is in place so that our VAXen can transfer daily test results to the windows server. The VAXen are all frozen at VMS 5.5-2. Unfortunately, all these are running OSU so we don't have Multinet licenses. We had looked at Multinet as an option but it was way too expensive for what we are doing and for the number of licenses required. The DECnet file transfer is part of some old third party software. We do have source but we don't have the resources right now for a rewrite. That's the background; now for my questions: 1. We are looking at upgrading from Win 2003 to Win 2008. Is anyone in this forum successfully running Pathworks 32 7.4 on Win 2008? 2. The HP website simply says that PW32 has been retired and that customers may search for third party alternatives.  Can someone point me to a decent (and hopefully affordable) alternative? I'm coming up with all HP or university _link_s from Google. Thanks in advance.

Std SP2 and Pathworks v7.4. Recently we have been getting system crashes during certain network operations and it's possible that it may be Pathworks related. I am guessing that maybe Pathworks does not play nicely with some new windows network patch. The system has been stable for almost three years with the same configuration. Since it has been stable, I haven't played with Pathworks since I originally installed it in 2006. I did have issues with the install because Pathworks messes up HP network teaming. To resolve this I put in a PCI NIC with only the Pathworks software bound to it. This software is in place so that our VAXen can transfer daily test results to the windows server. The VAXen are all frozen at VMS 5.5-2. Unfortunately, all these are running OSU so we don't have Multinet licenses. We had looked at Multinet as an option but it was way too expensive for what we are doing and for the number of licenses required. The DECnet file transfer is part of some old third party software. We do have source but we don't have the resources right now for a rewrite. That's the background; now for my questions: 1. We are looking at upgrading from Win 2003 to Win 2008. Is anyone in this forum successfully running Pathworks 32 7.4 on Win 2008? 2. The HP website simply says that PW32 has been retired and that customers may search for third party alternatives.  Can someone point me to a decent (and hopefully affordable) alternative? I'm coming up with all HP or university _link_s from Google. Thanks in advance. Wouldn't Kermit be useful in this situation? There used to be a an IP stack that was free but I doubt it is still available. DECnet support outside DEC products is limited. There is a working opensource DECnet kit for Linux though. Hans

2. The HP website simply says that PW32 has been retired and that customers may search for third party alternatives.  Can someone point me to a decent (and hopefully affordable) alternative? I'm coming up with all HP or university _link_s from Google. Thanks in advance. - Is there a UCX license on the VAX systems?  (Type UCX at the $ prompt to find out, or do a $LIC LIST.)  That would give you an FTP client and server to either push/pull the files. - Put the files in some directory (if not their native location), create a mapping for the OSU web server that points to that directory, and then have the PC pull the files using HTTP.

Hello all. I have an HP DL380 G4 server running Windows 2003 Server Std SP2 and Pathworks v7.4. Recently we have been getting system crashes during certain network operations and it's possible that it may be Pathworks related. I am guessing that maybe Pathworks does not play nicely with some new windows network patch. The system has been stable for almost three years with the same configuration. Since it has been stable, I haven't played with Pathworks since I originally installed it in 2006. I did have issues with the install because Pathworks messes up HP network teaming. To resolve this I put in a PCI NIC with only the Pathworks software bound to it. This software is in place so that our VAXen can transfer daily test results to the windows server. The VAXen are all frozen at VMS 5.5-2. Unfortunately, all these are running OSU so we don't have Multinet licenses. We had looked at Multinet as an option but it was way too expensive for what we are doing and for the number of licenses required. The DECnet file transfer is part of some old third party software. We do have source but we don't have the resources right now for a rewrite. That's the background; now for my questions: 1. We are looking at upgrading from Win 2003 to Win 2008. Is anyone in this forum successfully running Pathworks 32 7.4 on Win 2008? 2. The HP website simply says that PW32 has been retired and that customers may search for third party alternatives.  Can someone point me to a decent (and hopefully affordable) alternative? I'm coming up with all HP or university _link_s from Google. Thanks in advance. Frozen Vaxen. How chillen. I'm confused, I thought Pathworks ran on VAX (and Alpha) and used IP as a transport. I didn't know it had anything to do with Decnet. There are VMS versions of Samba but I don't know what would run on VMS 5.5-2 with OSU. How much do you spend on electricity air and maintenance for the Vaxen? You may already be spending more than what an upgrade would cost. Jeff Coffield www.digitalsynergyinc.com

Hello all. I have an HP DL380 G4 server running Windows 2003 Server Std SP2 and Pathworks v7.4. Recently we have been getting system crashes during certain network operations and it's possible that it may be Pathworks related. I am guessing that maybe Pathworks does not play nicely with some new windows network patch. The system has been stable for almost three years with the same configuration. Since it has been stable, I haven't played with Pathworks since I originally installed it in 2006. I did have issues with the install because Pathworks messes up HP network teaming. To resolve this I put in a PCI NIC with only the Pathworks software bound to it. This software is in place so that our VAXen can transfer daily test results to the windows server. The VAXen are all frozen at VMS 5.5-2. Unfortunately, all these are running OSU so we don't have Multinet licenses. We had looked at Multinet as an option but it was way too expensive for what we are doing and for the number of licenses required. The DECnet file transfer is part of some old third party software. We do have source but we don't have the resources right now for a rewrite. That's the background; now for my questions: 1. We are looking at upgrading from Win 2003 to Win 2008. Is anyone in this forum successfully running Pathworks 32 7.4 on Win 2008? 2. The HP website simply says that PW32 has been retired and that customers may search for third party alternatives.  Can someone point me to a decent (and hopefully affordable) alternative? I'm coming up with all HP or university _link_s from Google. Thanks in advance. Frozen Vaxen. How chillen. I'm confused, I thought Pathworks ran on VAX (and Alpha) and used IP as a transport. I didn't know it had anything to do with Decnet. There are VMS versions of Samba but I don't know what would run on VMS 5.5-2 with OSU. You must be new around here! Before Pathworks was called Pathworks, it was known as DECnet DOS  I haven't done anything with Pathworks in many years now and it may support TCP/IP *now* but originally it was DECnet only!

Wouldn't Kermit be useful in this situation? There used to be a an IP stack that was free but I doubt it is still available. DECnet support outside DEC products is limited. There is a working opensource DECnet kit for Linux though. Hans I'm not sure I understand how Kermit could possibly intercept calls from the fortran code to decnet and put them on the windows machine. There is a free IP stack