sikuli-driver team mailing list archive
-
sikuli-driver team
-
Mailing list archive
-
Message #23926
Re: [Question #243283]: Sikuli script when moved to 64bit environment throws an error
Question #243283 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/243283
Status: Answered => Open
Rubynator is still having a problem:
Raiman,
True, I associated all the .skL file with a batch file , to run them instantly from window by just double clicking on them.
So -r on command line since it's being called from a batch file is actually working fine.
I just tried from the command line , manually..as you said
C:\Sikuli\runIDE.cmd -r some-scriptname.skl -d3 -c and gives the same error,
everything is a fresh install ;(
Here's the debugged log;
C:\Sikuli>runide -r C:\Users\Rubynator\Desktop\assignment64.skl -d3 -c
'Files' is not recognized as an internal or external command,
operable program or batch file.
+++ running this Java
java version "1.7.0_51"
Java(TM) SE Runtime Environment (build 1.7.0_51-b13)
Java HotSpot(TM) Client VM (build 24.51-b03, mixed mode, sharing)
+++ trying to start Sikuli IDE
+++ using: -Xms64M -Xmx512M -Dfile.encoding=UTF-8 -Dsikuli.FromCommandLine -jar
C:\Sikuli\sikuli-ide.jar -r C:\Users\Rubynator\Desktop\assignment64.skl -d3 -c
[debug] SikuliIDE: Switching to SikuliScript with option -r, -t or -i
[debug] SikuliScript: CmdOrg: -r C:\Users\Rubynator\Desktop\assignment64.skl -d3 -
c
[debug] Running on Java 7 (1.7.0_51-b13)
[debug] --- Sikuli parameters ---
[debug] 1: -r
[debug] 2: C:\Users\Rubynator\Desktop\assignment64.skl
[debug] 3: -d3
[debug] 4: -c
[debug] FileManager: tempdir create: C:\Users\Rubynator\AppData\Local\Temp\Rubynator\tmp-681303371.sikuli
[debug] SikuliScript: givenScriptName: C:\Users\Rubynator\AppData\Local\Temp\Rubynator\tmp-681303371.sikuli\assignment64.sikuli
[error] FileManager: Script folder C:\Users\Rubynator\AppData\Local\Temp\Rubynator\t
mp-681303371.sikuli\assignment64.sikuli does not contain a script file named assignment64.xxx
[error] Terminating SikuliX after a fatal error! Sorry, but it makes no sense to
continue!
If you do not have any idea about the error cause or solution, run again
with a Debug level of 3. You might paste the output to the Q&A board.
[debug] SikuliXFinal: cleanUp: 0
C:\Sikuli>
I'm frustrated now..
--
You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.