July 2003 - Wine-Devel - list.winehq.org

Re: having problems with my spec file for cards.dll

by Steven Edwards

--- Jon Bright <jon(a)siliconcircus.com> wrote: > Should I understand from this that Wine should build under Cygwin? > Certainly, it doesn't here - there's a series of errors related to > functions with the @suffixes... > > If it's supposed to build, I can happily supply the errors in question... 99% of WINE should build under cygwin. I assume the problems you are having is in the linking of ntdll and kernel32. These linking errors wont be resolved until dll seperation is compleate. Almost all of the other dlls, programs and Wineserver should build with only minor tweaking/stubbing. Thanks Steven __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

July 25, 2003

Re: having problems with my spec file for cards.dll

by Dmitry Timoshkov

"Jon Bright" <jon(a)siliconcircus.com> wrote: > > will need to do anyway). Wine makefiles already have all the needed > > tweaks to strip stdcall @xx suffixes when building under MinGW or Cygwin. > > Should I understand from this that Wine should build under Cygwin? It has some problems (notably for ntdll, kernel and iphlpapi) but mostly it should build. Running Wine under Cygwin is a whole other story. > Certainly, it doesn't here - there's a series of errors related to > functions with the @suffixes... > > If it's supposed to build, I can happily supply the errors in question... It shouldn't have problems if you have reasonably recent binutils installed. -- Dmitry.

July 25, 2003

RE: Direct access to LPT1

by E Lea

> E> I'm playing around with a program that controls a small "design > E> cutter" - it's basically a plotter that connects via the parallel > E> port. > > E> There is some Windows CAD software that knows about the plotter and > E> sends commands to it, as far as I can tell in one of two ways: > > E> 1) Through a printer driver. It doesn't seem too bothered about the > E> details of the driver though. I'm assuming that one would normally > E> use a generic, text-only Windows driver. This method, apparently, has > E> the advantage of the driver buffering the output > > Wine can't run Ring 0 drivers, like something ending in .sys/ .vxd The plotter doesn't need a specific driver - it doesn't even have one. In Windows it uses any old printer driver just to open the printer port, then sends commands to the plotter through the printer driver. Should it not be possible to do this with Wine? Possibly not with CUPS though...

July 25, 2003

Re: having problems with my spec file for cards.dll

by Jon Bright

Hi, Dmitry Timoshkov wrote: > will need to do anyway). Wine makefiles already have all the needed > tweaks to strip stdcall @xx suffixes when building under MinGW or Cygwin. Should I understand from this that Wine should build under Cygwin? Certainly, it doesn't here - there's a series of errors related to functions with the @suffixes... If it's supposed to build, I can happily supply the errors in question... -- Jon Bright Lead Programmer, Silicon Circus Ltd. http://www.siliconcircus.com

July 25, 2003

RE: Direct access to LPT1

by Uwe Bonnes

>>>>> "E." == E Lea <ed(a)centralmanclc.com> writes: >>... E.> [ppdev] "378" = "/dev/parport0" E.> [ports] "read" = "0x779,0x378,0x379,0x280-0x2a0" "write" = E.> "0x779,0x378,0x379,0x280-0x2a0" E.> in my ~/.wine/config E.> Should this be enough to get it working? Or does the fact I get E.> error messages about not being able to open LPT1 mean that the E.> Windows program is behaving in such a way that the port access E.> translation you describe will never work? Probably not. Your program seems to use unsupported ways... >> Perhaps look around if you don't find some tool that talks to your >> device with direct hardware access. E.> Win31 >> programms might do so. E.> I unfortunately don't have any choice in the tool I use - I'm tied E.> to a specific app. Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

July 25, 2003

Re: having problems with my spec file for cards.dll

by Dmitry Timoshkov

