April 2001 - Wine-Devel - list.winehq.org

Re: Quickbooks 5 and printing

by Dan Engel

Sean A. Walberg wrote: > After a long break, I'd like to figure out why quickbooks 5 can't print. > wineps works, ie I can print in notepad, but QB seems to implement its own > printing mechanism. > I would like to figure it out, too. Here's what I've done so far: Using "--debugmsg warn+all,+relay,+text,+string" I found that it's trying to load "wineps.drv.dll" which translates into "libwineps.drv.so". This doesn't work, and it appears that the QB code is what's adding the .DRV to the WINEPS print driver name. I hacked around that by checking for WINEPS.DRV at the beginning of BUILTIN_LoadModule and replacing it with WINEPS. After that the .so file was being loaded but the dll, "wineps.dll" couldn't be found (again, according to BUILTIN_LoadModule). Doing some more hacking shows that the __wine_dll_register is being called for wineps.dll. It seems to me that this means that the name (wineps.dll) should be registered and therefore the dll should be found. I'll be hacking on this some more, as time allows. I'm extremely new to Wine code--I'm hoping that something I've done makes the problem obvious to a more seasoned veteran. . . :-) -Dan Engel

April 24, 2001

Re: fault handling - oof

by Francois Gouget

On Tue, 24 Apr 2001 lawson_whitney(a)juno.com wrote: [...] > I got what looked like a recursive page fault somewhere in > startup/fixup_imports until I reverted all 3. It _might_ be a local > misconfiguration, so don't waste too much time on it, but if you spot > something that could be a bit wrong in one of these patches, please let > me know. > > N 1 Apr 23 Alexandre Julliard (2,414) wine/dlls/msvcrt time.c > N 2 Apr 23 Alexandre Julliard (2,089) wine/include/msvcrt stddef.h > N 3 Apr 23 Alexandre Julliard (2,071) wine/debugger types.c > > I can't see how it could be any of them, but I guess it must be > stddef.h. The app insists so far on native msvcrt. I keep hoping that > will change. If you're using native msvcrt then the first two should have no impact. If you meant that the crash only occurs when you try using the builtin msvcrt then maybe it's the patch to time.c. But I would still don't see why... quite the opposite. Let us know if you find out more about this. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ {free} || die "";

April 24, 2001

fault handling - oof

by lawson_whitney＠juno.com

Good day! One or all of these 3 patches has somehow broken fault hanlding for my mail app. As I seem to have it sort of working again, I wanted to get out a warning, and sorry I can't be more specific yet. The app also doesn't like to be forced to use a local phone number that is not in its current list but still works. I can't blame it, but I am damned if I will have it adding $.05 to my phone bill every time I send or get mail. I got what looked like a recursive page fault somewhere in startup/fixup_imports until I reverted all 3. It _might_ be a local misconfiguration, so don't waste too much time on it, but if you spot something that could be a bit wrong in one of these patches, please let me know. N 1 Apr 23 Alexandre Julliard (2,414) wine/dlls/msvcrt time.c N 2 Apr 23 Alexandre Julliard (2,089) wine/include/msvcrt stddef.h N 3 Apr 23 Alexandre Julliard (2,071) wine/debugger types.c I can't see how it could be any of them, but I guess it must be stddef.h. The app insists so far on native msvcrt. I keep hoping that will change. Regards, Lawson ---cut here ________________________________________________________________ GET INTERNET ACCESS FROM JUNO! Juno offers FREE or PREMIUM Internet access for less! Join Juno today! For your FREE software, visit: http://dl.www.juno.com/get/tagj.

April 24, 2001

Re: problem with native dll's.

by Martin Pilka

> Yup, reverting your 04/13/2001 server patch enabled my no-Windows > install of Notes/Wine to start working again. > > With recent CVS versions of Wine, Notes 5.0.3 was dying with: > > err:win32:fixup_imports No implementation for KERNEL32.dll.0() imported > from C:\windows\system\netbios.dll, setting to 0xdeadbeef > err:win32:fixup_imports No implementation for KERNEL32.dll.0() imported > from C:\windows\system\netbios.dll, setting to 0xdeadbeef > err:ntdll:RtlpWaitForCriticalSection Critical section 0x40a9bd90 wait > timed out, retrying (60 sec) fs=021f i had the very same problem, "fixed" with "netbios=builtin" workaround... martin

April 23, 2001

Re: Virtual memory under Win95

by Alexandre Julliard

"Dmitry Timoshkov" <dmitry(a)sloboda.ru> writes: > Perhaps applications which use assumptions about Win95 virtual memory > management should be considered as broken? Or it is worth to support them? What should be considered broken is the memory management of Win95 ;-) But yes, we should probably forget about making this kind of things work, we cannot possibly support the Win95 memory model 100% right anyway. Especially since the app works with -winver nt40, I think that's a reasonable work-around. -- Alexandre Julliard julliard(a)winehq.com

April 23, 2001

Re: Msvcrt fixes

by Francois Gouget

