1. Jay Hastings
  2. PowerBuilder
  3. Monday, 4 May 2020 21:04 PM UTC

Installed PB 2019 on a Windows 10 machine. Migrated my apps from 12.6.  Compiled in 32 bit. Runs fine on that Windows 10 machine.  Running from Windows 7 complained of missing DLLs.  Got all the dlls listed in Help "runtime files" as being Core runtime files.  It keeps complaining that PBVM190.dll is not designed to run on Windows.  I then ran the runtime packager on my Win 7 machine but still no luck.

We're moving from Win 7 to Win 10 but it will take some time.  We're hoping to have one version of our apps that will run on both Win 10 and Win 7.

Is that possible and if so, what do I need to do?

 

Thank you

Jay

Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 4 May 2020 21:16 PM UTC
  2. PowerBuilder
  3. # 1

Hi Jay;

   Did you also copy to the deployment PC the following W7 DLLs: ATL80.dll, msvcp80.dll and msvcr80.dll files?

Regards ... Chris

 

 

Comment
  1. Roland Smith
  2. Tuesday, 5 May 2020 18:41 PM UTC
PB 2019 uses the 100 series C Runtimes. The only reason msvcr80.dll is required is the that the lib* dlls require it. From my testing the following are the bare minimum required:



atl100.dll, libjcc.dll, libjtml.dll, libjutils.dll, libsybunic.dll, msvcp100.dll, msvcr100.dll, msvcr80.dll, nlwnsck.dll

PBDWE190.DLL, PBSHR190.DLL, pbsysfunc190.dll, PBUIS190.dll, PBVM190.DLL



Of course the database driver will also be needed, PBODB190.DLL for example.

  1. Helpful
  1. Chris Pollach @Appeon
  2. Tuesday, 5 May 2020 19:07 PM UTC
Correct Roland but, the 80 series DLL's are required for W7 - not W10.
  1. Helpful
There are no comments made yet.
Jay Hastings Accepted Answer Pending Moderation
  1. Monday, 4 May 2020 21:24 PM UTC
  2. PowerBuilder
  3. # 2

Those are on the Win 7 machine in Windows/winsxs (and other directories).  I assume they were either there or the runtime packager installed them.

Comment
There are no comments made yet.
Arnd Schmidt Accepted Answer Pending Moderation
  1. Tuesday, 5 May 2020 08:03 AM UTC
  2. PowerBuilder
  3. # 3

Make sure you built and installed the correct "bitness" runtime Version, x64 (64-bit) vs. x86 (32-Bit).

hth .. Arnd

 

 

Comment
  1. Jay Hastings
  2. Tuesday, 5 May 2020 15:38 PM UTC
Yes. Compiled in 32 bit.
  1. Helpful
There are no comments made yet.
Ganesan Rajan Accepted Answer Pending Moderation
  1. Tuesday, 5 May 2020 12:44 PM UTC
  2. PowerBuilder
  3. # 4

Hi,

Add the dependency DLLs' file path in the system's environment variable. This may help.

 

Thanks,

Ganesan R

Comment
There are no comments made yet.
Olan Knight Accepted Answer Pending Moderation
  1. Tuesday, 5 May 2020 13:51 PM UTC
  2. PowerBuilder
  3. # 5

FYI -

   This is the minimal set of DLLs required to run a PB v12.x Classic 32 bit application:

 

Later -

 

Olan

Comment
  1. Jay Hastings
  2. Tuesday, 5 May 2020 15:37 PM UTC
I've been running PB 12.x for years. I'm migrating to PB 2019 to run in Windows 10.
  1. Helpful
There are no comments made yet.
Kenneth Davis Accepted Answer Pending Moderation
  1. Wednesday, 6 May 2020 19:00 PM UTC
  2. PowerBuilder
  3. # 6

Make sure you test the install on a Windows 10 machine that is not your PB2019 development pc.  

You might also try using dll walker on the W7 pc.   Hope this helps. :)  Ken

************

Similar errors..  

How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7

http://support.microsoft.com/kb/929833

 

 

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.