06-30-2011
If your bash script
pinged the virtual Windows machine every second or every few seconds, that would give a reasonably quick and reliable indication.
But I have to ask the obligatory question. Have you tried running your Windows software under
Wine? That might give you better control.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
i got the rpm file and installed it but nothing happens i went to the cmd line and got the wizard to come up and finshed it but still no a thing will any body help me set this thing up i'm using mandrak9 (1 Reply)
Discussion started by: amicrawler2000
1 Replies
2. Solaris
hello all I have prob with solaris 10 and vmware 5.5, 6.0 that befor it's good work and from yesterday when I try to add new vm in SCSI Controller from vmware it's Don't see any Hard Disk or controller when I used solaris 5 cd-cdrom
and DVD version but when try to make vm with IDE controller... (0 Replies)
Discussion started by: Hosam
0 Replies
3. OS X (Apple)
I sorry for not being able to follow the rules. (0 Replies)
Discussion started by: puertochico
0 Replies
4. Solaris
Hi
I want to install vmware on my laptop and get started by installing a Solaris 10 on it . Can aybody suggest any links, pdfs etc that describes the procedure step by step .The laptop is running windows Vista
Thanks in advance (2 Replies)
Discussion started by: asalman.qazi
2 Replies
5. Solaris
Hi,
I am going to install solaris cluster 3.2 in vmware esx 3.5 for demo, for cluster we need two different network interfaces for private and pubic connectivity, but we have single ethernet controller
how to create two different ethernet instance name with single ethernet controller in vmware... (1 Reply)
Discussion started by: rajasekg
1 Replies
6. Virtualization and Cloud Computing
Hi Gurus
Can anyone please send a trial license of VMware 7.1.1. I install it in my machine.
Thanks (2 Replies)
Discussion started by: andresguillen
2 Replies
7. SCO
Hi all, I'm looking for some friendly advice on running Openserver 5.0.6 on VMware. Does anybody fancy answering a few questions if I post them?
---------- Post updated at 02:14 PM ---------- Previous update was at 10:43 AM ----------
Well people are reading my post, so I'll try my questions!... (5 Replies)
Discussion started by: KevinGB
5 Replies
8. AIX
Hello Every body,
I will receive a workstation HP, with a processor Intel corei5, with Windows already installer.
I project to install :
1)a Vmware
2)a serveur aix
3)a redhat server
... etc.
My question is :
1) What kind of vmware should I install to support installation of an AIX... (3 Replies)
Discussion started by: mlaiti
3 Replies
9. SuSE
Dear Friends,
I have been working with vmware and it was working welll until few days ago. I am still able to log myself in and start the virtual windows. However, the network connection to the host computer is gone and I am not able to copy my files from vmware to the host machine. At the... (1 Reply)
Discussion started by: chirag.joshi
1 Replies
10. Ubuntu
Hi all
I have a very big problem with ..... > VMWare Workstation 7.1.4
Closes abruptly >> If I do anything
This video demonstrates the problem::
http://www.youtube.com/watch?v=n0OVSQY3LtI (0 Replies)
Discussion started by: aonallah
0 Replies
LEARN ABOUT DEBIAN
wineserver
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)