05-09-2001
Ooops! Why do you need to run DLLs on unix!
try WINE (Wine Is Not an Emulator):
Quote:
Wine is an implementation of the Windows 3.x and Win32 APIs on top of X and Unix. Think of Wine as a Windows compatibility layer. Wine provides both a development toolkit (Winelib) for porting Windows sources to Unix and a program loader, allowing unmodified Windows 3.1/95/NT binaries to run under Intel Unixes.
Wine does not require Microsoft Windows, as it is a completely alternative implementation consisting of 100% Microsoft-free code, but it can optionally use native system DLLs if they are available. Wine comes with complete sources, documentation and examples and is freely redistributable.
But don't expect everything will work. for 1 hours work i got a Windowz help window on linux. You may be lucky.
Wine Located here:
http://www.winehq.com/
HTH
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Okee problems...!!
What is happening: Unix server with some programms, workstations are windows 2000, the workstations work good but when you start a programm on the Unix server the CPU of the workstations go to 100% usage resulting that the system gets very slow. The programm well its running so... (2 Replies)
Discussion started by: zerocool
2 Replies
2. UNIX for Advanced & Expert Users
hi
i want run an unix application from a windows program/application.i am using SSH(command line version)to log on to a unix machine from windows. the application has to read a configuration file inorder to run. the configuration file .CFG is in bin in my home directory. but the application... (1 Reply)
Discussion started by: megastar
1 Replies
3. Filesystems, Disks and Memory
Hello Moto
I hope someone can help
We's here at work, have a unix box with sco openserver 5 on it, so it has a nice gui interface.. and also a fair few windows computers..
a system admin guy b4 me, has set up a user called neil, which can, when u try to access the unix box using windows... (2 Replies)
Discussion started by: haggo
2 Replies
4. UNIX for Advanced & Expert Users
Hi all,
I have an application which will run in both windows as well as Linux.
I ported it long back and it is working well.
Now we need to extend the functionality ,so i have written .dll's for
Windows.These dll's have certain dependancies as well.And these are
sucessful in windows.
... (1 Reply)
Discussion started by: platso
1 Replies
5. UNIX for Dummies Questions & Answers
My situation is that we have production unix scripts that ftp files over to a windows server. I'm not sure if its a 2000 or 2003 server as I dont work on server, more on the unix side. It turns out that they are changing servers on the network. So they are migrating our data over from say Server 1... (1 Reply)
Discussion started by: NycUnxer
1 Replies
6. AIX
Hi Friends,
I have this script for ftping files from AIX server to local windows xp.
#!/bin/sh
HOST='localsystem.net'
USER='myid_onlocal'
PASSWD='mypwd_onlocal'
FILE='file.txt' ##This is a file on server(AIX)
ftp -n $HOST <<END_SCRIPT
quote USER $USER
quote PASS $PASSWD
put $FILE... (1 Reply)
Discussion started by: rajsharma
1 Replies
7. Shell Programming and Scripting
Hi Experts,
I have a requirement where i need to setup a batch job which runs everymonth and move the pdf files from unix server to windows servers.
Could some body provide the inputs for this.
and also please provide the inputs on how to map the network dirve in the unix like that... (1 Reply)
Discussion started by: ger199901
1 Replies
8. Shell Programming and Scripting
Can anybody please help me on how to code for the below requirement:
I need to write a shell script (on different unix server) to copy files from multiple folders (ex. BRN-000001) from one windows server (\\boldls-mwe-dev4)to a different windows server(\\rrwin-ewhd04.ecomad.int). This shell... (4 Replies)
Discussion started by: SravsJaya
4 Replies
9. Shell Programming and Scripting
hi guys,
i need a script to sftp the file from windows to unix server ....(before that i have to check whether the file exists in the windows server or not
and again i have to reverse sftp the files from unix to windows server.....
regards,
Vasa Saikumar. (13 Replies)
Discussion started by: hemanthsaikumar
13 Replies
LEARN ABOUT SUSE
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)