http://bugs.winehq.org/show_bug.cgi?id=5967
------- Additional Comments From theorizer@freemail.hu 2006-20-08 05:45 ------- At work I use a licensed V4.05 with which I've experienced this problem. Honestly saying I've not tried the 5.21 eval version yet. But I've discovered some interesting things regarding the problem: the application correctly works with wine if you start it with
wine keil/c166/bin/l166.exe
or with any shorter command, but with longer ones as e.g.:
~/keil/c166/bin/l166.exe
or
./keil/c166/bin/l166.exe
(which in my case are the same) or anything else longer than the most above command line the thing doesn't work.
I've tried to copy it to the wine's c: drive and to start it from there with
wine c:/keil/c166/bin/l166.exe
Because of the too long command line the result is the same.
When I run l166.exe under windows the command line length doesn't affect anything. Nevertheless I can imagine that it's merely about a buffer overflow bug in the l166.exe application which doesn't cause crash under windows but it definitely does under wine.
Could you please try this command line story also with the eval version?