We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
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.
Hi David,
This problem sounds like you have installed the uVision4 Beta 1 upgrade to a different base folder than your toolchain.
The uVision 4 Beta 1 installer does not contain the toolchain, only uVision4 itself, therefore it needs to be installed on top of an existing uVision3 installation.
Firstly, make sure you have the latest version of your toolchain by starting uVision3 and clicking 'Help -> Check for Updates...' or visiting http://www.keil.com/update/
Next, uninstall uVision4 and re-install it to the same base folder as your up-to-date uVision3 installation (eg C:\Keil).
You should then be able to successfully load and compile your project.
P.S. I have verified that the crash you have seen when missing the tools.ini is a problem. This will be rectified as soon as possible. Thanks for your feedback.
Richard
Hi Richard,
thanks for the prompt reply.
I simply wanted to confirm that installing the uV4 Beta to the same base folder as my current uVision3 installation solved the problem.
Regards, David.
Hi,
I installed the beta as well and got the same error message about the missing TOOLS.INI. There is an easy solution: copy the TOOLS.INI file from your original uVision directory and it works.
There is another problem though that renders uVision4 unusable.
Try the following procedure: - Open uVision4 - Open an earlier project (uVision2 project file) - Close the project => you get a message the file will stored in the new format. Confirm that. - Then re-open the earlier project.
You then get an error message something went wrong when opening the new project file. The error details are:
Line 143 Fatal message: invalid character 0x7
After that the project content is incomplete and it is no longer possible to build it.
Unfortunate: I was really hoping that uVision4 would work better under VISTA then uVision3 because that one keeps crashing when certain editor options are activated.
Regards, Filip
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.
<SetRegEntry> <Number>0</Number> <Key>DLGTCYG</Key> <Name>8‘|ÿÿÿÿ2‘|«‘|ë‘|</Name>
"The uVision 4 Beta 1 installer does not contain the toolchain, only uVision4 itself, therefore it needs to be installed on top of an existing uVision3 installation."
The very nature of beta software means that it is essential to be able to install it in a safe place well away from the real work - and to be able to retain the existing tools undisturbed!
Hi Andy,
The uVision4 Beta installation will not in any way affect your current uVision3 installation. It only uses the toolchain DLLs, and will not damage the existing installation.
If you are still concerned about the possibility, then please wait for the official release.
Regards, Richard
Richard, come on! Do you think I'm going to risk ruining my functioning work environment to test your beta software? Given the comments here (one of them was posted by a colleague of mine!), well, I have better ways to commit suicide... :-)
But then what's the point of doing a beta release?!
Surely, the whole point of doing a beta release is to get feedback from real users? But those are precisely the users that will have real work at risk if it all goes terribly wrong...!
Hi Filip,
Please could you report this case to support.intl@keil.com
Thanks, Richard
How about setting up a specific forum for the beta?
Preferably one where issues like this could be tracked...
Here is a case where the experts should remember their own advice, "Please read the manual". If you install per the instructions you will have no problems opening either uV3 or uV4. You will have no problems opening a project common to either uV3 or uV4. I am running Win XP Pro SP3 and Vista Home Premimum. I have tried uV4 with MDK 3.4, PK51 8.17a and PK166 very old version without problems. I'm not totally sold on some of the new features but that's just my bias. Remember a bug just might be an undocumented feature ;-). Also, you might be forgetting the ability to 'RESTORE' from both Win XP or Vista to cover your.... Bradford