[Wine]warn:dosfs:DOSFS_FindUnixName (Xilinx)

[James Hawkins]

Have you bothered to look at the wine-devel docs?

"WARN - These are warning messages. You should report a warning when
something unwanted happens, and the function can not deal with the
condition. This is seldomly used since proper functions can usually
report failures back to the caller. Think twice before making the
message a warning."

Something unwanted happened: wine failed.  Craig was wise in showing
these warnings to wine-devel so that someone with enough knowledge on
wine can assess the underlying error.  You said it best yourself:

> They are there because they MAY indicate trouble.

That is exactly right.  These warnings quite possibly are the reason
wine is failing, and they should be looked into in order to find out
the problem.  Thanks Craig for posting as much information about the
problem as you have.  It will be a big help to all of the developers
that take a look at the problem.

One solution might be to run the program with WINEDEBUG=+loaddll so
the command would be:

WINEDEBUG=+loaddll wine nameofprog.exe

This will show you a list of the dlls that nameofprog.exe loads in
order to call those api's.  If you could send a message back to the
list with the output when you run this, we can see if you need to dl a
native dll and use that instead to get the program working.

On Sat, 28 Aug 2004 09:19:59 +0200, Rein Klazes <rklazes at xs4all.nl> wrote:
> On Fri, 27 Aug 2004 16:12:10 -0400, you wrote:
> 
> > > > Wine failed with return code 1
> > I think this is the error Craig is concerned with.  Even though he is
> > only getting warnings, those warnings are probably the cause of wine
> > failing.
> >
> > > Any reason why you think these warnings are a problem?
> > All warnings should be taken to heart.  A warning is a caution that
> > says "something might be wrong here so look into it."  If a program is
> > running smoothly and not messing up, then we shouldnt be issuing
> > warnings, because everything is running correctly.  Just like when
> > compiling, warnings should always be looked in to.
> 
> You have not bothered to look at the warnings, did you?
> 
> Read them: files are reported not to be there. There are plenty of
> reasons why that may be good or bad. Wine cannot possibly tell the
> difference. They are there because they MAY indicate trouble. The result
> is that enabling warnings will ALWAYS generate zillions of warnings,
> EVEN with perfect running programs and there is no trouble AT ALL.
> 
> Just try it.
> 
> 
> 
> Rein.
> --
> Rein Klazes
> rklazes at xs4all.nl
> 


-- 
James Hawkins