Welcome to Thinstall VS
Top  Next

Welcome to the Thinstall Virtualization Suite 3.0


The following links are useful to have:

Getting started: A quick walk-thru of how to capture and build virtualized applications  
Features: A list of a few key features in Thinstall  
Flash walk-thru demos:  
How to Thinstall an Application 
   Takes you through the process of virtualizing an application with Thinstall 3.0  
How to Thinstall IE based Java applets 
   Learn how to Thinstall the Java Runtime Environment and the host PC's Internet Explorer to run web applets without installation.  
How to Thinstall a .NET 2.0 Application 
   Learn how to Thinstall a .NET 2.0 application. See how Thinstall 3.0 can be used to package the .NET framework. (10 min)  
Thinstalling ActivePerl 
   Learn how to Thinstall ActiveState ActivePerl plus a perl script into a single EXE and have it run with a click and no installation.  

Thinstall 3.0 Discussion forum.
· Find out what apps other users have tested  
· Post your results  
· Request features  
· Ask general questions about Thinstall  
· Various tips & tricks, direct from the Thinstall development team  
    (you must be logged into your account to access the blog & discussion forum)

Changelog : What's new in this version
Reporting bugs and issues.  
Ideally we would like 2 things for any failing case:  
1. Trace files for the failing situation. Trace files record everything the application does and can often help us pinpoint problems without needing to reproduce the issue here.  
How to produce a trace file:  
- Before executing your Thinstalled application, please execute the program "Log Monitor". If you are testing your virtualized app on another PC, Log monitor can be run from a network share without installation.  
- Run your Thinstalled app until it fails or operates differently from the native version. At this point use the task manager to kill the application if a error message has appeared. By terminating the application soon after the error occurs, it limits the amount of extra information that needs to be recorded and sifted.  
2. We would like to be able to reproduce the problem here. To do this we will need a ZIP of your Thinstall package and detailed instructions on what to do if the problem does not occur on immediate startup. You can attach the ZIP file to your support ticket using the web interface or upload it using ftp to thinstall.com (user/pass = thinstall/thinstall). When creating the ZIP file, we do not need the "bin" directory since that is easy to recreate here, but we do need the project files produced by SetupCapture.  
If you can't send us the package files, the trace often provides enough clues to determine what is happening. A few common reasons people are not able to send us their captured package files:  
- Package files contain confidential information  
- Application requires a server component and the error does not occur until after connecting to the server  
To report a bug or problem, please log into your online Thinstall account at http://thinstall.com and open a trouble ticket