Hey Chris,



 Thanks for the reply.  When you say 6.3 is "hard wired" for jdk 1.7 can you be more specific?  I remember having to go through a bunch of config files and manually change settings to a newer jdk for this client on a previous version of EAS.  Not sure if it was 6.2 or 5.x, but I had to set the jdk manually along with path to the new jdk.  Guess it's going to be an adventure again trying to get up to 1.8.



 



Do you have any old clients still running EAS?  If you do, do you remember their configuration in terms of PB/EAS/JDK versions?  My end goal is to get them on PB2017 client (or 12.x if I have to) and maybe 12.x VM/components on EAS with the highest jdk I can get to work.  I remember that EAS 5.5 performed much better and was more stable, so ideally if it will install and run, that would probably be the best solution if it's even possible.  Thanks again and any additional help would be appreciated.

Hi Kevin;



   By "hard wired" I meant at installation time. You are correct ... its a bit of a PIA - but, you can change the configuration files to utilize a newer JDK.



   From my consulting days, I only have one GOC client that is still running EAS 5.5. They could not move to 6.x due to the performance degradation.



   For EAS migration though to .NET Web Services, I would contact Mr Don Clayton at Intertech. They have a lot of EAS experience and some novel ideas on how to migrate to IIS  and preserve most of the EAS features that your Apps might be using.



HTH



Regards ... Chris

I would think the PBVM version running on EAS would have to be the same as what you're deploying from, but maybe not.  The client in question does not currently have PB2017 so I can't try this out (yet).  I'm going to upgrade one of their current EAS apps to 12.5 or 12.6, whatever they have in house.  I know they at some point want to get at least the client portion on a supported release, so I'll probably first bring them up to 12.x, then maybe PB2017 if they decide they want to go that far.  Does PB2017 still have a PBVM?  Maybe I'll mess around and try to get that running on their dev EAS box or maybe a dev machine just for kicks and giggles, lol.  I know Chris had a bunch of EAS stuff running for Canada.  Idk if they have migrated them all or not.  I want to find out what others are doing if they are not rewriting at this time.

You said: "I can't verify because the version of EAServer I have won't install on Windows 10."  Does it really not install at all, or just installs but won't run?  Based on the version of Java the machine is at, there may be a bunch of config changes you need to make.  Last time I did work for this client, I think we upgraded to Java 1.5 or 1.6 and I had to make a whole lot of config file changes manually just to get it to run.

The PBVM install is just a group of runtime files that are also used by desktop apps. PBVM170.DLL is the main VM file