Re: Debug asertion failed! BF1942

J. Grant wrote:

> Hi,
>
> I was thinking of purchasing WineX so I could play BF1942 (as it says it
> is supported now).  

Correct. It's been supported since WineX 3.0.


> I selected the CVS version to test, however it is not working.
>
>
> I get the following text when running  BF1942 from an existing install (
> as winex install does not work, i get  an "unhandled exception" then it
> crashes" 


The install works just fine with the binaries. I'm not sure what 
consitutes an existing install? Using a windows registry/partition?

>
>
>
> "Your version of DirectX is 600, you need at least DirectX8.1"
>
> I click "ignore", it starts.  Any chance of your setting this version to
> 8.1 ? 


It already is, although there are 1001 ways for programs to determine 
what version of DirectX is actually present. This is pretty much not a 
big deal since, as you note, it starts. Unless you can provide me with 
an indication of what exactly the program is checking it's probably not 
going to rank too high on the todo list ;)

>
>
>
> I can watch the intro, and get to the menus, but as there is no keyboard
> input.  I can't do anything.  Are you aware of this problem?

I'm not sure that we've seen that problem. However, since you're using 
HEAD, the development branch, you're bound to get a momentary regression 
or two. Perhaps you could try using different settings for managed and 
for xvidmode and report any changes.


> I had to
> disable the HAVE_RAND X screen resize stuff in config.h before it would
> even compile.  Any ideas?  

Well the xrandr.h missing problem is due to the wonders of sourceforge. 
Sourceforge is delayed 24 hours, and I forgot to check in 1 file with a 
bunch of others - so you get a 1 day delay and the compile is broken for 
that day. There were a few manual ways around it, but you should just be 
able to do a cvs update now.


> I tested with UTF-8 locale, and old iso-8859-15 locale.
>
> Regards
>
> JG
>
> log follows:
>
>
>
>
>
> fixme:keyboard:MapVirtualKeyExA (37,1,0x08090809), hkl unhandled!
> fixme:keyboard:MapVirtualKeyExA (38,1,0x08090809), hkl unhandled! 

Well all of these indicate that a local is being used to translate the 
virtual key mapping. I would suspect that if this was the problem your 
controls would just be funny as the translation code page would be 
wrong. However, if you'd like to submit something for this, at the very 
least it's obvious from the code that the MapVirtualKeyEx functions 
should not be calling down to the MapVirtualKey functions - it should be 
the other way around - and the function exported from the user driver 
should be a MapVirtualKeyEx style function.

Ciao,
Peter




-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01