DarrenJHron's Posts

Well, the problem is not that the process are failing directly.  It is that the Main application Thinstall directory sandbox gets corrupted. For example. On a fresh system, never run anything... See more...
Well, the problem is not that the process are failing directly.  It is that the Main application Thinstall directory sandbox gets corrupted. For example. On a fresh system, never run anything before, nothing installed (Well, windows of course) I launch Chrome Thinapp (Applinked to Java 60). It works fine. On a fresh system, never run anything before, nothing installed. I launch Chrome Thinapp (Applinked to Java 55). It works fine Then I close out chrome completely (saying this before someone asks) I update the Java location to the new Java 60 thinapp...using the exact same name as the previous java (or even utilizing inplace upgrade aka java.exe.1)....again Chrome is Applinked with this Java location/name I Launch Chrome Thinapp (Now applinked to Java 60) It throws an Error about the program being corrupt. I revert Java to 55 It throws the same error I Delete the Thinstall\Google Chrome directory Launch Chrome Thinapp Works fine Update to Java 60 Launch Chrome, it fails Delete the Thinstall\Google Chrome Directory Launch Chrome, it launches. The problem is that the update applink corrupts the working Thinstall Directory.  This is a major issue for users where they will all need to delete their Thinstall directory to allow for the browser to work.  This would also reset how they have tweeked their browsers.  In terms of maintenance this is an issue.  So, what did i miss?  IS it something with The Java Sandbox, or is this how updating applinked apps works?  As in it breaks the app until reset? Would merged isolation mode fix this?  What am I missing in how it works with a new thinstall directory vs updating an application that has already created that thinstall directory? Thanks, Darren
I have not found anything on this, but here is an issue regarding ThinAPP with an Applink App being updated. Thinapp5 is being used I have Google Chrome 34, for example, with Java 55 Applinke... See more...
I have not found anything on this, but here is an issue regarding ThinAPP with an Applink App being updated. Thinapp5 is being used I have Google Chrome 34, for example, with Java 55 Applinked, for example. It works. If I go and do an update and package Java 60, for example, put it in the correct place, and launch Chrome, I get an error that the program needs to quit. If I revert to Java 55, it still fails. Only when I kill the thinstall directory and relaunch does it work. Any ideas? (Before you ask, the thinapps are named the same, Java.exe , and both are located in the proper thinapp location.  The strange thing is that things work if the thinstall directory is nuked...and only an issue with  a change in thinapp)
I went to the adobe test flash page and to youtube (any video)  Both cases it would say that flash was not installed (this is in regards to  a thinapp that did not have an external flash player a... See more...
I went to the adobe test flash page and to youtube (any video)  Both cases it would say that flash was not installed (this is in regards to  a thinapp that did not have an external flash player applinked to it).  Providing more details to the problem would be a repeat of the issues discussed already (Response #16 in this very thread). If I disable pepperflash an applink to an adobeflash things seem to work. The relevant part here is that this icon issue popped up about the same time that I had to start disabling pepperflash This was using ThinApp 5. Perhaps it was related to it moving.  I saw the Pepperflash folder in my capture, but didnt dig in to see it is empty.  Perhaps it is a temp (sandbox?) location that breaks pepper flash it thinapp.  It was a wild conjecture that I noticed this icon problem is in a similar location to where pepperflash was one.....
When investigating the work around for the icon issue, I noticed that this local directory is the same location as the pepper flash, which seems to no longer work (the flash work arounds do work ... See more...
When investigating the work around for the icon issue, I noticed that this local directory is the same location as the pepper flash, which seems to no longer work (the flash work arounds do work by disabling pepper flash and app linking to an adobe flash).  Could the two be related?  As in some sort of permissions issue in reading those locations that are causing both the icon and pepper to not be found.  The two both USED to work a few versions ago, and at about the same time stopped.
No, nothing in the event log.
Hi, I'm strugging with Browsers, Flash, Java, and getting things to work. Information: ThinApp 5.0 Firefox 27 and 28 Chrome 32, 33 Flash 12.0.0.77 (.44 and other previous versions as ... See more...
Hi, I'm strugging with Browsers, Flash, Java, and getting things to work. Information: ThinApp 5.0 Firefox 27 and 28 Chrome 32, 33 Flash 12.0.0.77 (.44 and other previous versions as well) Java 7.51  (and a few previous versions as well) Whether I bake it into the browsers *OR* run through the process of applinking, it is not working properly. In the case of Java:  When I go to a java test page (the java.com one, not one of the other unsigned ones on the net).  It either doesnt load the plugin, and/or crashes the browser (ThinApp Firefox or Chrome) In the case with Flash, the Adobe test page seems to load fine.  Then one goes to youtube, and it seems all the adds play fine, but the ACTUAL youtube video plays 2 seconds and gives an error.  THis latter part ends up being a big issue, because there are alot of important in house training videos in youtube format (so it HAS to work).  For the life of me, I can not understand why the flash adds work no problem, but the "real" video crashes. Same thing happens in Chrome (though I know it has a built in pepper flash, that has to be disabled otherwise it thinks flash is NOT installed....then l bake in or app link the other flash and get the same above behavior) Again, it does not matter if it is baked in or app linked.  SAME behavior.
I'm going to +1 this issue as well.  I am going to also submit an additional discussion as I am having trouble with Flash integrating with the web browsers as well.
Point of clarification:  Is the bug report for Chrome flash not working or the taskbar issue?
This also sounds very very similar to what we have been running into.  I just wanted to add that others are having inexplicable performance issues.  Looking forward to see if the suggestions work... See more...
This also sounds very very similar to what we have been running into.  I just wanted to add that others are having inexplicable performance issues.  Looking forward to see if the suggestions work in our area.