dbTalk Databases Forums  

Windows 2000 w/ sp4 workstation - SLOW. Please assist

comp.databases.btrieve comp.databases.btrieve


Discuss Windows 2000 w/ sp4 workstation - SLOW. Please assist in the comp.databases.btrieve forum.



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

Default Windows 2000 w/ sp4 workstation - SLOW. Please assist - 07-07-2003 , 08:15 AM






Running a win2k sp4 workstation. Our server at work is windows
2000 also. All workstations except mine are win98, and performance is
great. But on my machine, when I run our office app (Touchstone
2000), it loads slow, and takes a year to print. Is there
compatibility issues with Pervasive 7.0 (w/ sp6) aned the newest
version of btrieve? What can I check to find out why performance is so
slow...




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

Default Re: Windows 2000 w/ sp4 workstation - SLOW. Please assist - 07-11-2003 , 03:14 PM






BoDEAN <jbo (AT) aol (DOT) com> wrote

Quote:
Running a win2k sp4 workstation. Our server at work is windows
2000 also. All workstations except mine are win98, and performance is
great. But on my machine, when I run our office app (Touchstone
2000), it loads slow, and takes a year to print. Is there
compatibility issues with Pervasive 7.0 (w/ sp6) aned the newest
version of btrieve? What can I check to find out why performance is so
slow...


HERE are the results of the stress tests: Any ideas?


---- Results of Communications Testing ----
--Information : -----
--Information : Test started on Fri Jul 11 16:11:56 2003
--Information : Engine to test : Btrieve
--Information : Transport : All Available
--Information : Test level : Communications Stress Test
--Information : Target name : G:\TS2000
--Information : -----
Step 1 : Establish the workstation environment.
--Information : Winsock description : WinSock 2.0
--Warning : Winsock SPX is unavailable
--Warning : socket error = 10047
--Information : Winsock TCP/IP is available
--Warning : Winsock SPX is not available
--Information : Microsoft Networking API is available
--Warning : Could not load CALWIN32.DLL
--Warning : NetWare API is not available
--Warning : Could not load NETWIN32.DLL
--Warning : NetWare NDS API is not available
--Information : Access to Scalable SQL for Windows NT database names is available
Step 2 : Determine full target name.
--Information : Input target name is G:\TS2000
--Information : No IDSHOSTS file found.
--Information : Target does not appear to be IDS.
--Warning : NetWare NDS API is not available
--Warning : NetWare API not available for name parsing.
--Information : Calling Microsoft Networking API to parse input target.
--Information : Target server name BUDGET2
--Information : Fully qualified name \\BUDGET2\APPS\TS2000
Step 3 : Resolve full target name into a network address.
--Warning : NetWare NDS API not available for address resolution
--Warning : Unable to query NetWare NDS
--Warning : NetWare API not available for address resolution
--Warning : Unable to read NetWare Bindery via NetWare API
--Information : Using Winsock Name Resolution API to read NetWare Bindery
--Information : There may be a slight delay - please wait
--Warning : Unable to resolve server name via Winsock Name Resolution API
--Warning : GetAddressByName GetLastError 122
--Information : Attempting to access Windows NT server BUDGET2
--Information : Target engine SPX address : 00000000:00C09F1D77B7:8059
--Information : Target engine TCP address : 192.168.2.21:3351
Step 4 : Establish a connection to the target engine.
--Warning : TCP/IP setsockopt (SO_LINGER) error = 10014
--Information : Local TCP/IP address : 192.168.2.4
--Information : TCP/IP connection established (0x00d8)
--Warning : WinSock SPX not available
--Warning : Unable to connect via Winsock SPX.
Step 5 : Send data to/receive data from target server.
--Information : Making Btrieve Version call with TCP/IP.
--Information : Btrieve Version is 7.16 Windows NT.
--Information : Beginning TCP/IP Stress Test
--Information : TCP/IP Stress test canceled by user
--Information : Total TCP/IP requests processed : 565
Step 6 : Terminate the established connection.
--Information : TCP/IP connection terminated successfully.
--Information : -----
--Information : Test completed on Fri Jul 11 16:12:32 2003
--Information : -----


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.