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

Unable to use the uV4 Beta

I have just downloaded the uVision4 Beta and I have been so far unable to use it with a uV3 project due to a consistent crash. Note that I did not remove the uVision3 installation.

I am using Windows XP Professional, SP2.

The steps to reproduce the problem are the following:

1. Start uV4
2. Open the .uv3 project through Project > OpenProject... (and selecting 'Previous project files' on the drop-down list)

And the results:

1. An error message pops up with the following information:

"uVision - Path for Toolset undefined

'C:\Keil\TOOLS.INI' does not contain a tool path

You have selected a device where no toolchain has been installed."

I click on 'OK' to close the dialog.

2. Since there is no toolchain selected, nor can the project be compiled neither can a device be selected from the Device database under the 'Target Options'.

3. I then proceed to open the 'Components, Environment and Books' dialog in order to have a look whether the
'C:\Keil\TOOLS.INI' '(which is valid and present in the system).

4. There I try to see whether I can see more information about TOOLS.INI.

5. When clicking on the 'Folders/Extensions' tab on the 'Components, Environment and Books', uVision4 crashes with a standard Windows crash dialog without further information than 'uVision IDE has encountered a problem and needs to be closed' (note that this is an approximate translation from the original German message).

Is this a known bug? Is there a workaround?

Many thanks in advance.

Parents
  • Hi,

    In the mean time I have located the actual entry in the uvopt file produced by uVision4 that causes the problem. The last line is the actual culprit. I just hope it helps.

    Regards, Filip

            <SetRegEntry>
              <Number>0</Number>
              <Key>DLGTCYG</Key>
              <Name>8‘|ÿÿÿÿ2‘|«‘|ë‘|</Name>
    

Reply
  • Hi,

    In the mean time I have located the actual entry in the uvopt file produced by uVision4 that causes the problem. The last line is the actual culprit. I just hope it helps.

    Regards, Filip

            <SetRegEntry>
              <Number>0</Number>
              <Key>DLGTCYG</Key>
              <Name>8‘|ÿÿÿÿ2‘|«‘|ë‘|</Name>
    

Children