I agree with Raul that antivirus is usually the culprit when users complained your software stopped working this morning, it worked just fine yesterday, and they had not changed anything. All other programs in the computers work fine except your d*mn program.
More specifically, J can execute arbitrary socket calls and some antivirus/firewall would like to block such programs. You can confirm J803 itself had been corrupted or not, by performing a binary comparison with files from a fresh install. On Jan 10, 2015 5:08 AM, "Raul Miller" <[email protected]> wrote: > That sounds to me like either a malware infection or unreliable > hardware. Or maybe it's just Windows. That said, it could be the > actions of some user of the machine(s). > > I'm not sure how I'd isolate any of those kinds of glitches. I guess > the first thing I'd try is treating it as a windows problem, since > that sounds like the easiest thing to try. > > Thanks, > > -- > Raul > > On Fri, Jan 9, 2015 at 3:58 PM, Henry Rich <[email protected]> wrote: > > I have the j803 released version installed on the 32-bit Windows > machines at > > school, and 3 students have run into a situation where J fails on > startup, > > after a few days of normaloperation. The user profile is not the > problem, > > and reinstalling J makes it work; though on one of the machines I had to > > delete the J directory before reinstalling (on the others an install on > top > > of the old directory was OK). > > > > Does anyone have ideas about what's happening, or how I can figure it > out? > > > > Henry Rich > > ---------------------------------------------------------------------- > > 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
