Sponsored Content
Top Forums Programming The application was unable to start correctly(0xc0150002). Post 302992083 by SA_Palani on Tuesday 21st of February 2017 11:01:30 AM
Old 02-21-2017
Tools The application was unable to start correctly(0xc0150002).

Dear Team,

please help me on the issue "The application was unable to start correctly(0xc0150002).click ok to close the application"

Have created the build using installshield 2012. dll was generated from VS2008. Used 3rd party libraries.Included all the libraries,dll.
This was the first tme creating the installer using installshield. saw multiple sites were talked about his .I tried to resolve this issue following those guideline.still not able to find it out.

Thanks,
Regards,
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Start application after Oracle has started

Who can tell me how I can see to it that a application doesn't try to start it's processes untill Oracle has completely started. Thanx. (3 Replies)
Discussion started by: Piet
3 Replies

2. UNIX for Dummies Questions & Answers

how do i auto start application upon startup?

sorry, i'm a newbie to unix... but how do i or rather where do i write scripts that auto start my application e.g. Informix? in Windows it would be services but in UNIX where can i auto start my informix program? To run informix i just type "oninit". And do i have to login to any user before... (2 Replies)
Discussion started by: doofie
2 Replies

3. Linux

where to put an application if i want to start it on start up

hi i want to know the way by which i put any file somewhere and it get s started when the system restarts or bots i mean whenever my system starts that application must also start thanks (3 Replies)
Discussion started by: shukla_chanchal
3 Replies

4. Shell Programming and Scripting

Start and stop of an application thru shell scripts.

Hi, I just learnt the shell scripting and got working on that right now. I have one problem. Here i am having a java application that needs to be start and stop using two shell scripts, i.e., starting the java application using one shell script and stopping the application using another... (1 Reply)
Discussion started by: sadha
1 Replies

5. Shell Programming and Scripting

Unable to display correctly the contents of a file without a line feed

I am using AIX and ksh. I need to display the contents of a file that has a pid (process id). Because the file is open, it doesn't have the line feed or new line, so for some reason if I do this: `cat $pid` , where $pid is the name of the fully qualified file, it displays test3.sh: 426110:... (1 Reply)
Discussion started by: Gato
1 Replies

6. Shell Programming and Scripting

How can I start a SH application when someone makes a ssh connection?

Hello everyone, I'm trying to control the access in my server. I did an application that can read audit logs and sys logs with the purpose to send me a report by email with important information about the user. It's a SH file. My problem is start the program when someone makes a ssh connection.... (4 Replies)
Discussion started by: journey
4 Replies

7. UNIX for Dummies Questions & Answers

How to start application and keep script running

What I'm looking for is best explained with a little example. #!/bin/bash gedit echo "I need this message to appear while gedit is still running, but it appears only then when I close gedit." Of course most of the times you want the script to wait, but in this case I want to start a new... (5 Replies)
Discussion started by: MrZehl
5 Replies

8. UNIX for Advanced & Expert Users

script to remotely start an application instance

just wanted to ask if anybody have script template for the subject above so I can make ti as my guide? example a. server 1.1.1.1: restart script located at /etc/init.d/glassfish.sh b. server 2.2.2.2: central script that support admin will use to execute to restart the /etc/init.d/glassfish.sh... (0 Replies)
Discussion started by: lhareigh890
0 Replies

9. UNIX for Dummies Questions & Answers

Shell Scripting Stop/Start Application

I did a search of these forums but couldnt find a suitable resolution. I am attempting to script a stop and start of an application on AIX. Such as: However it has authentication where username and password prompts will appear after running the above command requiring input from a... (2 Replies)
Discussion started by: Soupy
2 Replies

10. Shell Programming and Scripting

Want to backup dirs on application start and close.

Hi I want to write a script that will back up one directory if a certain application launches and then backs up another directory if that same application is closed down. NFI where to start. It seems like cron isn't the tool for this because that is time based. I'm thinking I need... (6 Replies)
Discussion started by: zorrokan
6 Replies
WINEMAKER(1)						      Wine Developers Manual						      WINEMAKER(1)

