Hello!

I have problem accessing Pervasive/Linux from DOS.

BUTIL -STAT <file on the samba share and accessible by engine>

... Mikrokernel error = 20.

WIndows[98,2000,XP] Btrbox95/BDOSSTUB - OK.

DOS Client to Pervasive/NT - OK.

[samba log for DOS session]

...

[2003/10/17 11:42:40, 3] smbd/ipc.c:named_pipe(334)
named pipe command on <BMKDE\FUNCTION.PIP> name
[2003/10/17 11:42:40, 3] smbd/ipc.c:named_pipe(353)
unknown named pipe: setup 0x54 setup1=0

and tcpdump show only netbios-ssn traffic.

Named pipe issue?

Any ideas?

What requester are you loading for the DOS machine?

BREQTCP v7.90.00 and v8.00.114.00

UnixAuthentication=WORKGROUP in bti.ini

Have you gone through the "Running DOS applications on DOS" in the READDOS.TXT in the PVSW\BIN directory?
Here's the "Running DOS applications on DOS section:
DOS Btrieve application support on DOS workstations is only available
through the DOS TCP/IP or DOS SPX requesters. Both allow a DOS
application to communicate to a Windows NT/2000/XP or NetWare server
running the client/server version of Pervasive.SQL.

Using DOS TCP/IP Support (BREQTCP)
----------------------------------
To use the DOS TCP/IP requester on a DOS workstation, you must have
one of the following TCP/IP stacks:
- Microsoft LAN Manager
- Novell LAN Workplace
- FTP Software 2.2 or greater

You can enable the DOS TCP/IP requester configuration using the
following steps:

1. Copy the following files to the target directory where you
installed the Pervasive.SQL DOS client software. These files can
be found in the CLIENTS\DOS directory on your Pervasive.SQL CD
or in the PVSW\CLIENTS\DOS directory of a Pervasive.SQL server.
BREQTCP.EXE
BREQTCP.MSG
M3OPEN.EXE
MNOVLWP.EXE
MFTP22.EXE
MSOCKLIB.RC
VSLDOS.*

2. Rename your VSLDOS file to VSLDOS.INI in your target directory.

If your TCP stack is Rename this file to VSLDOS.INI
---------------------- ------------------------------
Microsoft LAN Manager VSLDOS.M3
Novell LAN Workplace VSLDOS.LWP
FTP Software VSLDOS.FTP

3. Edit AUTOEXEC.BAT file located in the root directory. Add the
following line to the file:
SET VSL=[jsb-location]

where [jsb-location] is the fully-qualified path of the directory
where you placed the VSLDOS.INI file. For example,
C:\PVSW\BIN for DOS.

4. Restart the computer to register the AUTOEXEC.BAT changes.

Once the DOS TCP/IP requester is setup, follow these steps to run a
DOS application:
1. Make sure your TCP/IP components are loaded, as described by your
TCP/IP stack provider.
2. Run the JSB executable appropriate for your TCP stack:
- M3OPEN.EXE (Microsoft)
- MNOVLWP.EXE (Novell)
- MFTP22.EXE (FTP)
3. Load BREQTCP.EXE.
4. Run your application.

** VENDOR-SPECIFIC NOTES **

MICROSOFT LAN MANAGER
---------------------
1. Ensure that the NUMSOCKETS parameter in the [SOCKETS] section of
TCPUTILS.INI is set to the maximum concurrent number of
connections required.
2. SOCKETS.EXE is a Terminate and Stay Resident (TSR) program that
allows applications to use the Microsoft LAN Manager TCP/IP stack.
SOCKETS.EXE must be located in the same directory as the other
Microsoft LAN Manager TCP/IP executable.

NOVELL LAN WORKPLACE
--------------------
Using Novell's LAN Workplace for DOS with BREQTCP.EXE requires that
the environment variable EXCELAN be set to the Novell base directory.
For example, if you installed LAN Workplace in the C:\NET directory,
do a SET EXCELAN=C:\NET prior to loading MNOVLWP.EXE and BREQTCP.EXE.

FTP SOFTWARE
------------
1. Ensure that you allocate enough TCP and packet buffers for your
application within the FTP kernel.
For example, 'kernel-name' -t 16 -p 20 allocates 16 TCP
connections and 20 packet buffers.
2. Once the maximum number of connections is reached, it may prove
difficult to effect any connection thereafter until all, or almost
all, connections have been closed. You are therefore recommended
to set the maximum number of connections to a high number.

To stop a DOS application, unload the requester components by
entering the command BREQTCP /u at the DOS prompt, followed by
[JSB executable] /U, where [JSB executable] is either M3OPEN.EXE,
MNOVLWP.EXE, or MFTP22.EXE. If running in a Windows DOS box, unload
the requester components before closing the DOS box.

Using DOS SPX Support (BREQUEST/BREQNT)
---------------------------------------
There are two DOS SPX Btrieve requesters. BREQNT.EXE is the "dual
mode" requester that can be used by a DOS application to communicate
to either a Windows NT/2000/XP or a NetWare server. BREQUEST.EXE is a
NetWare-only version of the DOS SPX requester. This exists for
historical purposes before Windows NT support was available, and is
still provided because it has a smaller memory requirement than
BREQNT. If you are accessing Pervasive.SQL on a NetWare server and if
you are running low on DOS conventional memory, you may need to use
BREQUEST. If you are accessing a Windows NT server, you must use
BREQNT.

A DOS application can be run with the SPX protocol to a remote server
engine by following these steps:
1. At a DOS prompt, load BREQNT.EXE or BREQUEST.EXE from the
\PVSW\BIN directory. This needs to be loaded in each DOS session
running a Btrieve application in a Windows environment.
2. Run your application.

To stop a DOS application, unload the requester by entering the
command BREQUEST /u or BREQTCP /u in the DOS box before closing it

Aggggrrrrr, Samba impossible.


Thanks.