Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (5)

Resolved PB2019 Runtime Installer still 32-bit?

  1. Misc
0
Votes
Undo
  1. Dale Fuller
    Dale Fuller
  2. PowerBuilder
  3. Friday, 14 June 2019 20:55 PM UTC

Just started playing with PB2019.  One of the things I checked that has been an issue for a couple years, is the Runtime packager still seems to be creating a 32-bit installer.  When is this going to be fixed?  Packaging for a 64-bit app dlls and then proceeding to install to a directory under C:\Program Files\...  still is being re-directed to the (x86) directory.  That should not happen!  It makes the packager virtually useless for deploying 64-bit runtimes.  :(   

A little disappointed.  Assume it will eventually get straightened out.

  1. 32-bit
  2. 64-bit
  3. DLL
  4. Runtime Packager
PDF Document Properties
using x.509 certificate with restclient in PB2019 ...
Responses (5)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 14 June 2019 21:10 PM UTC
  2. PowerBuilder
  3. # 1

Hi Dale;

   There should be a choice in the PB Packager utility between deploying a 32bit or 64bit run-time, as follows:

HTH

Regards ... Chris

Comment
Roland Smith
  1. Roland Smith
  2. Saturday, 15 June 2019 13:27 PM UTC
The question was about the installer itself, not the contents of it.
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Saturday, 15 June 2019 14:18 PM UTC
The key is the MSI bitness being generated. Not the bitness of the Packager. ?
  1. Helpful
There are no comments made yet.
Dale Fuller
Dale Fuller Accepted Answer Pending Moderation
  1. Sunday, 16 June 2019 14:51 PM UTC
  2. PowerBuilder
  3. # 2

The biness of the created msi.  Or, atleast how it is designed to behave.  Running an msi containing 64-bit components, when prompted for the install location,  if you specify  "C:\Progam Files\PBdll"   and click next.  The msi installs them under "C:\Progam File (x86)\PBdll".  Causing you to manually move the directory to where you want it and edit the path to reflect the change. 

Comment
Roland Smith
  1. Roland Smith
  2. Sunday, 16 June 2019 19:49 PM UTC
You should report that as a bug.

https://www.appeon.com/standardsupport/search

  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 17 June 2019 14:15 PM UTC
  2. PowerBuilder
  3. # 3

Hi Dale;

   I verified this morning that the 64bit MSI installer will ignore your request to install the PB 64bit run-time into the "C:\Program Files" folder and will always install the 64bit run time into the "C:\Program Files (x86)" folder instead.

  As Roland suggested, please open a support ticket for this issue. This is certainly a bug!

Regards ... Chris

 

Comment
Dale Fuller
  1. Dale Fuller
  2. Monday, 17 June 2019 18:00 PM UTC
Will do Chris. It's been a "bug" since the inception of the 64-bit binaries. Pretty basic and obvious one. Surprised it's slipped through this long.
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Monday, 17 June 2019 18:37 PM UTC
Hi Dale;

Saw your ticket .. thanks! Yes, Appeon is still working through Sybase legacy issues.

All: Please don not hesitate to open a Support Ticket for these legacy issues if you still encounter them. That way, it gets them on Appeon Engineering's "formal" ToDo list. ;-)

Regards ... Chris
  1. Helpful
There are no comments made yet.
Mark Lee @Appeon
Mark Lee @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 18 June 2019 09:29 AM UTC
  2. PowerBuilder
  3. # 4

 

Hi Dale,

Thanks for reporting this problem, we reproduced it on our end. 
You are correct about it. This issue exists since PB 12.6. Due to that the
created MSI installation package itself is a 32-bit application, if a user
specifies “C:\Program Files\...” as its installation path under 64bit OS, the
OS will redirect the installation path to "C:\Program Files (x86)\..."
automatically.

However, even though these 64 bit runtime files are installed to "C:\Program
Files (x86)\...", it won’t affect the normal use of your 64-bit PB application.
For example, accessing 64 bit ODBC data store or 64 bit registry nodes, etc. We
will consider supporting to install the 64 bit runtime files to "C:\Program
Files\..." in later versions.

Note: in PB 2019, the default installation paths of 64 bit/32 bit runtime
package in 64-bit OS are different: 
64 bit runtime package
C:\Program Files (x86)\Appeon\Shared\PowerBuilder\x64\ 
32 bit runtime package
C:\Program Files (x86)\Appeon\Shared\PowerBuilder\

But if this issue affects the actual use of your 64 bit application, please
open a new ticket with a reproducible small case. Thanks.

Regards,
Mark Lee
Comment
Dale Fuller
  1. Dale Fuller
  2. Tuesday, 18 June 2019 17:21 PM UTC
It's more of a conceptual thing. 64-bit apps and components belong under Program Files. 32-bit apps under (x86). And if you have both 32 and 64 bit apps (perhaps 3rd party) and you need separate paths for the different components... Tho you then have to play games with links and system32 and SysWOW64 directories.
  1. Helpful
Mark Lee @Appeon
  1. Mark Lee @Appeon
  2. Monday, 25 January 2021 03:25 AM UTC
Hi Dale，

Good news that PowerBuilder 2019 R3 GA (build 2670) is available for download. The issue you reported has been fixed in this release. Please download and install it to verify the issue you reported and let us know if any problems. You can get the installer from our Downloads portal at https://account.appeon.com/download/2019 (login required).



We welcome all feedback from you!



Regards,
  1. Helpful
There are no comments made yet.
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Monday, 25 January 2021 03:33 AM UTC
  2. PowerBuilder
  3. # 5

I recommend using the PowerClient feature of PB 2019 R3 and get rid off hassle of installing and updating desktop apps. It supports 64-bit, takes care of runtime and external DLLs, supports incremental updates, and has bunch of new security features.  https://www.appeon.com/conference/elevate-2020/live?id=288
 
By the way, we fixed the issue you mentioned in PB 2019 R3.  So even if you don’t want to use PowerClient, you should still upgrade.

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.