Larry Young schrieb: > Clearly, I had modified my (2004) msp430-bsl.exe, and I apologize for my > forgetfulness. However, after I downloaded the official msp430-bsl.exe > from the SourceForge archive of November, 2004, the same spurious "Write > InfoSegs" programming step occurs. The msp430-bsl.exe executable itself > must be invoking another module from somewhere on my computer. I would > expect such a secondary effect if running as a Python script, but does > the .exe version also depend on some other modules?
yes, unfortunately. the python.dll finds a python installation of the same version through the registry and depending on search order it might pick up a local version instead of the bundled one :/ chris
