[Wine] Cannot enter correct number in IP field

[L. Rahyen]

On Thursday November 1 2007 00:35, Marco Aurélio Carvalho wrote:
> Em Qua 31 Out 2007, L. Rahyen escreveu:
> > On Wednesday October 31 2007 18:54, Marco Aurélio Carvalho wrote:
> > > Em Ter 30 Out 2007, L. Rahyen escreveu:
> > > > On Tuesday October 30 2007 13:50, Marco Aurélio Carvalho wrote:
> > > > > Hi folks.
> > > > > I am trying to use a windows Sw in wine. It appears to work
> > > > > correctly but in the connection setup window I cannot fill the
> > > > > correct IP.
> > > >
> > > > 	Make sure that you are using latest WINE version. Currently this is
> > > > 0.9.48. Then go to http://bugs.winehq.org and fill a bug report about
> > > > a bug you found. Thanks.
> > > > 	Please note that this is just a user support mailing list and most
> > > > developers even don't read it. So it is important to report your bug
> > > > at http://bugs.winehq.org if you want to get your bug fixed.
> > > > 	Thank you for using WINE.
> > >
> > > I am using the latest version and reported the bug.
> > > The bug was discarded since there was another one similar.
> >
> > 	Discarded bugs marked as INVALID. Your bug is a duplicate of known
> > problem and was marked as such. Please note that it take typically weeks
> > or months to fix bug.
> >
> > > The explanation is that the font used in wine is bigger than the field
> > > and part of it is thrown away.
> > > The problem continues for me , since I do not know how to force wine to
> > > use another font in that field.
> >
> > 	First install standard Windows fonts. If still doesn't work, you can try
> > following workarounds:
> > 	See http://wiki.winehq.org/UsefulRegistryKeys , Fonts -> Replacements
> > section. Of course you need to know what font you want to replace.
> > 	Also you can try to use native comctl32.dll. Add "comctl32" override in
> > winecfg and it should work. To be sure that you really using native
> > comctl32.dll you can either choose "native" instead of default "native,
> > builtin" loading order or run WINE like this:
> >
> > WINEDEBUG=+loaddll wine program.exe
>
> I placed the native comctl32.dll on the same program directory and changed
> order to native, built in . Worked perfectly. Thank you very much!
>
> In general I am trying to use all windows programs with wine.
> If a program fails, how could I identify the dll where is located a certain
> API routine? Starting a program from a terminal gives us some log
> information but not the dll (at least I do not know how to enhace the log
> information to this level).
> I have some programs that access serial or parallel ports. They do not work
> under wine (the program that was the motive of this discussion works fine
> with serial port, others do not). Maybe there are native dlls that should
> be used in those cases too. But how to identify them?

	Remember, using of native dlls is a workaround - not a solution! If you think 
that native is better than builtin - you're wrong.
	If program.exe doesn't workand you want to try to find a workaround for the 
bug you found, run:

WINEDEBUG=+loaddll wine program.exe

	You will see what DLLs are used by program.exe. Try to override DLL that 
might be responsible for the bug. For example, comctl32.dll contains common 
GUI components used by Windows applications so if you override it you 
may "solve" some related problems.
	If you really want to know how to find such workarounds, you need to know at 
least the basics about Windows API. At least you need to know what is the 
purpose of each DLL. For example, see  
http://www.liutilities.com/products/wintaskspro/dlllibrary/comctl32/ for 
short description for comctl32.dll. See "Top System DLLs Listed in the 
WinTasks DLL Library" at the bottom of page: you will find links to other 
popular DLLs and their short description. If you want more information, use 
Google, read documentation, etc... Maybe at some day you write a patch to fix 
something in WINE and make our life better.
	But never forget to report bugs to the WINE' bugzilla! If you found 
workaround then mention it in your bug report along with other information.
	Thanks for using WINE.