I-NET 5.01 <-> Windows sockets
Posted in 1994
Topics: Server Administration
I am trying to use I-NET 5.01 for Windows with FTP Software's PCTCP v2.2. Symptom: Opening a database in I-DBA takes 8-10 minutes In HSTools it takes 1 minute to open and 30 seconds to close it again. I saw a posting by Eric Jones at Choice Hotels International who had a similar problem but got an error message when starting I-DBA: Cannot write to AUX port. I don't get the error message. It just hangs.trying to find the AUX-port. When I redirect the AUX-port to DebugWin I can see a stream of Windows sockets procedure calls when I-DBA starts up ( Mostly WINSOCK:select() and WINSOCK:__WSAFDlsSet() ). When the AUX-port is redirected, I-DBA runs like it should! Katherine Lang at Informix Technical Support answered Eric that he should try to remove the line debug-mode=1 from the [pctcp winsock] section. I didn't have that line, or section, so I couldn't remove it. I tried two other applications that use Windows socket - Oracle Sql*Net and Reflection FTP. They don't write anything on the AUX-port. I also have tried a number of releases of the winsock.dll, but the problem persists. It seems like I-NET, one way or the other, puts the Winsock.dll in debug-mode. Why? And how can I stop it? I don't want to distribute Debug Win with the applications we make in Hyperscript... Any answers appreciated Lars Fransson ______________________________________________________________________________ ____ ___ __/ /_ Lars Fransson / __ __ \\/ / __ \\ Dept. of Medical Informatics (MIB),Ostra Hospital / / / / / / / /_/ / Gothenburg, Sweden /_/ /_/ /_/_/\\____/ lars@ostra.se / +46 31 375609 ______________________________________________________________________________