"Jonathan Wilson" <jonwil(a)tpgi.com.au> wrote: > > Only native Win32 compilers do that. gcc under Linux doesn't generate > > that crap. > aah, I was using MingW on windows to test the dll. You can use Wine build system in order to test your dll. For that you just need to make your new dll a part of the Wine dll tree (which you will need to do anyway). Wine makefiles already have all the needed tweaks to strip stdcall @xx suffixes when building under MinGW or Cygwin. > Looks like my .spec file should work when I solve this bitblt problem, > finish testing and move the code over to linux to add it to my WINE tree. ok. -- Dmitry.

July 25, 2003

Re: having problems with my spec file for cards.dll

by Dmitry Timoshkov

"Jonathan Wilson" <jonwil(a)tpgi.com.au> wrote: > the MS Cards.dll is complled with "the dll does the cleanup" set to on > (i.e. its using retn xx instructions). That's how pascal (stdcall) calling convention works. > When I compile it, i get the @nn on the end of the names. Only native Win32 compilers do that. gcc under Linux doesn't generate that crap. > This is a problem since cards.dll exports the names without the @nn > How do I set things up in my .spec file? Same way as in all other .spec files in Wine: @ stdcall cool_cards_api() -- Dmitry.

July 25, 2003

having problems with my spec file for cards.dll

by Jonathan Wilson

the MS Cards.dll is complled with "the dll does the cleanup" set to on (i.e. its using retn xx instructions). When I compile it, i get the @nn on the end of the names. This is a problem since cards.dll exports the names without the @nn How do I set things up in my .spec file?

July 25, 2003

RE: Direct access to LPT1

by E Lea

> > E> 2) The second method is a direct connection to LPT1. > E> With Wine, in the first case I get a message in a dialog box saying > E> the call to "StartDocPrinter" failed and > E> fixme:winspool:StartDocPrinterA (hPrinter=0x1, Level=0x1, > E> pDocInfo=0x408a28dc): stub > E> to stdout. > E> In the second case I get a dialog saying "LPT1 was not found" and > E> fixme:dosfs:DOSFS_OpenDevice device open L"LPT1" not supported (yet) > E> err:file:CreateFileW Couldn't open device L"LPT1"! > E> to stdout. > E> Is this a config issue? I'm assuming that is should be easier for me > E> to get the second method working. > > No. You hit an area of unimplemented functionality. > > However Win can translate direct port accesses, either as root to inp/outp > or when configured right, via /dev/parport I have ppdev, parport_pc and lp kernel modules installed. And [parallelports] "Lpt1" = "/dev/lp0" [ppdev] "378" = "/dev/parport0" [ports] "read" = "0x779,0x378,0x379,0x280-0x2a0" "write" = "0x779,0x378,0x379,0x280-0x2a0" in my ~/.wine/config Should this be enough to get it working? Or does the fact I get error messages about not being able to open LPT1 mean that the Windows program is behaving in such a way that the port access translation you describe will never work? > Perhaps look around if you don't > find some tool that talks to your device with direct hardware access. Win31 > programms might do so. I unfortunately don't have any choice in the tool I use - I'm tied to a specific app.

July 25, 2003

[patch] build.sgml (was Re: documentation patches)

by Peter Hanecak

Hello again, On Fri, 25 Jul 2003, Peter Hanecak wrote: > On 22 Jul 2003, Vincent [ISO-8859-1] Béron wrote: > > > Le mar 22/07/2003 ŕ 12:43, Peter Hanecak a écrit : > > > > > > while building Wine on "RedHat 8"-like system I encountered two typos in > > > Wine documentation which prevented me from "compiling" documentation with > > > jade (openjade-1.3.1-9). > > There are then two things I have to solve: > > 1) patch to build.sgml: I was quite hasty and sent it before final test so > it is incomplete - I'll send verified and hopefully complete patch > soon. [quotes above has been shortened] I'm sending fixed patch for build.sgml - documentation "build" actualy finished without error. Sincerely Peter -- ======================================================== Peter Hanecak <hanecak(a)megaloman.sk> GPG pub.key: http://www.megaloman.sk/gpg/hanecak.txt ========================================================

July 25, 2003