Hi Allen,
... you asked in a previous entry to the topic ...
Quote:I wonder if anyone else on the Forum has had this kind of persistent problem and if so, what was done to fix it??
Yep. Several times - with Logic 6,7,8 and once so far with Logic 9. Every time it was something other than Logic that was the problem.
I have an SO2R K3 and Microham setup, with a pair of K3/0s running the shack remotely via Ethernet from an indoor radio shack in the house next to the kitchen. There are lots of USB devices and drivers involved. I use TRX Manager, Telnet, DX Atlas/Band Master (with OmniRig), in conjunction with Logic, all connected into Logic at the same time. If Logic has problems - they would be manifest at VK4IU.
The issue for me has always been something that came as a side effect of something I had installed - usually hardware with drivers of some sort.
The hardest part has always been working out "what" I changed to cause the problems in Logic. In the past, for family reasons, I often went weeks between periods of using Logic, installing almost anything in the periods between using Logic. But that's not necessary. I have been using Logic 9 daily, and a similar problem to yours still occurred with Logic 9 and I had no idea what had changed.
With Logic 9, the problem was my Nokia mobile phone Bluetooth connection. I was using Logic almost daily, and installed the software for my new mobile weeks before. I now know that the common demoninator was "serial port". I only discovered the problem when I wanted to re-configure Logic with Tools, Setup, Misc Ham setup. I would get obsecure .Net windows errors every time I tried. After some time, and help from Dennis, I realised the issue was with serial ports so I would purge the serial port definitions, re-install the serial devices, but the problem would reappear and persisted for months.
To cut a long story short - the problem was in the "enumerated Bluetooth devices" and their relationship to systems serial ports, and created by errors when the mobile phone BlueTooth software was installed - nothing what so ever to do with Logic. Logic just "triggered" the error when it tried to "enumerate the serial devices" using standard calls to Windows. I purged the USB configuration dozens of times, to no result, and finally when I deleted some "orphaned" Bluetooh devices I found in the Win 7 registry, I finally got a solution.
In my experience, there is only one way to go about solving these sorts of issues - simplyify, simplify, simplify.
Obviously, this is easier said than done. Step one is too simplify Logic itself - isolate the part of Logic that is triggering the errors.
You are getting OLE errors - Logic called other systems for information. So, I would remove as much of these "other systems" as I could - the Map or Telnet for example. Use DX Summit instead of Telnet. Stop using the Map, or DX Atlas. When Logic stops reporting errors, a step at a time, start using the tools again - hopefully, the error will appear with one of the steps, and you will know what to do. How long to test beofre the error appears - only you have a feeling for that.
If you got the error "setting the rig" - look at how Logic is driving the rig and simplify it - minimize the things between the rig and Logic. Ask yourself what happens when I do "that" in the spot log.
Work a step at a time, testing between each change.
For others to help in any practical way, you need to descibe your setup in detail.
For me, the most successful approach has been to first eliminate Logic from the problem. To do that, I use another PC, and install a minimal copy of Windows, then install Logic from the CD. I restore the log data, and, a step at a time, reconfigure Logic, testing as I go. One should get no problems, unless Logic is the problem. If no problems occur - I return to the original PC and simplify it. If I get problems with the "simpler PC installation and Logic" I know Dennis can help with Logic.
A second PC is easier than you think. If you download and install a copy of Oracles's VirtualBox (its free!) you can create as many "virtual PCs" as you want. Virtualbox allows you to run "virtual PCs", on top of your exisiting PC. Clearly, the "virtual PC" will be a little slow if your primary PC is too old. Memory is the key. If you have at least a dual core PC, with at least 2 GB of RAM you are "good to go" with VirtualBox. It is simple to do, and is just like using a "real PC". Look for a "Windows license" on the sticker of any old PC - XP (any version), Vista (any version), or Win7. You need a matching Windows installation CD - beg or borrow one. Your family or friends may have a "key" they no longer use. The value is in the key not the CD.
Most of us have owned several PCs over the years. Those old PCs and their licenses now have a use. Using VirtualBox, my old PCs live again as "virtual PCs" running versions of Windows and Linux on my "new PC". Yep - I too forgot to write the license key down before I threw out the old PC.
Mostly, it does not matter what version of Windows, so long as it is XP or later. Most of the change in Vista, Win7 and Win8 has been "cosmetic". Vista is great, most people hate it, and so a good market exsts in copies of Vista.
One of my "born again PCs" runs an original copy of Logic 9, with only the updates supplied by Dennis. I restore my Log into it, and use it as the "test bed" when I get errors running Logic.
So far, my score is Logic ZERO, Windows "a few".
Peter VK4IU
Peter VK4IU
You can help by posting images of
any errors and including your
Logic version.