http://bugs.winehq.org/show_bug.cgi?id=35178
Bug ID: 35178
Summary: FL Studio 11.x 'DirectWave' plugin doesn't work
(unsupported FSCTL_IS_VOLUME_MOUNTED ioctl)
Product: Wine
Version: 1.7.8
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: focht(a)gmx.net
Classification: Unclassified
Hello folks,
a user in #winehq reported this.
I was able to reproduce the problem with the demo version of FL 11 using the
following recipe (quoting IRC log):
--- quote ---
<alexmarkley> i am running into an issue with FL Studio 11 running on Linux
under Wine 1.7.8
<alexmarkley> most everything appears to be working, but there are a couple of
important software instrument plugins that fail to load any sounds
...
<alexmarkley> focht: File -> New from template -> Minimal -> Basic with limiter
<alexmarkley> focht: sub-window "Pattern 1", right click "Kick" -> Insert ->
DirectWave
<alexmarkley> focht: in the DirectWave window which appears, click the down
arrow next to "Select Preset"
<alexmarkley> focht: if you don't have any DirectWave presets, you can download
a free one
<alexmarkley> from within the GUI there
<alexmarkley> anyway, once you select the preset you will see it loads the
program, but clicking the piano keys results in no sound
<alexmarkley> focht: you will also notice that, in the loaded program, each
entry in the "Size" column is zero
<alexmarkley> focht: which is bad... in native windows (running in VirtualBox)
i see non-zero values for every one of those entries
--- quote ---
Relevant part of trace log:
--- snip ---
$ pwd
/home/focht/.wine/drive_c/Program Files/Image-Line/FL Studio 11
$ WINEDEBUG=+tid,+seh,+relay wine ./FL.exe >>log.txt 2>&1
...
0024:Call KERNEL32.LoadLibraryW(006ec0fc L"C:\\Program Files\\Image-Line\\FL
Studio 11\\Plugins\\Fruity\\Generators\\DirectWave\\DirectWave.dll")
ret=00e4a66a
0024:Call PE DLL (proc=0xbe7eca6,module=0xbe20000
L"DirectWave.dll",reason=PROCESS_ATTACH,res=(nil))
...
0024:Call KERNEL32.ExpandEnvironmentStringsA(02a447c8 "C:\\Program
Files\\Image-Line\\FL Studio
6\\Data\\Patches\\Packs\\SampleFusion\\Orchestral\\Strings\\Mellotron_02\\SYM_STR_C_2.wav",0033a07c,00000fff)
ret=0be383ea
0024:Ret KERNEL32.ExpandEnvironmentStringsA() retval=00000078 ret=0be383ea
...
0024:Call KERNEL32.CreateFileA(0033ae28
"\\\\.\\C:",80000000,00000007,00000000,00000003,00000000,00000000) ret=0be59e4d
...
0024:Ret KERNEL32.CreateFileA() retval=000001f0 ret=0be59e4d
...
0024:Call
KERNEL32.DeviceIoControl(000001f0,00090028,00000000,00000000,00000000,00000000,0033ae24,00000000)
ret=0be59e8e
...
0024:Ret KERNEL32.DeviceIoControl() retval=00000000 ret=0be59e8e
...
0024:Call KERNEL32.GetLastError() ret=0be59e98
0024:Ret KERNEL32.GetLastError() retval=00000032 ret=0be59e98
--- snip ---
The 'DirectWave' plugin library uses FSCTL_IS_VOLUME_MOUNTED ioctl to check if
the specified volume is mounted before accessing each file (track).
Wine doesn't implement/stub that ioctl hence the failure, resulting in tracks
listed with zero size (as reported).
MSDN:
http://msdn.microsoft.com/en-us/library/windows/desktop/aa364574%28v=vs.85%…
--- quote ---
FSCTL_IS_VOLUME_MOUNTED control code
Determines whether the specified volume is mounted, or if the specified file or
directory is on a mounted volume.
To perform this operation, call the DeviceIoControl function with the following
parameters.
BOOL DeviceIoControl(
(HANDLE) hDevice, // handle to device
FSCTL_IS_VOLUME_MOUNTED, // dwIoControlCode
NULL, // lpInBuffer
0, // nInBufferSize
NULL, // lpOutBuffer
0, // nOutBufferSize
(LPDWORD) lpBytesReturned, // number of bytes returned
(LPOVERLAPPED) lpOverlapped // OVERLAPPED structure
);
...
Return value
If the volume is currently mounted, DeviceIoControl returns a nonzero value.
Otherwise, DeviceIoControl returns zero (0). To get extended error information,
call GetLastError.
Remarks
The NTFS file system treats a locked volume as a dismounted volume. Therefore,
this call returns zero (0) after a volume is locked on the NTFS file system.
--- quote ---
For quick test I short-circuited the ioctl handling on the client side (ntdll)
like the existing FSCTL_LOCK_VOLUME and FSCTL_UNLOCK_VOLUME cases, returning
'success'.
It made the plugin happy and the wav files were correctly loaded/processed.
A more thorough solution is probably enhancing server/mountmgr.
Source:
http://source.winehq.org/git/wine.git/blob/5ba7f79bad4f4832d98d0f2897aea697…
--- snip ---
1495 NTSTATUS WINAPI NtFsControlFile(HANDLE handle, HANDLE event,
PIO_APC_ROUTINE apc,
1496 PVOID apc_context, PIO_STATUS_BLOCK io, ULONG code,
1497 PVOID in_buffer, ULONG in_size, PVOID out_buffer, ULONG
out_size)
1498 {
...
1509 switch(code)
1510 {
1511 case FSCTL_DISMOUNT_VOLUME:
...
1517 case FSCTL_PIPE_PEEK:
1518 {
...
1590 case FSCTL_LOCK_VOLUME:
1591 case FSCTL_UNLOCK_VOLUME:
1592 FIXME("stub! return success - Unsupported fsctl %x (device=%x
access=%x func=%x method=%x)\n",
1593 code, code >> 16, (code >> 14) & 3, (code >> 2) & 0xfff, code
& 3);
1594 status = STATUS_SUCCESS;
1595 break;
...
1619 case FSCTL_PIPE_LISTEN:
1620 case FSCTL_PIPE_WAIT:
1621 default:
1622 status = server_ioctl_file( handle, event, apc, apc_context, io,
code,
1623 in_buffer, in_size, out_buffer, out_size
);
1624 break;
1625 }
1626
1627 if (status != STATUS_PENDING) io->u.Status = status;
1628 return status;
1629 }
--- snip ---
$ sha1sum flstudio_11.0.4.exe
f9bdc2fb0b8d18ffce90e048b12a0c196d0b82d0 flstudio_11.0.4.exe
$ du -sh flstudio_11.0.4.exe
301M flstudio_11.0.4.exe
$ wine --version
wine-1.7.8-278-g53dc001
Regards
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=28266
Summary: Wise Registry Cleaner: Error message at startup
Product: Wine
Version: 1.3.27
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: lukasz.wojnilowicz(a)gmail.com
Created an attachment (id=36217)
--> (http://bugs.winehq.org/attachment.cgi?id=36217)
Error message
Steps to reproduce:
1) remove ~/.wine
2) install Wise Registry Cleaner
3) wine WiseRegCleaner.exe
Behaviour:
Error message (See attachment).
Expected behaviour:
No error message.
Terminal output:
fixme:resource:GetGuiResources (0xd4,0): stub
Additional info:
Access violation at address 00456D49 in module 'WiseRegCleaner.exe'. Read of
address 000006BD.
Workaround:
WINEDEBUG=+relay
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=18637
Summary: Nokia Map Loader 2.0 (.NET 3.0 app) needs
DisableProcessWindowsGhosting stub
Product: Wine
Version: 1.1.22
Platform: Other
URL: http://europe.nokia.com/get-support-and-software/produ
ct-support/maps-support/compatibility-and-downloads
OS/Version: other
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: user32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: focht(a)gmx.net
Hello,
as it says ...
--- snip ---
System.EntryPointNotFoundException: Unable to find an entry point named
'DisableProcessWindowsGhosting' in DLL 'user32.dll'.
at Lizard.Windows.Native.NativeMethods.DisableProcessWindowsGhosting()
at Lizard.Windows.NonClientBaseForm.OnHandleCreated(EventArgs e)
at System.Windows.Forms.Control.WmCreate(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmCreate(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at Lizard.Windows.NonClientBaseForm.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr
wparam, IntPtr lparam)
--- snip ---
A simple stub is enough.
See: http://msdn.microsoft.com/en-us/library/ms648415.aspx
Regards
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=40614
Bug ID: 40614
Summary: Cisco Jabber 11.6 crashes due to missing
dbghelp.dll.EnumerateLoadedModulesExW
Product: Wine
Version: 1.9.9
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: dbghelp
Assignee: wine-bugs(a)winehq.org
Reporter: robert.munteanu(a)gmail.com
Distribution: ---
Created attachment 54473
--> https://bugs.winehq.org/attachment.cgi?id=54473
Backtrace
Fresh wine prefix, 32-bit install. After installing Cisco Jabber I get a crash,
backtrace pointing to
Unhandled exception: unimplemented function
dbghelp.dll.EnumerateLoadedModulesExW called in 32-bit code (0x7b43e23c).
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=40655
Bug ID: 40655
Summary: Cisco Jabber 11.6 spins forever, needs
msvcr120.dll.?_Id@_CurrentScheduler@details@Concurrenc
y@@SAIXZ
Product: Wine
Version: 1.9.10
Hardware: arm
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: robert.munteanu(a)gmail.com
Distribution: SUSE
Fresh wine prefix, 32-bit install. After installing Cisco Jabber and starting
it the UI has a spinner which never disappears.
The program generates no backtrace, but the terminal contains the following
interesting line:
wine: Call from 0x7b43d626 to unimplemented function
msvcr120.dll.?_Id@_CurrentScheduler@details@Concurrency@@SAIXZ, aborting
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=37334
Bug ID: 37334
Summary: Cisco Jabber fails to run
Product: Wine
Version: 1.7.27
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: daniel.masur(a)idealo.de
Created attachment 49647
--> https://bugs.winehq.org/attachment.cgi?id=49647
Console output upon running CiscoJabber.exe
Hi.
As a normal user, after installing ie7 into a fresh .wine folder using:
WINEARCH='win32' winetricks ie7
copying ksuser.dll into system32
and then installing the Cisco Jabber Client using:
WINEARCH='win32' wine msiexec /i CiscoJabberSetup.msi
I get the attached console output when running the following:
bash -c "LC_MESSAGES=C WINEARCH='win32' wine .wine/drive_c/Program\
Files/Cisco\ Systems/Cisco\ Jabber/CiscoJabber.exe"
bash -c "LC_MESSAGES=C ..." for englishifying the console output.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=37228
Bug ID: 37228
Summary: Cisco Jabber will not run
Product: Wine
Version: 1.7.25
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: davidc502(a)tds.net
Created attachment 49501
--> https://bugs.winehq.org/attachment.cgi?id=49501
Errors when trying to run Jabber through console.
Cisco Jabber does not run after install. A grey screen pops up, but shortly
after am requested to close unresponsive application.
URL to the ciscoJabberSetup.msi ->
http://personalpages.tds.net/~davidc502/Jabber/
See attached for Errors whilst trying to run Jabber in Console window.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=32482
Bug #: 32482
Summary: Windows Sysinternals "PsInfo" tool fails to retrieve
"Physical Memory" value from
"HKLM\\Hardware\\ResourceMap\\System Resources"
registry key
Product: Wine
Version: 1.5.19
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: programs
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: focht(a)gmx.net
Classification: Unclassified
Hello folks,
Windows Sysinternals "PsInfo" tool fails to query for some system properties...
Making this bug about "Physical Memory".
Output:
--- snip ---
$ wine ./PsInfo.exe
PsInfo v1.77 - Local and remote system information viewer
Copyright (C) 2001-2009 Mark Russinovich
Sysinternals - www.sysinternals.com
Querying information for nexus4...fixme:ole:CoInitializeSecurity
((nil),-1,(nil),(nil),0,3,(nil),0,(nil)) - stub!
System information for \\nexus4:
Uptime: Error reading uptime
Kernel version: Microsoft Windows XP, Uniprocessor Free
Product type: Professional
Product version: 5.1
Service pack: 3
Kernel build number: 2600
Registered organization:
Registered owner:
IE version: 6.0000
System root: C:\windows
Processors: 4
Processor speed: 2.6 GHz
Processor type: Intel(R) Pentium(R) 4 CPU
Physical memory: 0 MB
Video driver:
--- snip ---
Trace log (processor info = ok, physmem = missing):
--- snip ---
...
0024:Call advapi32.RegOpenKeyExW(80000002,0042f520
L"Hardware\\Description\\System\\CentralProcessor\\0",00000000,00020019,0032f96c)
ret=00404a33
0024:Ret advapi32.RegOpenKeyExW() retval=00000000 ret=00404a33
0024:Call advapi32.RegQueryValueExW(00000054,0042f510
L"~MHz",00000000,0032f970,0043c0e4,0032f968) ret=00404a58
0024:Ret advapi32.RegQueryValueExW() retval=00000000 ret=00404a58
0024:Call advapi32.RegQueryValueExW(00000054,0042f4e8
L"ProcessorNameString",00000000,0032f970,0043d538,0032f968) ret=00404a81
0024:Ret advapi32.RegQueryValueExW() retval=00000000 ret=00404a81
0024:Call advapi32.RegCloseKey(00000054) ret=00404a95
0024:Ret advapi32.RegCloseKey() retval=00000000 ret=00404a95
0024:Call advapi32.RegOpenKeyW(80000002,0042f210
L"Hardware\\ResourceMap\\System Resources\\Physical Memory",0032f930)
ret=00403b17
0024:Ret advapi32.RegOpenKeyW() retval=00000002 ret=00403b17
--- snip ---
Wineboot already creates a couple of hardware related registry keys:
Source:
http://source.winehq.org/git/wine.git/blob/7f9dfe273a80d31e3f8c5bd0c100c813…
Might be useful to add "Hardware\\ResourceMap\\System Resources" key here along
with actual physmem value.
Regards
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=10522
Summary: endless WM_PAINT loop bug (update regions, queue paint
count)
Product: Wine
Version: CVS/GIT
Platform: PC
URL: http://www.microsoft.com/whdc/devtools/debugging/install
x86.mspx
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: wine-user
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: focht(a)gmx.net
Created an attachment (id=9265)
--> (http://bugs.winehq.org/attachment.cgi?id=9265)
trace with WINEDEBUG=+tid,+message,+win,+server
Hello,
I've seen this bug a while ago in other apps but ignored it because it was not
easily to reproduce.
Well until recently when I tested some stuff with windbg from "Debugging Tools
for Windows" (Microsoft).
I used debugging tools version 6.8.4.0 and recent GIT
(wine-0.9.49-302-g58b85bb).
Immediately when a child window was opened using toolbar (register, locals, ..
whatever), windbg would become unresponsive, eating most CPU.
Happens in both GUI modes - "floating/docking toolwindow" and "MDI emulation.
Though "MDI emulation" is more obvious, it actually shows the endless
refreshing (window caption).
Attached is WINEDEBUG=+tid,+message,+win,+server log.
Additionally I added a trace message which prints the current queue paint count
(when incremented or fetched) which makes some things easier to spot.
Printed as "inc_queue_paint_count: %d" and "get_message_paint_count: %d".
The window hierarchy is as follows:
--- snip ---
*root*=0x10020
Shell_TrayWnd=0x10022
WinDbgFrameClass=0x10024
DockClass=0x10026
ToolbarWindow32=0x10028
msctls_statusbar32=0x1002a
tooltips_class32=0x1002e
WinBaseClass=0x10030
ToolbarWindow32=0x10032
SysListView32=0x10034
SysHeader32=0x10036
RichEdit20W=0x10038
--- snip ---
After the child windows are created the queue paint count never drops to zero,
resulting in endless WM_PAINT processing.
Maybe some update (region) code path missed or flags problem?
I played a bit with ignoring null region updates and it seemed to help a bit
(preventing endless WM_PAINT loop) though other stuff wasn't drawn properly
then.
Regards
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=31874
Bug #: 31874
Summary: this program crash when changing the UI style
Product: Wine
Version: 1.5.14
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jactry92(a)gmail.com
Classification: Unclassified
Created attachment 41947
--> http://bugs.winehq.org/attachment.cgi?id=41947
'backtrace.txt' is log produced by wine
I used wine 1.5.14 in Ubuntu 12.04.1 32bit to run this
program('client.exe'):http://222.200.98.151/ubuntu/Downloads/client.tar.gz
And it crash when I try to change the UI style(client the button which was
marked by a red circle in the picture in attachment)
After it crach you can't run it again.In order to reappear it, you can change
the value of 'HKEY_CURRENT_USER/Software/ChinaGDS/S2000/JySvr1/UI' to '0'.
'backtrace.txt' is log produced by wine
This is output information in console:
$ wine client.exe
fixme:wbemprox:client_security_SetBlanket 0x442fcd80, 0x13dd68, 10, 0, (null),
3, 3, (nil), 0x00000000
fixme:wbemprox:client_security_Release 0x442fcd80
fixme:process:GetProcessWorkingSetSize (0xffffffff,0x328ed8,0x328edc): stub
wine: Unhandled page fault on read access to 0x00000020 at address 0x4b0b0f
(thread 0025), starting debugger...
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.