UNC path related problem

[tinoper]

Hey there, I have a Windows app (Borland based) working under openSuSE+Wine 1.7.2.
But (always has one) this WinApp works check UNC path and my Wine installation doesn't give the correct information that this app needs about UNC path.

I would like to understand how "unc" directory works under .wine/dosdevices because it seems like nothing changes after that.
I have folder shared a server on "192.168.1.2" named "logic".
I mount \\192.168.1.1\logic on "/mnt/IGA" without any issues.After that I "try" to make a symbolic link between that and unc folder on .wine/dosdevices but it seems like it doesn't works.

If you had to do something like this please drop me a line about it

Regards,
Martin

ps: I checked http://www.winehq.org/site/docs/wineusr ... ure#AEN415 article without success

[oiaohm]

tinoper lot of people do make a few mistakes following those instructions first time.

Code: Select all

mkdir ~/.wine/dosdevices/unc
mkdir ~/.wine/dosdevices/unc/192.168.1.2
ln -s /mnt/IGA ~/.wine/dosdevices/unc/192.168.1.2/logic

ln command does not create folders. No folders it fails. Please try this correct method it still might not work. Wine UNC support is mostly bogus. Due to this some locking is not protected as it should be. So backup logic before doing this. In fact I would skip doing the ln -s first instead just create folder logic and make a copy of logic locally and test if application works in wine correctly doing that first.

Unc support in wine is well tested with single instance access to a share. It is not well tested with multi instance access to a share.

[tinoper]

oiaohm thanks for your reply.
I was created those folders but maybe I did make others mistakes.
Also I try to doing a local copy of "logic" folder but problem still continue.
The exe file that I run doesn't detect path as UNC .It seems like only check winecfg network map.
I was executed in many ways : wine "logic.exe" / wine "h:\logic\logic.exe" ,etc

How can I check that my UNC setup it's working?

Regards,
Martin

[oiaohm]

Remember what I said about UNC being mostly bogus.

Under cmd in wine you will be able to cd to the UNC path if it detected and correct. Will not be able to even list it contents.

Wine own application support for UNC paths is almost non existent so testing if UNC paths are working is hard.

Most users are after the map to drive letter that does not require UNC path. Yes wine does not provide a browser-able network(since it really does not provide a network). UNC in wine is very much have application that supports UNC and give it a UNC path and hope the redirection works.

Wine running binaries from a UNC path forget it wine UNC support is not in the wine loader. Running binaries must be a winecfg mapped drive or strange/bad things happen.

Now of course the project will always accept patches to expand UNC function support.

Basically UNC paths exist to allow applications to work that keep on requesting UNC paths. So its mostly bogus and highly buggy due to be so lightly tested.