I reported this bug for Tokyo 10.2 Update 1. Can anybody confirm (just to make sure I'm not crazy)?

-
I reported this bug for Tokyo 10.2 Update 1. Can anybody confirm (just to make sure I'm not crazy)?

https://quality.embarcadero.com/browse/RSP-18768
https://quality.embarcadero.com/browse/RSP-18768

Comments

  1. Roy WollAugust 9, 2017 at 10:57 AM

    Mine are all updated after installing 10.2 Release 1
    https://plus.google.com/photos/...

    ReplyDelete
  2. Zachary BurnsAugust 9, 2017 at 11:10 AM

    Thanks Roy....I'll delete that directory and re-run the installer from the 10.2.1 ISO again and see what happens.

    ReplyDelete
  3. Alexander BrazdaAugust 9, 2017 at 11:40 AM

    I tested in MacOS 10.12 and works fine after re install paserver on mac from ..\Embarcadero\Studio\19.0\PAServer\PAServer19.0.pkg
    I have used web installer to update my instance (also it was installed with de web installer not ISO installer)

    ReplyDelete
  4. Zachary BurnsAugust 9, 2017 at 12:27 PM

    Reinstalling it from the ISO worked and things compile fine now. Thanks. I also updated my RSP ticket with Embarcadero. Thanks all!

    ReplyDelete
  5. InstallAware SoftwareAugust 10, 2017 at 9:00 AM

    Time and again, the ISO installer proves itself. I know the team are very excited about the work they have done for the new installer, but I would once again respectfully submit to their consideration the offer to modernize and unify the online/offline installers under the existing ISO model (which works online too anyways). There's a lot that can be improved across the board.

    ReplyDelete
  6. InstallAware SoftwareAugust 10, 2017 at 9:09 AM

    In fact, here's some low-cost high-impact ideas:

    1) Switch to the Native Engine and abandon the Windows Installer engine. The Native Engine runs circles around Windows Installer, requires substantially less temporary disk space (especially gigabytes less when uninstalling), and in general can be summarized as lightning-speed.

    2) Get rid of all the separate installation steps for things like .NET, MS SDK docs, etc. All of these can and should be consolidated into the main installation - so there are no surprise popups, and unattended installations succeed 100% without user interaction (be that when running a silent install, or an install started interactively but continued away from keyboard).

    3) Retain your security by authenticating web media block downloads from your own servers. As I had mentioned earlier, InstallAware can fetch web media blocks from locations held in script variables - which means you are free to use whatever authentication scheme you want to build on your servers.

    I understand the main reason InstallAware was dumped was the thinking that #3 is not possible with InstallAware...which is an unfortunate misunderstanding.

    I don't understand why they never switched to the Native Engine, which would have reduced installation speeds by 10 times, if not 100 or more (at least, with the latest "file copy physics" optimizations in InstallAware).

    Then again, the customer is always right - and there could be many things I don't know about.

    ReplyDelete

Post a Comment