Squidly_Man's Posts

Per the "VMware ThinApp 4.5 - What's New" article (http://blogs.vmware.com/thinapp/2010/03/vmware-thinapp-45-whats-new.html)...... Back in ThinApp 4.5 VMware released an "OptimizeFor=Disk" par... See more...
Per the "VMware ThinApp 4.5 - What's New" article (http://blogs.vmware.com/thinapp/2010/03/vmware-thinapp-45-whats-new.html)...... Back in ThinApp 4.5 VMware released an "OptimizeFor=Disk" parameter. New package.ini parameter: OptimizeFor      ThinApp 4.5 adds a new optional package.ini parameter called "OptimizedFor" which can be set to either "Memory" (default) or "Disk". ThinApp's new performance and memory sharing features may result in larger package files.  In the worst case scenario packages can be twice as large as  before but in most cases the size difference, if any, is will be less  significant. If disk size is more important than memory utilization and  startup performance, you can set "OptimizeFor=Disk" in package.ini under  [BuildOptions]. The result of such a change will cause package sizes to  be similar as 4.0.4 and lower. In ThinApp 4.5, virtual executable files  such as EXEs and DLLs are not compressed inside of packages on disk  even when CompressionType=fast is enabled unless OptimizeFor=Disk is  also set. This is primarily because VMware also included startup and bandwidth optimizations in the form of memory remapping to allow for faster starts and more efficient streaming into memory of the package contents. Startup time improvements      For many users,  application startup time is one of the most important criteria for user  acceptance. In ThinApp 4.5, many applications will start significantly  faster. For example, Power Point 2007 loads approximately twice as fast  compared with previous versions of ThinApp when launched from a local  hard drive with a cold disk cache. Time in seconds to startup Power Point 2007, 2nd+ execution, cold disk cache Bandwidth consumption improvements      Compared  with ThinApp 4.0.4, ThinApp 4.5 typically uses less bandwidth to stream  an application from a network share during initial application startup.  For Office 2007 applications, the amount of bandwidth consumed to  stream an application from a network share has been reduced by  approximately 50% (half the bandwidth required from 4.0.4). This  improvement comes from a new build optimization process that performs  static analysis on executable data and arranges packages such that less  executable code needs to be present on client systems in order to begin  execution. Example bandwidth consumption (in MB) when streaming Word 2007 All of this and much more can be read in the below ThinApp Blog article. VMware ThinApp 4.5 – What’s new? -Dean F. -http://pub.vmware.com/thinapp4/help/
Boot time services are possible if that is what you are looking for. When capturing your application with ThinApp, services will also be capture.  Before building the package, go into the PACK... See more...
Boot time services are possible if that is what you are looking for. When capturing your application with ThinApp, services will also be capture.  Before building the package, go into the PACKAGE.INI file and look for the [{Entry Point}] specific values (where {Entry Point} is the name of your service executables). [Entry Point] ;Services={service_name} Disabled=1 To make this virtual service appear as a Windows boot time service, unremark the Services= line and change Disable=1 to Disabled=0 (or just delete that line) and then build your package. As an example, I'm posting an Entry Point for the .NET FrameWork service for an application which needs .NET FrameWork started and running.  While this isn't needed for the ThinApp package to work (as the ThinApp package would just autostart the service), the end users complained of the startup time - therefore, registering the .NET FrameWork service within the ThinApp package as a service in the native system gets the ThinApp package launched on startup/login for the user. Here you will note I removed the "Disabled=1" line and the Services line is bolded. [mscorsvw.exe] Source=%SystemRoot%\Microsoft.NET\Framework\v2.0.50727\mscorsvw.exe Shortcut=PaintDotNet.dat Services=clr_optimization_v2.0.50727_32 Icon=%SYSTEMROOT%\SYSTEM32\Shell32.dll,14 -Dean F. http://pubs.vmware.com/thinapp4/help
I would suggest reviewing the ThinApp Blog article discussing the differences between the Isolation Modes, posted by Peter Bjork -  http://blogs.vmware.com/thinapp/2009/11/thinapp-101-differences... See more...
I would suggest reviewing the ThinApp Blog article discussing the differences between the Isolation Modes, posted by Peter Bjork -  http://blogs.vmware.com/thinapp/2009/11/thinapp-101-differences-between-the-isolation-modes.html -Dean F. http://pubs.vmware.com/thinapp4/help
1.  For this you may wish to have the SAP GUI ThinApp package dump to a native folder (i.e. a folder in your project set to MERGED isolation which, in the project, is empty).  That same folder fo... See more...
1.  For this you may wish to have the SAP GUI ThinApp package dump to a native folder (i.e. a folder in your project set to MERGED isolation which, in the project, is empty).  That same folder for the Office/Excel package should probably be marked in the same fashion but in reality only needs to be set to WRITECOPY for the Office/Excel ThinApp package to see it. The other way to do this is do a RequiredApplink in the SAP ThinApp package to the Office/Excel ThinApp package so it opens the ThinApp'ed Excel into the SAP ThinApp virtual bubble. 2.  You'll have to set (or reset if not correct) the Icon= value for the entry point.  See the ThinApp Help on how to do this. http://pubs.vmware.com/thinapp4/help/pkg_Icon.html Hope this helps! -Dean F. http://pubs.vmware.com/thinapp4/help
If it's a setting you can apply under the "Regional And Language" Windows Control Panel Applet, then I would speculate you might be able to virtualize it with ThinApp as ThinApp can isolate langu... See more...
If it's a setting you can apply under the "Regional And Language" Windows Control Panel Applet, then I would speculate you might be able to virtualize it with ThinApp as ThinApp can isolate language and locale info (since these are generally per user type of settings).  If, however, it's something you have to do at the system/kernel level, then I would say most likely no. Hope this helps, -Dean F. http://pubs.vmware.com/thinapp4/help
Once the new license is installed into ThinApp, you may also use Relink.exe to update the ThinApp packages with the new runtime (which includes the license as well). http://pubs.vmware.com/thina... See more...
Once the new license is installed into ThinApp, you may also use Relink.exe to update the ThinApp packages with the new runtime (which includes the license as well). http://pubs.vmware.com/thinapp4/help/wwhelp/wwhimpl/js/html/wwhelp.htm?href=upgrade_ThinApp_version_of_pkg.html
Referencing the ThinApp Troubleshooting procedures on the ThinApp Blogs (http://blogs.vmware.com/thinapp/2010/10/thinapp-troubleshooting-methods.html), I'd say you need to run a "washed" test nex... See more...
Referencing the ThinApp Troubleshooting procedures on the ThinApp Blogs (http://blogs.vmware.com/thinapp/2010/10/thinapp-troubleshooting-methods.html), I'd say you need to run a "washed" test next. That is, start removing the local components one at a time and re-test. At some point, the application should fail based on your production test scenario. However, if the the application doesn't fail, then run a "clean" test with the reverted snapshot of the CnB workstation. If the application passes that, then the issue is most likely an environmental one and thus you should consider those items associated it. As an example, I often name the CnB "localhost" so that any application that tries to pick the workstation name for the registry or some configuration would pick that name which can resolve to any local workstation. Testing Procedure   Dirty Test      A dirty test is one that is conducted on the CnB with the application still locally installed. Any issues arising from this test will most likely be code related and will present obvious issues right away.   Washed Test      Simply use Add/Remove Programs to uninstall the application from the CnB. Then run the ThinApp to test. If any issues occur here, the likelihood that they are related to missing components or settings is very high.   Clean Test      Revert your CnB back to a clean state and test your ThinApp. This test builds upon the ides of the washed test and will also provide insight to any potential issues that may result from files and setting that are not removed during an uninstall procedure.   Production Test      Using your ThinApp, test in a live production workstation. Local policy, security applications and other items may cause issues. This test will allow you to determine if problems are environmental in nature.<br><br><br><br><br>-Dean F. http://pubs.vmware.com/thinapp4/help
That's not an issue with Windows. If you count the number of characters in the "COPY TO" path in the above image, you'll see it's longer than the Windows XP maximum path length. Save the captur... See more...
That's not an issue with Windows. If you count the number of characters in the "COPY TO" path in the above image, you'll see it's longer than the Windows XP maximum path length. Save the capture to something shorter "Z:\Captures\{my project folder}" instead of installing to a different location on your capture and build (CnB) system. ThinApp troubleshooting blog articles (http://blogs.vmware.com/thinapp/troubleshooting) discuss this as a workaround to the Windows OS path length limitations. -Dean F. http://pubs.vmware.com/thinapp4/help
Have you seen this ThinApp Blog article? http://blogs.vmware.com/thinapp/2008/10/step-by-step-in.html I'm not totally certain (as I wasn't the author), but I believe this was the reason for t... See more...
Have you seen this ThinApp Blog article? http://blogs.vmware.com/thinapp/2008/10/step-by-step-in.html I'm not totally certain (as I wasn't the author), but I believe this was the reason for the VBScript. -Dean F. http://pubs.vmware.com/thinapp4/help
Your Entry Point source is listed as... Source=%Drive_C%\Program Files\NSWCCD\ASSET530\bin\assetwui.exe Try changing this to... Source=%ProgramFilesDir%\NSWCCD\ASSET530\bin\assetwui.exe ... See more...
Your Entry Point source is listed as... Source=%Drive_C%\Program Files\NSWCCD\ASSET530\bin\assetwui.exe Try changing this to... Source=%ProgramFilesDir%\NSWCCD\ASSET530\bin\assetwui.exe Also, try adding both a Working Directory and Command Line options. On the CommandLine= option, you can wrap it in quotes (maybe the program needs that) and add your necessary command line switches to the end (see my "{your switches here}" Example: Source=%ProgramFilesDir%\NSWCCD\ASSET530\bin\assetwui.exe CommandLine="%ProgramFilesDir%\NSWCCD\ASSET530\bin\assetwui.exe" {your switches here} WorkingDirectory=%ProgramFilesDir%\NSWCCD\ASSET530\bin -Dean F. http://pubs.vmware.com/thinapp4/help
Please see the ThinApp Release Notes for a list of some of the more prominent bugs resolved in ThinApp 4.6. http://tinyurl.com/ThinAppRelNotes -Dean F. http://pubs.vmware.com/thinapp4/he... See more...
Please see the ThinApp Release Notes for a list of some of the more prominent bugs resolved in ThinApp 4.6. http://tinyurl.com/ThinAppRelNotes -Dean F. http://pubs.vmware.com/thinapp4/help
See http://ora-12564.ora-code.com for a more detailed description on your posted Oracle error and what to do within Oracle to find the cause of the error... ...and... http://tinyurl.com... See more...
See http://ora-12564.ora-code.com for a more detailed description on your posted Oracle error and what to do within Oracle to find the cause of the error... ...and... http://tinyurl.com/263lzh3 for additional research and write-ups on the specific Oracle error. These may help shed light on what specific mods need to be made to the ThinApp package to make it a fully self contained and desktop non-specific app. -Dean F. http://pubs.vmware.com/thinapp4/help
The registry key to modify is:-Dean F. http://pubs.vmware.com/thinapp4/help
When you go to capture any Office app, just keep hitting cancel on the Name/Initals box. This will ensure this data is not captured. I believe the ThinApp blog articles (or at least the comme... See more...
When you go to capture any Office app, just keep hitting cancel on the Name/Initals box. This will ensure this data is not captured. I believe the ThinApp blog articles (or at least the comments) mention this. http://blogs.vmware.com/thinapp If you don't wish to recapture, you can always edit the HKEY_CURRENT_USER.txt file, provided you know the info to wipe. I don't have it at my fingertips, but when I find it, I'll make sure to post it. -Dean F. http://pubs.vmware.com/thinapp4/help
Sounds like you downloaded the View 4.5 Beta which includes the ThinApp beta. The ThinApp download from the ThinApp site is the 4.5 GA version (not the beta). -Dean F. http://pubs.vmware... See more...
Sounds like you downloaded the View 4.5 Beta which includes the ThinApp beta. The ThinApp download from the ThinApp site is the 4.5 GA version (not the beta). -Dean F. http://pubs.vmware.com/thinapp4/help
Also, if you're running ThinApp 4.5, you can run RELINK.EXE on your existing production packages on your network share to change out their ThinApp licenses - even if they are already built with T... See more...
Also, if you're running ThinApp 4.5, you can run RELINK.EXE on your existing production packages on your network share to change out their ThinApp licenses - even if they are already built with ThinApp 4.5. -Dean F.
Depending upon how your "utility functions" are called, you can set isolation parameters such as Folder Isolation settings to MERGED for those particular folders (or the whole project if you real... See more...
Depending upon how your "utility functions" are called, you can set isolation parameters such as Folder Isolation settings to MERGED for those particular folders (or the whole project if you really need it to see everything on the native system except the actual app). See the pub article "[Defining Isolation Modes for the Physical File System|http://pubs.vmware.com/thinapp4/help/setup_capture_define_isolation.html]" for additional assistance in File System Isolation. Additionally, depending if the call is for a child executable or for a secondary DLL (where the function is stored), you can define those to be executed/loaded external to the "Virtual Bubble" or within the "Virtual Bubble. Set "[ChildProcessEnvironmentExceptions|http://pubs.vmware.com/thinapp4/help/pkg_ChildProcessEnvExceptions.html#996885]" for specific DLLs which should be launched external to the Virtual Bubble (i.e. On the native system) and set "[ExternalDLLs|http://pubs.vmware.com/thinapp4/help/pkg_ExternalDLLs.html]" to define a DLL to be loaded by the Windows OS instead of the ThinApp Runtime. Also review the "[Configuring Objects and DLL Files|http://pubs.vmware.com/thinapp4/help/pkg_object_DLL_parameters.html]" document for good measures. :smileycool: -Dean F.
Currently it is not possible to exclude files from the sandbox which only exist within the Virtual Bubble and are opened with WRITE access. What GGeldorp suggested is probably the closest you ... See more...
Currently it is not possible to exclude files from the sandbox which only exist within the Virtual Bubble and are opened with WRITE access. What GGeldorp suggested is probably the closest you can get - assuming you add in some scripting as well. -Dean F.
Use either OnFirstParentExit or OnLastProcessExit to kill the process. The ThinApp Blog article "[Using IE 7 on Vista as a Virtual Entry Point|http://blogs.vmware.com/thinapp/2008/10/using-i... See more...
Use either OnFirstParentExit or OnLastProcessExit to kill the process. The ThinApp Blog article "[Using IE 7 on Vista as a Virtual Entry Point|http://blogs.vmware.com/thinapp/2008/10/using-ie-7-on-v.html]" has a great example of the kill-process-on-exit procedure. You can also review other ThinApp Blog scripts to see if they have more what you're looking for. -Dean F.
There are way too many possibilities here. So...rather than feed you the exact script (which would probably not work for your environment anyways ), let's post the things you need to know in... See more...
There are way too many possibilities here. So...rather than feed you the exact script (which would probably not work for your environment anyways ), let's post the things you need to know in the order you will probably want to learn them. How to Script within ThinApp - ThinApp Script Template - Scripting Validation Logic Into a ThinApp Project/Package - Google Search of VBScripting Subnet Detection Examples - -Dean F.