On Jun 16, 10:08=A0pm, "Bill Bach" <golds...@[EMAIL PROTECTED]
> wrote:
> Status 91 typically indicates an invalid SPX configuration on the
> workstation. =A0Many 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. =A0This 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).
> =A0 =A0 =A0 =A0 Goldstar Software Inc.
> =A0 =A0 =A0 =A0 Pervasive-based Products, Training & Services
> =A0 =A0 =A0 =A0 Bill Bach
> =A0 =A0 =A0 =A0 BillB...@[EMAIL PROTECTED]
> =A0 =A0 =A0 =A0http://www.goldstarsoftware.com
> =A0 =A0 =A0 =A0 *** Chicago: Pervasive Service & Sup****t Class - May
2008=
***
>
> rubes wrote:
>
> > 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 ??
>
> --
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
|
