- JARBUNDLER ERROR NOT REPORTED COPYING JAR FILE TO UPDATE
- JARBUNDLER ERROR NOT REPORTED COPYING JAR FILE TO PC
- JARBUNDLER ERROR NOT REPORTED COPYING JAR FILE TO DOWNLOAD
However, when I run the executable within the generated application bundle, it does work. The build process succeeds without complaint, but the resulting application does not launch. Same menu, same functions, ect.I am building a Java 9 application for MacOS using Javapackager, via ant. They are identical machines except for 9 verses 16 channels. I would not worry about the 9CH DMR(AVC 776) as the two DVRs are kissing cousins. If you can use Video Server E then it should take Steve's AP.
JARBUNDLER ERROR NOT REPORTED COPYING JAR FILE TO PC
Then again it may not surprise me as it may have a different chip set on the PC board compared to the AVC 760 style boards. I am surprised that Steve's AP did not work with your DVR if it does use Video Server E. If your DVR does in fact use Video Server E, then you might be able to use Video Viewer. It was kind of confusing at the time for some dealers as you might get some of the stock that they were trying to deplete of the Video Server S models, or you might get a Video Server E model.
When this DVR first came out it did in fact use Video Server S.ĪVTech came out with a model of DVRs at the time, and the newer DVRs used Video Server E.ĪT that very moment in time they changed some of the chips on the board, and then updated the AVC 777, and the AVC776 to use Video Server E. I am surprised that you did not see your DVR on this page:
If it has an internet connection then it would be the AVC 777W. Your DVR is an AVTech DVR model number AVC 777. After that, it thinks that it's an n_Device=5, which is a "9CH DMR."īased on everything I've read, I think this Lorex device is actually an AVC760 jpeg (thus the 732E disk that came with it.)Īnyone know anything about it? Am I just wasting my time trying to get this app to work on it? It just seems so close, yet so far. When the app starts, it gives my DVR a "777W" ID, then the b_V732E flag = True. I've called Lorex, but the support folks didn't even know that I could go to the AVTech site and get stuff that would work with this DVR - go figure.Īnyway, after debugging Steve's app for a while (some variables were inititalized improperly), I've gotten as far as the InitSerialCmd function. I've owned it (brand new) for about 2 months. Unfortunately, I can't find any info on the web about it. That gave me a hint about the true background of the DVR. The "driver" disk (not a driver, but app) is titled PCD-732E and comes with Video Server E (v1.0.6.6).
I've read this thread many times, but hadn't gotten around to playing with the app until today.
JARBUNDLER ERROR NOT REPORTED COPYING JAR FILE TO DOWNLOAD
It would have been nice to just be able to download the applet from any given machine, and just put a wrapper around it to provide an application GUI framework, but it's not quite so clean. This is why you may have noticed that the control buttons can sometimes take a while to appear when the application is first launched, and there could be other side effects.
JARBUNDLER ERROR NOT REPORTED COPYING JAR FILE TO UPDATE
To be honest the whole thing is a bit untidy the applet on which it is based mixed up processing and GUI threads horribly, so there are more threads trying to update the display than the main dispatch thread. I'm more than happy for folks to have the source for my port of my application. Just grabbing the applet for the 780 machine, decompiling it, and then calling it from a Java app should work I'd have thought. I've not looked too much at the detail of the HTTP login process, but I'd not be at all surprised if the 780 has a different protocol again. There seem to then be two basic second stage login processes, one for the 78x machines, and one for the others. I'm not sure what machines these actually correspond to, but the DVR760 reports itself as a 783E and proceeds on that basis. The client thus gets passed back a ProductID which is one of:
0 kommentar(er)
