Forum Replies Created
-
Posts
-
Bummed. I rebooted the computer and the problem is back, despite MuvAudio 3’s virtual drivers having been disabled and Total Recorder 8 having been removed. I’ll have to try rolling back to the previous beta, if I still have the installer, and see what happens. I’ll try to post back later today.
Hi Leif,
I *think* that this may have been a conflict with either MuvAudio 3 or with Total Recorder 8 Pro – both install virtual sound drivers. Total Recorder is now gone and MuvAudio’s virtual drivers have been disabled and, as far as I can tell, the problem is gone. I’ll keep you posted,
Thanks,
Mike
PS I’ve been running the betas as you’ve released them, so the previous version was 1.3.01
Just a quick note – BAE under Windows 7 64-bit is consistently sounding awful each time I invoke an application that needs to use it. I have to re-run the wizard to get my sound back (sound crackles and is scratchy). This is new behaviour with the latest beta.
Heh, heh – no apologies required! The important thing, in my opinion, is that the cause is known and a solution available.
Thanks – Breakaway really makes a huge difference to my enjoyment of my system 🙂 and I’d hate to be without it.
Mike
OK – thanks Leif! It happened again last night, after my son had another session with GoogleEarth 5. However, as you note, I had run Process Explorer earlier in the day. What I find odd is that I ran Process Explorer at 8 in the morning and all was well until about 8 pm! Anyway, Process Explorer is now banned from my computer/
Cheers,
Mike
Well… it wasn’t Sysinternals Process Explorer or Process Monitor and it wasn’t Google Earth. I’ve tried running other "stuff" that I ran yesterday that I don’t normally run (Corel PaintShop Pro X2 Ultimate, Magix PhotoDesigner – this has reminded me to uninstall this one!), but no joy. When I came back to the computer, my son was frustrated because GoogleEarth kept taking him to a Google site in Firefox3. All I can think is that some cookie or active-x app was downloaded that WinLicense didn’t like? Of course, as noted above, an AV/AS sweep came up clean and it was a reboot that solved the problem. I wish, now, that I had logged what was active in memory before the reboot.
As predicted, a reboot solved the problem. Annoying thing is that I am still in the dark as to what caused it. Before I realized that it was related to Breakaway (I realized this later, after trying to interact with the systray icon and getting the error again), I "freaked" out a bit and disconnected from my network and ran first a quick scan and then a deep scan with my AV/AS. Nothing showed up, so it must have been one of the other apps that I ran yesterday.
Later today I will try to replicate this issue and isolate the program. I’ll post back.
Odd. This problem began affecting me for the first time last night. I’m running Vista Ultimate 64 and Breakaway 2 – both completely up to date. The only thing I can think of that I did differently yesterday was to run SysInternals Process Explorer and Process Monitor, but neither are in memory anymore. The problem appeared while my son was using GoogleEarth 5, if that helps (though I’ve not had a problem in the past). I run Vipre Antivirus and Antispyware and Windows Firewall.
Very annoying as I can see no way of recovering Breakaway short of rebooting, which I’m about to do now!
I’m running Vista Ultimate 64-bit and there is no taskbar option for Breakaway there, either. AFAICR, 64-bit versions of Windows (don’t know about XP, actually), don’t allow third party taskbar toolbars. I had trouble with this under Vista 32-bit as well (ClipMate 7 and X1 Professional toolbars didn’t work there, and don’t work under 64-bit, either).
Just an update – I had to restart again to update IE 7 and didn’t see the error message on that or two subsequent reboots.
Well, it’s early days yet, but I was seeing the startup error on every system start. I just rebooted after using WinPatrol Plus to set a 50 second delay for Breakaway startup and didn’t see hide nor hair of the error.
I can confirm that I have the same issue under WinXP Pro Sp-3. I run WinPatrol Plus and wonder if delaying having Breakaway startup might help… Will experiment and report back.
