Wine Registry

From Wine-Wiki

Jump to: navigation, search

Contents

[edit] Information

The Wine registry has been constantly worked on and has replaced the config file. In June 2005 Winecfg, was activated and now saves changes to the registry. Dimi Paun maintains a list of where you can now set different options for Wine, and the scope they have here http://winehq.org/site/status_options

There are four human readable files that are used to store registry information:

  • system.reg
    This file contains HKEY_LOCAL_MACHINE.
  • user.reg
    This file contains HKEY_CURRENT_USER.
  • userdef.reg
    This file contains HKEY_USERS\.Default (i.e. the default user settings).
  • wine.userreg
    Wine saves HKEY_USERS to this file (both current and default user), but does not load from it, unless userdef.reg is missing.

As all of these files are text files, unlike Windows, you can actually use an ordinary text editor on them if you want (but do make sure you don't have Wine running when modifying them, otherwise your changes will be discarded).

In addition to these files, Wine can also optionally load from global registry files residing in the same directory as the global wine.conf (i.e. /usr/local/etc if you compiled from source). These are:

  • wine.systemreg
    Contains HKEY_LOCAL_MACHINE.
  • wine.userreg
    Contains HKEY_USERS.

Currently the deprecated config file will still affect some settings. [Update] The config file has been competely deprecated. Be aware that due to the fast pace of wine development, some sections of the registry may change at a future date.


Further Reading

[edit] The Registry Settings

[edit] Windows Version

Some applications work only with version=win98, and other applications work only with version=win2k. If an application won't start and pops up a message like 'This program requires Windows 2000/XP' then you may try to change this setting to get this program to work.

[edit] Wine Dll Overrides

You can use winecfg to save settings to the registry or WINEDLLOVERRIDES from the command line.

Command line example: WINEDLLOVERRIDES="comctl32=n;commctrl=n" wine foo.exe

Following native DLLs can't be used in Wine: ntdll.dll, gdi32.dll, kernel32.dll, advapi32.dll, winsock32.dll, and some others. Many DLLs from Windows XP don't work either. Use their Windows 98 equivalents or builtin DLLs instead.

For more information see the environment variable "WINEDLLOVERRIDES" in The Wine Man Pages

A user queried the use of this expression [Apr 06]:

"*"="native, builtin"

Does the "*" mean that if the driver, dll, exe in question is not listed in the DllOverrides section, that it defaults to using the native version of the file and, if not available, then tries to find and run a builtin version?

M. McCormack:"*" no longer does anything, and should be removed from registries. It's original intent was to force using native dlls over builtin dlls whenever found. It encouraged people to copy all the dlls from a windows install into their .wine, and was therefore removed.

The user queried further: if the file with the * in front of it exists, what would be Wine's behavior towards it. What I mean is, what does the * in the file name mean to Wine? Is it just a standard wildcard to match many files to one entry?

A. Julliard: The wildcard means that it matches that file in any directory. The same entry without wildcard would match only when loading from the system directory. wine archive

[edit] Fonts

Truetype Fonts

Here is the homepage for corefonts: http://corefonts.sourceforge.net/

Apparently these are the MS fonts (Andale Mono,Arial, Comic Sans MS, courier, Georgia, Impact, Times New Roman, Trebuchet, and Verdana), which are allowed to be redistributed unaltered, according to the EULA and FAQ linked to on the page, so the maintainer has done so. These can be installed via Portage, for Gentoo users, but this package is available via all (or most) distribution repositories - Google search for corefonts. Debian even has an msttcorefonts package in its 'contrib' section (stable, testing, and unstable).

The corefonts homepage makes RPMs, the original .exe files and cabextract available. Some distributions, such as SuSE, actually offer to install the MS core fonts unrepackaged (directly from the Microsoft site, I believe) via YaST. You may have to accept a licence for each individual font and it is often a slow process. So it's nice to have the *.exe files available from somewhere else, as well as the RPM.

The standard location for fonts under X.org is in /usr/share/fonts, but of course other users' locations may be different. If still using XFree86, the fonts may be in /usr/lib/X11/fonts, or /usr/X11R6/lib/X11/fonts/, and any given distro may have a custom location over and above that. However, once the corefonts are installed, a simple locate arial.ttf should indicate the path for these fonts. External True Type fonts are listed in the Wine Registry

HKEY_LOCAL_MACHINE=>Software=>Wine=>Fonts=>External Fonts

Apparently Wine or winecfg scans your system for True Type fonts and registers/lists what it finds, all by itself.

[edit] Forum Discussions

[edit] Wine's Registry format

A Programmer noted [Jun 05]:Wine Archive Wine loads the entire registry when it first runs, which can get become a waste - even if it's going to be swapped off anyway [...]It's also not the fastest method of input and especially output to the registry. [...and then suggested] Using a small helper app to sync our plain-text registry files into a db format would let us maintain a human-readable format of our registry, while also reducing the overhead required by the current registry format.[...] - It would also provide us with a quicker and easier way to search through the registry - so we could finally implement the Find feature in wine's regedit without much effort ( Not that it couldn't be done as is, but things would definitely be easier ).


