Attaching critical personal accounts to these free Sweden Virtual phone numbers is not recommended, as these accounts can be recovered by other users via SMS afterwards. https://tempsmss.com/country/sweden-phone-number/ https://tempsmss.com/blog/
Go to file
James Juran 7c0b4c3d38 Updated documentation/no-windows. 1999-06-05 08:46:10 +00:00
console Converted to the new debug interface, using script written by Patrik 1999-05-14 08:17:14 +00:00
controls Support TPM_RETURNCMD in TrackPopupMenu. 1999-05-29 10:56:43 +00:00
debugger Fixed a few typos. 1999-05-24 08:14:30 +00:00
dlls Authors: Chris Morgan <cmorgan@wpi.edu>, James Abbatiello <abbeyj@wpi.edu> 1999-05-29 14:16:56 +00:00
documentation Updated documentation/no-windows. 1999-06-05 08:46:10 +00:00
files Added support for the undocumented combination 1999-05-22 16:04:57 +00:00
graphics Speedup enhancement for the 8->16 and 8->32 copy loop hotspots, 1999-06-05 08:45:32 +00:00
if1632 fixed builtin mmsystem.dll init sequence 1999-05-24 08:25:09 +00:00
include Got rid of THREAD_InitDone. 1999-05-29 14:27:26 +00:00
ipc Converted to the new debug interface, using script written by Patrik 1999-05-14 08:17:14 +00:00
library More include optimisations and fixes. 1999-02-28 19:14:33 +00:00
libtest Built-in dlls now have resources attached via the PE-header like 1999-04-25 18:31:35 +00:00
loader Got rid of THREAD_InitDone. 1999-05-29 14:27:26 +00:00
memory Converted to the new debug interface, using script written by Patrik 1999-05-23 10:25:25 +00:00
misc Fixed some warnings. 1999-05-29 11:08:36 +00:00
miscemu Wait until child initialized before returning from PROCESS_Create. 1999-05-24 08:10:46 +00:00
msdos Added INT_Int16AddChar. 1999-05-22 11:27:40 +00:00
multimedia removed obsoleted init.c source file 1999-05-24 08:24:52 +00:00
objects Converted to the new debug interface, using script written by Patrik 1999-05-23 10:25:25 +00:00
ole Microsoft com vtable compatibility workaround for g++. Basically adds 1999-05-22 11:41:38 +00:00
programs Bug fixes. 1999-05-08 10:50:34 +00:00
rc Fixed compilation. 1999-03-14 13:56:59 +00:00
relay32 Use register functions with arguments for LogApiThk... 1999-05-24 08:09:34 +00:00
resources Built-in dlls now have resources attached via the PE-header like 1999-04-25 18:31:35 +00:00
scheduler Got rid of THREAD_InitDone. 1999-05-29 14:27:26 +00:00
server Made handle table a separate object. 1999-06-04 19:49:54 +00:00
tools ver.h is a legacy header. winver.h should be used instead. 1999-05-29 11:15:39 +00:00
tsx11 Converted to the new debug interface. 1999-05-14 08:11:40 +00:00
win32 Fix <return> key (somehow we get a control keystate). 1999-05-29 10:55:08 +00:00
windows Got rid of THREAD_InitDone. 1999-05-29 14:27:26 +00:00
.cvsignore Initial revision 1998-10-04 18:02:24 +00:00
ANNOUNCE Release 990523. 1999-05-23 10:42:57 +00:00
AUTHORS Updated authors list from the Changelog. Please let me know if you 1999-05-02 18:13:33 +00:00
BUGS Updated. 1999-04-19 16:19:25 +00:00
ChangeLog Release 990523. 1999-05-23 10:42:57 +00:00
DEVELOPERS-HINTS Updated for new naming conventions. 1999-02-26 12:33:21 +00:00
LICENSE Release 970720 1997-07-20 16:23:21 +00:00
Make.rules.in Get include files from the current directory first. 1999-05-15 10:41:15 +00:00
Makefile.in Implement DocumentProperties, DeviceCapabilities, beginnings of 1999-05-17 16:20:51 +00:00
README Update to reflect recent changes and discussions. 1999-04-26 14:57:06 +00:00
WARRANTY Release 970720 1997-07-20 16:23:21 +00:00
configure Create a new configuration manifest constant HAVE_OSS_MIDI. 1999-05-22 18:52:21 +00:00
configure.in Create a new configuration manifest constant HAVE_OSS_MIDI. 1999-05-22 18:52:21 +00:00
wine.ini Changed serial ports in wine.ini to /dev/ttySX from /dev/cuaX in 1999-05-17 15:03:47 +00:00
winedefault.reg Default values for registry. 1999-04-11 17:09:20 +00:00

