wine users - Jul 2011 - Blip&Blop - old issue gone, new issue up

Trying to run THIS
(http://appdb.winehq.org/objectManager.php?sClass=version&iId=5130) game
using a current wine build (latest dev) results in the game STARTING, changing
the resolution, showing the intro... But as soon as you press ESC it freezes
(music keeps playing).
If you don't press ESC, intro runs, high scores are displayed on title
screen, and then nada...

Any ideas on getting this to work?

Terminal output? That's really the only way to have even the faintest clue
about what's actually happening....  as always, if the output is really
long, please put it up on pastebin and post a link to the text here, rather than
posting the text itself.

Also, knowing your distribution and distro version, the actual version of Wine
(via wine --version), and your video card and driver version/type would also be
helpful.

On Fri, Jul 22, 2011 at 8:56 AM, Jenia <wineforum-user at winehq.org>
wrote:
>
> motub wrote:
>> What happens if you manually (using nvidia-settings) reduce your color
depth to 16 and try running the program again?
>> Try Windows 98 or 95 and see if that makes any difference.
>
There is a FAQ entry about running games in other than 32 bit screen
depth.  Please read it.

James

jjmckenzie wrote:
> On Fri, Jul 22, 2011 at 8:56 AM, Jenia <wineforum-user at winehq.org>
wrote:
> 
> > 
> > motub wrote:
> > 
> > > What happens if you manually (using nvidia-settings) reduce your
color depth to 16 and try running the program again?
> > > Try Windows 98 or 95 and see if that makes any difference.
> > > 
> > 
> > 
> There is a FAQ entry about running games in other than 32 bit screen
> depth.  Please read it.
> 
> James
As my above post says, the depth is not the problem.

Maybe you've missed the post where I noted that I did, in fact, modify my
color depth to 16bpp, but nevertheless, I tried again, this time by creating a
separate x screen...

No change doing it that way - thing still freezes as soon as I press ESC (music
keeps playing though)

OK, I can confirm this. I just found an abandonware version.

Before anyone complains, here's the license (from the installer):
> Permission to copy and distribute this software and its documentation
without written agreement is hereby granted only for non-commercial purposes.
Distributing Blip & Blop 'bundled' in with ANY product is considered
to be a 'commercial purpose'. This entire copyright notice must appear
in all copies of this software.
> 
> IN NO EVENT SHALL LOADED STUDIO BE LIABLE TO ANY PARTY FOR DIRECT,
INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE
OF THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF THE AUTHOR HAS BEEN ADVISED OF
THE POSSIBILITY OF SUCH DAMAGE.
> 
> THE AUTHOR SPECIFICALLY DISCLAIMS ANY WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. THE SOFTWARE PROVIDED
HEREUNDER IS ON AN "AS IS" BASIS, AND LOADED STUDIO HAS NO OBLIGATION
TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS. If you
would like to do something with this software that this copyright prohibits
(such as distributing Blip & Blop commercially), please contact LOADED
Studio.
> 
> Audience issues
> 
> Blip & Blop contains scenes of explicit violence and is intended for
mature audience only.

As far as I can tell, that means it's OK that I'm using this for a test,
especially since the developer's website is inaccessible/dead (but I'm
not posting the link in case the admins disagree).

That said, the game installed on Linux Mint Debian 32-bit with no overrides and
started fine in 16-bit color (nVidia 275.09.07), but, just as Jemia found,
attempting to start the actual game from the intro screen failed. The music
continues to play, but the screen freezes on whatever section of the intro film
it was on. I ran it in a virtual desktop window of 640x480 to see what would
happen if I manually closed the game window (as opposed to kill -9 in a second
terminal) and I got a Windows "Waiting for program" dialog, which said
(translated), "A simulated logoff or close action is busy, but the program
is not responding. If you end this process, you will lose all unsaved
data." with an "End process" or "Cancel" button.

Terminal output:

