Windows network disk mount problems

Open forum for end-user questions about Wine. Before asking questions, check out the Wiki as a first step.
Forum Rules
Locked
werbor
Newbie
Newbie
Posts: 3
Joined: Sun Nov 11, 2018 2:20 pm

Windows network disk mount problems

Post by werbor » Sun Nov 11, 2018 3:38 pm

My problem is this: I want to gain access to read the file located in the network folder at //192.168.1.2/share mounted like windows network drive (P:\).
For this, I mounted windows share via fstab:
//192.168.1.10/share /drive_p/ cifs credentials = / etc / winpassword, iocharset = utf8, sec = ntlmssp, rw 0 0.

Then I run the program (WBEXEC32.exe) to read from the data file. To select a data file, I select the following path:
Z:\drive_p\data.btr, and I get access to the data.

Then I, through winecfg-> drives edit the path of disk Z: on /drive_p. Then I run the program (WBEXEC32.exe) to read from the data file. To select a data file, I select the following path:
Z:\data.btr, and I get error: Btrieve error 11 (invalid file name) ..


Then I, through winecfg-> drives, add a new P: drive that refers to /drive_p. Then I run the program (WBEXEC32.exe) to read from the data file. To select a data file, I select the following path:
P:\data.btr, and I also get error: Btrieve error 11 (invalid file name) ..

Btrieve error 11 (invalid file name)

The filename specified for the Table Location has a defined
file location which is not a valid DOS filename. This error is
also returned if you specify filename with extension .^^^ or data
buffer for Begin or End continous operation is illegal.

You may get this error from Windows 95 DOS boxes for several reasons:
- Remove LASTDRIVE= from CONFIG.SYS.
- Windows 95 REV B OEM with versions of BREQUEST prior to 6.16.445
can cause Status 11's and Status 12's. Update BREQUEST.
- Older versions of CLIB for NetWare 4.10 can cause Status 12's,
depending on the location of the file. Update CLIB.NLM
- Windows 95 with Novell Client32 and NetWare 3.11 sometimes get
status 11 or 12. Load SHORTAFX.NLM on the NetWare 3.11 server.
The Readme included with the Novell Client32 for Win95 indicates
that this patch fixes long file name resolution problems, but
this also addresses "status 11 and status 12 in a DOS box" problems.


I need your help!

User avatar
dimesio
Moderator
Moderator
Posts: 12672
Joined: Tue Mar 25, 2008 10:30 pm

Re: Windows network disk mount problems

Post by dimesio » Sun Nov 11, 2018 7:35 pm

Z: is a symlink to your root directory. Wine cannot access anything outside the wineprefix without it.

By your own account, the app is able to access the data through Z:, so what are you trying to accomplish by changing it?

werbor
Newbie
Newbie
Posts: 3
Joined: Sun Nov 11, 2018 2:20 pm

Re: Windows network disk mount problems

Post by werbor » Mon Nov 12, 2018 2:22 am

If the data file is stored on a local computer, then any symbolic link (P :, W:) to the folder with the data file does not cause errors in the program (WBEXEC32.exe).
If the data file is stored in a network folder and I mount it to my file system and create a symbolic link for example P :, W: then an error occurs. Mounted the network folder both within and outside of the wineprefix, still an error.
Do not pay attention to editing Z :.

User avatar
dimesio
Moderator
Moderator
Posts: 12672
Joined: Tue Mar 25, 2008 10:30 pm

Re: Windows network disk mount problems

Post by dimesio » Mon Nov 12, 2018 6:55 am

There's a longstanding bug about network shares: https://bugs.winehq.org/show_bug.cgi?id=425. It's not likely to be fixed any time soon, if ever.

werbor
Newbie
Newbie
Posts: 3
Joined: Sun Nov 11, 2018 2:20 pm

Re: Windows network disk mount problems

Post by werbor » Mon Nov 12, 2018 11:50 am

Thanks for the help, dimesio

Locked