README

1. INTRODUCTION

Wine is a program which allows running Microsoft Windows programs
(including DOS, Windows 3.x and Win32 executables) on Unix.  It
consists of a program loader which loads and executes a Microsoft
Windows binary, and a library that implements Windows API calls using
their Unix or X11 equivalents. The library may also be used for
porting Win32 code into native Unix executables.

Wine is free software, and its license (contained in the file LICENSE)
is BSD style.  Basically, you can do anything with it except claim
that you wrote it.


2. REQUIREMENTS

To compile and run Wine, you must have one of the following:

	Linux version 2.0.36 or above
	FreeBSD-current or FreeBSD 3.0 or later
	Solaris x86 2.5 or later

Although Linux version 2.0.x will mostly work, certain features
(specifically LDT sharing) required for properly supporting Win32
threads were not implemented until kernel version 2.2.  If you get
consistent thread-related crashes, you may want to upgrade to 2.2.

You also need to have libXpm installed on your system. The sources for
it are probably available on the FTP site where you got Wine. They can
also be found on ftp.x.org and all its mirror sites. If you are using
RedHat, install the xpm and xpm-devel packages. Debian users need
xpm4.7, xpm4g, and xpm4g-dev 3.4j.

On x86 Systems gcc >= 2.7.2 is required. You also need flex version 2.5
or later and yacc. Bison will work as a replacement for yacc. If you are
using RedHat, install the flex and bison packages.

3. COMPILATION

To build Wine, first run "./configure" and then run "make depend; make".
This will build the library "libwine.a" and the program "wine".

The program "wine" will load and run Windows executables.
The library "libwine.a" can be used to compile and link Windows source
code under Unix.  If you have an ELF compiler, you can use
"./configure --enable-dll" to build a shared library instead. To see
other configuration options, do ./configure --help.

To upgrade to a new release by using a patch file, first cd to the
top-level directory of the release (the one containing this README
file). Then do a "make clean", and patch the release with:

    gunzip -c patch-file | patch -p1

where "patch-file" is the name of the patch file (something like
Wine-yymmdd.diff.gz). You can then re-run "./configure", and then
run "make depend; make".


4. SETUP

Once Wine has been built correctly, you can do "make install"; this
will install the wine executable, the Wine man page, and a few other
needed files.

Wine requires you to have a file /usr/local/etc/wine.conf (you can
supply a different name when configuring wine) or a file called .winerc
in your home directory.

The format of this file is explained in the man page. The file
wine.ini contains a config file example which has to be adapted
and copied to one of the two locations mentioned above.

See www.winehq.com/config.html for further configuration hints.


5. RUNNING PROGRAMS

When invoking Wine, you may specify the entire path to the executable,
or a filename only.

For example: to run Solitaire:

	wine sol		   (using the searchpath to locate the file)
	wine sol.exe

	wine c:\\windows\\sol.exe  (using a DOS filename)

	wine /usr/windows/sol.exe  (using a Unix filename)

Note: the path of the file will also be added to the path when
      a full name is supplied on the commandline.

Wine is not yet complete, so some programs may crash. You will be dropped
into a debugger so that you can investigate and fix the problem. For more
information on how to do this, please read the file documentation/debugging.
If you post a bug report, please read the file documentation/bugreports to
see what information is required.


6. GETTING MORE INFORMATION

FAQ:	The Wine FAQ is located at http://www.winehq.com/faq.html.

WWW:	A great deal of information about Wine is available from WineHQ at
	http://www.winehq.com/. Untested patches against the current release
	are available on the wine-patches mailing list; see 
	http://www.winehq.com/dev.html#ml for more information.

HOWTO:	A pre-release version of the Wine HOWTO is available at
	http://www.westfalen.de/witch/wine-HOWTO.txt .

Usenet:	Please browse old messages on http://www.dejanews.com/ to check whether 
	your problem is already fixed before posting a bug report to the 
	newsgroup. 

	The best place to get help or to report bugs is the Usenet newsgroup
	comp.emulators.ms-windows.wine. Please read the file 
	documentation/bugreports to see what information should be included 
	in a bug report.

CVS:	The current Wine development tree is available through CVS.
	Go to http://www.winehq.com/dev.html for more information.

If you add something, or fix a bug, please send a patch ('diff -u'
format preferred) to julliard@lrc.epfl.ch for inclusion in the next
release.

--
Alexandre Julliard
julliard@lrc.epfl.ch