Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
I have been using this software for a few months now and just love it!!! I have just (1) problem, every time that I either change users or shutdown my system, I always have to re-name my COMM port because the software tells me that the port is being used by another program. I am not a real "computer guy", but this sounds like a system problem, not a software problem. Does anyone have any idea how I might be able to eliminate this problem??
I think the only way to solve this would be to find out what it is that's using the com port; but I don't really know how you would do that. I take it from what you say that it's not a real com port, but a virtual one for a serial/USB adapter?
What I have to do is go into system, hardware, device manager, ports, COM ports, port settings, advanced. This is were I have to change the port number each time I either turn off my computer (not stand by) or change users. My daughter also has a separate user account on my computer. This sounds like a problem with my PC, not with your software. I just don't know how to fix it.
You could try using Process Explorer to find out which process has the serial port open. Run it, and click on 'Find handle' from the Find menu. Type 'serial' in the box and click 'Search'.
I from time to time get a com port error when I start cumulus. My way around the problem is disconnecting the WX from the cable, start cumulus then plug the WX back in when Cumulus tries to find the station at startup.
Some months ago I had a problem with my toshiba notebook com port (A real one) that I use for programming various pieces of equipment for work. One day I found the com1 not communicating. After much bother the only way I could get it to work was to uninstall the com1 port, scan for hardware changes, it would reinstall and then it would work. If I hibernate the notebook and start back up the com1 port still works until a reboot is performed. Then it's back to remove, rescan etc.
I used this as a workaround as I usually hibernate the notebook and only reboot it weekly or so.
I knew something on startup was grabbing hold of the port.
After months of googling and fiddling, I was printing a doc to acrobat pdf and noticed out of the corner of my eye that it was printing to acrobat on "COM1" I thought "wtf!" So having a look at the ports in acrobat printer properties I saw that in fact it was connected to port COM1, I changed the port to pdf something or other and presto, all is fine, until actobat updates and then the update grabs hold of the com1 port again. Now I know the problem as soon as acrobat updates I check the port settings.
I don't know if this story will help you or not but if it does great, if not, it shows just how a silly, stupid setting can create months of investigation.
Good Luck Tom.
Gerard
PS: I don't know how computer savvy you are so if you need more details post back here, or PM or email me.