A. Julliard: Actually the current method is probably the fastest for everything except the initial read. Admittedly it's not very elegant, but it's simple and allows us to store everything in text format. So I'm not at all convinced that using a real database would be worth the trouble.

D. Lambert: Samba already uses something called 'TDB', and it's been suggested that the two projects could share a case - insensitive - filename layer based on it; Could you look into using that?

K. Porter: Today's Samba announcement includes something about the ability to handle NT registry files: <http://us2.samba.org/samba/ftp/pre/WHATSNEW-3-0-20pre1.txt>

J. Liggart [Jun 05]: Have you thought about using XML as a potential format? Since the registry is a non-relational tree database, this seems to fit quite well. Plus, there's a few libraries that would do the dirty work for us (libxml, expat, many others, name your pick). It could even be possible to modularize the registry using technologies like XInclude or XLink.

M. Fuchs: the tree format would match. But this would not really make things better. You would also have to read the registry at once at startup time. The best solution would be to use native Windows registry format. This way you could use real Windows registry files, and can read and update registry piecewise. It's organized like a little file system - or database if you want to see it this way. It's not documented. But you could have a look at the ReactOS implementation, which claimes to be compatible to NT4. Win Archive

B. DeMorrow: [...]I'm really not convinced that we need to be compatible with Windows' registry file format at that level. . . That would only benefit applications that don't use the Win32API to access the registry - and as far as I know, Windows doesn't allow you to access the registry like that, so there shouldn't be any applications that would benefit from that. . .

S. Shemesh: How about an application that carries a binary registry hive around, and uses "LoadHive" to merge it (temporarily) into the registry? How about deploying Wine in such a way that it uses the existing user profile, user.dat and all? User.dat is a registry file, that goes through load hive. The way I see the ultimate outcome, Wine should have "Registry providers". These would allow it to use several different registry back ends. The default one would probably be the one used today, but this way we could plug in an SQL back end if needed, as well as a Windows compatible one, if needed.

J. Schmied commented that: Wine had support for reading win2000 registry files once. It was dropped some time ago. I had implemented it around 1999/2000.Have a look in the CVS.

[The discussion turned to implementing the Find function for the registry]Wine Archive

[edit] Current Status

[...] this was a long time comming. Glad to see we're within the deadlines :) Brian [Vincent], now we can update the User Guide too, and get the stuff you wrote some time ago into the official docs. Wine Archive

Feel free to add missed and, or further changes

[edit] Tips and Tricks

[edit] Clipboard

