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

Re: ReactOS GPL vs. proprietary drivers - NTFS Driver under Linux + WINE
by Steven Edwards Oct. 20, 2003

Oct. 20, 2003

Hello Jan, Comments are inline. --- Jan Kratochvil <rcpt-ros-kernel.AT.reactos.com(a)jankratochvil.net> wrote: > Hi, > > As GPLed Linux-NTFS still has no NTFS r/w capability I completed the > project > for reliable r/w access in Wine way by using MS-Windows ntfs.sys > driver. > > Captive-NTFS > http://www.jankratochvil.net/ I have forwarded this reply to wine-devel as they my find captive NTFS interesting > My project is GPL-2.0 and it incorporates ReactOS kernel sources > currently also > carrying GPL-2.0 license. There are rumours GPL may be problem for > linking with > proprietary code (ntfs.sys&ntoskrnl.exe). I interpret it as GPL only > affects > _distribution_ of the program while no proprietary code is > distributed with my > package. Proprietary code is only run-time linked by the end-user. > > > In a GPL-related discussion here two monts ago ReactOS developers > were open for > reusal of existing proprietary drivers for ReactOS as one of the > significant > feature of ReactOS. I would like an affirmation from the major > ReactOS > developers they are not going to try to sue me for releasing Captive > NTFS. I dont think you have to worry about any ReactOS developers filing suit. I would be more worried about one from Microsoft =). In fact I am very happy to see this. I would like to see the interface you have developed evolve in to a a full compatiblty layer addon for WINE so they can support other drivers. I must confess I have not had a chance to look at the code but if it works as you say then this is great news! If you dont distribute Captive NTFS with a Microsoft NTFS driver then you should not have a problem. You are correct the GPL seems to only cover distribution not use. Thanks Steven __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com

1 0

will it?
by John Smith Oct. 20, 2003

Oct. 20, 2003

now that windows drivers will work in linux, can wine run directx easy? with wine on linux, and having windows drivers, the wine shouldn't have any troubles whatsoever acting as windows

1 0

Re: MDI windows, MDIClient and mdiclient
by Fabian Cenedese Oct. 20, 2003

Oct. 20, 2003

>I'm trying to see why a propritery program misbehaves under wine, by comparing it to Windows. When running it under Windows, I don't have the luxury of OutputDebugString. Maybe even better: http://www.codeproject.com/useritems/DLL_Injection_tutorial.asp Already with a sample about logging winsock functions. bye Fabi

1 0

Re: named pipes problem?
by Alexandre Julliard Oct. 20, 2003

Oct. 20, 2003

Daniel Marmier <d.marmier(a)bluewin.ch> writes: > Are you talking about support for TLS in wine? > If so, is that already assigned? No, the problem is TLS support in glibc itself, since that bypasses our pthread wrappers. We don't need to use glibc-style TLS in Wine since we can use the Win32 TLS support instead. -- Alexandre Julliard julliard(a)winehq.com

2 1

named pipes problem?
by Gregory M. Turner Oct. 20, 2003

Oct. 20, 2003

