after the download, running Camelot

[jpol...@wcs.org]

Hi:  Curious about capabilities of Camelot, I downloaded Java, and Camelot into Windows 10 platform.  Click on the bat and nothing happens.  Could use some basic cookbook advice - to get it running.  Thanks, John

[Chris Mann]

Hi John,

Thanks for trying out Camelot.  From what you've described, it sounds like the .bat file is not in the same location as Camelot itself.  There's a few ways this could happen:

1. If the .bat file is copied from the .zip, but stored in a separate folder to the ".jar"
   
2. If the .bat file is ran, but the .zip file was not extracted in full first.
   

I can see the latter being the more likely scenario. If you right click on the .zip and extract it, and then try from the extracted folder, does this help?

-Chris

[Heidi Hendry]

Double Clicking on the bat file should start a command prompt. Are you getting that?

The first time I ran Camelot, it took a little while to setup the folders. so I had to be patient.

Try running it again... and wait.. it should open a browser up

[jpol...@wcs.org]

extracted all from zip to one folder. Double-clicked on the batch file (with the chain icon) and was asked if sure I wanted to run, said yes, but no action (2 x).   There is a "jar" file.  What is its significance?

[jpol...@wcs.org]

60+MB jar file and ~ 1 MB batch file in same folder.  No action.  Suggestions?

On Tuesday, November 8, 2016 at 5:01:32 AM UTC-5, jpol...@wcs.org wrote:

[Chris Mann]

The way to dig in to what is going on is to do the following:

1. Browse into the camelot-1.0.1 directory that was extracted
2. Hold down the Shift key and right click in the directory.  Select "Open in Command Window"
3. In the command window, type "java -jar camelot-1.0.1.jar"

This does the crux of what the .bat file does.  If Camelot runs successfully, after a few seconds you'll get a message starting with:

"Camelot started on part 5341"

But as Camelot does not run, I expect there'll be some other error.  If so, do post it here.

-Chris

[jpol...@wcs.org]

Thanks.  I may try that.  On other hand, it seems as if you guys are circulating this to test and improve the program.  Reading the material that came with it, it was particularly attractive because of its accessibility.  In that context, the ease of access to start up should be optimal, it should be really easy to get it going to match with - how easy it made the rest seem.

On Tuesday, November 8, 2016 at 5:01:32 AM UTC-5, jpol...@wcs.org wrote:

[Heidi Hendry]

It's definitely weird you are not getting a command prompt window, but that sounds operating system specific. As any file with a bat extension should start command prompt.
Maybe you could also try opening a command prompt first and try the batch file from there

[Chris Nagy]

this happened to me on one of my computers -- i had to make sure the correct java dev kit was installed.

[Heidi Hendry]

Chris, can you tell us more about that, so we can make sure we have something in the instructions? What OS was the machine? And what did you work out?

[Chris Nagy]

Sure. Some info that may or may not be important: I was testing Camelot running over our office network, so the Camelot files itself were on a local server that runs several drives that all of our computers can access. I was using altered environment variables where the db was saved in a particular folder on the network drive.

It had worked fine on my personal computer; this was the second computer I tried it on (so I knew it should work). I ran Camelot's .bat, and got a command window for a split second, it disappeared and nothing happened.

I somehow found a command to make the command window stay open and saw there was an error message (paraphrased) "unknown command: java" or something similar.

read this in camelot instructions:

Camelot requires Java 8u91 (on later) to be installed on the system it will run on before it can be used.

Java can be downloaded here: http://www.oracle.com/technetwork/java/javase/downloads/index.html

If using OSX, you will need to install the "JDK". For Windows and Linux, you can install either the "JRE" or the "JDK".

I went to the site and DLed the JDK for win 64
http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
this file: Java SE Development Kit 8u111

worked after that

[Heidi Hendry]

Thanks Chris N, for noticing that!! 

[jpol...@wcs.org]

Thanks.  Got swamped by proposals.  Will try reload java.

[jpol...@wcs.org]

Got it.  Thanks Chris and Heidi.

[Heidi Hendry]

Oh great to hear!! :-)

[Colin Cook]

I tried this fix with the Java upload but it still didn't work. What did work was to leave the command prompt window open, open the bat file in an editor and then copy and paste the text to the command window. Ran OK then.

I also installed this on a Macbook Pro but ran into issues with Safari not being able to access the local host address. Googling this revealed it is a common issue with the OSX and I haven't found a fix that works yet.

[Colin Cook]

Damn. Came back to look at the page again and ran into a similar issue. Any clues as to how to resolve this? Running on Win10 64 using Chrome.

This site can’t be reached

localhost refused to connect.

[Chris Mann]

