plugin installation into Delphi 10 Seattle x86 failed...

delphi package - automated exception handling

plugin installation into Delphi 10 Seattle x86 failed...

Postby MarkusD » Wed Jan 04, 2017 9:54 am

Hi,

double clicking on for example "ActiveControl.mep" gives me an error message:
Code: Select all
plugin installation into BCB 10 Seattle failed...
plugin installation into Delphi 10 Seattle x86 failed...
plugin installation into Delphi 10 Seattle x64 failed...

There are no files in:
Code: Select all
C:\Program Files (x86)\madCollection\Plugins\win32
C:\Program Files (x86)\madCollection\Plugins\win64

Theses above folders are empty.

But, I do have files:
Code: Select all
C:\Users\[User]\AppData\Local\VirtualStore\Program Files (x86)\madCollection\Plugins\win32\ActiveControl.pas
C:\Users\[User]\AppData\Local\VirtualStore\Program Files (x86)\madCollection\Plugins\win32\ActiveControl230.dpk
C:\Users\[User]\AppData\Local\VirtualStore\Program Files (x86)\madCollection\Plugins\win32\LocaleInfo.pas
C:\Users\[User]\AppData\Local\VirtualStore\Program Files (x86)\madCollection\Plugins\win32\LocaleInfo230.dpk
C:\Users\[User]\AppData\Local\VirtualStore\Program Files (x86)\madCollection\Plugins\win32\MemoryInfo.pas
C:\Users\[User]\AppData\Local\VirtualStore\Program Files (x86)\madCollection\Plugins\win32\MemoryInfo230.dpk
C:\Users\[User]\AppData\Local\VirtualStore\Program Files (x86)\madCollection\Plugins\win32\SystemInfo.pas
C:\Users\[User]\AppData\Local\VirtualStore\Program Files (x86)\madCollection\Plugins\win32\SystemInfo230.dpk

Code: Select all
C:\Users\[User]\AppData\Local\VirtualStore\Program Files (x86)\madCollection\Plugins\win64\ActiveControl.pas
C:\Users\[User]\AppData\Local\VirtualStore\Program Files (x86)\madCollection\Plugins\win64\ActiveControl230.dpk
C:\Users\[User]\AppData\Local\VirtualStore\Program Files (x86)\madCollection\Plugins\win64\LocaleInfo.pas
C:\Users\[User]\AppData\Local\VirtualStore\Program Files (x86)\madCollection\Plugins\win64\LocaleInfo230.dpk
C:\Users\[User]\AppData\Local\VirtualStore\Program Files (x86)\madCollection\Plugins\win64\MemoryInfo.pas
C:\Users\[User]\AppData\Local\VirtualStore\Program Files (x86)\madCollection\Plugins\win64\MemoryInfo230.dpk
C:\Users\[User]\AppData\Local\VirtualStore\Program Files (x86)\madCollection\Plugins\win64\SystemInfo.pas
C:\Users\[User]\AppData\Local\VirtualStore\Program Files (x86)\madCollection\Plugins\win64\SystemInfo230.dpk

My question is, how to I get the plugins:
Code: Select all
ActiveControl.mep
LocaleInfo.mep
MemoryInfo.mep
SystemInfo.mep

up an running? Where do these plugins show up? Do I have to do anything else after the installation of the plugins? The info at http://www.madshi.net/madExceptPlugins.htm is not that clear about this.

Thanks in advance, Markus
MarkusD
 
Posts: 9
Joined: Wed Jan 04, 2017 9:32 am

Re: plugin installation into Delphi 10 Seattle x86 failed...

Postby madshi » Fri Jan 06, 2017 6:12 pm

Ah, that's probably my fault. Newer OSs are quite picky about where programs may write to. In your case you've installed madCollection into the Program Files directory, which is just fine. But madExcept is not really allowed to write into that directory, so the plugin directory is not writable. As a result the OS redirects the write attemps to your Users folder. Which makes sense, but which means that things get screwed up and don't properly work, unfortunately.

I'll put this on my to do list to investigate/change. Probably I need to move the plugin folder to the Users folder somehow. Unfortunately that means the files get scattered all over your harddisk which I really hate. But that's the way Microsoft wants to have it, apparently... :(

As a temporary workaround, I suppose you could cleanup the Users folder and then add write access to the Plugin folder to your user (or even "Everyone"). Once madExcept is allowed to write to the Plugins folder, everything will (hopefully) start to work as expected.
madshi
Site Admin
 
Posts: 9411
Joined: Sun Mar 21, 2004 5:25 pm

Re: plugin installation into Delphi 10 Seattle x86 failed...

Postby davornik » Sat Jan 07, 2017 7:19 pm

Hm, i have this "problem" also. Folder where I install all my components is not in Program Files, but in ex. C:\Embarcadero_components\. I have some other version of Delphi installed and tested but only for Seattle it says "failed".

Link:
https://postimg.org/image/j0so0iyux/

Direct link:
https://s28.postimg.org/mx5zwijul/mad_Except_plugin_failed.jpg
davornik
 
Posts: 2
Joined: Fri Feb 28, 2014 12:37 pm

Re: plugin installation into Delphi 10 Seattle x86 failed...

Postby MarkusD » Mon Jan 09, 2017 9:47 am

madshi wrote:Ah, that's probably my fault. Newer OSs are quite picky about where programs may write to. In your case you've installed madCollection into the Program Files directory, which is just fine. But madExcept is not really allowed to write into that directory, so the plugin directory is not writable. As a result the OS redirects the write attemps to your Users folder. Which makes sense, but which means that things get screwed up and don't properly work, unfortunately.

Yes, applications are not allowed to write into the "C:\Program Files (x86)\" folder, but this is since Windows Vista. Quit some time ago. :confused:

madshi wrote:I'll put this on my to do list to investigate/change. Probably I need to move the plugin folder to the Users folder somehow. Unfortunately that means the files get scattered all over your harddisk which I really hate. But that's the way Microsoft wants to have it, apparently... :(

That would be fine, if you can fix it. And yes, I agree, things get scattered around. But on the other side, user files shouldn't have ever stored in the "C:\Program Files (x86)\" folder anyway. But until Windows XP it was possible and easy to do, and we also used that folder to store user data in our software. But when we first used our software with CITRIX things went very ugly. And beginning with Vista we had to redesign some parts of our software to make sure no user file will ever end up in "C:\Program Files (x86)\". That's life. :wink:

madshi wrote:As a temporary workaround, I suppose you could cleanup the Users folder and then add write access to the Plugin folder to your user (or even "Everyone"). Once madExcept is allowed to write to the Plugins folder, everything will (hopefully) start to work as expected.

I tried that, and I still get the same error messages after double clicking the .mep files. But they are stored in the "C:\Program Files (x86)\madCollection\Plugins\win32" and "C:\Program Files (x86)\madCollection\Plugins\win64" now and there are no files under "C:\Users\[User]\AppData\Local\VirtualStore" anymore. When I force an exception in our applications I don't see any difference in the error report. Once again the question, where do I see the impact of the installed .mep files? Should I see some difference in the "madExcept 4.0.16 settings" dialog in the Delphi IDE?

TIA, Markus
MarkusD
 
Posts: 9
Joined: Wed Jan 04, 2017 9:32 am

Re: plugin installation into Delphi 10 Seattle x86 failed...

Postby madshi » Sat Mar 11, 2017 10:14 am

Sorry for very late reply.

I've just tries this again on my PC, and it works just fine for all Delphi versions installed on my PC, including Delphi 10 Seattle.

After installing the plugin, the plugin should be visible on this settings page:

http://help.madshi.net/madExceptSettings8.htm

You still need to "check" the plugin there to enable it for your project, and then recompile. It works for me, but I do have madExcept installed in a folder where the user has write access to.
madshi
Site Admin
 
Posts: 9411
Joined: Sun Mar 21, 2004 5:25 pm

Re: plugin installation into Delphi 10 Seattle x86 failed...

Postby MarkusD » Thu Mar 23, 2017 8:44 am

madshi wrote:...
You still need to "check" the plugin there to enable it for your project, and then recompile. It works for me, but I do have madExcept installed in a folder where the user has write access to.

I think as a developer you should not expect that a user installs a software in a folder where the user has write access to, after the installation. This is not the default behaviour in Windows. In my opinion you should change the way files are stored. User files should go to "CSIDL_APPDATA\[Application]" or "CSIDL_PERSONAL[Application]". This would solve the problem.

just my 2 cents.

TIA, Markus
MarkusD
 
Posts: 9
Joined: Wed Jan 04, 2017 9:32 am


Return to madExcept

Who is online

Users browsing this forum: No registered users and 6 guests