dbTalk Databases Forums  

Upgrade to XP from 98 produces LOCK errors (code 81)

comp.databases.btrieve comp.databases.btrieve


Discuss Upgrade to XP from 98 produces LOCK errors (code 81) in the comp.databases.btrieve forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Mister Smith
 
Posts: n/a

Default Upgrade to XP from 98 produces LOCK errors (code 81) - 12-12-2003 , 08:42 AM






Greetings ... the situation is thus: Windows 98 workstation, system
transferred to new hardware & upgraded to XP Pro. Server is NT 4.11
w/SP7, all has been working fine for ages. Btrieve version is 6.15;
BTRIEVE.NLM is 6.15.2, requester is 4.11q, XP Novell client is latest,
server is IPX only. Old networked contact manager Maximizer 5.0, when
upgraded, gives LOCK errors with code 81. I've checked BTI.INI and
the MAXLOCKS registry entry; the latter was 220 as recommended by
documentation.

Strangely, previous workstations were upgraded successfully! That
would lead me to think that perhaps the Novell client version is to
blame, but I thought I'd ask for the your thoughts before downgrading
the client.

Many thanks,
Michael Smith

Reply With Quote
  #2  
Old   
Gordon
 
Posts: n/a

Default Re: Upgrade to XP from 98 produces LOCK errors (code 81) - 12-12-2003 , 02:39 PM






"All has been working for ages"

Well, it must have if you're still on 6.15.2. You'll definitly want to
update to 6.15.430 and add "-r=1500" to the load bspxcom line.

Wouldn't have a clue what XP does whith IPX/SPX, but don't think it'll
be much good. You'll need to set an unique internal network address
and fix the protocol to support one frametype only.

You might want to check for .LCK files, indicating workstation engines
are being used instead of the server engine. If any of the above
conditions isn't met, I'd definitly expect them to be there. How about
upgrading to the current version of Pervasive? It's tested and
supported on all current Windows platforms.


On 12 Dec 2003 06:42:45 -0800, nunayer (AT) aol (DOT) com (Mister Smith) wrote:

Quote:
Greetings ... the situation is thus: Windows 98 workstation, system
transferred to new hardware & upgraded to XP Pro. Server is NT 4.11
w/SP7, all has been working fine for ages. Btrieve version is 6.15;
BTRIEVE.NLM is 6.15.2, requester is 4.11q, XP Novell client is latest,
server is IPX only. Old networked contact manager Maximizer 5.0, when
upgraded, gives LOCK errors with code 81. I've checked BTI.INI and
the MAXLOCKS registry entry; the latter was 220 as recommended by
documentation.

Strangely, previous workstations were upgraded successfully! That
would lead me to think that perhaps the Novell client version is to
blame, but I thought I'd ask for the your thoughts before downgrading
the client.

Many thanks,
Michael Smith

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

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


Reply With Quote
  #3  
Old   
Mister Smith
 
Posts: n/a

Default Re: Upgrade to XP from 98 produces LOCK errors (code 81) - 12-12-2003 , 09:33 PM



Gordon <grafzerk (AT) bigfoot (DOT) no.spam.please.com> wrote

Quote:
"All has been working for ages"

Well, it must have if you're still on 6.15.2. You'll definitly want to
update to 6.15.430 and add "-r=1500" to the load bspxcom line.

Wouldn't have a clue what XP does whith IPX/SPX, but don't think it'll
be much good. You'll need to set an unique internal network address
and fix the protocol to support one frametype only.

You might want to check for .LCK files, indicating workstation engines
are being used instead of the server engine. If any of the above
conditions isn't met, I'd definitly expect them to be there. How about
upgrading to the current version of Pervasive? It's tested and
supported on all current Windows platforms.


On 12 Dec 2003 06:42:45 -0800, nunayer (AT) aol (DOT) com (Mister Smith) wrote:

Greetings ... the situation is thus: Windows 98 workstation, system
transferred to new hardware & upgraded to XP Pro. Server is NT 4.11
w/SP7, all has been working fine for ages. Btrieve version is 6.15;
BTRIEVE.NLM is 6.15.2, requester is 4.11q, XP Novell client is latest,
server is IPX only. Old networked contact manager Maximizer 5.0, when
upgraded, gives LOCK errors with code 81. I've checked BTI.INI and
the MAXLOCKS registry entry; the latter was 220 as recommended by
documentation.

Strangely, previous workstations were upgraded successfully! That
would lead me to think that perhaps the Novell client version is to
blame, but I thought I'd ask for the your thoughts before downgrading
the client.

Many thanks,
Michael Smith


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

http://www.q-ry.nl/
Thanks for your reply. Yes, there are LCK files being produced. So
you think upgrading the BTRIEVE setup on the Novell server will be
effective? I'm willing to give it a go. As for upgrading to
Pervasive 8, that's most likely out of the question; this office is
most definitely NOT interested in change until it's forced upon them,
as are most of the small businesses with which I deal. They are wary,
and rightly so, of upgrades. Upgrades tend to break things. As this
98-to-XP move has done. I wouldn't've upgraded the OS at all if it
weren't for the fact that the new Dell in question has hardware that's
no longer supported in 98.

The really peculiar thing about this is that earlier 98-to-XP upgrades
went swimmingly, introducing no problems with Maximizer. (Now,
getting their DaVinci internal email system, vintage 1994, to work
with XP was a bit of a feat ...)


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.