Posted by Grant Foraker on July 03, 2012 at 12:23:46: Uploaded files: 2
On Friday had both the Host and Guest running at peak performance. Happy, happy, joy, joy!!!
Sunday afternoon fired up the PC and not even Comet on the Host would work. Realized that I was no longer on the office network and that the Host's office IP was "disconnected". Switched to 127.0.0.1. That got the Host working again. But, the Guest thought 127.0.0.1 was it's IP and couldn't find CometServices on the Host.
VMware had install two "NIC"s with fixed IP's. CometServices saw them and was listening on 11750. So I switched to 192.168.56.1. Host was working but the Guest would try to start but bombed off with startup errors.
I had built my Guest profile on \\ssasd32 (Host) and by sharing out \\ssasd32\comet. Standard procedure and it worked fine at the office. VMware has some strange, non-standard, ways of networking. ssasd32 never shows up in "Network". Instead VMware installs "vmware-host\Shared Folders" (see screen shot) and maps it as drive Z:. Using their sharing wizard, I was able to add Comet into the shared folder.
I dragged a new Comet shortcut over from the share. Notice, because of the blank in the path it's double quoted.
So, shouldn't I use the same path construction in my INI. Doesn't work. See screen shot #2. Nor quoteless.
Only thing that works is to use Z:. It's painfully slow.
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.