Does everybody's kernel32 named pipes test pass (in wine)? Named pipes are acting very wierd here, lots of segfaults and other wierdness... the test seems to freeze attempting to create the alarmThread in test_NamedPipe_2 (test 3 of 4). The wineserver holds up OK, but the client side looks a mess. This is similar to other behavior I see in other contexts... perhaps, the pattern is, after I create a named pipe, subsequent calls to CreateThread never return or cause segfaults and general instability. Am I the only one? The following is a snippet from "strace -f wine kernel32_test.exe.so pipe" where wine starts to go south.... [pid 28568] write(1, "pipe.c:459:", 11pipe.c:459:) = 11 [pid 28568] write(1, "exercizeServer starting\n", 24exercizeServer starting ) = 24 [pid 28568] write(1, "pipe.c:470:", 11pipe.c:470:) = 11 [pid 28568] write(1, "Client connecting...\n", 21Client connecting... ) = 21 [pid 28568] rt_sigprocmask(SIG_BLOCK, [HUP INT USR1 USR2 ALRM IO], [RTMIN], 8) = 0 [pid 28568] writev(4, [{"\207\0\0\0\222\0\0\0\0\0\0\0\0\0\0\300\0\0\0\0\0\0\0\0"..., 64}, {"\\\0\\\0.\0\\\0P\0i\0P\0e\0\\\0t\0e\0s\0t\0s\0_\0.\0"..., 146}], 2 <unfinished ...> [pid 28570] <... poll resumed> [{fd=5, events=POLLIN}, {fd=4, events=POLLIN}, {fd=7, events=POLLIN}, {fd=9, events=POLLIN}, {fd=11, events=POLLIN}, {fd=13, events=POLLIN}, {fd=15, events=POLLIN}, {fd=16, events=POLLIN, revents=POLLIN}, {fd=-1}, {fd=-1}, {fd=-1}, {fd=-1}, {fd=-1}, {fd=-1}, {fd=24, events=POLLIN}, {fd=23, events=POLLIN}], 16, -1) = 1 [pid 28570] read(16, "\207\0\0\0\222\0\0\0\0\0\0\0\0\0\0\300\0\0\0\0\0\0\0\0"..., 64) = 64 [pid 28570] read(16, "\\\0\\\0.\0\\\0P\0i\0P\0e\0\\\0t\0e\0s\0t\0s\0_\0.\0"..., 146) = 146 [pid 28570] write(17, "\17\0\0\300\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 64) = 64 [pid 28570] poll( <unfinished ...> [pid 28568] <... writev resumed> ) = 210 [pid 28568] read(5, "\17\0\0\300\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 64) = 64 [pid 28568] rt_sigprocmask(SIG_SETMASK, [RTMIN], NULL, 8) = 0 [pid 28568] write(1, "pipe.c:481:", 11pipe.c:481:) = 11 [pid 28568] write(1, "connect failed, retrying\n", 25connect failed, retrying ) = 25 [pid 28568] gettimeofday({1066424342, 296207}, NULL) = 0 [pid 28568] gettimeofday({1066424342, 296363}, NULL) = 0 [pid 28568] select(0, NULL, NULL, NULL, {0, 199844} <unfinished ...> [pid 28575] --- SIGSTOP (Stopped (signal)) @ 0 (0) --- [pid 28574] --- SIGSTOP (Stopped (signal)) @ 0 (0) --- [pid 28575] modify_ldt(17, {entry_number:40, base_addr:0x40af3000, limit:4095, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:0, seg_not_present:0, useable:0}, 16 <unfinished ...> [pid 28574] modify_ldt(17, {entry_number:39, base_addr:0x408c3000, limit:4095, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:0, seg_not_present:0, useable:0}, 16 <unfinished ...> [pid 28575] <... modify_ldt resumed> ) = 0 [pid 28574] <... modify_ldt resumed> ) = 0 [pid 28575] sigaltstack({ss_sp=0x408d1000, ss_flags=0, ss_size=1048576} <unfinished ...> [pid 28574] brk(0 <unfinished ...> [pid 28575] <... sigaltstack resumed> , NULL) = 0 [pid 28574] <... brk resumed> ) = 0x3c009000 [pid 28575] rt_sigaction(SIGINT, {0x40081bf2, [INT USR2], SA_RESTORER|SA_STACK|SA_RESTART, 0x45a14eb8}, <unfinished ...> [pid 28574] brk(0x3c00a000 <unfinished ...> [pid 28575] <... rt_sigaction resumed> NULL, 8) = 0 [pid 28574] <... brk resumed> ) = 0x3c00a000 [pid 28575] rt_sigaction(SIGFPE, {0x40081b76, [INT USR2], SA_RESTORER|SA_STACK|SA_RESTART, 0x45a14eb8}, <unfinished ...> [pid 28574] sigaltstack({ss_sp=0x406a1000, ss_flags=0, ss_size=1048576} <unfinished ...> [pid 28575] <... rt_sigaction resumed> NULL, 8) = 0 [pid 28574] <... sigaltstack resumed> , NULL) = 0 [pid 28575] rt_sigaction(SIGSEGV, {0x40081aa4, [INT USR2], SA_RESTORER|SA_STACK|SA_RESTART, 0x45a14eb8}, <unfinished ...> [pid 28574] rt_sigaction(SIGINT, {0x40081bf2, [INT USR2], SA_RESTORER|SA_STACK|SA_RESTART, 0x45a14eb8}, <unfinished ...> [pid 28575] <... rt_sigaction resumed> NULL, 8) = 0 [pid 28574] <... rt_sigaction resumed> NULL, 8) = 0 [pid 28575] rt_sigaction(SIGILL, {0x40081aa4, [INT USR2], SA_RESTORER|SA_STACK|SA_RESTART, 0x45a14eb8}, <unfinished ...> [pid 28574] rt_sigaction(SIGFPE, {0x40081b76, [INT USR2], SA_RESTORER|SA_STACK|SA_RESTART, 0x45a14eb8}, <unfinished ...> [pid 28575] <... rt_sigaction resumed> NULL, 8) = 0 [pid 28574] <... rt_sigaction resumed> NULL, 8) = 0 from there it just degrades into a soup of SIGSEGV and rt_sigprocmask(), like: [pid 28575] --- SIGSEGV (Segmentation fault) @ 0 (0) --- [pid 28574] <... rt_sigprocmask resumed> NULL, 8) = 0 [pid 28575] rt_sigprocmask(SIG_UNBLOCK, ~[], <unfinished ...> [pid 28574] --- SIGSEGV (Segmentation fault) @ 0 (0) --- [pid 28575] <... rt_sigprocmask resumed> NULL, 8) = 0 [pid 28574] rt_sigprocmask(SIG_UNBLOCK, ~[], <unfinished ...> [pid 28575] --- SIGSEGV (Segmentation fault) @ 0 (0) --- [pid 28574] <... rt_sigprocmask resumed> NULL, 8) = 0 [pid 28575] rt_sigprocmask(SIG_UNBLOCK, ~[], <unfinished ...> [pid 28574] --- SIGSEGV (Segmentation fault) @ 0 (0) --- [pid 28575] <... rt_sigprocmask resumed> NULL, 8) = 0 [pid 28574] rt_sigprocmask(SIG_UNBLOCK, ~[], <unfinished ...> [pid 28575] --- SIGSEGV (Segmentation fault) @ 0 (0) --- [pid 28574] <... rt_sigprocmask resumed> NULL, 8) = 0 [pid 28575] rt_sigprocmask(SIG_UNBLOCK, ~[], <unfinished ...> this never ends. Attaching to various threads (when I am so lucky as to be able to) is not very instructive (to me ;)). -- gmt

