Posted by Grant Foraker on December 22, 2003 at 12:11:34:
On my laptop I have a standalone version of Comet 2004 which is working fine. No CFAM. /PN=ROAD built using ROAD.INI
I recently updated my office server to Windows 2003 and have my office workstation running Comet 2004 with no problem. No CFAM.
However, my laptop is now failing to load Comet properly. /PN=LAPTOP
The startup log looks like ...
14:44:23
14:44:23 12/19/2003
14:44:23 COSC Startup in progress
14:44:23 Loading COSH: Prog = Q:\COSH.EXE, Args = /PN=LAPTOP /WD="Q:\"
14:44:23 COSH has been started
14:44:23 COSH? (1)
14:44:23 COSH? (2)
14:44:23 COSH? (3)
14:44:23 COSH window found
14:44:23 COSH registration in progress
14:44:23 COSH Startup in progress...
14:44:23 Comet 2004 Version 604.328
14:44:23 System Version: Microsoft XP Version 5.1 Service Pack 1 (Build 2600)
14:44:23 Using Parameters: /PN=LAPTOP /WD="Q:\"
14:44:23 Checking Type-L Directory : Q:\\
14:44:23 Check Failed, error=2.
14:44:23 Checking Type-L Directory : Q:\\REL\
14:44:23 Checking Type-L Directory : Q:\\UTL\
14:44:23 Checking Type-L Directory : Q:\\COS\
14:44:23 Checking Type-L Directory : Q:\\RAM\
I also get a Comet Startup Warning "Cannot locate driver table .DDL,
TEM.DDL, and PRINT.DDL. The first three chracters of the file name is truncated.
The INI file has ...
[SITE]
Name = Office;
Adr1 = ;
Adr2 = ;
Adr3 = ;
Phn# = ;
Fax# = ;
Attn = ;
Internet Addr = ;
Server = N01, TCP, L, 192.168.16.22;
Server = N02, TCP, L, 192.168.16.2;
and
NODE]
Name = LAPTOP;
Desc = ;
Misc = ;
Path = ;
Phn# = ;
Fax# = ;
User = ;
Internet Addr = ;
Server = N01,S;
Server = N02,F;
When I upgraded the server, I switched from 10.0.0.x to 192.168.16.x.
The laptop is running Comet Security with both Comet 2004 and CS32 licenses at 192.168.16.22.
The "Using Configuration" line appears to be missing from the COSC log and Comet falls into /C mode when I click OK to the missing DDL
message.
I also noticed that the Edit/Settings has changed and the N01 plus IP
address is gone.