PropIDE went postal on me!!!
I don't know what happened. Last night everything worked fine, has for weeks.
This morning I get an access violation of some *.*api.dll and it locks up the IDE.
Nothing but Taskman could shut it down.
I performed an unistall and reinstalled Ver1.o again and the same thing.
I guess I'm looking at reloading my operating system now.
Has anybody got a been-there-done-that they would like to share?
This morning I get an access violation of some *.*api.dll and it locks up the IDE.
Nothing but Taskman could shut it down.
I performed an unistall and reinstalled Ver1.o again and the same thing.
I guess I'm looking at reloading my operating system now.
Has anybody got a been-there-done-that they would like to share?
Comments
Now I can no longer run 1.0 without problems.
BUT!!! There is hope.
Version 1.02 works fine without any problems for me.
I downloaded it off of this forum packed with the Text-To-Speech spin download.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
NerdMaster
For
Life
What Thread is it in?
Download the first file which is about 800k.
Version 1.02 should be in there.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Paul Baker
Propeller Applications Engineer
Parallax, Inc.
I can't move my mouse pointer over the IDE app window without a half dozen access violations and !@#$%^.dll's puking all over me.
Help!
I've tried removing and reinstalling, it does no good.
What did you guys do to pi$$ off Bill Gates that bad ;^)
FYI, my OS at home is XP Home Edition, Service Pack I.
My work IDE app is ok, there I run XP Professional with an IT dept to watch over me.
Thanks, Tom Perkins
Post Edited (tperkins) : 1/8/2007 9:20:19 PM GMT
Try version 1.02 on your home computer.
I had the same problem and once I tried the 1.02 beta the bug went away.
You can download it at the address I posted above.
Once at home, I tried again to run the IDE from the desktop icon, same result.
I uninstalled and reinstalled the software, booting the machine after each action.
Same result.
I wondered if getting into the software a different way would do anything, so I right clicked on a Spin file and opened the IDE from there.
It has run okay since then (about 7:10pm).
I can't figure it.
Yours, Thank you, Tom Perkins
The offending module is “SHLWAP.dll” and substituting v1.02
is the only way or getting back on the air.
Anyway, I compiled a couple programs downloaded to prop and EEPROM, Everything seems fine know!
What kind of system are you guys running?
I've got a rebuilt Dell using an asus Motherboard, running·Windows XP pro.
tperkins,
I ran it on XP home for a while and had no problems.
If the IDE version is reported correctly in Help>About, I still have v1.0 running.
It seemed to recover after I right clicked on a Spin file and selected Open, and then the IDE ran ok and I can run it from the Icon since then.
Of the many strange things I've seen electronics do, this is in the top ten for an app to die like that on many OS's and platforms on the same day.
And it's not like there are that many people running the Prop IDE, what, are there 1,000 yet?
I think something also took out my Norton Antivirus app, because it needed an un/reinstall last night. It kept on saying I needed a license...
...when I was looking at the license/keycode in my hand.
Some really bad bug get out on 1/7/07?
Yours, Tom Perkins
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Check out my game page: http://maze3d.no-ip.org (Swedish only, sorry.)
I don't think it was a bug of that type.
My Prop IDE v1.00 died about a month ago.
I just think version 1.0 of the propeller tool has a glitch in it that saves a weird value somewhere and crashes the program on bootup.
V1.02 seems to be corrected somehow.
I agree. I was being ficious when I mentioned Y2K. The oddity in my situation was merely the fact that it ran fine for such a time before giving me any heartburn. All's Well That Ends Well. Thanks again for the tip.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Paul Baker
Propeller Applications Engineer
Parallax, Inc.
"object info" window (when you hit F8) isn't the right size if you have selected a larger font?
Maybe make this window resizable, at least? It's pretty painful to use on my laptop at the
moment.