3 6

Re: S3 texture compression patent
by Ivan Leo Murray-Smith Oct. 20, 2003

Oct. 20, 2003

>Is it a patent for a hrdware solution, or for software? If software then in >Europe, at least in Germany and others, it wouldn't matter because >softwarepatents are not possible (and hopefully never will). Software patents are illegal in all the EU, and it will stay like that thanks to the latest copyright directive, the EUCD. Also, this thread should be on wine-license. It wouldn't be hard to host wine in the EU, codeweavers can just get some host space from any EU hoster, and set up and publish remotely.

3 3

Asprotected programs crash with current wine-cvs
by Oleg Prokhorov Oct. 20, 2003

Oct. 20, 2003

Hello Alexandre , current CVS version has regression. All Asprotected (probably) programs crash due to the fact that Asprotect assumes that executables are being loaded from kernel32.dll, so stack return address passed to executable entry (in the other words executable entry was called from kernel32.dll) points to somewhere inside kernel32.dll. Later Asprotect uses this return address to detect kernel32.dll export section and dig it for required kernel32.dll function (LoadModule, VirtualAlloc etc). The problem is that now executable entry loaded under wine is being started from somewhere inside ntdll.dll, so Asprotected kernel32.dll function finding routines fail with crash. I'm not sure what's the best way to solve it, is some ntdll.dll process startup code relocating to kernel32.dll good enough ? -- Best regards, Oleg mailto:xolegpro(a)rbcmail.ru

1 0

RE: WWN: wn20031017_192.xml
by Brian Vincent (C) Oct. 20, 2003

Oct. 20, 2003

> Test these lines > BEGIN { FS = "\"" } > { A+=$2 } > { B+=$4 } > END { print "<person posts=\""A"\""" size=\"" B"\""" > who=\""$6"\" />" } Works like a charm! Thanks! --------------- Brian Vincent Copper Mountain Telecom vincentb(a)coppercolorado.com

1 0

Re: S3 texture compression patent
by Ivan Leo Murray-Smith Oct. 19, 2003

Oct. 19, 2003

>But what would that mean for the developers in the US? Just because the >sources are hosted in EU would still render them useless for US developers. No, if you're in the US and publish something in the EU, you aren't violating any US law, as you aren't publising anything in the US. If this isn't the case, the US constitution must have a few bugs in it. This would also mean moving the mailing list archives and the CVS to the EU, but I don't think this will happen, unless you show that there is a patent violation and that wine will never work without violating that patent.

2 1

Re: Setupapi Win16/32 (Again) and PSDK porting fixes
by Gregory M. Turner Oct. 19, 2003

Oct. 19, 2003

On Saturday 18 October 2003 01:57 pm, Steven Edwards wrote: > With this > patch all of the objects for setupapi.dll can be built on > MS_VC with the PSDK. There are a few minor issues but nothing > to major doesn't this: -typedef struct _CABINET_INFOA { +typedef struct _CABINET_INFO_A { PCSTR CabinetPath; PCSTR CabinetFile; PCSTR DiskName; USHORT SetId; USHORT CabinetNumber; -} CABINET_INFOA, *PCABINET_INFOA; +} CABINET_INFO_A, *PCABINET_INFO_A; -typedef struct _CABINET_INFOW { +typedef struct _CABINET_INFO_W { PCWSTR CabinetPath; PCWSTR CabinetFile; PCWSTR DiskName; USHORT SetId; USHORT CabinetNumber; -} CABINET_INFOW, *PCABINET_INFOW; +} CABINET_INFO_W, *PCABINET_INFO_W; mean we should do this: -DECL_WINELIB_TYPE_AW(CABINET_INFO); -DECL_WINELIB_TYPE_AW(PCABINET_INFO); +DECL_WINELIB_TYPE_AW(CABINET_INFO_); +DECL_WINELIB_TYPE_AW(PCABINET_INFO_); ? -- gmt "class 'SfxPoolCancelManager' only defines a private destructor and has no friends" -- gcc, resorting to unnecessary character attacks

2 3