And if so, running J in this way wouldn't start a *remote* J, but a *local* one. It's only the files that are remote, the computer you're at still has to do all the work.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Monday, January 17th, 2022 at 6:48 PM, bill lam <[email protected]> wrote: > Did you mean you had installed J on a windows network drive such as > > \\somepc\somefolder\ or it mapped as H:\ , such that the physical location > > of the folder is on another pc ? It maybe some windows permission security > > features that disallowed execution of programs on remote pc. > > On Tue, 18 Jan 2022 at 8:37 AM greg heil [email protected] wrote: > > > No > > > > i expect though > > > > that would mean the > > > > client would need > > > > to run a separate instance? > > > > ~greg heil > > > > picsrp.github.io > > > > i.tgu.ca/real_cal > > > > -- > > > > from: Raul Miller [email protected] > > > > reply-to: [email protected] > > > > to: General forum [email protected] > > > > date: Jan 17, 2022, 4:24 PM > > > > subject: Re: [Jgeneral] networked exe's > > > > > I should also ask -- have you done any of J's "Socket" labs? > > > > 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 ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
