|
Wednesday, 23 June 2010 |
|
Leading networking experts, including Jim Metzler, provide essential tips and strategies on how to rethink your management strategy and implement techniques that allow networking teams to understand performance, make the most of the infrastructure, and offload low-level tasks so that they can focus on improving performance and making progress.
Published by: SearchNetworking.com
Read more at: |
|
Read more...
|
|
|
Thursday, 27 May 2010 |
|
Attend this live webcast on May 27th and hear from Bo Raun, Search Architect at Nordjyske Medier's, as he discusses their IT strategy and how to make the transition to open source Solr.
Published by: Lucid Imagination and Findwise SE
Read more at: |
|
Read more...
|
|
|
Tuesday, 25 May 2010 |
Hi,
I have installed "oracle forms6 runtime + reports" as a Thinapp. The Thinapp works fine. I can also open the thinapp a second or third time.
But when I close the Programm the process "ifrun60.exe" remains active (Oracle Forms Runform)!!
If I try to start the programm again it waits until i kill the "old" process. After killing the process the thinapp application starts.
The Problem occurs on Windows7 32bit and 64bit.
Under Windows XP the thinapp works fine.
I tried to build the thinapp and run the thinapp in compatibility mode (Windows XP SP3) but the problem was the same.
With Process Explorer i only found out that some Threads are running. (some with Wait:UserRequest some with Wait:wrQueue)
When I install the "oracle forms6 runtime + reports" as a regular application under windows 7 it works fine.
No processes remain open when I close the application.
Are there parameter/switches for the thinapp.
Any suggestions, ideas?
Br
George
Read more at: |
|
Read more...
|
|
|
Tuesday, 25 May 2010 |
|
PC makers Acer, Asus, Lenovo and MSI are expected to introduce up to 40 new ultra-thin lightweight laptops based on Intel's new 32 nanometre core processors
Read more at: |
|
Read more...
|
|
|
Monday, 24 May 2010 |
|
Agreed, it does sound strange and would be something ThinApp should solve. I think you should file a support ticket so we could get this investigated in-depth.
Read more at: |
|
Read more...
|
|
|
Friday, 21 May 2010 |
Hello Phil,
the log monitor problem could be solved with a new install of ThinApp 4.5.
For dotNet and VC++ Runtime, we install them native on the machines. The capture machine also has the same dotNET and VC++ Runtime releases installed as the target machines.
Is there a problem using a native installed dotNet or VC++ runtime? Since it doesn't happened in 4.0.4. I think it should work.
Read more at: |
|
Read more...
|
|
|
Friday, 21 May 2010 |
|
For all of you Mac users out there, you already know that VMware Fusion is a fantastic tool that lets you have your cake and eat it too. Personally, I love VMware Fusion. I'm not a huge OS X guy, but love my shiny MacBook Pro. But, without Fusion, I wouldn't be doing much with the machine.
. more...
Read more at: |
|
Read more...
|
|
|
Thursday, 20 May 2010 |
|
checkout http://blogs.vmware.com/thinapp/2009/05/internet-explorer-plugins.html its probably a plugin conflict or isolation issue.
Read more at: |
|
Read more...
|
|
|
Thursday, 20 May 2010 |
ezequiel,
your Excel2007.exe entry point is pointing to E:\Program Files\Microsoft Office\Office12\EXCEL.EXE. Did you install to E:\? and is there an E:\ drive available to be read from on the other machines?
I doubt this is related but your OptionalAppLinks= line is incorrect:
ptionalAppLinks=plugins\*.exe
You also mention that you ran it on the server you captured on, but it won't run on the PCs. You should try packaging on a clean PC rather than a server OS.
Phil
Read more at: |
|
Read more...
|
|
|
Thursday, 20 May 2010 |
Lars, you will need to use something like:
CommandLine=cmd.exe /c start /min /b batchfile.bat
an alternative to this is to use a VBS script with a line similar to this:
oShell.Run Chr(34) & "batchfile.bat" & Chr(34), 7, True
the window display can be changed by changing the integer - see http://msdn.microsoft.com/en-us/library/d5fk67ky%28VS.85%29.aspx
Phil
Read more at: |
|
Read more...
|
|
|
Thursday, 20 May 2010 |
Ghoost,
you forgot one method:
Method3: Virtualize the application on a clean machine and use APPLINK.
Allows you to deploy the application on any machine and provide reuse of the .NET 3.5 application files to other ThinApps.
Eg: Office 2010 needs .Net 3.5.
1. dotNet3.5 is not installed natively.
2. Run Prescan.
3. Install dotNet3.5.
4. Run Postscan and build the dotNET3.5 package.
5. Run Prescan.
6. Install Office 2010.
7. Run Postscan and edit the PACKAGE.INI changing the OptionalAppLinks= parameter to specify the dotNET3.5 package.
8. copy the dotNET3.5 package to the folder specified by the OptionalAppLinks= parameter, which is usually a relative folder path, to the Office2010 package
NOTE: This package should work on any machine with the same or newer OS/SP level as the package machine.
Phil
Read more at: |
|
Read more...
|
|
|
|
<< Start < Prev 1 2 3 4 5 6 7 8 9 10 Next > End >>
|
| Results 1 - 21 of 1242 |
