https://bugs.gpodder.org/show_bug.cgi?id=1489
Andrew Bennett <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #24 from Andrew Bennett <[email protected]> 2012-12-16 08:19:19 GMT --- My new Win7 Pro desktop (~2 months old) just ran into this problem on gPodder launch. I am not sure what triggered it to occur in the first place - I've had gPodder 3.3.0 running for 2 weeks now, and only recently saw this issue. In looking at my path, there are a couple entries for c:\windows\... types of things, and probably another dozen all related to Intel software. It appears to be some sort of Intel licensing / permit / signing stuff. I'll look into it in the near future. Searching the Internet for "Intel icls client" does yield a number of results that seem to indicate this Intel software is causing various problems with other software packages, some Python related. To get gPodder to launch without the R6034 error/dialog was relatively easy workaround: - open a Command Prompt - type: path (enter) Look at your path. It may be complicated, and have a number of entries after "PATH=" that are directories on your system. You'll have to figure out what you need here. You may just need the c:\windows entries like mine: (please adjust as you compare with your path, esp regarding 'wbem' and 'WindowsPowerShell') - type: set path=c:\windows\system32;c:\windows;c:\windows\system32\wbem;c:\windows\system32\WindowsPowerShell\v1.0 (enter) You'll come back to the prompt. Keep this prompt open! Find your gPodder icon. - right click on the icon, choose Properties, then Shortcut - in the command prompt, change directory to the 'Start in' directory, without the double quotes. Something like: cd \Program Files (x86)\gPoddder (enter) now type: gpodder.exe gPodder should launch without the dialog and the R6034 error. How does it work beyond this? I don't know - I just figured this out. But I assume perfectly and as we expect. Note: you'll have to repeat this process each time you need to launch gPodder unless someone comes up with an equivalent way of doing a Unix/Linux shell script in Windows to do all of my above steps. Note 2: It's after midnight local time, so I'm not responsible for errors in the above. As-is! But please correct. thp: Same process might fix bug 1710. -- Configure bugmail: https://bugs.gpodder.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes. _______________________________________________ gPodder-Bugs mailing list [email protected] https://lists.berlios.de/mailman/listinfo/gpodder-bugs
