Hi Edwin,
Further to your kind assistance, I've tried to install the JMS in a Production Server but alas I've been struggling to repaet what you've done in a matter of seconds over our Test system.
I've beeen looking around and perhaps it could be of help if the system would tell which first files/ directory falls into error. I m not confortable about chmod 777 everything...
Just a though.
Thaks anyway,
NonoFr

I had similar problems and ended up just ftp'ing my local host image with patches applied...and it's been smooth sailing from there...hope that helps

When there is a permission error, unfortunatelly, the standard joomla low level API does not provide additional informtation.
This is probably for security reason.
Therefore JMS does not received the information concerning the origin of the problem.
The only solution in this case if you want to have a better report of the reason would be to modify the standard joomla "JFolder" or "JFile" class or also the one that "unzip" the files to add traces.

It is not in the objective of JMS to modify Joomla when this is not absolutelly required and here mainly when this is in development.
We already tried to see if it was possible to increase the level of trace of joomla to report more info but we have not found any possibility yet.

If you are losing time to search the reason, we also have a billable support that you can use and we will add traces in the joomla core to identify the reason.
Traces that we will remove just after the diagnosis.