Hi Colin,

The "localhost refused to connect"-type message will occur when Camelot isn't running in the background.  On Windows, I'd suggest trying to run the batch script again, or copy and paste the command from the batch file (note: Camelot will stop running if you close the batch window which started it.).

For OSX, I'd suggest first seeing if Java is installed.  If you open the OSX Terminal and type "java -version", it should say something like:

java version "1.8.0_112"

Java(TM) SE Runtime Environment (build 1.8.0_112-b15)

Java HotSpot(TM) 64-Bit Server VM (build 25.112-b15, mixed mode)

If you get something closer to "Command not found", try installing the latest version of the JDK (Java Development Environment) from the Java website again.  Links for this are in Camelot's user guide.

Once you see the "java -version" command give something similar to the above message, try again to run the ".command" file distributed with Camelot.

If you happen to figure out why Camelot isn't running directly from the batch file, please do let us know.

Chris

[Heidi Hendry]

Hi Colin, 
With the Mac, perhaps try instead of http://localhost:xxxx, replace the word localhost with the IP address of the Mac ??? Or the name of the Mac?
That's a bit weird though.

With the Win 10 and Chrome, make sure that command window is still running, it needs to keep running in the background.

I preferred to run Camelot using the direct command line, so:
java -jar camelot-x.x.x.jar (replacing the x's with the numbers of the version)

As long as your command prompt is in the right folder location, that should work.

Hope something in there helps?

Regards

Heidi

[Colin Cook]

Reran the bat file (Win10) and it works (after doing the copy and paste trick). It doesn't state in the instructions that you have to run the bat file every time you want to use Camelot (I thought it was just part of the installation process). Running the command file on the Mac gets it to work too. Just have to sort out how to get it to run direct from a bat file now so I don't have to copy and paste every time.

Hoped it would be a bit simpler. I'm thinking about using Camelot to manage photos for community groups doing fauna surveys. Hence my questions about running it over Dropbox.

[Heidi Hendry]

Hi Colin,
It's great that you think Camelot could be used with community groups. When it comes to running it over the internet, you need more than just Camelot. Dropbox is not suitable regardless.
You would want something like
Amazon Web Hosting or at the bare minimum your own server attached to the internet.
You would probably also want user logins (in case someone is terrible at identifying or someone mucks things up) - which is not in this release.
You can probably employ someone (possibly even one or both of us) to get this set up. (I'm in Hanoi, Vietnam & Chris is in Sydney, Australia. )
The software is open source, so if you found your own Clojure programmer, then they could make the relevant changes needed.
It's definitely feasible but not with Dropbox or Google Drive.

--
You received this message because you are subscribed to a topic in the Google Groups "Camelot Project" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/camelot-project/V4f1as6c5xQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to camelot-proje...@googlegroups.com.
To post to this group, send email to camelot...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/camelot-project/37cac0f3-fb08-4c4a-a8cd-bbcab3a8614d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Regards Heidi Hendry

[Colin Cook]

Heidi,

I'd probably work with CeRDI on this, as I'm currently collaborating with them on a couple of other projects. They do work with community groups (eg SWIFFT) and could possibly help you if you needed some input. For now, I'll have a test drive through Camelot and see if it would be suitable for our intended users.

Colin

[Colin Cook]

Just have to sort out how to get it to run direct from a bat file now so I don't have to copy and paste every time.

OK, got it working. Not sure if this is usual, but I had to wait a while for the program to start. Might be my PC.

[Mauricio Peñaranda del Carpio]

Hi Chris Mann

I did as you indicated and the error that pops up is: Unable to access jarfile camelot-1.0.1.jar. Do you know what iam doing wrong?

[Mauricio Peñaranda del Carpio]

Hi Chris Mann

I did as you indicated but i got an error: Unable to access jarfile camelot-1.0.1.jar. Do you know what iam doing wrong?

El martes, 8 de noviembre de 2016, 6:01:32 (UTC-4), jpol...@wcs.org escribió:

[Chris Mann]

Hi Mauricio,

There's two main scenarios that could cause that error.

Scenario 1: The zip file for 1.0.1 has not been "unzipped", or not all files were extracted from it.
Solution: Check that the zip file is completely extracted first.

Scenario 2: The zip file for 1.0.2 is extracted, but the batch file is from an old (1.0.1) version of Camelot.
Solution: Make sure all files extracted from each version of Camelot are kept together.

Finally, if the version of Camelot you have is 1.0.1, there are a couple of bugs in 1.0.1 that are fixed in the newer version.  I would recommend downloading 1.0.2:

http://camelot.bitpattern.com.au/release/camelot-1.0.2.zip

Hope that helps,

-Chris