do NON Windows TCP/IP DOS Requesters exist? 
Author Message
 do NON Windows TCP/IP DOS Requesters exist?

do NON Windows TCP/IP DOS Requesters exist?

dear Pervasive and community,

The DOS/BTRIEVE applications I currenty work with use
- PSQL 7 on a Netware 4.11 Server and BREQUEST'ers for DOS

I am moving the whole database and application to a
Pervasive 2000 installation on a Linux Server.

For the most part Windows95/NT computers sucessfully use the
DOSBOX TCP/IP Requesters and can interface with the databases.
But I have a large number of pure DOS computers that don't have
M$ Windows at all.

I have not been able to find a replacement for BREQUEST.EXE or
BREQNT.EXE - that seem to solely use IPX/SPX for communications.
Can BREQNT be configured to use TCP/IP to access the server in a
pure DOS environment?

Would there be a chance to get the requesters to work with a special
TCP/IP client.  Like ..
- Packet drivers or
- MS's TCP/IP for Windows4Workgroup or
- Novell's ODI DOS client with 32bit TCP/IP Stack
????

my best regards,
Stefan Becker

LUFA Speyer (EDV)

tel  : +49 (0)6232-629542
fax  : +49 (0)6232-629544
http://www.***.com/



Tue, 04 May 2004 19:50:02 GMT
 do NON Windows TCP/IP DOS Requesters exist?

Starting with PSQL 7, SP3:

DOS TCP/IP requester (BREQTCP.EXE): Allows a DOS application to run in
 any Windows DOS box or on a DOS workstation, and communicate to a
 remote Pervasive.SQL 2000i server engine via the TCP/IP protocol.

Look in the client folder of the server for READDOS.TXT.

John Schexnaydre


do NON Windows TCP/IP DOS Requesters exist?

dear Pervasive and community,

The DOS/BTRIEVE applications I currenty work with use
- PSQL 7 on a Netware 4.11 Server and BREQUEST'ers for DOS

I am moving the whole database and application to a
Pervasive 2000 installation on a Linux Server.

For the most part Windows95/NT computers sucessfully use the
DOSBOX TCP/IP Requesters and can interface with the databases.
But I have a large number of pure DOS computers that don't have
M$ Windows at all.

I have not been able to find a replacement for BREQUEST.EXE or
BREQNT.EXE - that seem to solely use IPX/SPX for communications.
Can BREQNT be configured to use TCP/IP to access the server in a
pure DOS environment?

Would there be a chance to get the requesters to work with a special
TCP/IP client.  Like ..
- Packet drivers or
- MS's TCP/IP for Windows4Workgroup or
- Novell's ODI DOS client with 32bit TCP/IP Stack
????

my best regards,
Stefan Becker

LUFA Speyer (EDV)

tel  : +49 (0)6232-629542
fax  : +49 (0)6232-629544
http://www.lufa-speyer.de/



Tue, 04 May 2004 20:57:59 GMT
 do NON Windows TCP/IP DOS Requesters exist?
Did you check out the thread that starts with the following message?

You need MS-Client for DOS with "full redirector"; it won't work with
anything else. Full client will take up 100k resident memory, so if
you can't spare this much: forget it!

Microsoft network drivers are broken! I'm not really sure at which
level the problems start, but the only way I ever got any of this to
work, was by having the Microsoft client connect to the Novell ODI
layer.

When running through the ODI layer, SPX is significantly faster than
TCP.

I can see why you'd want to go to Linux, we're running it ourselves.
We even have it setup as our primary domain controller. Our primary
server is a Novell server though, and we're quite happy with it. The
only problem with this kind of hybrid network is to keep it
synchronized since they can't be administered as one. Why not keep the
Novell server (and upgrade it to a faster machine) and add the Linux
server to fill your additional needs?



Quote:
>do NON Windows TCP/IP DOS Requesters exist?

>dear Pervasive and community,

>The DOS/BTRIEVE applications I currenty work with use
>- PSQL 7 on a Netware 4.11 Server and BREQUEST'ers for DOS

>I am moving the whole database and application to a
>Pervasive 2000 installation on a Linux Server.

>For the most part Windows95/NT computers sucessfully use the
>DOSBOX TCP/IP Requesters and can interface with the databases.
>But I have a large number of pure DOS computers that don't have
>M$ Windows at all.

>I have not been able to find a replacement for BREQUEST.EXE or
>BREQNT.EXE - that seem to solely use IPX/SPX for communications.
>Can BREQNT be configured to use TCP/IP to access the server in a
>pure DOS environment?

