ReceiveTempSMS
/
Sweden-Number
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Remove references to debugmsg and winedefault.reg.

This commit is contained in:
Ivan Leo Puoti 2004-07-21 21:20:07 +00:00 committed by Alexandre Julliard
parent 5dd35d2a3f
commit 398d78e6fb
6 changed files with 18 additions and 35 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
documentation/PACKAGING
View File

@ -468,14 +468,6 @@ Example (split this into %build and %install section for rpm:
# The Wine server is needed.
install -m 755 server/wineserver $BR/usr/X11R6/bin/
Here we unfortunately do need to create wineuser.reg and winesystem.reg
from the Wine distributed winedefault.reg. This can be done using regedit
once for one example user and then reusing his WINEPREFIX/user.reg and
WINEPREFIX/system.reg files.
FIXME: this needs to be done better.
install -m 644 wine.sytemreg $BR/etc/wine/
install -m 644 wine.userreg $BR/etc/wine/
There are now a lot of libraries generated by the build process, so a
separate library directory should be used.

12
documentation/configuring.sgml
View File

@ -2709,12 +2709,12 @@ export LIB_ODBC_DRIVER_MANAGER=/usr/lib/libodbc.so.1.0.0
calling code and the Unix ODBC library.
</para>
<para>
If you have any problems then you can use the debugmsg channel
odbc32 to trace what is happening. One word of warning. Some
programs actually cheat a little and bypass the ODBC library. For
example the Crystal Reports engine goes to the registry to check on
the DSN. The fix for this is documented at unixODBC's site where
there is a section on using unixODBC with Wine.
If you have any problems then you can use WINEDEBUG=+odbc32 command
before running wine to trace what is happening. One word of
warning. Some programs actually cheat a little and bypass the ODBC
library. For example the Crystal Reports engine goes to the registry
to check on the DSN. The fix for this is documented at unixODBC's
site where there is a section on using unixODBC with Wine.
</para>
</sect2>
<sect2>

4
documentation/implementation.sgml
View File

@ -133,12 +133,12 @@ WINEDEBUG=+key,+keyboard wine > key.log 2>&1
<constant>SUBLANG_*</constant> definitions are in
<filename>include/winnls.h</filename>, which you might need to
know to find out which numbers your language is assigned, and
find it in the debugmsg output. The numbers will be
find it in the WINEDEBUG output. The numbers will be
<literal>(SUBLANG * 0x400 + LANG)</literal>, so, for example
the combination <literal>LANG_NORWEGIAN (0x14)</literal> and
<literal>SUBLANG_DEFAULT (0x1)</literal> will be (in hex)
<literal>14 + 1*400 = 414</literal>, so since I'm Norwegian, I
could look for <literal>0414</literal> in the debugmsg output
could look for <literal>0414</literal> in the WINEDEBUG output
to find out why my keyboard won't detect.
</para>
<para>

2
documentation/multimedia.sgml
View File

@ -990,7 +990,7 @@
<para>
Configuration of low level drivers is done with the Wine configuration file.
Default keys are provided in winedefault.reg.
Default keys are provided in wine.inf.
</para>
<para>

13
documentation/printing.sgml
View File

@ -135,7 +135,7 @@
<para>
You also need to add certain entries to the registry.
The easiest way to do this is to customize the PostScript
driver contents of <filename>winedefault.reg</filename> (see below) and use the
driver contents of <filename>wine.inf</filename> (see below) and use the
Winelib program <command>programs/regedit/regedit</command>. For
example, if you have installed the Wine source tree in
<filename>/usr/src/wine</filename>, you could use the following
@ -143,24 +143,19 @@
<itemizedlist>
<listitem>
<para>
<userinput>cp /usr/src/wine/winedefault.reg ~</userinput>
<userinput>#vi /usr/share/wine/wine.inf</userinput>
</para>
</listitem>
<listitem>
<para>
<userinput>vi ~/winedefault.reg</userinput>
</para>
</listitem>
<listitem>
<para>
Edit the copy of <filename>winedefault.reg</filename> to suit your
Edit the copy of <filename>wine.inf</filename> to suit your
PostScript printing requirements.
At a minimum, you must specify a PPD file for each printer.
</para>
</listitem>
<listitem>
<para>
<userinput>regedit ~/winedefault.reg</userinput>
<userinput>$wineprefixcreate</userinput>
</para>
</listitem>
</itemizedlist>

14
documentation/registry.sgml
View File

@ -19,23 +19,19 @@
them are necessary for even installers to operate correctly.
The keys that the Wine developers have found necessary to
install applications are distributed in a file called
<filename>winedefault.reg</filename>. It is automatically
<filename>wine.inf</filename>. It is automatically
installed for you if you use the
<filename>tools/wineinstall</filename> script in the Wine source,
but if you want to install it manually, you can do so by using the
<command>regedit</command> tool to be found in the
<filename>programs/regedit/</filename>
directory in Wine source.
<filename>winedefault.reg</filename> should even be applied if
<filename>wine.inf</filename> is applied even if
you plan to use a native Windows registry, since Wine needs some
specific registry settings in its registry (for special
workarounds for certain programs etc.).
In the main Wine source code directory in a <glossterm>terminal</glossterm>, run:
</para>
<screen>
<prompt>$ </><userinput>cd programs/regedit</>
<prompt>$ </><userinput>./regedit ../../winedefault.reg</>
</screen>
This is done automatically by wine the first time you run it.
</para>
</sect2>
<sect2>
@ -60,7 +56,7 @@
<para>
The initial default registry content to be used by the Wine
registry files is in the file
<filename>winedefault.reg</filename>. It contains directory
<filename>wine.inf</filename>. It contains directory
paths, class IDs, and more; it must be installed before most
<filename>INSTALL.EXE</filename> or
<filename>SETUP.EXE</filename> applications will work.