August 2002 - Wine-Devel - list.winehq.org

Re: 10072002 version - printing bug

by leanne

leanne wrote: > Huw D M Davies wrote: > >> On Wed, Jul 24, 2002 at 05:33:54PM +0800, leanne wrote: >> >>> Dear all, >>> >>> I found the 10072002 version of WINE that the layout of printout got >>> problems. >>> some letters overlap. >>> >> >> This is probably a bug in the Type 42 font download code. Could you >> try editting your ppd file (by default generic.ppd) and chaging the line >> *TTRasterizer: Type42 >> to >> *TTRasterizer: None >> this will get Wine to download the fonts as Type 1 outlines instead. >> >> Let me know if it makes a difference. >> >> Huw. >> > I did but still got the same result. I read the documentation about > printing. > I am using CUPS for printing > Should I config ppd file? > I did it anyway. I installed cups-drivers-1.9-0 > I unzipped and copied HP-LaserJet_4-ljet4-cups.ppd.gz in my ~/.wine/ > and I have added [ppd] in "config" > but got the same result. > > My printer is HP Laserjet 1200. When I set up the printer using CUPS > I am using HP Laser-4 driver and I can print test page. > > Many Thanks. Please have a look of the scanned version of my 2 printouts. (http://www.comp.polyu.edu.hk/~csltsang/wine_printout.png You will see some English letters are overlapping. And for the Chinese on the 2nd memo, it should contain 5 words but now only the first word can be printed.

Aug. 23, 2002

Re: quick question about windows.h and then a long one if anyone is interested.

by Steven Edwards

> You should use Wine headers only. If they are incomplete or cause you trouble those > incompatibilities should be fixed. WINE headers work well under mingw. I am trying to build the wine programs and dlls with mingws headers so I can see where they are incompleate. It would be nice if long term all of our projects could share one set of headers. ReactOS is in the process of merging its header base with mingw so we wont need to maintain our own set of Win32api headers. Thanks Steven __________________________________________________ Do You Yahoo!? Yahoo! Finance - Get real-time stock quotes http://finance.yahoo.com

Aug. 23, 2002

Re: spec file format changed?

by Michael Cardenas

Hello again. I found this cvs entry: http://cvs.winehq.com/patch.py?id=1020902756411430620894865 Describing how imports have to be moved to Makefiles and out of spec files. and by looking at parser.c in winebuild, I see that when alexandre removed the need for "type win32" entries, he made it a required change, so now winebuild terminates if it finds a "type win32" line in a spec file. michael -- michael cardenas | lead software engineer | lindows.com | hyperpoem.net "Be the change you want to see in the world" - Mahatma Gandhi

Aug. 23, 2002

Bad icon drawing under native comctl32

by Bill Medland

Any ideas? I'll try and get together a reasoanbly sized test case. When our application runs using the native comctl32 the icons in the SysListview32 are displayed with random black pixels in the background. The pattern varies between icons and between runs of the application. Bill

Aug. 22, 2002

Re: wine systray and KDE tray

by Bill Medland

----- Original Message ----- From: "Medland, Bill" <Bill.Medland(a)accpac.com> To: "Wine devel (E-mail)" <wine-devel(a)winehq.com> Sent: Monday, August 12, 2002 11:25 AM Subject: wine systray and KDE tray > I just noticed the other day that the icon that used to appear nicely in the > KDE's tray has gone and now the WINE systray comes up (but without the icon > in it). Is this a deliberate change? > > Bill > > For the record, I've just solved this by changing the Managed back to Y; I guess I got confused. Bill

Aug. 22, 2002

spec file format changed?

by Michael Cardenas

Hello all. I'm trying to compile our wine tree with the latest release of wine, and it seems that some of the codeweavers' helper applications don't want to compile. Specifically, when tring to do a "make" in the utils directory, it complains about the spec file for geticon. LD_LIBRARY_PATH="/home/mbc/src/wineall/wine/library:/home/mbc/src/wineall/wine/dlls:$LD_LIBRARY_PATH" /home/mbc/src/wineall/wine/tools/winebuild/winebuild -fPIC -L/home/mbc/src/wineall/wine/dlls -sym geticon.tmp.o -o geticon.spec.c -spec ./geticon.spec ./geticon.spec:3: Expected name, id, length or ordinal make[1]: *** [geticon.spec.c] Error 1 make[1]: Leaving directory `/home/mbc/src/wineall/utils/geticon' make: *** [geticon] Error 2 Has the spec file format changed? According to the manpage in it's dir, it's the same, and according to the docs on winehq the format is unchanged. thanks for your time michael -- michael cardenas | lead software engineer | lindows.com | hyperpoem.net "A painting of a rice cake does not satisfy hunger." - Ancient saying

Aug. 22, 2002

Wine Win98 setup problems...

by Steve M

Hi, I am having problems getting Wine to startup right. I would like to know, is there a way you can use Windows 98 Second Edition setup CD from within Wine, or does it have to be pre-installed? (e.g. I did it with wine --winver win98 setup.exe) and here are the errors it came up with: fixme:cdrom:CDROM_GetIdeInterface not implemented for BSD fixme:reg:GetSystemInfo noy yet supported on this system wine: Unhandled exception, starting debugger... err:seh:EXC_DefaultHandling Unhandled exception code c0000005 flags 0 addr 0x2811563e I loaded the program using KDE 3.0, included in FreeBSD 4.6 Stable. Basically, this is the wine that came "out of the box"(as opposed to the tarball). I have checked other posts and I have corrected my .wine/config file for my cdrom, but it still comes up with the same error(This was based on the GetSystemInfo error msg). The only thing I changed was my config file and the error that complained about the SHAREDMEMLOCATION variable, which I copied from the source tarball(Wine-20020804.tar.gz). I tried to compile that source which is the same one on the CD, but to no avail. --------------------------- checking Wine base files --------------------------- 001. Checking for file "wine"... OK. 002. Checking for correct .so lib config (please wait)... Read on closed filehandle <LDCONF> at ./winecheck.pl line 225. Use of uninitialized value at ./winecheck.pl line 232. DEBUG: found libwine: OK. ----------------------------- checking config file ----------------------------- 003. Checking config file access... OK. >>> Checking drive A settings: 004. Checking Path option... OK. 005. Checking Type option... OK. 006. Checking device /dev/fd0... OK. 007. Checking Filesystem option... OK. --> OK. >>> Checking drive C settings: 008. Checking Path option... OK. 009. Checking Type option... OK. 010. Checking Filesystem option... OK. --> OK. >>> Checking drive D settings: 011. Checking Path option... OK. 012. Checking Type option... OK. 013. Checking device /dev/acd0c... OK. 014. Checking Filesystem option... OK. --> OK. >>> Checking drive E settings: 015. Checking Path option... OK. 016. Checking Type option... OK. 017. Checking Filesystem option... OK. --> OK. >>> Checking drive F settings: 018. Checking Path option... OK. 019. Checking Type option... OK. 020. Checking Filesystem option... OK. --> OK. --------------------- checking system devices used by Wine --------------------- 021. Checking sound device /dev/dsp... CRITICAL (no kernel driver for /dev/dsp?). - ADVICE: module loading problems ? Read /usr/src/linux/Documentation/modules.txt. 022. Checking audio mixer device /dev/mixer... OK. 023. Checking MIDI sequencer device /dev/sequencer... BAD (no kernel driver for /dev/sequencer?). - ADVICE: module loading problems ? Read /usr/src/linux/Documentation/modules.txt. ----------------------- checking registry configuration ------------------------ 024. Checking availability of winedefault.reg entries... OK. 025. Checking availability of windows registry entries... CRITICAL (entry "Default Taskbar" not found). - ADVICE: Windows registry does not seem to be added to Wine, as this typical Windows registry entry does not exist in Wine's registry. Thi lete original Windows registry entry set will *not* be available with a no-windows install, of course, so you'll have to live with that.. 25 tests. 0 suspicious, 1 bad, 2 critical, 0 failed. Wine configuration correctness score: 68.64% ... Any hints on how to correct these errors? Also, my /dev/dsp is symlinked to /dev/dsp0. I have a Sound Blaster Live, which comes up as follows: bash-2.05a# dmesg | grep pcm pcm0: <Creative EMU10K1> port 0xe000-0xe01f irq 11 at device 12.0 on pci0 ... Anything to make this thing work right, is worth a try! Thanks for your time! __________________________________________________ Do You Yahoo!? HotJobs - Search Thousands of New Jobs http://www.hotjobs.com

Aug. 22, 2002

IDA stopped working

by Shachar Shemesh

Hi all, somewhere back (havn't checked when, yet), some change in WINE made IDA (The Interactive Disassembler) stop working. I am talking about the bought version, have not checked the free one. Initial analysis (using IDA) suggest some heavy anti-disassembler techniques were used in this executable. One thing that is immediatly visible, however, is that the base address (as well as the address IDA is loading under windows) is different than the on in WINE. Wine: Execution starts at 0x006fb000 Windows, as well as static base address: Execution starts at 0x00599000 I believe this may be a hint, together with the fact it is employing some wierd arithmetics on the PC to stop static analysis using tools such as IDA ;-). Before I go through the tiring process of CVSing back and finding the patch that killed it, anyone happens to know who's using 00599000 and causing the conflict? Is there any simple way to check this? Shachar

Aug. 22, 2002

Re: Declaring debugging channel

by Dimitrie O. Paun

On August 22, 2002 11:36 am, Andriy Palamarchuk wrote: > In what cases do I need to declare a debugging > channel? > As I see some debugging channels are declared with > WINE_DECLARE_DEBUG_CHANNEL (e.g. channels cursor, > icon, resource). You normally need to just declare a default one with WINE_DEFAULT_DEBUG_CHANNEL Normally, if the source is nicely partitioned in files, there is no need to use more than one channel per file, and hence no need to use WINE_DEFAULT_DEBUG_CHANNEL. This is needed only when you want to use in one file more then the default channel. > Some other channels are used and not declared > anywhere, e.g. (e.g. channels in comctl32.dll - > animate, comtl, comboex). Eh??? [dimi(a)dimi wine]$ grep -n DEBUG dlls/comctl32/animate.c 38:WINE_DEFAULT_DEBUG_CHANNEL(animate); [dimi(a)dimi wine]$ grep -n DEBUG dlls/comctl32/comboex.c 36:WINE_DEFAULT_DEBUG_CHANNEL(comboex); > Documentation in DEVELOPER-HINTS seems obsolete > regarding this. Indeed. I will prepare a patch. -- Dimi.

Aug. 22, 2002

Declaring debugging channel

by Andriy Palamarchuk

In what cases do I need to declare a debugging channel? As I see some debugging channels are declared with WINE_DECLARE_DEBUG_CHANNEL (e.g. channels cursor, icon, resource). Some other channels are used and not declared anywhere, e.g. (e.g. channels in comctl32.dll - animate, comtl, comboex). Documentation in DEVELOPER-HINTS seems obsolete regarding this. Andriy __________________________________________________ Do You Yahoo!? HotJobs - Search Thousands of New Jobs http://www.hotjobs.com

Aug. 22, 2002