Code:
vr jul 22 07:06  motub Blip Blop $:  env
WINEPREFIX="/home/motub/.wine-blipblop" wine BlipBlop.exe
fixme:dsalsa:IDsDriverBufferImpl_SetVolumePan (0x163320,0x163220): stub
fixme:win:EnumDisplayDevicesW ((null),0,0x32f7c4,0x00000000), stub!
err:x11settings:X11DRV_ChangeDisplaySettingsEx No matching mode found 640x480x16
@85! (desktop)
fixme:d3d_surface:surface_cpu_blt Filter WINED3DTEXF_LINEAR not supported in
software blit.
fixme:d3d_surface:surface_cpu_blt Filter WINED3DTEXF_LINEAR not supported in
software blit.
fixme:d3d_surface:surface_cpu_blt Filter WINED3DTEXF_LINEAR not supported in
software blit.
fixme:d3d_surface:surface_cpu_blt Filter WINED3DTEXF_LINEAR not supported in
software blit.
fixme:d3d_surface:surface_cpu_blt Filter WINED3DTEXF_LINEAR not supported in
software blit.
fixme:d3d_surface:surface_cpu_blt Filter WINED3DTEXF_LINEAR not supported in
software blit.
fixme:d3d_surface:surface_cpu_blt Filter WINED3DTEXF_LINEAR not supported in
software blit.
fixme:d3d_surface:surface_cpu_blt Filter WINED3DTEXF_LINEAR not supported in
software blit.
fixme:d3d_surface:surface_cpu_blt Filter WINED3DTEXF_LINEAR not supported in
software blit.
fixme:d3d_surface:surface_cpu_blt Filter WINED3DTEXF_LINEAR not supported in
software blit.
fixme:d3d_surface:surface_cpu_blt Filter WINED3DTEXF_LINEAR not supported in
software blit.
fixme:d3d_surface:surface_cpu_blt Filter WINED3DTEXF_LINEAR not supported in
software blit.
fixme:d3d_surface:surface_cpu_blt Filter WINED3DTEXF_LINEAR not supported in
software blit.
fixme:d3d_surface:surface_cpu_blt Filter WINED3DTEXF_LINEAR not supported in
software blit.
fixme:d3d_surface:surface_cpu_blt Filter WINED3DTEXF_LINEAR not supported in
software blit.
fixme:d3d_surface:surface_cpu_blt Filter WINED3DTEXF_LINEAR not supported in
software blit.
fixme:d3d_surface:surface_cpu_blt Filter WINED3DTEXF_LINEAR not supported in
software blit.
fixme:d3d_surface:surface_cpu_blt Filter WINED3DTEXF_LINEAR not supported in
software blit.
fixme:d3d_surface:surface_cpu_blt Filter WINED3DTEXF_LINEAR not supported in
software blit.
fixme:d3d_surface:surface_cpu_blt Filter WINED3DTEXF_LINEAR not supported in
software blit.
fixme:d3d_surface:surface_cpu_blt Filter WINED3DTEXF_LINEAR not supported in
software blit.
fixme:d3d_surface:surface_cpu_blt Filter WINED3DTEXF_LINEAR not supported in
software blit.
fixme:d3d_surface:surface_cpu_blt Filter WINED3DTEXF_LINEAR not supported in
software blit.
fixme:d3d_surface:surface_cpu_blt Filter WINED3DTEXF_LINEAR not supported in
software blit.
fixme:d3d_surface:surface_cpu_blt Filter WINED3DTEXF_LINEAR not supported in
software blit.
fixme:d3d_surface:surface_cpu_blt Filter WINED3DTEXF_LINEAR not supported in
software blit.
fixme:d3d_surface:surface_cpu_blt Filter WINED3DTEXF_LINEAR not supported in
software blit.
fixme:d3d_surface:surface_cpu_blt Filter WINED3DTEXF_LINEAR not supported in
software blit.
fixme:d3d_surface:surface_cpu_blt Filter WINED3DTEXF_LINEAR not supported in
software blit.
fixme:d3d_surface:surface_cpu_blt Filter WINED3DTEXF_LINEAR not supported in
software blit.
fixme:d3d_surface:surface_cpu_blt Filter WINED3DTEXF_LINEAR not supported in
software blit.
fixme:d3d_surface:surface_cpu_blt Filter WINED3DTEXF_LINEAR not supported in
software blit.
fixme:d3d_surface:surface_cpu_blt Filter WINED3DTEXF_LINEAR not supported in
software blit.



The fixme goes on until the program is closed, however that occurs. A crash/hang
due to hitting ESC does not introduce new data.
 
Interestingly (or perhaps not), the program closes fine (from the virtual
desktop "X" button) if you don't hit ESC to attempt to play.

Installing d3dx9 via winetricks had no effect.  

Sadly, Jemia, I can't tell you what might help, but I can at least confirm 
your issue.

Sorry for being unclear, James XD the post where I said I tried 16bit is the
post after the one with the log.

Several attempts later, some cases give me the message motub shows above, while
others just give me my earlier posted log merely without the last line.

File a bug.

Jenia, please file the bug, as you are the one most concerned. If you attach the
bug to Blip & Blop in the AppDB, I can follow the link to confirm with my
data.

http://bugs.winehq.org/show_bug.cgi?id=27870