Propeller Tool Stopped Working

dbpage

I have started getting the following intermittent error on launch: "Access violation at address 004DD86F in module 'Propeller.exe'. Read of address 5F545349" (image attached). The error frequency is increasing to more than 80% of the time. The Propeller Tool works fine after a rare successful launch.

I run Windows 7 Enterprise Service Pack 1 on a HP EliteBook 840.

The Propeller Tool has worked fine for months on this machine, but something changed. Uninstall, restart, re-install don't work, even with a newly downloaded Propeller Tool archive. Various compatibility settings (e.g., Windows XP Service Pack 2 or 3) and running as administrator does not improve the error rate.

Is the problem unique to my machine?

LoopyByteloose

Is this an actual Parallax Propeller Tool or a similar device not made by Parallax?

Some of these USB-to-Serial copy devices are actually shut out by the software drivers provided for Windows by licensed USB device manufacturers.

If it is a genulne Parallax device and nothing else seems to work, contact Parallax Customer Support as they certainly want to know and want to help resolve this.

dbpage

Genuine Parallax Propeller Tool downloaded from parallax.com.

The problem first appeared when I would launch the Propeller Tool by double clicking on a spin file. My workaround was to launch the Propeller Tool, then open a spin file. I now get the error when I launch the Propeller Tool directly instead of a spin file.

A check of my hard drive found no file system or bad sector errors.

I'm not sure about the USB-to-serial comment. I'm just trying to launch the Propeller Tool. I do see some FTDI and Parallax updates to Bus & VCP drivers installed in July. This roughly corresponds to development of the failure to launch.

kwinn

This could be an intermittent memory error of the PC ram or on the hard disk. Or it could be something else. I would suggest uninstalling and reinstalling the FTDI drivers and Propeller Tool to see if that solves the problem. It's a fairly quick and easy first step.

Heater.

There is an outside chance your Prop Tool binary is corrupted. Perhaps download a new one.

Given that the same code has been in use for years and you are the first to report such an error I'm leaning toward the faulty RAM idea as well. Perhaps you can find a RAM test program to check it out.

Perhaps remove your USB drivers and launch the Tool to see what happens.

dbpage

I corrected some registry entries and the tool starts now.

I hesitated to report the issue because the tool has been working for many years. But the operating environment is constantly changing, and the possibility exists for future issues to arise.

In the absence of others reporting this problem, I will consider the matter unique and closed.

Thanks!

Heater.

That sounds very strange.

What registry setting did you tweak?

dbpage

I moved the propeller tool from the hard drive to a removable drive. The registry was still pointing to my hard drive.

I regret bothering the forum for a personal problem.

Phil Pilgrim (PhiPi)

DB,

Never regret "bothering" the forum. That's why we're here. Besides, your experience may resonate with someone else having the same or similar problem.

-Phil

NWCCTV

I'm with kwinn on this one, Quite possibly a memory issue.