Posted by Barbara Brazil on June 25, 2010 at 13:28:50:
I just had the opportunity to set up a brand new Comet workstation. It had been years since I had done this and I was curious to see if changes MS and we had made since then would make this process any easier than what I remembered.
My new workstation is a freshly installed Windows 7 Ultimate (64-bit). My existing Comet machine is XP Pro. I decided to have it be my Comet server and have the Win 7 machine just be a workstation.
Here's how it went...
On the XP machine:
- Set up my Comet executables folder for sharing
- Made a Comet profile for the Win 7 machine and SYSGENed
On Win 7:
- Set my Windows Workgroup to the same as my XP workgroup. Now I can see the XP's Comet folder.
- Made a desktop shortcut to Comet.exe on the XP machine. Since this is 64-bit Windows I used the /32 argument. Set my "start-in" folder to the XP's Comet folder since that's where my .cfg is.
- Launched Comet. Comet came up! I did get messages from the Win 7 firewall asking if CLibNetserve and CosC should be allowed access. I said YES. I noticed in startup details that CometLib hadn't registered. I restarted Comet again this time specifying "run as administrator". Now it runs perfectly and I don't have to run as admin any more.
One nuisance was the "Publisher can't be verified" message whenever I ran Comet. I solved that by clicking on "Tools" in Internet Explorer. Chose Internet Options. Selected the Security tab. Clicked Local Internet. Clicked Sites, then Advanced. I added my XP server to the list of websites for this zone as file://MyServerName. No more "Publisher..." warning message.
Note that I didn't run any Comet install program. That's not necessary anymore. Comet.exe takes care of copying whatever I need.
Actually the process was easier than I expected. I hope you have the same experience.
bb
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.