Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Can not install v12 runtime as path too long in Windows7

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Can not install v12 runtime as path too long in Windows7

    Have a look at the picture, my laptop can not handle such a long path...needless to say this was NOT a problem in v10.5, course they did not have all the node_modules and its many sub-levels as in pic.

    What is the work around?

    Thanks.

    dewayne
    Attached Files

    #2
    Re: Can not install v12 runtime as path too long in Windows7

    IT would seem the path is really too long to me.
    But, I don't use paths that long for anything
    Dave Mason
    [email protected]
    Skype is dave.mason46

    Comment


      #3
      Re: Can not install v12 runtime as path too long in Windows7

      You will note that almost 90% is coming from the v12 runtime. Very little from our app about 20 characters from our app (Pro Maintainer v12 demo). How would you handle the remaining text....? Can you recommend a shorter path? Thanks.

      Comment


        #4
        Re: Can not install v12 runtime as path too long in Windows7

        My apps are usually in a folder like c:\\abc\datafile
        Installing alpha using an installer is done with the /s switch and automatically goes in the progfiles folder. Since I use a .exe to run the app, I just let the installer place it in the runtime folder. Understand, this is a new way for me, so I may find some bugs with it, but so far, it is working.
        my paths never have spaces or real long names though.
        Dave Mason
        [email protected]
        Skype is dave.mason46

        Comment


          #5
          Re: Can not install v12 runtime as path too long in Windows7

          Evening.

          This is our Target path on the Desktop ICON.

          F:\Factory_A\A5V12 Runtime\alpha5.exe" F:\Factory_A\Application\PM Pro Web.adb -icon="PMProWebv12.ico" -title="Factory A"

          Alpha Anywhere Runtime goes into A5V12 Runtime.
          our app goes into Application

          Does not seem too complex. Can you see a problem there? In over 15 years since v4 not a problem with this path.

          In my initial post it is the LONG names in the alpha anywhere that are causing the problem.

          v10.5 and earlier was not getting an error.

          dew

          Originally posted by DaveM View Post
          My apps are usually in a folder like c:\\abc\datafile
          Installing alpha using an installer is done with the /s switch and automatically goes in the progfiles folder. Since I use a .exe to run the app, I just let the installer place it in the runtime folder. Understand, this is a new way for me, so I may find some bugs with it, but so far, it is working.
          my paths never have spaces or real long names though.

          Comment


            #6
            Re: Can not install v12 runtime as path too long in Windows7

            Do other directories get created but the installer balks on the indicated directory? I ask because I don't see an explicit statement that the path is too long, just that it can't be created. Does the installer work on other machines than your laptop?
            There can be only one.

            Comment


              #7
              Re: Can not install v12 runtime as path too long in Windows7

              I just retried it on an older laptop win7 machine here and it went right in. No issues. Maybe a bug report could help?
              Dave Mason
              [email protected]
              Skype is dave.mason46

              Comment


                #8
                Re: Can not install v12 runtime as path too long in Windows7

                Thanks for the suggestion. Once the Christmas festivities have quieted down, I will do that.

                Comment


                  #9
                  Re: Can not install v12 runtime as path too long in Windows7

                  From #4 above: Alpha still creates it' own shortcut on the desktop, so I found this works.
                  Batch run by the installer with del "%HOMEDRIVE%%HOMEPATH%\Desktop\amgsrt.lnk" in it. deletes the named shortcut. "amgsrt.lnk" needs to be renamed to match the alpha shortcut name to work.
                  like: del "%HOMEDRIVE%%HOMEPATH%\Desktop\alphav12Runtime.lnk" or such as is normal
                  Dave Mason
                  [email protected]
                  Skype is dave.mason46

                  Comment


                    #10
                    Re: Can not install v12 runtime as path too long in Windows7

                    Top of the Christmas Season to you. What installer do you use? We have tried 3 installers & some work on Windows 7 but crash when using same install template on Windows 10. Otherwords, both machines are compiling the same installation exe of the same folders.

                    Originally posted by DaveM View Post
                    From #4 above: Alpha still creates it' own shortcut on the desktop, so I found this works.
                    Batch run by the installer with del "%HOMEDRIVE%%HOMEPATH%\Desktop\amgsrt.lnk" in it. deletes the named shortcut. "amgsrt.lnk" needs to be renamed to match the alpha shortcut name to work.
                    like: del "%HOMEDRIVE%%HOMEPATH%\Desktop\alphav12Runtime.lnk" or such as is normal

                    Comment


                      #11
                      Re: Can not install v12 runtime as path too long in Windows7

                      astrum
                      Most of my installs are now on wi10, but I have windows 7 here and test with it.
                      I actually install to c:\temp3 and then run the alpha installer from there. Then the bat file to delete the shortcut.
                      the app files get placed in whatever folder I need or the user prefers.
                      Special work for clients, I get the name of their server and folder we are going to use and then place the data files there. I pre-shadow the db and then send the files to that designated folder. My exe starts alpha with all paths already set in the client scenario. so there is a shortcut built straight to my .exe in the alpha folder
                      Do not wish to confuse the user( my apps can do that later)
                      Last edited by DaveM; 12-28-2016, 10:53 PM.
                      Dave Mason
                      [email protected]
                      Skype is dave.mason46

                      Comment


                        #12
                        Re: Can not install v12 runtime as path too long in Windows7

                        Thanks for that....what installer do you use to COMPILE the application? We use CreateInstall. Seems we get a createinstall crash everytime it gets to node_modules in the v12 runtime. If we REMOVE node_modules from the v12 runtime...the exe is compiled PERFECTLY.

                        Curious ERROR when we deleted the node_modules from the runtime. Check pic below



                        What to do? Change installer that we have been using for 8 years or ?

                        My ? to Alpha, why such a LONG path name for the various folders in node_modules. This not only crash's our installer but gives an error when I delete this folder.

                        Comment


                          #13
                          Re: Can not install v12 runtime as path too long in Windows7

                          The really long paths are out of our control, and cause problems for our own installer as well. The paths come from (and are dictated by) node.

                          Instead of "installing" the node files, we use a zip file of the node folder, and extract the zip into the target location. This bypasses the path length issues. (This is the command prompt you may see open up during the Alpha Anywhere installer with a bunch of text quickly scrolling by.)

                          If you are building your own installer instead of using the runtime installer, you could zip up the node_modules folder from your installation, then have your installer extract the zip to the target directory.

                          Lenny Forziati
                          Vice President, Internet Products and Technical Services
                          Alpha Software Corporation

                          Comment


                            #14
                            Re: Can not install v12 runtime as path too long in Windows7

                            thanks for that, I will have our programmer test it out. We use CreateInsall & have been for years. I do not understand how a folder within the runtime is out of your control. Like I said that folder (node-inspector) was NOT there in the first few flavours of the runtime as we added patches. Does deleting the node-inspector have ANY impact on our desktop version which is 99% of our users? Could you also give me more details on your "runtime installer" you refer to.

                            Comment


                              #15
                              Re: Can not install v12 runtime as path too long in Windows7

                              I'm not the person that creates the Alpha installs, but I'll certainly share what I know.

                              What is used by Alpha Anywhere is not out of our control. We have made a conscious decision to use node for the significant functionality that it offers, so we include it. However, we have no control over the paths required by node and cannot modify them, or node will not operate. Many in the development community at large consider node's path structure to be "broken" for a number of reasons - if you explore the node_modules folder, you will see very deep nesting and many duplicated files. Alpha cannot do anything about this except remove the functionality from the product, which is not something that we will be doing.

                              When I say "runtime installer", I am referring to a5v12_RuntimeSetup.exe which we distribute to customers that purchase the Alpha Anywhere runtime. This is an installer executable created using Wise. Like your installer, it also cannot install everything under the node_modules folder because of path length problems. As a work-around, we do not "install" these files from Wise, but instead have Wise unzip an archive to the node_modules folder.

                              The recommended way of installing your own runtime applications is to use this installer and then install any other files needed for your specific application. That can be wrapped in your own custom installer, put into a zip file, or any number of other methods to distribute what you have built. If you use this recomended approach, our installer will handle the long paths under node_modules for you, as described above. If you do not want to (or cannot) run the Alpha-supplied installer, then it would be up to you to come up with a similar work-around to handle the path length limitations.

                              I am not familiar enough with the individual node packages to comment on which ones may or may not be strictly required. Furthermore, which ones get used will depend on the exact functionality in your application. In general though, Alpha Anywhere functionality DOES use node even for desktop applications.

                              You could try moving/renaming/deleting a folder within node_modules (e.g. node-inspector) and then test your application to see if it is still fully functional. That would be the only way to know for sure if it is required for your specific application.

                              Lenny Forziati
                              Vice President, Internet Products and Technical Services
                              Alpha Software Corporation

                              Comment

                              Working...
                              X