As Segin noted: There are two clipboards [...] select some text in Wine, and middle click in a Xterm, nothing happens! Go back to the Windows app, tell it to copy the text, and try to paste it into the xterm, nothing again! (I think it's a bug IMHO)

P.Krylov: You need to set the Wine registry entry X11 Driver/UsePrimarySelection to 'Y'. I submitted a patch for Winecfg to do it, but it wasn't accepted and it was a long time ago... wine archive

[edit] Importing a Windows .reg File

B. Vincent: An app I have uses the registry as a massive data store. There are literally thousands of keys and values sitting in there. It would be nice to export a small branch of the registry and just import that into Wine.

A. Hanulla: If I remember correctly, [...] the following command is enough: 

$ regedit file.reg

R. Shearman: This doesn't work for Windows NT .reg files though, as they are generated in Unicode format by default. It shouldn't require too many changes for regedit to work with Unicode files. The changes to the profile functions in kernel32 to work with Unicode were simple enough.


[edit] Graphics

[edit] GLSL

enabling GLSL: (HKCU/Software/Wine/Direct3D/UseGLSL = enabled) wine archive

[edit] texture repacking

repacking can be quite CPU intensive, and warhammer 40k is the only game so far that needs nonpower2 texture repacking so it's turned off by default but can be turned on via the following registry key:

HKEY_CURRENT_USER/Software/Wine/Direct3D Nonpower2Mode [repack]

[edit] Writing to the Registry

A developer using perl wrote: I'm trying to find some elegant method to access registry keys added during one WINE session, i.e. without restarting WINE.

Test case description:

  1. Open WINE session
    wineconsole --backend=user cmd
  2. During session, insert some new registry key
    regedit new-entry.reg
  3. Try to access the new registry entry from bash
    cat ~/.wine/system.reg |grep AutoHotkey (fails)

L. Zhang:Accessing the Wine registry directly is probably not the right way to do it, you should go through the Windows registry API calls, i.e. RegQueryValue.

The devloper pointed to http://winehq.org/site/docs/wineusr-guide/using-regedit there are two ways to access the registry - using file access and using regedit.

L. Zhang:Yes, but the documentation specifically says only to access the file when Wine is not running.

B. Medland: Use the shell 

wine regedit -e /tmp/$$.reg <branch> && cat /tmp/$$.reg && rm -f /tmp/$ $.reg

The developer noted; I simply want registry export to STDOUT nothing else. [He then considered a new tool for wine]... able to output registry entries to STDOUT.

D. Riekenberg: Did you test reg.exe / regini.exe ? [...] Both are from Microsoft.

Example: 

$ wine reg.exe query "HKCU\Software\wine\MSHTML"
! REG.EXE VERSION 3.0
HKEY_CURRENT_USER\Software\wine\MSHTML
GeckoUrl REG_SZ http://source.winehq.org/winegecko.php

[the disucssion continued]

[edit] Automated Registry Entries

A wine user reported [Mar 07]: currently each user of my Wine-installation has to run "wine regedit" and add the ActivePerl directory manually to the HKEY_CURRENT_USER/Environment/Path variable. Is there please a way for adding "c:\Perl\bin" to the %Path% without regedit, so that I could do it in wineprefixcreate?

B. Medland: What I do is use regedit /e to export the HKLM/System/CurrentControlSet/Control/Session Manager/Environment, grep to extract the current path, and see if the addition is already in it and sed to put it in, then use regedit <filename> to put the modified path in. (in other words regedit can be run in batch mode) Seeing as how you are talking about perl you'd probably prefer a tiny perl script to do that bit. [wine user]

The user reported another solution: just changed this line in the file share/wine/wine.inf:

HKLM,System\CurrentControlSet\Control\Session Manager\Environment,"PATH",2,"%11%;%10%;C:\apps\actperl\bin;Z:\epoc32\tools;Z:\epoc32\gcc\bin"

And it somehow gets copied to every new Wine user (which I wanted). I wonder what does the "2" above mean...

Another comment was made [July 07 wine devel]: I have a shell script that calls winepath -w to get the windows path from a unix path. Then I want to stick the value into the registry by a search and replace in ${WINEPREFIX}/*.reg.

A. Julliard: That's a bad idea. You should use regedit, which will avoid potential conflicts with a running session, and will take care of the encoding (the Ansi codepage is *not* the right encoding for reg files).

[edit] Anti-aliasing

A user said [July 05]: I want to turn off Wine Anti-aliasing. I was able to do it in the config file, but now I don't know. 'winecfg' doesn't have any such setting. Can it be turned off in the registry ? If so what is the setting ? Wine Archive

H. Davies: Add the values

"ClientSideAntiAliasWithRender"="N"
"ClientSideAntiAliasWithCore"="N"

to the key HKCU\Software\Wine\X11 Driver


[edit] Screen Resolution

Stefan D�singer [Dec 05]: Cedega changes the screen resolution, but desktop dimensions are unchanged. That's a Xrandr issue: Wine uses Xrandr to change the screen resolution: Both the virtual Desktop and the Screen resolution are changed. Cedega only changes the Screen resolution just as if you typed Ctrl + alt + "+". The reason why Wine so is a mouse locking issue: dinput.dll fails to lock the mouse inside the Wine window often, and if the Desktop is bigger than the screen, one can accidentally move the mouse outside the game window. The solution to this one is to fix dinput and avoid the use of Xrandr.

You can prevent Wine from using XRandR to change screen resolution setting the key UseXRandR to "N" in the X11 Driver registry section. wine archive

[edit] Forum Comments

HKCU/Sofware/Wine/AppDefaults/radmin.exe/X11 Driver/Desktop registry key to "1024x768" doesn't work.

[wine-users Apr 06] It's no longer possible to set that per-application in the registry. See http://winehq.org/?issue=310#Major%20Changes%20to%20Desktop%20Mode

[edit] Startup

in a discussion regarding of the startup folder several opinions were made: D. Lichteman [Feb 07] suggested: disabling the Run key [...] malicious programs now use the run registry location as opposed to the Startup folder.

Another suggested: How about prompting the user during startup? e.g., "Start <title> using command line <program + args>? Yes/No ([x] Don't ask again"

J. Alberty: Why not integrate this functionality into wineboot? That way if a user wants to completely deny the start-up folder they can just not add wineboot to the list of programs to be started on login, but if they want that functionality they can simply add wineboot to the list of programs for start up when they login? It would allow similar functionality to windows whilst still keeping it a separate system. [wine archive]

Some regular developers raised security concerns, yet others advocated following the behaviour of Windows. M. Koshelev sent a couple of version of he patche to wine-patches and Alexandre committed the "like windows behavior" patch that starts the startup programs without asking the user (as part of wineboot), and we had decided to think about what we were going to do for security later.

[edit] Configuring Sound

Occasionally when your sound driver has some bugs (aRts seems to be regularly mentioned), you cannot successfully run winecfg to set up sound for Wine. This has been noticed and worked on several times, with a measure of success. However, you can easily work around this problem using regedit, the registry editor. Don't be too fearful of working with the registry. Make a backup if needed and lets dive in and get our feet wet. (Don't forget that wine can be 'reinstalled' rather quickly by deleting all the files in .wine and typing winecfg, but just as a reminder...make sure to backup any files you need first.)

Run "wine regedit", and locate the path:

  • HKEY_CURRENT_USER/Software/Wine/Drivers

Change the value of the key "Audio" according to your system. If this is a fresh install, the "Audio" key may not be present, so just create a new one. This key is created when winecfg saves changes for the first time.

  • Audio = "" to disable the default sound driver
  • Audio = "OSS" to select the OSS sound driver. (This value has been reported as case sensitive)
  • Audio = "ALSA" to select the ALSA sound driver.

Disabling the sound driver has allowed the Audio tab in winecfg to work on some systems, but on systems with aRts this may not work. Selecting the sound driver with winecfg will allow sound to work for your applications even if the Audio tab crashes.

References: wine archive

[edit] Printing

A user queried: Is there a detailed explanation of the printer setup in the registry of modern Wine (0.9.38) ? I can't seem to find any documentation and I'm having some weird printing problems that I would like to resolve and I think the key may be in the registry.

D. Riekenberg [Wine user Jun 2007]

  • Wine with CUPS:
    • Find your Printers: from CUPS
    • PPD-File for your Printer: from CUPS
    • Print the Postscript-File: lpr
  • Wine without CUPS:


A user said: the first printing driver is the WINE PS driver and that its path is:

[System\\CurrentControlSet\\Control\\Print\\Environments\\Windows 4.0\\Drivers\\PS Driver]

D. Riekenberg [Sept 07 wine user]: That path was right on win9x, but NT and wine use now for win9x Drivers:

[System\\CurrentControlSet\\Control\\Print\\Environments\\Windows 4.0\\Drivers\\Version-0\\PS Driver]

in fact the PS driver can be reached under different names by the programs emulated by WINE. The Name "PS Driver" was replaced in November 2006. We now use the Printer-Name also for the Drivername

This is the correct Path for NT Drivers since W2K ("EPSON Stylus C48" as example Driver)

[System\\CurrentControlSet\\Control\\Print\\Environments\\Windows NT x86\\Drivers\\Version-3\\EPSON Stylus C48]

With a recent chage (wine-0.9.45), wine [resets] both entries for the Drivers. You can delete the Registry-Path "HKEY_LOCAL_MACHINE\\System\\CurrentControlSet\\Control\\Print", and wine creates all needed entries.


one user noticed an error and wondered if it was connected to printing and wine registry settings: err:heap:HEAP_CreateSystemHeap system heap base address 0x80000000 not available

D. Riekengerg [pointed out this is not a problem with printing sept 07 wine user]: Your Kernel is not correct configured to work with Wine. 3GB User Memory Area is needed, but some kernels are compiled with 2GB/2GB splitting. Many Windows Applications expect the Heap at a fixed address.

[edit] Ports

Keep in mind that wine is a fast moving target, so some of this info may become quickly out of date. It is however a starting point for research and if you can update a point, please add a note about the date and do so.

H. Bostick explained Permission difficulties can prevent access to the ports[Oct 05] : [one users settings for] com ports [were] only available to root, and Wine is not intended to be run by root (and in fact should not be run by root). On my system, /dev/ttyS1 is a symlink to /dev/tts/1 which is owned by root and the tty group. Is your user a member of all such groups that might own the serial ports (tty, serial, com, dialup or dialout, etc)? Please check this (easiest would be to look in /dev and see what group exactly owns the ports and add yourself to it), and after doing so, remove (delete, rm -rf) the /.wine directory in /root (root's HOME folder), as root having a Wine configuration will mess up your user configuration, then try your program again. [wine archive]


[edit] Serial Com Port

A programmer found a program that: did not "see" the COM ports until I added the following entries into the registry:

[HKEY_LOCAL_MACHINE\hardware\devicemap\serialcomm]
"COM2"="COM2"
"COM1"="COM1"

[Nov 05] One user reported: I have found that while many apps will happily Just Work, some apps need the following entries in system.reg: wine archive

[HARDWARE\\DEVICEMAP\\SERIALCOMM] 1131331688
"COM1"="COM1"
"COM2"="COM2"

A user Jun 08 wine user asked about USB serial devices: how should I specify ttyUSB in the registry?

O. Kaaven: You don't.[..]The registry isn't involved at all.[..] You just symlink it into .wine/dosdevices, e.g. 

ln -s /dev/ttyUSB ~/.wine/dosdevices/com1

[edit] Parallel Port

Sept 06 wine user a poster : I need [..] to set the port numbers for direct access. In the old version of wine it was: 

[ports]
"read"  = "0x378-0x37f,0x778,0x779-0x77a" "write"  =
"0x378-0x37f,0x778,0x779-0x77a"

D. Skorka: According to the Wine Users Guide ... http://wiki.winehq.org/UsefulRegistryKeys [these settings go] under HKCU/Software/Wine/VDM/ppdev

However the poster said: I know about this UsefulRegistryKeys but there is only how to set mapping between port_number and /dev/parportN device. I need the direct access to the port without some device.

D. Kegel: Believe it or not, the same registry keys control both modes of parallel port access. See http://source.winehq.org/source/dlls/winedos/ioports.c

The poster reported success:I have solved my problem, [as] I have set the registry in /software/wine/vdm/ppdev 

[Software\\Wine\\VDM\\ppdev] 1158041439 
"378"="/dev/parport0"
"379"="/dev/parport0"
"37a"="/dev/parport0"
"37b"="/dev/parport0"
"37c"="/dev/parport0"
"37e"="/dev/parport0"
"37f"="/dev/parport0"
"778"="/dev/parport0"
"779"="/dev/parport0"
"77a"="/dev/parport0"

and the most important thing was to run the application in win 98 "emulation mode". (I [had] ran it in win NT mode)

A programmer wrote [May 2007 wine user] I have a .sys driver for parallel port communication. But it seems wine didn't support loading the driver.

D. Riekenberg: As the first step, you should try to avoid the special Driver and use the Parallelport-Driver from Windows. The default Location in the ObjectManager for the first Parallel Port is: "\Device\Parallel0". 

(HKLM\Hardware\Devicemap\Parallel Ports\")

But Parallel Ports are unsupported in wine yet.... (For serial Ports, the Driver is: "dlls\ntdll\serial.c")

The programmer added: And directly accessing to parallel port is not allowed on the XP host, therefore _outp and _inp are useless.

D. Riekenberg: You need to use the Windows-API for the access: CreateFile / ReadFile / WriteFile and DeviceIOControl. [Mar 2007]


[2006]Direct access to the parallel port is necessary for programs such as EPROM burners or ones that use dongles.

This is very slow under wine and puts heavy load on the CPU, which is a known bug 3845 .

There are two ways:

1) The correct and safe way (which works with every parallel port):

Add a device mapping by adding the registry key "Software\Wine\VDM\ppdev". Then add a string entry for every port you want to use: 

"378" with value "/dev/parport0" for LPT1,
"278" with value "/dev/parport1" for LPT2,
...

Not all distributions provide the /dev/parport? entries by default, since they're not needed for normal printing. You can create /dev/parport0 with mknod /dev/parport0 c 99 0

Make sure that you have the ppdev driver in your kernel.

Now create a group for all users that should be allowed to access the parallel port and give /dev/parport? to it or just set the rights on /dev/parport? to 777.

2) Quick and dirty (which will only works with parallel ports that are located at the I/O locations the IBM PC uses for parallel ports):

Create the registry key "Software\Wine\VDM\Ports" and add string entries 

"read" = "0x779,0x379,0x280-0x2a0"
"write" = "0x779,0x379,0x280-0x2a0"

Run wine as root and you can use LPT1 and LPT2. [Ed. Note running wine as root is not recommended unless you are an expert user of wine.]

[Nov 05] a user posted: Try to set the windows version [as 2000 and then] add the following registry keys 

[HKEY_USERS\S-1-5-4\Software\Wine\VDM\Ports]
"read"="0x278-0x27f,0x378-0x37f"
"write"="0x278-0x27f,0x378-0x37f"

and run wine as root. That's how I made an eprom burner that has to do direct parallel port access work. wine archive

Scanners may give messages similar to what was described by one man: 

fixme:vxd:VXD_Open Unknown/unsupported VxD L"plkscnr.vxd". Try setting Windows version to 'nt40' or 'win31'.
fixme:vxd:VXD_Open Unknown/unsupported VxD L"scandrv.vxd". Try setting Windows version to 'nt40' or 'win31'.

many vxd drivers dont currently work on Wine due to design reasons. This can be avoided by changing the version of Windows using winecfg

P. Krause: It could be that you application tries to use the vxd files when running on Windows 2000, but do the I/O itself when running under Windows 98. wine archive

Further Reading

[edit] ODBC

A user posted: I have in an existing windows installation a large number of 'system DSN data sources' which I would like to have under wine. Is it possible to import these?

Another posted: The system DSN's are stored in the windows registry and can be exported using "regedit". Run regedit under windows and locate

HKEY_LOCAL_MACHINE/SOFTWARE/ODBC

right-click on the ODBC node to export its contents to a file. The result is a text file in a very similar format to the wine registry file and I believe it can be imported using the wine version of "regedit". Or you can just paste the contents into the (text based) wine registry file whilst changing the headers to match the wine registry header's style. wine archive

[edit] Time

During a discussion about where to store the information M.McCormack offered: TimeZones are stored in what Wine called the %CurrentVersion% key. It's easy enough to change the program that generates the data to put them in Windows NT\CurrentVersion if that's what is decided to be correct.

A. Jullard: In theory it should be under both, but for now we probably should put it under Windows NT only, until we find an app that depends on the Win9x location.

[edit] Drives

A user reported that for a cdrom:

HKLM/Software/Wine/drives (with name "D:", type "REG_SZ", and data "cdrom").

Drive Label and Serial settings seems to be unsupported.

[edit] Path

A user asked where to set the path for Wine. J. Earnst [Oct 05] Use regedit and edit the key at wine archive:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Environment

Another user found his software tried to add the path to autoexec.bat [Dec 05]: the GTK dll path was in autoexec.bat, but it seems wine doesn't take care about it, so i added the dll path to the wine path in system.reg:

PATH"="c:\\windows\\system;c:\\windows;c:\\Program Files\\FichiersCommuns\\GTK\\2.0\\bin"

[edit] Path for Dlls

A programmer noted that Dreamweaver MX6 looks in the registry: For additional directory locations to search for DLLs.

HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\App Paths\\EXENAME.EXE

M. McCormack [Oct 06]: The App Pathes key is checked by ShellExecute, not by CreateProcess. [He then explained how to work around this] Try running "wine start exename.exe" wine archive

[edit] Networking

[edit] Netbios

J. Lang: [April 06] [For] NetBIOS [...] the registry has to be set up [...] You have to set up the WINS servers, if you use them. This isn't documented except in the code (dlls/netapi32/nbt.c.) It's marked with the usual @@ Wine registry key tag. There are some other things you can tweak if necessary. I suppose this could go into winecfg. It can't go into wine.inf, because we can't guess correct values. .[...] Broadcast name resolution works without any setup, and WINS can be added by those that use it. (That should probably be documented someplace.) wine archive

[edit] DNS NameServer

R. Klazes [Nov 05]: Lots, if not most, of applications would use the winsock function gethostbyname, which is handled by the Unix gethostbyname function. That works fine ;)

If I add the string registry value

HKLM\System\CurrentControlset\Services\Tcpip\Parameters\DhcpNameServer

and fill it the IP address of a name server it works here. A NT4 nslookup.exe worked immediately, a Win2K version only if I did set the version to NT4. wine archive


[edit] Proxy Server

R. Holt [Dec 05] was trying to use wine with some M$ software from behind [a] company firewall: All outgoing connections need to go through our proxy server.[...] To get it to work, I edited my ~/.wine/user.reg and added in the section titled:

[Software\\Microsoft\\Windows\\CurrentVersion\\Internet Settings] 1133455573
"ProxyEnable"=dword:00000001
"ProxyServer"="www-proxy.[redacted].org:8080"

A poster tried:

ftp_proxy=ftp://[redacted.bla.com.port]
http_proxy=http://proxy...
https_proxy=http://proxy... no_proxy='localhost, [redacted]'

Any ideas why it doesn't start the download?

M. Hearn:Wine doesn't currently support these environment variables. I sent a patch to add support for $http_proxy so this would work but it hasn't been checked in yet. Until Alexandre makes a decision you must manually fiddle with the registry to set the proxy settings. wine archive

The user then reported I added below

[Software\\Microsoft\\Windows\\CurrentVersion\\Internet Settings]
147164925
@=""

[The following]

"ProxyEnable"=dword:00000001
"ProxyServer"="proxy.[redacted:port]"

in the user.reg and it started and completed the download. But after this, iexplore.exe just blinked and closed again

[edit] Internet Explorer

Faking it..

P. Vriens [Jul 06 regarding MSN Messenger] if you add \HKLM\SOFTWARE\Microsoft\Internet Explorer\Version (REG_SZ with 6.0.2900.2180) it installs.

D. Kegel: So many apps need this that I use a shell script to create it: http://kegel.com/wine/fakeie.sh.txt (One of these days I'll make that script use regedit...) wine archive

[edit] Links

[edit] Wine Links

Retrieved from "http://wiki.jswindle.com/index.php/Wine_Registry"
Personal tools