On Thu, Mar 17, 2011 at 7:20 PM, bill lam <[email protected]> wrote: > I believe this is a window security issue since /regserver is going to > create a key inside HKLM which only admin grade user is allowed to do. > Furthermore windows consider running a program from a network drive is a > security risk and will prompt to ask for permission, but your batch file > does not contain codes to do this job, so that it was skipped.
That is an interesting idea, but I am not sure it accounts for everything that I was seeing: [1] Why can I not execute the code from a network drive if the issue is that the registry does not change from when I successfully run it on my c: drive? [2] Why can I not run it on another machine, after installing j602 and running jreg.bat on that machine? Note that I believe tried running jreg.bat and then just running the my own program, and that did not seem to work. > I suggest you could pre-install and pre-registry j executables into each > user's local drive so that the batch file need not be run. I believe I tried that. I believe also that it did not help with the error I was getting when I run the code off a network drive, on my machine. (I would have double checked on the other machine, but it's not mine and I have to get ahold of the guy who is using it to even try, and he is in a meeting. But I would like to solve the issue on my machine before I go out and try it on his.) That said: at one point, I was exploring the possibility of running using various different implementations of J.dll. I had found that I could run jreg.bat with j.exe on my machine using the j.dll that comes with j64-602 and the j.exe that comes with 32 bit j602. Today, I tried using j.exe /unregister, to see if I could clean up any problems introduced there, but when I try that I get an error popup that says "Unregister not supported." In any event, I went into the registry and manually deleted the keys (described in jdllcomx.cpp's comments) from my various J servers, and re-registered j602 using jreg.bat and it is now working on my machine. I think I need to manually delete these keys from Gary's machine to get it working for him (since I think the first time I tried I was using the eratz j.exe from j602 and j.dll from j64-602). But I will first try the simpler approach (just re-registering j602 using jreg.bat) and see if that is adequate. -- Raul ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
