This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

uV2 fails to notice LX51 is done

Using uV2 2.38, C51 7.06, LX51 3.58, on Windows 98SE, all of a sudden uV2 no longer seems to notice when LX51 is done with linking and thus uV2 could proceed with HEX file creation. It just sits there, with a handle to the no longer existing LX51 process in hand, hogs 90+ percent of the CPU, and that's it.

Does anybody have an idea what could be wrong here (besides the tools being a bit dated)? This same setup worked perfectly only until very recently, and I'm not aware of having touched any parts of the setup that could possibly influence this.

Parents Reply Children
No data