Quote:
Originally Posted by MrNishino
To clarify: since we’re looking for the Wine executable, that means that the patch modifies the Wine executable, not the SH4 executable?
|
No, the patch does modify sh4.exe...
We just need to find WINE to make sure that we are telling MacOS to run 'wine'.
Best DOS example I can think of (since DOS is very simple, and it's all command line):
Let's say you want to edit a file named "textfile.txt", but it is on D:\.
All system files (including the program "edit") are on "C:\".
You must either:
1: Be at:
and type:
OR
2: Be at:
and type:
OR
3: From
ANYWHERE ELSE, such as:
Quote:
E:\games\too\many\folders\and\even\more\folders
|
You must type:
We are specificaly calling each program and file by their location.
Now UNIX/BSD(UNIX)/MacOS/Linux:
IF a directory is in the "PATH", then the OS will look for the executable (such as wine) there.
IF the executable is not in any of those directories it will give an error.
So all we are doing is looking for "wine" so we can tell the OS to /run/this/file/located/right/here.
It's like asking someone "Can you go get some milk from [store name here]?"
And *NOT* leaving them to their own devices.
Hopefully I didn't lose you with my rambling...
Barracuda