1.The SIEBEL add-in uses SIEBEL Automation API, so if a SIEBEL application is lauched before QTP, QTP will still be able to indentify the Siebel objects. This is because even though Siebel runs inside a web Browser, QTP will not identify the Browser properly but rather identify it as a normal native window.
2.Any Windows application that uses just native Windows objects (Windows, Dialog, WinEdit etc) can be lauched before QTP itself. QTP uses native system APIs (Let FindWindow, FindWindowEx etc.) to identify these objects and is therefore not dependent no the prior lauching of QTP. Java applications also can be identified even if the application is lauched before QTP. QTP uses three Windows environment variables (_JAVA_OPTIONS, IBM_JAVA_OPTIONS and JAVA_TOOL_OPTIONS) to inject its JVM hook and the application is hooked irrespective of whether QTP is lauched or not.
3.The SAP add-in uses SAP Scripting GUI and therefore a SAP GUI application will still be identified correctly even if lauched before QTP.