Posted by Neil Badger on August 12, 2004 at 16:59:54:
Over the last week I updated all my latgest customers branches to cmt2004. I believe Comet was at 337 when I started and was at 339 when I finished. There is a head office and 7 branches. The branches run WINXP as their server and the h.o. w2k3, most workstations are still win98 but some are winxp.The servers comet directories are "cmt2004", all workstations use directory "comet". In theory any workstation at any branch can pcanywhere into any other branch. In practice it is smainly H.O. dialling into the branches. I would appear to have two different version of comet, when I dial into the earlier installations they connect ok and allow me to do stuff, when I go into the later ones, they tell me I need to do the auto update. I do, but if i dial straight back in, it still wants to do the upgrade. After this if I go into the earlier ones, it wants to do the update the first time but is then quite happy on subsequent visits. I am not sure if i ran the comet anywhere update thing at each branch and wasn't sure if I should as it stayed at 337 whilst comet went up to 339. I think the versions of cosw 27.5.2004 at 2.27 & cosp 31/3/2004 at 1 am are the versions that dont seem to stay, whilst cosw 1/7/04 @ 7.37 & cosp 16/6/04 @ 7.27 are the good ones. But I haven't actually got the slightest idea waht I am supposed to be checking. I need them to all be at the same level as I dial up automatically at night and run script files that do not allow for an occasional additional question. After upgrading they often fall over also, as they try to rerun comet.exe but the win98 workstations run cosw.exe. I hope this question makes sense to you because it doesn't to me.
Totally confused badge.