On Mon, 23 Apr 2001, Michael Mauch wrote: > Francois Gouget <fgouget(a)free.fr> wrote: [...] > The ctime manpage here is from 1996 (glibc-2.0.7 I guess), it came with > the distribution. I don't see any glibc-2.1.3 or glibc-2.2 manpages, > only texinfo/info files. Maybe they don't maintain man pages anymore. > > The localtime info from glibc-2.2 says: > | > | - Function: struct tm * localtime (const time_t *TIME) > | The `localtime' function converts the simple time pointed to by > | TIME to broken-down time representation, expressed relative to the > | user's specified time zone. > | > | The return value is a pointer to a static broken-down time > | structure, which might be overwritten by subsequent calls to > | `ctime', `gmtime', or `localtime'. (But no other library function > | overwrites the contents of this object.) > | > | The return value is the null pointer if TIME cannot be represented > | as a broken-down time; typically this is because the year cannot > | fit into an `int'. > | > | Calling `localtime' has one other effect: it sets the variable > | `tzname' with information about the current time zone. *Note Time > | Zone Functions::. > | > | Using the `localtime' function is a big problem in multi-threaded > | programs. The result is returned in a static buffer and this is used in > | all threads. POSIX.1c introduced a variant of this function. > > And then follows the description for localtime_r(). Ah, well, that's much better. It great even. So it's not glibc's fault. <venting> And, wonder of wonders, I even have it on my system. It's provided by glibc-doc in 'file:/usr/share/doc/glibc-doc/html/chapters_20.html'. But of course!!! That's such an obvious place to look at. Who would be so naive as to type 'man localtime'! Of course you won't find it if you go to the index page because it's all screwed up. The best way is to 'grep -l localtime /usr/share/doc/glibc-doc/html/*.html'. And it's wonderfully inconsistent with the man pages provided by the manpages-dev package. But I'm sure this will be fixed in 3-4 years time. I love Debian. </venting> -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ War doesn't determine who's right. War determines who's left.

April 23, 2001

Re: Msvcrt fixes

by michael.mauch＠gmx.de

Francois Gouget <fgouget(a)free.fr> wrote: [patch for glibc manpage] > I wonder where I should send it. Since I'm lazy I guess I will just > send it over to Debian where it will join the 2+ years old bug reports > for the manpages-dev package. (maybe I should check the source first > though :-/) The ctime manpage here is from 1996 (glibc-2.0.7 I guess), it came with the distribution. I don't see any glibc-2.1.3 or glibc-2.2 manpages, only texinfo/info files. Maybe they don't maintain man pages anymore. The localtime info from glibc-2.2 says: | - Function: struct tm * localtime (const time_t *TIME) | The `localtime' function converts the simple time pointed to by | TIME to broken-down time representation, expressed relative to the | user's specified time zone. | | The return value is a pointer to a static broken-down time | structure, which might be overwritten by subsequent calls to | `ctime', `gmtime', or `localtime'. (But no other library function | overwrites the contents of this object.) | | The return value is the null pointer if TIME cannot be represented | as a broken-down time; typically this is because the year cannot | fit into an `int'. | | Calling `localtime' has one other effect: it sets the variable | `tzname' with information about the current time zone. *Note Time | Zone Functions::. | | Using the `localtime' function is a big problem in multi-threaded | programs. The result is returned in a static buffer and this is used in | all threads. POSIX.1c introduced a variant of this function. And then follows the description for localtime_r(). Regards... Michael

April 23, 2001

Re: Msvcrt fixes

by Andreas Mohr

On Mon, Apr 23, 2001 at 12:27:58AM -0700, François Gouget wrote: > Btw, the Linux localtime documentation sucks. It's even worse than > the MS one!!! Err, fix it ? ;-) Really, what is an Open Source programmer supposed to do when he realizes that something sucks ? Food for thought, -- Andreas Mohr Stauferstr. 6, D-71272 Renningen, Germany Tel. +49 7159 800604 http://home.germany.net/100-30936/

April 23, 2001

Re: Msvcrt fixes

by Francois Gouget

On Mon, 23 Apr 2001, Andreas Mohr wrote: > On Mon, Apr 23, 2001 at 12:27:58AM -0700, François Gouget wrote: > > Btw, the Linux localtime documentation sucks. It's even worse than > > the MS one!!! > > Err, fix it ? ;-) > > Really, what is an Open Source programmer supposed to do when he realizes > that something sucks ? Would that do it? --- cut here --- --- ctime.3.orig Mon Apr 23 00:47:46 2001 +++ ctime.3 Mon Apr 23 00:50:24 2001 @@ -139,7 +139,9 @@ information about the current time zone, \fItimezone\fP with the difference between Coordinated Universal Time (UTC) and local standard time in seconds, and \fIdaylight\fP to a non-zero value if standard US daylight -savings time rules apply. +savings time rules apply. The return value points to a statically +allocated \fItm\fP structure which might be overwritten by subsequent +calls to any of the date and time functions. .PP The \fBasctime()\fP function converts the broken-down time value \fItimeptr\fP into a string with the same format as \fBctime()\fP. --- cut here --- I wonder where I should send it. Since I'm lazy I guess I will just send it over to Debian where it will join the 2+ years old bug reports for the manpages-dev package. (maybe I should check the source first though :-/) -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ The software said it requires Win95 or better, so I installed Linux.

April 23, 2001

Re: Virtual memory under Win95

by Uwe Bonnes

>>>>> "Dmitry" == Dmitry Timoshkov <dmitry(a)sloboda.ru> writes: ... Dmitry> Could you (or anybody else with a Win95 machine) add the Dmitry> following lines at the end of the previous test program and Dmitry> report the result? This is with win98seg hMapping = 0014 p = 82D7E000 VirtualQuery(82D7E000) ret=0x1c BaseAddress = 82D7E000 AllocationBase = 82D7E000 AllocationProtect = 0x00000001 RegionSize = 0x0400f000 State = 00002000 Protect = 00000001 Type = 00020000 VirtualQuery(82D8E000) ret=0x1c BaseAddress = 82D8E000 AllocationBase = 82D7E000 AllocationProtect = 0x00000001 RegionSize = 0x03fff000 State = 00002000 Protect = 00000001 Type = 00020000 -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

April 23, 2001