Compiler update

[Gabriel]

Hi all,

I've just purchased updates for both my PCM and PCH.
If I have any issues with the installation, how do I roll back?
(Ive never had to do it)

I have all the CRG files from previous versions and update .exe files.

How is 5.078 working out for you all?

G.
_________________
CCS PCM 5.078 & CCS PCH 5.093

[newguy]

You don't necessarily roll back, just install into a slightly different directory. I have C:\Program Files (x86)\PICC4099 and PICC5073 and PICC5074, etc. I also rename the shortcut to the compiler so that it also includes the version number. Your new license files will work with any earlier version of the compiler.

As far as how 5.078 is working out, I haven't encountered a bug yet. But that said I think Windows pushed an update lately that has partially borked things as over the weekend and on Monday at work I had several instances of the IDE hanging (something about an access violation). All triggered by a mistake in code I was trying to compile. When the IDE attempted to invoke or print the error(s), that's when it would hang. This was with 5.078 and 5.074, which I consider to be stable and have been using for ~8 or 9 months with absolutely no issues prior to this past weekend. ...That's why I suspect that MS has something to do with it.

[Gabriel]

So... use the old installer.exe to reinstall ccs on a different folder and then run the update.exe on that new folder?
Is that correct?
_________________
CCS PCM 5.078 & CCS PCH 5.093

[newguy]

Almost.
1) Uninstall old version, providing that you haven't placed any code into the CCS install directory.
2) Reinstall old version, but instead of accepting the install path, hit browse and rename \PICC to \PICC5xxx where 5xxx is your old version number.
3) Point the installation to wherever you place your new license files.
4) Rename the shortcut the installer places on your desktop to "PIC C 5.xxx"
5) Install any additional compiler versions you'd like, but install each in its own directory, \PICC5073, \PICC5077, \PICC5078 for example. Be sure to rename each of the new shortcuts to include the version number. These subsequent installations will automatically find the license files from the original installation in step 2.

I have 4.099, 4.141, 5.073, 5.074, 5.077, and 5.078 installed on my machine. At home I actually have 3.236 and 3.249 installed as well. At any rate the old versions 4 are for some pretty old projects that were originally developed using them. I haven't had time to try to compile those old projects using a newer version PLUS I'm kind of scared to change over given the number of units in the field that are bug free. "If it's not broken, don't touch it." I can definitely uninstall 5.073 and 5.077, but I have to confirm that code compiled using 5.074 is okay when compiled with 5.078. If that doesn't introduce any odd behaviour, then I can safely remove 5.074. I just haven't had time to do all this yet.

[Ttelmah]

and.

Rename the ccsdownload.exe file in the directory something like ccsdownload.not. This then stops the compiler automatically checking for updates.
In each new program, include in your comments the compiler version used. If you update, note this in the comments.
When you archive a project, include the compiler used in the archive. This way you can go back years later and rebuild the project with the same compiler and includes.

[PCM programmer]

You guys are referring to the IDE version of the compiler. I believe he
has the command line versions. Look at his sig line.

He needs to tell us what he recently bought, IDE or command line ?

[Gabriel]

Command line with MPLAB 8.92
_________________
CCS PCM 5.078 & CCS PCH 5.093

[PCM programmer]

What version of Windows do you have ?

[Gabriel]

Win 7.
_________________
CCS PCM 5.078 & CCS PCH 5.093

[PCM programmer]

The main thing is to rename "update.exe" to pch5078.exe and
pcm5078.exe after you download each one. Then save them in folder.