Hello ppl, I have an application that gets updates via a network path for example \\192.168.40.100\ is the update-server in WINE i can only make the updates if I mount via samba the available share z:/ -> is the \\192.168.40.100 And I must configure the server to show updates in Z: so that the wine clients can make the updates. To update the windows clients I change the config again to \\192.168.40.100\ Any Idea to keep this in only one way
There's a recipe at http://bugs.winehq.org/show_bug.cgi?id=425#c9 Basically, use smbmount to mount the share somewhere, then make a symlink in ~/.wine/unc pointing to it. Good luck!
vitamin wrote:> > xekhz wrote: > > I get this error > > err:file:GetLongPathNameW UNC pathname L"\\\\192.168.40.100\\airc\\updates\\sca\\install.exe" > > > > BUT if I execute winebrowse form a terminal it works. > > winebrowse "\\\\192.168.40.100\\airc\\updates\\sca\\install.exe" > > > > So what is the problem ?? > > > Read the bug Dan pointed to. Only some limited functionality is implemented. And the bug itself is not closed.I read it, but if winebrowse or winepath resolves the UNC correctly, how can I debug to see whats is really happening?
It is the path threw the wine. Some ways are implemented others are not. You can use wine debuging channels and run a trace threw winebrowse and you will see it is not using GetLongPathNameW . GetLongPathNameW is looking up information on the file. UNC is working. Getting more information about the file not working in this case. Yep two bugs.
oiaohm wrote:> It is the path threw the wine. Some ways are implemented others are not. > > You can use wine debuging channels and run a trace threw winebrowse and you will see it is not using GetLongPathNameW . > > GetLongPathNameW is looking up information on the file. > > UNC is working. Getting more information about the file not working in this case. > > Yep two bugs.How can fool wiine so that it continues the process.