wine users - Jan 2009 - Re: Cannot run Win16 installer for Judaic Classics

It gets more fun. I popped in the original data disk, mounted it, and
correspondingly changed the path to the cdrom device (E:) in winecfg. I tried
starting the program, and it complained that  it could not find a valid cdrom. I
edited fstab (because current distributions mount removable devices differently,
which results in unpredictable path names for mounted removable file systems,
and makes it difficult to provide the path to an as of yet unmounted filesystem)
and added a trusted entry for the cdrom device, and tried starting the program
both with mounted and with unmounted cdrom, but again had no success.

Where should I look for the problem? Remember that it is a win 3.1/win95 program
(but win32).

I even tried through winecfg forcing it to emulate win95 and win3.1, but to no
avail.

onecoolcouple wrote:
> added a trusted entry for the cdrom device, and tried starting the program
both with mounted and with unmounted cdrom, but again had no success.
As I said before, it might be writing the path you installed it from somewhere
to ini/cfg/registry.

On 2009-02-03 (Tuesday) 08:24:55 onecoolcouple wrote:
> Is there an easy way to find out what files the program accesses or tries
> to access when it runs under Wine
	Yes. There is many ways to do this. One of them is to run your program like 
this:

WINEDEBUG=+file wine notepad

	Obviously, instead of "notepad" you should use name of your program.
You can
use grep to filter for particular pattern (for example, if you interested 
only in files with .txt extension you can run this command:

WINEDEBUG=+file wine notepad | grep -i .txt

	Alternatively you can use strace. For example (this command will work in 
zsh):

strace wine notepad |& grep -i .txt

	If you are using bash you can use this command instead:

strace wine notepad 2>&1| grep -i .txt

	You should use grep to filter strace output to see only things you interested 
in: for example extension, path (full or partial) or file related operations 
(for example "grep -i stat64\(" or "grep -i open\("). I
suggest you to play
with notepad to understand how it works then try it with your program.