Sponsored Content
Special Forums UNIX Desktop Questions & Answers start windows appl. from unix Post 79000 by sjweiler on Sunday 24th of July 2005 02:12:19 PM
Old 07-24-2005
Running window's apps in unix/linux

The correct url for wine is www.winehq.com.
Wine is free solution for running windows apps.
CrossOver office costs money but it makes it easier to get apps installed.
I use Cedega to play games in linux too.
 

8 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Trying to shut down and start a Windows process

Hi , Good day people. I want to know if i can shut down a particular service that runs in windows from solaris through a script . Scenario : we have a distributed environment where we want to shut down a service that runs under windows through a shell script in solaris , is this kinda action... (3 Replies)
Discussion started by: vivsiv
3 Replies

2. Programming

how to start a c++ exe on unix from windows.

I'm very new to c++ & unix programming. I have a c++ exe that runs on the unix box, but I am trying to write a c++ windows app that executes the program on unix. I have tried execv(), but it doesn't seem to work or I'm doing something wrong. Would really like to see examples if at all possible. ... (5 Replies)
Discussion started by: ch5082
5 Replies

3. Programming

solaris appl migration: sprintf decimal separator

Hi, I am trying to migrate an application from Solaris to AIX 5.3.1. In both platforms the locale settings are as follows: Result of executing "locale" LANG=C LC_CTYPE="C" LC_NUMERIC="C" LC_TIME="C" LC_COLLATE="C" LC_MONETARY="C" LC_MESSAGES="C" In solaris when you execute this... (5 Replies)
Discussion started by: coldas57
5 Replies

4. Windows & DOS: Issues & Discussions

How to start a vbs from a windows batch file?

Morning, I'm trying to execute a vbs from a .bat file. Can someone tell me what the difference is between these statements: start c:\lib\runit.vbc c:\lib\runit.vbs When I run the batch with the 'start' parameter it doesn't seem to do anything. (1 Reply)
Discussion started by: Grueben
1 Replies

5. Windows & DOS: Issues & Discussions

Start windows application (.bat) from Unix

How can I start an application sitting on a windows machine (XP) from Unix shell script (AIX server) ? (6 Replies)
Discussion started by: pkan
6 Replies

6. Shell Programming and Scripting

How to start powershell with shebang from windows/cygwin/bash?

I would like to the the windws8/cygwin/bash shebang feature to start a powershell script. I do a "chmod +x set-sound.ps1" and then at a bash prompt I do ./set-sound.ps1 The first line of ./set-sound.ps1 #!powershell.exe -ExecutionPolicy unrestricted The result is the result: ... (5 Replies)
Discussion started by: siegfried
5 Replies

7. HP-UX

Compile krb5-appl 1.0.3 on hpux

asprintf.c: In function 'vasprintf': asprintf.c:58: error: 'SIZE_MAX' undeclared (first use in this function) asprintf.c:58: error: (Each undeclared identifier is reported only once asprintf.c:58: error: for each function it appears in.) Someone know how to fix? Thanks (2 Replies)
Discussion started by: Linusolaradm1
2 Replies

8. Windows & DOS: Issues & Discussions

How can I start a cygwin application from windows 7 command prompt?

I have compiled an application called tmesh.exe, that was compiled for the cygwin, win7 platform. I wonder, if I do that outside X window, Is there a chance that I can run it on the command prompt of windows 7? (tmesh:4048): Gtk-WARNING **: cannot open display: THANKS Jack (3 Replies)
Discussion started by: lucky7456969
3 Replies
WINESERVER(1)							  Windows on Unix						     WINESERVER(1)

NAME
wineserver - the Wine server SYNOPSIS
wineserver [options] DESCRIPTION
wineserver is a daemon process that provides to Wine roughly the same services that the Windows kernel provides on Windows. wineserver is normally launched automatically when starting wine(1), so you shouldn't have to worry about it. In some cases however, it can be useful to start wineserver explicitly with different options, as explained below. OPTIONS
-d[n], --debug[=n] Set the debug level to n. 0 means no debugging information, 1 is the normal level, and 2 is for extra verbose debugging. If n is not specified, the default is 1. The debug output will be sent to stderr. wine(1) will automatically set the debug level when start- ing wineserver if the +server option is set in the WINEDEBUG variable. -f, --foreground Make the server remain in the foreground for easier debugging, for instance when running it under a debugger. -h, --help Display a help message. -k[n], --kill[=n] Kill the currently running wineserver, optionally by sending signal n. If no signal is specified, sends a SIGINT first and then a SIGKILL. The instance of wineserver that is killed is selected based on the WINEPREFIX environment variable. -p[n], --persistent[=n] Specify the wineserver persistence delay, i.e. the amount of time that the server will keep running when all client processes have terminated. This avoids the cost of shutting down and starting again when programs are launched in quick succession. The timeout n is in seconds, the default value is 3 seconds. If n is not specified, the server stays around forever. -v, --version Display version information and exit. -w, --wait Wait until the currently running wineserver terminates. ENVIRONMENT VARIABLES
WINEPREFIX If set, the content of this variable is taken as the name of the directory where wineserver stores its data (the default is $HOME/.wine). All wine processes using the same wineserver (i.e.: same user) share certain things like registry, shared memory and kernel objects. By setting WINEPREFIX to different values for different Wine processes, it is possible to run a number of truly independent Wine sessions. WINESERVER Specifies the path and name of the wineserver binary that will be launched automatically by wine. If not set, wine will try to load /usr/bin/wineserver, and if this doesn't exist it will then look for a file named wineserver in the path and in a few other likely locations. FILES
~/.wine Directory containing user specific data managed by wine. /tmp/.wine-uid The directory containing the server Unix socket and the lock file. These files are created in a subdirectory generated from the WINEPREFIX directory device and inode numbers. AUTHORS
The original author of wineserver is Alexandre Julliard. Many other people have contributed new features and bug fixes. Please check the file Changelog in the Wine distribution for the complete details. BUGS
If you find a bug, please submit a bug report at http://bugs.winehq.org. <http://bugs.winehq.org> AVAILABILITY
wineserver is part of the Wine distribution, which is available through WineHQ, the Wine development headquarters, at http://www.winehq.org/. <http://www.winehq.org/> SEE ALSO
wine(1). Wine 1.2-rc6 October 2005 WINESERVER(1)
All times are GMT -4. The time now is 11:21 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy