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

Ds-5 Eclipse cannot read environment file env.ini

I have installed ARM DS-5 on my PC (Windows 10 64-bi); When launching Eclipse I got an error message:

Could not read environment file C:...\ds5\win_64\r5p0-27rel0\sw\info\env.ini": Operation not permitted

I have Full Control of this env.ini file and can open it with notepad to read/write; So not really a file permission issue.

Any idea why Eclipse cannot start?

Parents
  • Hello Zhe,

    After a bit of investigation on my side, I think I can see the problem. I suspect you don't have the "Personal" registry key set in "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders". Your colleagues probably do have this set, which is why their DS-5 launches without issue. I wouldn't recommend setting registry keys yourself though - instead, if, prior to launching DS-5 from the command prompt, you set the environment variable "MY_DOCS" to point to your "My Documents" folder, I believe DS-5 should launch successfully.

    Let me know if that works.

    There are a couple of issues on our side here: 1) we're using a now-deprecated way of deriving My Documents, 2) we are reporting the wrong error message. I will endeavour to get those fixed.

    Best regards,
    Jonathan

Reply
  • Hello Zhe,

    After a bit of investigation on my side, I think I can see the problem. I suspect you don't have the "Personal" registry key set in "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders". Your colleagues probably do have this set, which is why their DS-5 launches without issue. I wouldn't recommend setting registry keys yourself though - instead, if, prior to launching DS-5 from the command prompt, you set the environment variable "MY_DOCS" to point to your "My Documents" folder, I believe DS-5 should launch successfully.

    Let me know if that works.

    There are a couple of issues on our side here: 1) we're using a now-deprecated way of deriving My Documents, 2) we are reporting the wrong error message. I will endeavour to get those fixed.

    Best regards,
    Jonathan

Children