[Bug 49611] Midisoft Studio 4 crashes when opening a file

Wed Jul 29 01:29:29 CDT 2020

https://bugs.winehq.org/show_bug.cgi?id=49611

--- Comment #54 from Michael F Winthrop <michael.f.winthrop at gmail.com> ---
(In reply to Olivier F. R. Dierick from comment #52)
> Hello,
> 
> I downloaded Midisoft Studio 4 from a torrent archive (and scanned it for
> viruses).
> 
> I could create a simple track and save/open it in SNG and MID format.
> 
> However, opening one of the more complex sample MID files provided by the
> application itself results in a 'Out of Memory' error followed by various
> warnings and incomplete track loading, or by an application lock.
> 
> So, there is definitely an issue.
> 
> The terminal output is nearly empty and doesn't give any clue.
> 
> --- terminal output after an unsuccessful MID loading ---
> 0074:err:ntoskrnl:ZwLoadDriver failed to create driver
> L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\wineusb":
> c0000142
> 003c:fixme:service:scmdatabase_autostart_services Auto-start service
> L"wineusb" failed to start: 1114
> 0024:fixme:ntdll:NtQuerySystemInformation info_class
> SYSTEM_PERFORMANCE_INFORMATION
> 00c8:fixme:midi:handle_midi_event Unexpected event received, type = a from
> 14:0
> (... the previous line repeats with the following occuring every few lines)
> 00c8:fixme:midi:handle_midi_event Unexpected event received, type = d from
> 14:0
> (... same as above)
> 0024:err:ole:CoReleaseMarshalData StdMarshal ReleaseMarshalData failed with
> error 0x8001011d
> --- end of terminal output ---
> 
> --- terminal output when loading a file result in a process lock ---
> 00c4:fixme:ntdll:NtQuerySystemInformation info_class
> SYSTEM_PERFORMANCE_INFORMATION
> wine: Unhandled page fault on read access to 01CF0298 at address 7ECC1AD1
> (thread 00c4), starting debugger...
> 00e4:err:ntdll:RtlpWaitForCriticalSection section 00110060
> "/media/wine-shares/git/dlls/ntdll/heap.c: main process heap section" wait
> timed out in thread 00e4, blocked by 00c4, retrying (60 sec)
> --- end of terminal output ---
> 
> I couldn't get a backtrace or even a winedbg crash dialog.
> 
> My version of Wine 5.13 is a vanilla PE build (without wineusb support but
> that shouldn't make any difference here).
> 
> The application doesn't start in WinME or lower mode (app crashes at
> startup). It runs in Win2000 and above mode, so I settled for the default
> win7 mode.
> 
> Through it is not clear yet what it is, I confirm the issue.
> 
> Regards.

Sir,
I decided to do a fresh install of wine:
I did the following in a terminal:

"sudo apt autoremove wine-devel wine-devel-amd64 wine-devel-i386 winehq-devel
winetricks"

"sudo apt-get remove --autoremove wine-*"

"sudo apt install wine-devel"
(I already have the development ppa installed so this was no problem)

"sudo nano /etc/environment"
>>>added new line above PATH  ==>  WINEARCH=win32

"export WINEPREFIX=/home/dad/.prefix32"
"env WINEARCH=win32 winecfg"

wine: created the configuration directory '/home/dad/.prefix32'
0012:err:ole:marshal_object couldn't get IPSFactory buffer for interface
{00000131-0000-0000-c000-000000000046}
0012:err:ole:marshal_object couldn't get IPSFactory buffer for interface
{6d5140c1-7436-11ce-8034-00aa006009fa}
0012:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub,
hres=0x80004002
0012:err:ole:CoMarshalInterface Failed to marshal the interface
{6d5140c1-7436-11ce-8034-00aa006009fa}, 80004002
0012:err:ole:get_local_server_stream Failed: 80004002
0014:err:ole:marshal_object couldn't get IPSFactory buffer for interface
{00000131-0000-0000-c000-000000000046}
0014:err:ole:marshal_object couldn't get IPSFactory buffer for interface
{6d5140c1-7436-11ce-8034-00aa006009fa}
0014:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub,
hres=0x80004002
0014:err:ole:CoMarshalInterface Failed to marshal the interface
{6d5140c1-7436-11ce-8034-00aa006009fa}, 80004002
0014:err:ole:get_local_server_stream Failed: 80004002
Could not load wine-gecko. HTML rendering will be disabled.
wine: configuration in '/home/dad/.prefix32' has been updated.

>>>Created a file called Downloads on /home/dad/.prefix/drive_c
>>>Copied the install application here

>>>In Downloads directory executed "wine explorer"

>>>In Explorer, double clicked install app.

0009:err:shell:HCR_GetFolderAttributes should be called for simple PIDL's only!
dad at dad314159:~/.prefix32/drive_c/Downloads$ cd ..
dad at dad314159:~/.prefix32/drive_c$ cls

Command 'cls' not found, but there are 17 similar ones.

>>>Ran:
(
 #!/bin/bash
  timidity -iA -Os &
)
in a shell script. Can only be run once before starting WINE.

>>>Ran "aconnect --list"

client 0: 'System' [type=kernel]
    0 'Timer           '
    1 'Announce        '
client 14: 'Midi Through' [type=kernel]
    0 'Midi Through Port-0'
client 20: 'USB Uno MIDI Interface' [type=kernel,card=1]
    0 'USB Uno MIDI Interface MIDI 1'
client 128: 'TiMidity' [type=user,pid=25442]
    0 'TiMidity port 0 '
    1 'TiMidity port 1 '
    2 'TiMidity port 2 '
    3 'TiMidity port 3 '

NOTE: Unless client 128: 'Timidity' exists, no audio will be heard. Any other
client number fails.

"winecfg"
>>>Located and added ASWVEDIT.EXE and STUDIO.EXE and made both WinXP O/S

>>>From a Studio4 Icon on my desktop:
command in properties->application tab is:
env WINEPREFIX="/home/dad/.prefix32" wine C:\\windows\\command\\start.exe /Unix
/home/dad/.prefix32/drive_c/Studio4/STUDIO.EXE

Other than notes on the screen were off by three extra steps (e.g., middle E
was shown as middle C, but the audio output was actually E, everything worked
perfectly!!!!  (Always this way in WINE, but offset in notation does not happen
in VirtualBox)
==============================================================================
I always had a MIDI device on usb when running this app, so I never saw what it
would do without one. You might try the "settings" tab set to "No MIDI". Close,
and restart.

The WINE 5.13 installed Studio recognizes usb input from a MIDI piano without
problems as long as there is a MIDI input on a USB port. The MIDI setup is via
"settings" tab in the program.

When the app was running under wine 3.x I used WinXP mode (32 bit). It noted
about a Gig of memory space available. It played output through timidity       
(
 #!/bin/bash
  timidity -iA -Os &
)
in a shell script. Can only be run once before starting WINE.

At some point, "timidity" was no longer reachable under old and updated O/S 
because "aconnect" had the default output assigned to another application.
Thereafter I could not get audio because wine uses the default output every
time. Also the notes on the screen were off by three extra steps (e.g., middle
E was shown as middle C, but the audio output was actually E. The MIDI output
was correct and the output was excellent. I used its' MIDI files with other
programs. The notation is the best I have ever seen. Beats Rosegarden and
MuseScore all to death.

I do/did not have any problems running on VirtualBox with a WinXP O/S when in
KDE Ubuntu 16.04 and now in Kubuntu 18.04. I think WINE is better (safer) to
use than VirtualBox so I made a project of many years duration until it worked,
but as you see, it is a problem again.

My very best to the WINE team.

-- 
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.