e-Sword

[Steven Vollom]

>>> try it like this:
>>> open konsole
>>> navigate to your wine e-Sword directory:
>>>
>>> cd .wine/drive_c/Program Files/e-Sword
>>>       
Dear Eberhard,

I tried what you suggested from the Konsole, first exactoly like you 
suggested then with other combinations of slash, because Windows uses a 
back-slash.  I even did it where it would probably be Linux then change 
to Windows in the middle of the command.  Take a look.  Same answer each 
time  No such file or directory.?

> steven at Yeshua:~$ cd .wine/drive_c/Program Files/e-Sword
> bash: cd: .wine/drive_c/Program: No such file or directory
> steven at Yeshua:~$ cd .wine/drive_c\Program Files\e-Sword
> bash: cd: .wine/drive_cProgram: No such file or directory
> steven at Yeshua:~$ cd .wine\drive_c\Program Files\e-Sword
> bash: cd: .winedrive_cProgram: No such file or directory
> steven at Yeshua:~$ cd /.wine/drive-d/Program Files/e-Sword
> bash: cd: /.wine/drive-d/Program: No such file or directory
> steven at Yeshua:~$ cd /.wine\drive_c\Program Files\e-Sword
> bash: cd: /.winedrive_cProgram: No such file or directory
> steven at Yeshua:~$
I notice that where the first back-slash takes place the computer 
rejects it, so that was a bad idea.  Nothing produced a lot of errors.  
Just the one.

>>> then start e_Sword from there:
>>>
>>> wine e_Sword.exe
>>>
>>> My hope is that we will get some error messages on konsole that could 
>>> possibly help us to see what the problem 
> Please have e-Sword and the konsole which started e-sword, open and 
> directly side by side. Then do your "click, where nothing happens" and 
> let us know what konsole shows at that very moment.
>   
I tried this even though e-Sword did not open from konsole.  I 
re-entered the command and tried again to open e-Sword from the konsole, 
to see if any reaction would take place then.
> Hopefully we will see, what the application tries to do, but does not 
> succeed in doing.
>   
No activity at all.
>
> There are better debug options in wine but I am not familiar with them 
> and would have to investigate, if this one does not reveal anything.
> useful.
>
> You can also find many informations about "e-sword with wine" on google. 
> Mostly they are relating to msls31.dll which is missing and 
>   
I looked in the folder that contains the .dll files and found that 
msls31.dll was not there, so I downloaded it and put it in that folder, 
but still nothing changed.  The riched20.dll was in the folder.
> riched20.dll, which should be set to "built in" for e-Sword.exe via winecfg.
>
> The memory hasn't arrived yet?
>   

Steven