Is anybody running SB Client 2.4.2.8 on Windows 2000 or XP?
If yes, any problems?
If not the above version, what SB Client version are you running
on Windows 2000 or XP?
We are running out of machines we can buy with NT, so any
information SB Client and Win2K or XP is appreciated.
We are in the process of updating our app so that we can use
newer SB Clients, but it will take time.
Thanks for your time.
PS. Please reply to my e-mail as well. Thanks.
However, since it is not a supported platform - these problems don't get
resolved. We try reinstalling SBClient and if that does not work then the
OS....
Colin
"Ivo Duarte" <duar...@hotmail.com> wrote in message
news:b0491ee6.02011...@posting.google.com...
I have a customer who uses version 2.4 on W2K and though it works it is not
without its problems. It is very resource hungry and there was some problem
trying to publish it on Citrix.
You could try running the version 4 client mentioned on the previous replies
(bearing in mind the issues raised, with which I concurr) provided that you
don't use GUI, file transfer routines or SBClient calls. Even so, I feel
you would be best off giving it a try first ...
HTH
--
Brett Callacher
Turnaround Technology Ltd
"Colin Alfke" <som...@microsoft.com> wrote in message
news:Gq5G...@picksource.com...
We have managed to get 2.4 working on Citrix, but on an NT box.
I don't know about Win2K.
Can you expand "resource hungry".
Thanks.
"Brett Callacher" <br...@turntech.co.uk> wrote in message
news:u4vrq2t...@corp.supernews.com...
We have managed to get 2.4 working on Citrix, but on an NT box.
I don't know about Win2K.
Can you expand "resource hungry".
Thanks.
"Brett Callacher" <br...@turntech.co.uk> wrote in message
news:u4vrq2t...@corp.supernews.com...
I really recommend upgrading to the 32bit client (4.5.x +). I think 5.0.4 is
the first one certified for Win 2000. Yes, there will be some issues with
differences. When we went to 4.5.4 there were some routines and a couple of
reports we needed to update to work correctly - and you need to re-compile
any compiled SB processes but it's not too bad. Of course, we haven't taken
the plunge to 5.x yet - I'm still waiting for the delivery....
You may want to wait a couple of months to learn which clients are getting
certified on XP and then go to that level so you won't have to worry for a
couple more years.....
My 1.35 Canadian which is getting close to .02 USD!!!
Colin
"Ivo Duarte" <duar...@hotmail.com> wrote in message
news:PIU38.14254$JM6.2...@news20.bellglobal.com...
Colin has already responded to this - that is processor usage jumps to 100%
whenever this version of SBClient is active. It shouldn't be too surprising
as it was written when 32bit Windows was still an Apple in Gates eye. (all
puns intended) :-)
--
Brett Callacher
Turnaround Technology Ltd
"Ivo Duarte" <duar...@hotmail.com> wrote in message
news:pMU38.14256$JM6.2...@news20.bellglobal.com...
SBClient Windows 2000 (and XP) Install Instructions
Windows 2000 changes the default permissions for Users (that is,
restricted users) in HKEY_LOCAL_MACHINE registry branch from Read/Write
to Read only. To solve it, registry entries for BTRieve Technologies
need to be expanded.
Here is the general install procedure, with additional steps explained:
- install SBClient on Windows 2000 as previously described, i.e. as
power user (or administrator)
- after the installation, invoke 'regedt32' via Start Menu:Run option.
- find the key HKEY_LOCAL_MACHINE\Software\Btrieve Technologies.
- click on 'Security' option on menu bar select Permissions option.
- when the dialog comes up, click on 'Advanced' button.
- select the 'Users' group (or the appropriate user group for
your setup).
- IMPORTANT: in addition to the default permissions of:
Query Value, Enumerate Subkeys, Notify and Read Control
add:
Set Value, Create Subkey and Delete.
This will be displayed in the entries list as a separate line with
'Special' Permissions.
In addition, if the boot disk is NTFS, go to WINNT directory and locate
BTrieve log files mkdewe.trn and mkdemsg.log. Change the permissions for
these files to allow access for all (i.e. tick all the checkboxes on
'Security' tab).
If you now save the changes, SBClient will work fine.
--
Posted via dBforums
http://dbforums.com