I've been wondering about this for a while. I use the windows version of ePSXe because the linux version is still at 1.6.0 which has some issues with Chrono Cross that 1.7.0 fixes. Anyway. It works pretty well in wine most of the time but there's one problem I've been having. Whenever I start it by double clicking the ePSXe.exe from a gui file manager it runs just fine. However, if I try to start it from the command line using "wine ~/.wine/drive_c/epsxe170/ePSXe.exe" it gives me some trouble. The application runs just fine but it tells me "ePSXe is NOT completely configure go to Config -> bios to configure it" Okay I think, easy enough, but when you go to configure it the app can not find the bios, nor can it find any of the plugin files. The configure wizard presents you with a bunch of blank space where plugin names should be. I do not understand this. What is the difference between the command I am typing and the command the machine received upon double clicking the exe file? This problem is preventing me from creating a one click shortcut on my taskbar or on any of my menus. It is only a minor annoyance but it is one I would absolutely love resolved.
Okay. I posted this question maybe twenty minutes ago and then I figured out the answer. You need to cd into the directory in which ePSXe.exe is located first. I have done this when i used .wine as my WINEPREFIX (default) before though and never had it work (ie. cd ~/.wine/epsxe170) This time around what I did was make a wine prefix called ePSXe which is entirely devoted to the emulator and I unzipped it directly in that directory, as opposed to placing it inside of drive_c. Thus an appropriate command line launch procedure is as follows: cd ~/.wine/wineprefixes/ePSXe/ ; WINEPREFIX=~/.wine/wineprefixes/ePSXe wine ./ePSXe.exe Like I've said. I have tried changing directories into the default wine prefixes epsxe location in the past and still watched the configurator fail on command line launch. However I have usually kept it in drive_c/epsxe170 of that prefix and perhaps I have not tried to cd into that exact directory. I do not recall whether I have done so or not, although I don't see why I would not have tried it. At this point I feel I may have wasted the time of any of our forum members who have viewed this post, so I can only hope this information helps someone else.