[Jprogramming] What makes a Windows installation read-only?

[Henry Rich]

Yeah.  I just added that.

Henry Rich

On 5/3/2020 4:23 PM, David Mitchell wrote:
> Henry,
>
> This is what the AIO install says:
>
> https://code.jsoftware.com/wiki/System/Installation/J901/AIO
>
> You will be asked to choose between an installation for all users or 
> 'just for me'.
>
> Installing 'just for me' produces an unshared installation (by default 
> to your user directory C:\Users\Fred) and does not require admin 
> privilege, either during installation or during later upgrades.
>
> A shared installation (by default to C:\Program Files) requires admin 
> privilege, both for the initial installation and for subsequent 
> upgrade to addons. That is, you will have to Run as Administrator any 
> time you want to upgrade J packages if you install into a shared 
> directory.
>
> David Mitchell
>
> On 5/3/2020 12:17, Henry Rich wrote:
>> I point the users to the installation page.  Can you give me a 
>> sentence to add to my instructions so they won't encounter this problem?
>>
>> Henry Rich
>>
>> On 5/3/2020 12:15 PM, Norman Drinkwater wrote:
>>> If they are an administrator on the computer, they can use the 
>>> all-in-one
>>> installer to install for all users. Then J runs with admin rights and
>>> pacman will work fine. If they aren't an administrator, they can only
>>> install as a user. The current behavior conforms to windows guidelines,
>>> though I understand that it's inconvenient.
>>>
>>> On Sun, May 3, 2020 at 10:33 AM Henry Rich <henryhrich at gmail.com> 
>>> wrote:
>>>
>>>> I have a J application, distributed as a Addon.  When it starts, it 
>>>> runs
>>>> Pacman to check for updates.
>>>>
>>>> A couple of users report that the catalog is read-only and thus they
>>>> can't run Pacman without administrative rights.  As they are Windows
>>>> users, this means that they have to Run as Administrator. This is
>>>> undesirable.
>>>>
>>>> Does anyone know what causes this state of affairs?  Is it 
>>>> something in
>>>> the way they installed J, or how they have their Windows system set 
>>>> up?
>>>> I don't think it's an antivirus issue.
>>>>
>>>> And is there a workaround for them to give J the rights to manage its
>>>> stuff?
>>>>
>>>> Henry Rich
>>>>
>>>> -- 
>>>> This email has been checked for viruses by AVG.
>>>> https://www.avg.com
>>>>
>>>> ----------------------------------------------------------------------
>>>> For information about J forums see http://www.jsoftware.com/forums.htm
>>>>
>>> ----------------------------------------------------------------------
>>> For information about J forums see http://www.jsoftware.com/forums.htm
>>
>>
> ----------------------------------------------------------------------
> For information about J forums see http://www.jsoftware.com/forums.htm