MPLab X v2.05 cannot read ccs Plug-in

[pieter]

I can not get MPLab X V2.05 to show the ccs MPLabX plug-in, So many hours wasted on this.
Installed, uninstalled and re-installed MPLabX v2.05
Installed ccs MPLab X plug-in in default MPLabX dir.
"Available plugins" show 0 plugins, "Reload Catalog" gives proxy time out.

When I manually try to read "downloaded plug-ins", MPLabX looks for a .nbm file... the ccs plug-in installs something else.

Any ideas someone please?

[Ttelmah]

You are running the 'install', 'as administrator'. This is _required_ for it to work.
Just 'being' an administrator, is not the same. You must right click on the 'install MPLAB plug-in', and select 'run as administrator'. It won't register properly otherwise.

[pieter]

No luck, I already tried every rule in the book, worked through every ccs and microchip document.

[Ttelmah]

Odd.
I just installed MPLAB 2.05, on a laptop.
Then installed the plug in. Running as administrator.
Then went to the plug-in entry inside MPLAB, which immediately said that the plug in was 1.46, and 1.56 was available, and upgraded automatically (interesting since this was the latest plug in from the CCS download page).
MPLAB, now shows CCS as available, and allows me to select it as the compiler.
Nothing special done, except 'clean' install, from scratch.

Best Wishes

[gpsmikey]

Having just tripped over a similar issue with my registration files, my suspicious nature here says to check for stuff down in the "virtual store" - it seems once windows puts something there, it looks there first so even when you KNOW you have the right files where they are supposed to be, the wrong ones got put in the "virtual store" and are screwing it all up. I think one of the times that happens is if you are only running as an admin, but the program does not have admin rights when it runs (there seems to be a number of trap doors that can get you with this creature). Look down under your account in "C:\Users\mikey\AppData\Local\VirtualStore" (change the user name obviously).

mikey
_________________
mikey
-- you can't have too many gadgets or too much disk space !
old engineering saying: 1+1 = 3 for sufficiently large values of 1 or small values of 3

[Ttelmah]

I'd agree with this.

The classic on this is 'being' administrator, but not running as administrator.

When you run a program (even if you are administrator), the 'rights' are those defined by the program's settings, which if a file is downloaded are automatically 'user' rights. This is the point about 'run as administrator', which overrides this. However problem is that as Gpsmikey says, if the file has been run with the wrong permissions, it gets written into the VirtualStore, with these lower rights.....

Quite a lot of stuff runs into problems with this....

[pieter]

Much appreciated, but nothing there.
I have uninstalled MPLabX, deleted existing folders and done a clean installation. All with "Run as Administrator". Still the same problem.

I will install this now on another laptop to see what happens.

[Ttelmah]

It is not MPLABX that you have to 'run as administrator', but the plug-in installer.

[pieter]

Installed MPLab X V2.05 on a laptop
Run as Administrator installed CCS plug-in

The same problem.
Tools, Plugins, shows 26 plugins installed.
Tools, Available Plugins, where CCS should now show, is nothing.

[gpsmikey]

One question I have to ask since I don't see it mentioned - are we all talking the same flavor of windows ? I was talking win7/64 (although I have not installed Mplabx on it). What versions are involved here - sometimes we find describing the answer to a problem we are looking different directions

mikey
_________________
mikey
-- you can't have too many gadgets or too much disk space !
old engineering saying: 1+1 = 3 for sufficiently large values of 1 or small values of 3

[pieter]

Windows 7 Pro, 32bit

[Ttelmah]

The laptop I used was W7 Pro/32. An SSD based 'clean' machine I use for testing. My main machine is W7 Ultimate/64, and already has this setup on it, but this has been upgraded to this point, rather than a clean install.

Obvious thing would be that there is something 'in common', but 'different' about the machines. For example a specific anti-virus package, or a download that has been corrupted.

Does the poster get the question from Windows about whether they should trust these installs?. Also did he re-download, or is he using the same downloaded copy?. Both of mine were 'fresh' downloads, done when I tested.

Best Wishes