Hi Duane,
thx for your advice. In the meantime, I've installed the program in a
VMware virtual machine (and it does fine). But it would definitely be
much more convenient to have it running on wine!
The way you describe sounds straight enough even for a 'simple' user
like me. But I'm running a bit short of time in the moment (who isn't?)
and will revert to this case as soon as I can afford...
Frank
Duane Clark wrote 07.12.2006 23:23:
[...]
How much effort do you want to put into getting it to run? Probably an
old app intended to run under Win98 can be made to run under Wine
without too much trouble. Since it is an old program, I don't suppose a
trail version is available on the web somewhere.
If you want to spend a bit of time, you might want to open up a bug on
it, and post in this thread the bug number. I would be interested in
seeing if it is a problem in reading the database files.
As an idea of things you might end up doing, probably the first step
would be to set an environment variable to get relay traces:
export WINEDEBUG=+relay
Then run the program, redirecting the output to a file:
wine myprogram.exe >& wine.log
That will probably make your program run very slow, and wine.log could
become 100s of MBytes, so plenty of disk space and a fast computer help.
Once the problem happens, exit the program. See if the error message is
in the log file:
grep "Data type mismatch" wine.log
If it is, the lines before that might give some clues to what the
program is doing, and which DLL is the problem.
Is this a path you are interested in taking?
_______________________________________________
wine-users mailing list
wine-users@xxxxxxxxxx
http://www.winehq.org/mailman/listinfo/wine-users
