Can anyone provide some help Please??
Following is the setup
Netware servers v5 and above
Btrieve v6.10
While trying to run a remote netware btrieve application from a
windows 2000 client , we get btrieve errors status 91 for some servers
and status 22 for others?

Any tips ??

Status 91 typically indicates an invalid SPX configuration on the
workstation. Many older NetWare boxes use 802.3 network frame type,
while Windows defaults to 802.2 frame type.

Two solutions:
1) Properly enable 802.2 on the NetWare servers (Recommended).
2) Manually change the SPX configuration to force the IPX frame type to
802.3.

As for the Status 22, this indicates a record length is too long for
the requested data buffer. This is a status code, not necessarily an
error, because sometimes the data buffer is indeed longer and the
application just wants to read part of it.

This issue can be caused by running an older program with a newer set
of data (that was extended by the app developer).
Goldstar Software Inc.
Pervasive-based Products, Training & Services
Bill Bach
BillBach (AT) goldstarsoftware (DOT) com
http://www.goldstarsoftware.com
*** Chicago: Pervasive Service & Support Class - May 2008 ***


rubes wrote:



--

Status 91 typically indicates an invalid SPX configuration on the
workstation. Many older NetWare boxes use 802.3 network frame type,
while Windows defaults to 802.2 frame type.

Two solutions:
1) Properly enable 802.2 on the NetWare servers (Recommended).
2) Manually change the SPX configuration to force the IPX frame type to
802.3.

As for the Status 22, this indicates a record length is too long for
the requested data buffer. This is a status code, not necessarily an
error, because sometimes the data buffer is indeed longer and the
application just wants to read part of it.

This issue can be caused by running an older program with a newer set
of data (that was extended by the app developer).
Goldstar Software Inc.
Pervasive-based Products, Training & Services
Bill Bach
BillBach (AT) goldstarsoftware (DOT) com
http://www.goldstarsoftware.com
*** Chicago: Pervasive Service & Support Class - May 2008 ***


rubes wrote:



--

Status 91 typically indicates an invalid SPX configuration on the
workstation. Many older NetWare boxes use 802.3 network frame type,
while Windows defaults to 802.2 frame type.

Two solutions:
1) Properly enable 802.2 on the NetWare servers (Recommended).
2) Manually change the SPX configuration to force the IPX frame type to
802.3.

As for the Status 22, this indicates a record length is too long for
the requested data buffer. This is a status code, not necessarily an
error, because sometimes the data buffer is indeed longer and the
application just wants to read part of it.

This issue can be caused by running an older program with a newer set
of data (that was extended by the app developer).
Goldstar Software Inc.
Pervasive-based Products, Training & Services
Bill Bach
BillBach (AT) goldstarsoftware (DOT) com
http://www.goldstarsoftware.com
*** Chicago: Pervasive Service & Support Class - May 2008 ***


rubes wrote:



--

On Jun 16, 10:08*pm, "Bill Bach" <golds... (AT) speakeasy (DOT) net> wrote:
Thanks for the help. What is the procedure to properly enable 802.2 on
the NetWare servers (v 5). Also observed that a netware btrieve
application runs properly ( Netware 5.0) on DOS machines and Windows
98. However, it gives status 20 record manager inactive' on a Windows
2000/XP client on the local network.

Please help

On Jun 16, 10:08*pm, "Bill Bach" <golds... (AT) speakeasy (DOT) net> wrote:
Thanks for the help. What is the procedure to properly enable 802.2 on
the NetWare servers (v 5). Also observed that a netware btrieve
application runs properly ( Netware 5.0) on DOS machines and Windows
98. However, it gives status 20 record manager inactive' on a Windows
2000/XP client on the local network.

Please help

On Jun 16, 10:08*pm, "Bill Bach" <golds... (AT) speakeasy (DOT) net> wrote:
Thanks for the help. What is the procedure to properly enable 802.2 on
the NetWare servers (v 5). Also observed that a netware btrieve
application runs properly ( Netware 5.0) on DOS machines and Windows
98. However, it gives status 20 record manager inactive' on a Windows
2000/XP client on the local network.

Please help

The problem is the Microsoft SPX stack, which works differently in the
newer operating systems. Check your DOS machines -- I bet you have the
802.3 stack loaded, right?

If you have 802.2 enabled already on the network on ANY server, first
you need to find the IPX network address for that protocol. Otherwise,
you risk causing more problems than you'll solve. If you do NOT have
802.2 anywhere, then you can pick your own network number from any 8
hex digits. Use a random number if you want, or use something like
00802200, 00008022, FEEDFACE, BEEFBABE, or whatever.

Once you have an IPX network number, you need to enable the stack. An
article that explains the whole stinking mess can be found here:
http://support.novell.com/techcenter...a19930905.html

With newer versions of the NetWare OS, you may also be able to run
INETCFG and use the menu options to configure it for you...
Goldstar Software Inc.
Pervasive-based Products, Training & Services
Bill Bach
BillBach (AT) goldstarsoftware (DOT) com
http://www.goldstarsoftware.com
*** Chicago: Pervasive Service & Support Class - May 2008 ***





--

The problem is the Microsoft SPX stack, which works differently in the
newer operating systems. Check your DOS machines -- I bet you have the
802.3 stack loaded, right?

If you have 802.2 enabled already on the network on ANY server, first
you need to find the IPX network address for that protocol. Otherwise,
you risk causing more problems than you'll solve. If you do NOT have
802.2 anywhere, then you can pick your own network number from any 8
hex digits. Use a random number if you want, or use something like
00802200, 00008022, FEEDFACE, BEEFBABE, or whatever.

Once you have an IPX network number, you need to enable the stack. An
article that explains the whole stinking mess can be found here:
http://support.novell.com/techcenter...a19930905.html

With newer versions of the NetWare OS, you may also be able to run
INETCFG and use the menu options to configure it for you...
Goldstar Software Inc.
Pervasive-based Products, Training & Services
Bill Bach
BillBach (AT) goldstarsoftware (DOT) com
http://www.goldstarsoftware.com
*** Chicago: Pervasive Service & Support Class - May 2008 ***





--

The problem is the Microsoft SPX stack, which works differently in the
newer operating systems. Check your DOS machines -- I bet you have the
802.3 stack loaded, right?

If you have 802.2 enabled already on the network on ANY server, first
you need to find the IPX network address for that protocol. Otherwise,
you risk causing more problems than you'll solve. If you do NOT have
802.2 anywhere, then you can pick your own network number from any 8
hex digits. Use a random number if you want, or use something like
00802200, 00008022, FEEDFACE, BEEFBABE, or whatever.

Once you have an IPX network number, you need to enable the stack. An
article that explains the whole stinking mess can be found here:
http://support.novell.com/techcenter...a19930905.html

With newer versions of the NetWare OS, you may also be able to run
INETCFG and use the menu options to configure it for you...
Goldstar Software Inc.
Pervasive-based Products, Training & Services
Bill Bach
BillBach (AT) goldstarsoftware (DOT) com
http://www.goldstarsoftware.com
*** Chicago: Pervasive Service & Support Class - May 2008 ***





--