wine users - Jul 2004 - Results of Regression Testing with DVD Lab and Wine

I'm looking for some advice on the amount, type and relevance of 
information to post to the wine-developers group or to file a bug report 
and which is the preferred place to send my information.

I have been trying to get DVD Lab 1.3.1 (the latest stable release), a 
DVD authoring software, running in Wine.  There are three flavors of 
this application--the stable release, a beta and a Pro beta--and all 
behave the same way in wine.  This is MediaChance software and is 
available for a thirty-day trial at:
http://www.mediachance.com/dvdlab/history.html

I compiled wine myself, a "no windows" installation, on a
"hybrid"
Mandrake 9.2.  I have made numerous modifications to my system which 
includes running kernel 2.6.5 and gcc 3.3.1.  I have tried installing 
this program after installing DCOM98, the windows installer, and Visual 
Basic Runtime--all with no tangible results.  I have tried numerous 
cominations of builtin, native dll loading.  Again, with no tangible 
results.

The symptoms are that there are no thumbnails nor preview of a loaded 
video file.  Everything else in the software appears to function 
properly.  I observed these symptoms in the 20040615 snapshot.  I then 
tried the 20040408 snapshot and these symptoms disappeared, although the 
preview played at 1/5 to 1/7 speed.  I did regression testing and 
discovered that these symptoms first appeared with the following commit:

ChangeSet ID:.         12218
CVSROOT:.                /opt/cvs-commit
Module name:.          wine
Changes by:.              juliard@wine.codeweavers.com.   2004/05/01  
23:20:06 

Command Line:  wine c:\\Program\ Files\\DVDlab\\DVdlab.exe

I get this error message each time I close the program:

err:dc:DCE_FreeWindowDCE [0x20050] GetDC() without ReleaseDC()!

Additionally, I ran DVD Lab with the following command line:

WINEDEBUG=+relay wine c:\\Program\ Files\\DVDlab\\DVdlab.exe

and the program didn't start.  I know that the Wine Users' Guide says 
that the program will run more slowly, but I was able to brew a pot of 
coffee and start drinking the first cup before I finally entered 
<Ctrl-C> <BG>.  I have extracted one series of messages that
streamed by:
> 0009:Ret  x11drv.GetPixel() retval=00010000 ret=4091348b
> 0009:Call kernel32._LeaveSysLevel(4092bcc0) ret=408f95c3
> 0009:Call ntdll.RtlLeaveCriticalSection(4092bcc0) ret=404f9597
> 0009:Ret  ntdll.RtlLeaveCriticalSection() retval=00000000 ret=404f9597
> 0009:Ret  kernel32._LeaveSysLevel() retval=00000000 ret=408f95c3
> 0009:Ret  gdi32.GetPixel() retval=00010000 ret=005c4c65
> 0009:Call gdi32.GetPixel(00001c18,00000005,00000000) ret=005c4c5a
> 0009:Call kernel32._EnterSysLevel(4092bcc0) ret=408f9418
> 0009:Call ntdll.RtlEnterCriticalSection(4092bcc0) ret=404f946a
> 0009:Ret  ntdll.RtlEnterCriticalSection() retval=00000000 ret=404f946a
> 0009:Ret  kernel32._EnterSysLevel() retval=4057a620 ret=408f9418
> 0009:Call kernel32._EnterSysLevel(4092bcc0) ret=408f9418
> 0009:Call ntdll.RtlEnterCriticalSection(4092bcc0) ret=404f946a
> 0009:Ret  ntdll.RtlEnterCriticalSection() retval=00000000 ret=404f946a
> 0009:Ret  kernel32._EnterSysLevel() retval=4057a620 ret=408f9418
> 0009:Call kernel32._EnterSysLevel(4092bcc0) ret=408f9418
> 0009:Call ntdll.RtlEnterCriticalSection(4092bcc0) ret=404f946a
> 0009:Ret  ntdll.RtlEnterCriticalSection() retval=00000000 ret=404f946a
> 0009:Ret  kernel32._EnterSysLevel() retval=4057a620 ret=408f9418
> 0009:Call kernel32._LeaveSysLevel(4092bcc0) ret=408f95c3
> 0009:Call ntdll.RtlLeaveCriticalSection(4092bcc0) ret=404f9597
> 0009:Ret  ntdll.RtlLeaveCriticalSection() retval=00000000 ret=404f9597
> 0009:Ret  kernel32._LeaveSysLevel() retval=00000000 ret=408f95c3
> 0009:Call kernel32._EnterSysLevel(4092bcc0) ret=408f9418
> 0009:Call ntdll.RtlEnterCriticalSection(4092bcc0) ret=404f946a
> 0009:Ret  ntdll.RtlEnterCriticalSection() retval=00000000 ret=404f946a
> 0009:Ret  kernel32._EnterSysLevel() retval=4057a620 ret=408f9418
> 0009:Call kernel32.LOCAL_Lock(000010bf,0000317e) ret=408f94ef
> 0009:Ret  kernel32.LOCAL_Lock() retval=403761ea ret=408f94ef
> 0009:Call kernel32.LOCAL_Unlock(000010bf,0000317e) ret=408f95ea
> 0009:Ret  kernel32.LOCAL_Unlock() retval=00000000 ret=408f95ea
> 0009:Call kernel32._LeaveSysLevel(4092bcc0) ret=408f95c3
> 0009:Call ntdll.RtlLeaveCriticalSection(4092bcc0) ret=404f9597
> 0009:Ret  ntdll.RtlLeaveCriticalSection() retval=00000000 ret=404f9597
> 0009:Ret  kernel32._LeaveSysLevel() retval=00000000 ret=408f95c3
> 0009:Call kernel32._LeaveSysLevel(4092bcc0) ret=408f95c3
> 0009:Call ntdll.RtlLeaveCriticalSection(4092bcc0) ret=404f9597
> 0009:Ret  ntdll.RtlLeaveCriticalSection() retval=00000000 ret=404f9597

I chose the "x11.drv GetPixel() retval=" as the start point.

I have snapshots available to demonstrate the symptoms but I don't like 
to post those things as attachments to lists unless people know they're 
coming.

Once again, I'm asking whether any of this info is irrelevant and what 
is the best venue for posting it--wine-developers list or bug report.  
The users guide is not clear on this point.

I would like to be as involved as I can in this project.  I am not a 
programmer, however, but I am really good at following instructions.  
Also, I haven't learned how to use winedebug--yet.

If there are specific questions about the way this software operates, I 
think the author will answer them.

Thanks,

Dan