"file not found" [detailed]

[FYR]

Wine 1.1.15
trying to run Flat Assembler 1.67.36 which was moved in /home/.wine/drive_c beforehand.

error when trying to compile/run a file: "file not found".

[austin987]

On Sun, Mar 22, 2009 at 6:56 AM, FYR <[email protected]> wrote:

Wine 1.1.15

Upgrade to 1.1.17

trying to run Flat Assembler 1.67.36 which was moved in /home/.wine/drive_c beforehand.

Moved? You should install it properly, like you would on Windows.

error when trying to compile/run a file: "file not found".

Terminal output?

Though it still may not work....I seem to remember a bug in bugzilla
about this program, but can't seem to find one about compiling...


--
-Austin

[FYR]

On Sun, Mar 22, 2009 at 6:56 AM, FYR <[email protected]> wrote:

Wine 1.1.15

Upgrade to 1.1.17

once it's available for my distro, sir.. but good point.

trying to run Flat Assembler 1.67.36 which was moved in /home/.wine/drive_c beforehand.

Moved? You should install it properly, like you would on Windows.

ZIP file. -- and no Registry keys needed AFAIK.

error when trying to compile/run a file: "file not found".

Terminal output?

no.
you open an example file, it's displayed OK and can be edited etc.
but when you try to compile/run it:

hopefully 1.1.17 will fix this. if not, I'll be back.

[austin987]

On Sun, Mar 22, 2009 at 11:29 AM, FYR <[email protected]> wrote:

austin987 wrote:

trying to run Flat Assembler 1.67.36 which was moved in /home/.wine/drive_c beforehand.

Moved? You should install it properly, like you would on Windows.

ZIP file. -- and no Registry keys needed AFAIK.

Just making sure.

austin987 wrote:

error when trying to compile/run a file: "file not found".

Terminal output?

no.
you open an example file, it's displayed OK and can be edited etc.
but when you try to compile/run it:
[Image: http://i42.tinypic.com/np0s4i.png ]
hopefully 1.1.17 will fix this. if not, I'll be back.

It very well may be a wine bug. May be an issue with case sensitivity.
You might try ensuring all files are lower case, just in case.


--
-Austin

[FYR]

I see the problem.........
Wine doesn't let FASM go and include the needed files..
i.e. doesn't let the program access a given file.

now why does this happen, Wine doesn't "understand" how the program wants to access the file?
I saw stuff like this in previous versions of Wine..

how can I set the path or something, I don't know what can be done?

[austin987]

On Sun, Mar 22, 2009 at 1:05 PM, FYR <[email protected]> wrote:

I see the problem.........
Wine doesn't let FASM go and include the needed files..
i.e. doesn't let the program access a given file.

now why does this happen, Wine doesn't "understand" how the program wants to access the file?
I saw stuff like this in previous versions of Wine..

how can I set the path or something, I don't know what can be done?

Set PATH in registry.


--
-Austin

[FYR]

more detail, please. where is this Registry?

also -- I'm thinking that Wine stops certain "methods" of file grabbing that are similar to what viruses use.......

[austin987]

On Sun, Mar 22, 2009 at 2:58 PM, FYR <[email protected]> wrote:

more detail, please. where is this Registry?

$ wine regedit

also -- I'm thinking that Wine stops certain "methods" of file grabbing that are similar to what viruses use.......

No, it doesn't.

--
-Austin

[FYR]

nice regedit-like thing (is it actually a Win32 program?)..
.. anyway, I don't know where and how to set the PATH variable.

[austin987]

On Sun, Mar 22, 2009 at 3:43 PM, FYR <[email protected]> wrote:

nice regedit-like thing (is it actually a Win32 program?)..

Sorta...winelib.

 .. anyway, I don't know where and how to set the PATH variable.

Same as on windows:

[HKLM\\System\\CurrentControlSet\\Control\\Session Manager\\Environment]

--
-Austin

[vitamin]

error when trying to compile/run a file: "file not found".

Terminal output is where?

[FYR]

here's your terminal output buddy!

Code: Select all

drunk@beertruck:~/fasmw16736$ wine FASMW.EXE
drunk@beertruck:~/fasmw16736$    

I failed it 3 times and it still didn't output any error -- 'cause in Wine's point of view, there wasn't one.

[FYR]

[HKLM\\System\\CurrentControlSet\\Control\\Session Manager\\Environment]

thanks, set it to:

Code: Select all

C:\windows\system32;C:\windows;C:\;C:\fasmw16736;C:\fasmw16736\INCLUDE;C:\fasmw16736\examples

problem remains.

[FYR]

thanks everybody for your help.
I don't see the point of wasting our time with this.

1) I'm not using the latest version of Wine
2) Linux version of FASM (commandline only) runs flawlessly

would've been nice to be able to use the actual IDE, but it's of small importance indeed.

-- to the Developers: --
if this is indeed a glitch in how Wine gives apps access to files, you might want to check out FASM's source code to see where the problem might come from.

thanks for your time, and thanks for a great piece of software.

if anyone has any more suggestions, I'll try -- otherwise it's all good still.

[rein]

-- to the Developers: --
if this is indeed a glitch in how Wine gives apps access to files, you might want to check out FASM's source code to see where the problem might come from.

Well, checking the documentation ( fasm.pdf) tells you that:

"The example source provided with this version require you have environment variable INCLUDE set to the path of the include directory"

or:

"put the following two lines into your c:\fasmw\fasmw.ini file:
[Environment]
Include = c:\fasmw\include
"

You can quickly test this by running wine with a command like:

INCLUDE='c:\fasmw\include' wine fasm.exe

(works fine here) or put it in the registry or the ini file as indicated.

[FYR]

yeah, RTFM applies very well once again.
I did look into the INI, but saw nothing and I never thought of reading the PDF.

thank you rein.