>Would there be a chance to get the requesters to work with a special
>TCP/IP client.  Like ..
>- Packet drivers or
>- MS's TCP/IP for Windows4Workgroup or
>- Novell's ODI DOS client with 32bit TCP/IP Stack
>????

>my best regards,
>Stefan Becker

>LUFA Speyer (EDV)

>tel  : +49 (0)6232-629542
>fax  : +49 (0)6232-629544
>http://www.lufa-speyer.de/

 Gordon Bos
 Q-RY Solutions
 +31-(0)15-2564035

 http://www.q-ry.nl/



Wed, 05 May 2004 03:17:10 GMT
 do NON Windows TCP/IP DOS Requesters exist?
Probably a better sugestion.

Yes there are DOS IP requesters.
No they do not work to a Pervasive.SQL Linux server as they were never
updated for it.  I have tried and the best I was ever able to do was
either a hang or a status 91.

There is an alternative though.
Run Telnet on the DOS client and run all of the applications on the
Linux box locally.  I have heard this has the advantage of only
sending screen updates acros the network and is FAST.
Since it only sends TEXT screen updates, it even works well over slow
links.

Leonard

On Fri, 16 Nov 2001 20:17:10 +0100, Gordon

Quote:

>Did you check out the thread that starts with the following message?

>You need MS-Client for DOS with "full redirector"; it won't work with
>anything else. Full client will take up 100k resident memory, so if
>you can't spare this much: forget it!

>Microsoft network drivers are broken! I'm not really sure at which
>level the problems start, but the only way I ever got any of this to
>work, was by having the Microsoft client connect to the Novell ODI
>layer.

>When running through the ODI layer, SPX is significantly faster than
>TCP.

>I can see why you'd want to go to Linux, we're running it ourselves.
>We even have it setup as our primary domain controller. Our primary
>server is a Novell server though, and we're quite happy with it. The
>only problem with this kind of hybrid network is to keep it
>synchronized since they can't be administered as one. Why not keep the
>Novell server (and upgrade it to a faster machine) and add the Linux
>server to fill your additional needs?



>>do NON Windows TCP/IP DOS Requesters exist?

>>dear Pervasive and community,

>>The DOS/BTRIEVE applications I currenty work with use
>>- PSQL 7 on a Netware 4.11 Server and BREQUEST'ers for DOS

>>I am moving the whole database and application to a
>>Pervasive 2000 installation on a Linux Server.

>>For the most part Windows95/NT computers sucessfully use the
>>DOSBOX TCP/IP Requesters and can interface with the databases.
>>But I have a large number of pure DOS computers that don't have
>>M$ Windows at all.

>>I have not been able to find a replacement for BREQUEST.EXE or
>>BREQNT.EXE - that seem to solely use IPX/SPX for communications.
>>Can BREQNT be configured to use TCP/IP to access the server in a
>>pure DOS environment?

>>Would there be a chance to get the requesters to work with a special
>>TCP/IP client.  Like ..
>>- Packet drivers or
>>- MS's TCP/IP for Windows4Workgroup or
>>- Novell's ODI DOS client with 32bit TCP/IP Stack
>>????

>>my best regards,
>>Stefan Becker

>>LUFA Speyer (EDV)

>>tel  : +49 (0)6232-629542
>>fax  : +49 (0)6232-629544
>>http://www.lufa-speyer.de/

> Gordon Bos
> Q-RY Solutions
> +31-(0)15-2564035

> http://www.q-ry.nl/



Wed, 05 May 2004 12:21:47 GMT
 
 [ 4 post ] 

 Relevant Pages 

1. Artefact DOS TCP/IP Requester

2. TCP/IP DOS Support For Btrieve Requester

3. "new" DOS TCP/IP Requester

4. Btrieve 7 and DOS Requester on TCP/IP

5. TCP/IP DOS Requester

6. Dos TCP/IP Requester Very Very Slow

7. DOS V6, Windows 95 and TCP/IP

8. 24321-FL-TAMPA/ST. PETERSBURG-C-Windows 95-Windows NT-SQL-TCP/IP-C, Windows 95, Windows NT, SQL, TCP/IP

9. 24321-FL-TAMPA/ST. PETERSBURG-C-Windows 95-Windows NT-SQL-TCP/IP-C, Windows 95, Windows NT, SQL, TCP/IP

10. general tcp/IP network error after changing sql server tcp/ip address

11. Comparing NetBios->TCP/IP vs TCP/IP Sockets running SQL Server ODBC

12. Configuration Informix server with reaseau TCP/IP /Configuration serveur Informix avec reaseau TCP/IP


 
Powered by phpBB® Forum Software