Jump to content
Sign in to follow this  
IanM

V6.96 Breaks Existing Mplab Integration

Recommended Posts

BUG:

The change in the Sourceboost toolsuite exe file names (V6.96 replaced the first dot with an underscore) upsets pre-existing MPLAB integration. (not surprising really). Unfortunately the stub exes with the old names that warn of the changed names use a GUI dialog box with an OK button which MPLAB suppresses so all one gets is a chord sound and a hung MPLAB!

 

RESOLUTION:

The procedure in the Sourceboost language manuals 'Setting the MPLAB Language Tool Locations' resolves the problem but is rather tedious.

 

If one is happy using Regedit, the key 'HKEY_CURRENT_USER\Software\Microchip\MPLAB IDE\Tool Locations' can be exported to a file, then a text editor may be used to replace as follows:

 

.pic.exe -> _pic.exe

.pic16.exe -> _pic16.exe

.pic18.exe -> _pic18.exe

 

then after checking NO 3rd party toolsuits were modified, it may be re-imported. MPLAB will then use the new sourceboost exes with no further trouble. N.B. the reg file will be full of GUIDs that *must* match those of the toolsuites so *DONT* copy it to another PC!

 

SUGGESTED IMPROVEMENT:

To make the warning about the changed exe file name visible in MPLAB, the stub exes need fixing so that if a parameter other than /? is passed to them, they report to STDOUT, *not* to a dialog box and return immediately with an appropriate errorlevel.

Share this post


Link to post
Share on other sites
BUG:

The change in the Sourceboost toolsuite exe file names (V6.96 replaced the first dot with an underscore) upsets pre-existing MPLAB integration. (not surprising really). Unfortunately the stub exes with the old names that warn of the changed names use a GUI dialog box with an OK button which MPLAB suppresses so all one gets is a chord sound and a hung MPLAB!

 

RESOLUTION:

The procedure in the Sourceboost language manuals 'Setting the MPLAB Language Tool Locations' resolves the problem but is rather tedious.

 

If one is happy using Regedit, the key 'HKEY_CURRENT_USER\Software\Microchip\MPLAB IDE\Tool Locations' can be exported to a file, then a text editor may be used to replace as follows:

 

.pic.exe -> _pic.exe

.pic16.exe -> _pic16.exe

.pic18.exe -> _pic18.exe

 

then after checking NO 3rd party toolsuits were modified, it may be re-imported. MPLAB will then use the new sourceboost exes with no further trouble. N.B. the reg file will be full of GUIDs that *must* match those of the toolsuites so *DONT* copy it to another PC!

 

SUGGESTED IMPROVEMENT:

To make the warning about the changed exe file name visible in MPLAB, the stub exes need fixing so that if a parameter other than /? is passed to them, they report to STDOUT, *not* to a dialog box and return immediately with an appropriate errorlevel.

 

Thanks for the suggestion. It sounds like this registry change should be done by SourceBoost installer. We'll investigate and if looks good add this feature into next SourceBoost release.

 

Regards,

Pavel

Share this post


Link to post
Share on other sites
Thanks for the suggestion. It sounds like this registry change should be done by SourceBoost installer. We'll investigate and if looks good add this feature into next SourceBoost release.

I suggest being *extremely* careful about rolling it into the installer. Modifying undocumented MPLAB registry entries is fairly risky and liable to break if Microchip make any significant changes to MPLAB. Also this setting is per user so if the installer is run as Administrator then another user name is actually used to run MPLAB, the wrong user's settings would have been changed.

Perhaps a separate utility with as many safety checks as you can come up with would be better.

Share this post


Link to post
Share on other sites

Join the conversation

You are posting as a guest. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  

×
×
  • Create New...