No announcement yet.

Access Client Solutions splash screen disappeared in

  • Filter
  • Time
  • Show
Clear All
new posts

  • Access Client Solutions splash screen disappeared in

    I have installed Access Client Solutions version in order to test it before it is rolled out in production.

    It looks like the splash screen has disapeared and I know for sure that this will cause our users to
    click multiple times on the icon believing they haven't hit it.

    Am I doing something wrong?
    Or have IBM removed it?

  • #2
    Does that mean that none of you are using ACS?


    • #3
      Clicking on Access Client Solutions displays a very quick screen, then takes about 20 seconds to display the main screen. Yes, it will probably cause users to click the icon more than once; I did the first few times I clicked on it.


      • #4
        Honestly, I hadn't noticed that the splash screen was gone... but, you're right, it's gone.

        Curiously, if I start it from an MS-DOS prompt by switching to the appropriate directory and running "java -jar acsbundle.jar" it will show a splash screen. But, if I start it via the icon it installs in Windows, it will not. Likewise, if I manually modify the icon to run the same "java -jar" command, it will not show the splash screen.

        It really doesn't matter to me if its shown or not.


        • #5
          Thank you very much for your replies.

          @Scott: you are right - it is shown when starting it from the command line but not in the other situations.
          It might not being a problem because we are starting it from a bat file calling java.
          But in previous versions the splash screen were missing and this gave us problems because the users clicked
          multiple times on the icon getting black screens because they haven't entered their credentials at that time.
          Then they called support for help.


          • #6
            I am having the same issue. Users are getting very confused. Has anyone found a work around?


            • #7
              Originally posted by jkaufman View Post
              I am having the same issue. Users are getting very confused. Has anyone found a work around?
              Actually I came up with a solution

              Using group policy I am creating an icon on everyone's desktop that points directly to the .jar file. Since all users have the same .hod filename and path, I can pass that in as an argument. User double clicks "Terminal A" or "Terminal B" icon and ACS displays the splash screen and then opens the 5250 session


              • #8
                Custom software development is basically the designing of software programs for a single user or a set of users in an organization. Such software is specifically designed to better address the unique needs of these users better than more widespread and general off-the-shelf software available in the market. Such custom software development services involve much more than just coding the program-it involves building it from scratch so as to be able to meet the needs of the individual customer. The entire process of custom software development involves much more than just coding however, because the very nature of software development itself requires for a series of "customization" (or personalization) efforts before a final product (code) is ready to go. Perhaps one of the most prominent examples of custom software development services is that of Apple's iPhone and iPad. The iPhone was specifically designed with its user in mind. It is a touch screen mobile device that allows its owner to browse the internet, listen to music, take pictures and videos, check emails, check maps and more without having to physically touch the device. The unique iPhone's design also made it highly susceptible to being damaged or broken, which required a lot of user intervention in terms of repositioning the device, having it secured in a pocket or car, and so forth. In contrast, the Android mobile applications designed for the Android platform do not suffer from these limitations because they run primarily on a standard interface and they are developed using standard software that has been standardized across many different platforms.