Posted by Barbara Brazil on October 03, 2006 at 09:41:05:
In Reply to: Odd happenings with CAUPDVSN.TXT posted by Tom Fulton on October 03, 2006 at 09:22:44:
Tom:
I can answer a couple of your questions. First, remember that anything in $(CATEMP) will be erased whenever Comet is restarted. So, that's what happened to the caupdvsn.txt file you had manually created with the 373 in it. Second, the reason you saw 372 instead of 373 the next time it started up is because that is the version of CosW, not CosH. It just so happens that CosW didn't change between 372 and 373. So that stuff is all explainable and OK.
As far as the last problem is concerned, it sounds like some access is not allowed at the time the Comet service is being started. Remember that this is being done early in the Windows startup procedure. By any chance is $(CATEMP) a mapped drive?
bb