Posted by Grant Foraker on June 02, 2004 at 12:43:50:
While visiting a small customer, I convinced the manager to let me set up a demo of Comet 2004 v334 on his workstation. The demo ran fine.
Once the other user was off I upgraded the system to Comet v336.
Returning to the manager to continue the sales pitch, I attempted to start Comet. It took much longer than normal before a small Cosw error message appeared stating that cosc and other comet modules could not be loaded and that I should check to see if they were in the start up directory. When I reinstalled 334 (ZIP) the demo again worked. I installed 335 (EXE) and that worked.
This is a Windows 2000 peer-to-peer network with the Comet executables located on the host at C:\COMET. All the files are "L". The manager has a network drive mapped as Q:. The shortcut is q:\cosw.exe /PN=ONSITE /D. The "Flying C" splash screen never appeared. Tested the host workstation in demo mode using 336 and it worked.