NAME
winemaker - generate a build infrastructure for compiling Windows programs on Unix SYNOPSIS
winemaker [ --nobanner ] [ --backup | --nobackup ] [ --nosource-fix ] [ --lower-none | --lower-all | --lower-uppercase ] [ --lower-include | --nolower-include ] [ --mfc | --nomfc ] [ --guiexe | --windows | --cuiexe | --console | --dll ] [ -Dmacro[=defn] ] [ -Idir ] [ -Pdir ] [ -idll ] [ -Ldir ] [ -llibrary ] [ --nodlls ] [ --nomsvcrt ] [ --interactive ] [ --single-target name ] [ --generated-files ] [ --nogenerated-files ] ] [ --wine32 ] work_directory | project_file | workspace_file DESCRIPTION
winemaker is a perl script designed to help you bootstrap the process of converting your Windows sources to Winelib programs. In order to do this winemaker can perform the following operations: - rename your source files and directories to lowercase in the event they got all uppercased during the transfer. - perform Dos to Unix (CRLF to LF) conversions. - scan the include statements and resource file references to replace the backslashes with forward slashes. - during the above step winemaker will also perform a case insensitive search of the referenced file in the include path and rewrite the include statement with the right case if necessary. - winemaker will also check other more exotic issues like '#pragma pack' usage, use of "afxres.h" in non MFC projects, and more. Whenever it encounters something out of the ordinary, winemaker will warn you about it. - winemaker can also scan a complete directory tree at once, guess what are the executables and libraries you are trying to build, match them with source files, and generate the corresponding Makefile. - finally winemaker will generate a global Makefile for normal use. - winemaker knows about MFC-based project and will generate customized files. - winemaker can read existing project files. It supports dsp, dsw, vcproj and sln files. OPTIONS
--nobanner Disables the printing of the banner. --backup Directs winemaker to perform a backup of all the source files in which it makes changes. This is the default. --nobackup Tells winemaker not to backup modified source files. --nosource-fix Directs winemaker not to try fixing the source files (e.g. Dos to Unix conversion). This prevents complaints if the files are read- only. --lower-all Tells winemaker to rename all files and directories to lowercase. --lower-uppercase Tells winemaker to only rename files and directories that have an all uppercase name. So "HELLO.C" would be renamed but not "World.c". --lower-none Tells winemaker not to rename files and directories to lower case. Note that this does not prevent the renaming of a file if its extension cannot be handled as is, e.g. ".Cxx". This is the default. --lower-include Tells winemaker that if it does not find the file corresponding to an include statement (or other form of file reference for resource files), then it should convert that filename to lowercase. This is the default. --nolower-include Tells winemaker not to modify the include statement if it cannot find the referenced file. --guiexe | --windows Specifies that whenever winemaker finds an executable target, or a target of unknown type, it should assume that it is a graphical application. This is the default. --cuiexe | --console Specifies that whenever winemaker finds an executable target, or a target of unknown type, it should assume that it is a console application. --dll This option tells winemaker that whenever it finds a target of unknown type, i.e. for which it does not know whether it is an exe- cutable or a library, it should assume it is a library. --mfc Specifies that the targets are MFC based. In such a case winemaker adapts the include and library paths accordingly, and links the target with the MFC library. --nomfc Specifies that targets are not MFC-based. This option disables use of MFC libraries even if winemaker encounters files "stdafx.cpp" or "stdafx.h" that would cause it to enable MFC automatically if neither --nomfc nor --mfc was specified. -Dmacro[=defn] Adds the specified macro definition to the global list of macro definitions. -Idir Appends the specified directory to the global include path. -Pdir Appends the specified directory to the global dll path. -idll Adds the Winelib library to the global list of Winelib libraries to import. -Ldir Appends the specified directory to the global library path. -llibrary Adds the specified library to the global list of libraries to link with. --nodlls This option tells winemaker not to use the standard set of winelib libraries for imports. That is, any DLL your code uses must be explicitly passed to winemaker with -i options. The standard set of libraries is: odbc32.dll, odbccp32.dll, ole32.dll, oleaut32.dll and winspool.drv. --nomsvcrt Sets some options to tell winegcc not to compile against msvcrt. Use this option if you have cpp-files that include <string>. --interactive Puts winemaker in interactive mode. In this mode winemaker will ask you to confirm each directory's list of targets, and then to provide directory and target specific options. --single-target name Specifies that there is only one target, and that it is called "name". --generated-files Tells winemaker to generate the Makefile. This is the default. --nogenerated-files Tells winemaker not to generate the Makefile. --wine32 Tells winemaker to generate a 32-bit target. This is useful on wow64 systems. Without that option the default architecture is used. EXAMPLES
Here is a typical winemaker use: $ winemaker --lower-uppercase -DSTRICT . The above tells winemaker to scan the current directory and its subdirectories for source files. Whenever if finds a file or directory which name is all uppercase, it should rename it to lowercase. It should then fix all these source files for compilation with Winelib and generate Makefiles. The '-DSTRICT' specifies that the STRICT macro must be set when compiling these sources. Finally winemaker will create a Makefile. The next step would be: $ make If at this point you get compilation errors (which is quite likely for a reasonably sized project) then you should consult the Winelib User Guide to find tips on how to resolve them. For an MFC-based project you would have to run the following commands instead: $ winemaker --lower-uppercase --mfc . $ make For an existing project-file you would have to run the following commands: $ winemaker myproject.dsp $ make TODO
/ BUGS In some cases you will have to edit the Makefile or source files by yourself. Assuming that the windows executable/library is available, we could use winedump to determine what kind of executable it is (graphical or console), which libraries it is linked with, and which functions it exports (for libraries). We could then restore all these settings for the corresponding Winelib target. Furthermore winemaker is not very good at finding the library containing the executable: it must either be in the current directory or in the LD_LIBRARY_PATH. Winemaker does not support message files and the message compiler yet. SEE ALSO
The Winelib User Guide: http://www.winehq.org/docs/winelib-guide/index wine(1) AUTHORS
Francois Gouget for CodeWeavers Dimitrie O. Paun Andre Hentschel Wine 1.2-rc6 Sep 2009 WINEMAKER(1)
All times are GMT -4. The time now is 03:22 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy