If j.dll is not available on the client machine and it's available on the server machine, that's a permissions issue.
But, sure, windows favors thinking about permissions recursively which roughly means the same thing as "cascading". Anyways, if you look at the permissions on irfanview and they are different from the permissions on J or its dlls, that should be a clue. (It does not matter what we think the permissions are, it only matters what the permissions actually are.) -- Raul On Mon, Jan 17, 2022 at 8:38 PM greg heil <[email protected]> wrote: > > i think the client machine > has all the relevant permissions > on the drive/folder > (eg irfanview etc worked) > > jQt failed with the message > (in the CMD shell) of > j.dll not being available > > perhaps there are > some kind of > cascading permissions here? > > ~greg heil > picsrp.github.io > i.tgu.ca/real_cal > > -- > > from: Raul Miller <[email protected]> > to: General forum <[email protected]> > date: Jan 17, 2022, 5:14 PM > subject: Re: [Jgeneral] networked exe's > > >This actually sounds like you are attempting bill lam's scenario -- you are > >attempting to run J on a client machine from a file system on the server > >machine. > > >This means that most of what I had been asking about was irrelevant for your > >situation. > > >It also suggests that the problem is probably a file permissions issue. > > >When you're on the client machine, if you look at properties of the file on > >the server machine, if you go to the security tab -- do you have execute > >permission? > > Thanks, > -- > Raul > . > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
