← Back to team overview

sikuli-driver team mailing list archive

[Question #243283]: Sikuli script when moved to 64bit environment throws an error

 

New question #243283 on Sikuli:
https://answers.launchpad.net/sikuli/+question/243283

Hi! 

I know similar bugs have been filed on this, but according to Raiman It wasn't a bug.
So, I've a script ready and work fine on my local 32bit WIN 7system. Now I exported it with CTRL-SHIFT-E to a skl. file and shared it with my co workers. They have 64Bit Win7, and installed fresh version of java and sikuli.
When they try to run .skl script on their environment they keep getting this weird file missing error. 
So sharing .skl isn't enough? Am I supposed to share the whole sikuli source? 
This is a roadblock now, please help!  Below is the output!

C:\Users\Rubynator\Desktop>assignment64.skl

C:\UsersRubynator\Desktop>C:\Sikuli\Runide -r *.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 *.skl -d3 -c
[debug] SikuliIDE: Switching to SikuliScript with option -r, -t or -i
[debug] SikuliScript: CmdOrg: -r *.skl -d3 -c
[debug] Running on Java 7 (1.7.0_51-b13)
[debug] --- Sikuli parameters ---
[debug] 1: -r
[debug] 2: assignment64.skl
[debug] 3: -d3
[debug] 4: -c
[debug] FileManager: tempdir create: C:\Users\Rubynator\AppData\Local\Temp\Rubynator\tmp-906484839.sikuli
[debug] SikuliScript: givenScriptName: C:\Users\Rubynator\AppData\Local\Temp\Rubynator\tmp-906484839.sikuli\assignment64.sikuli
[error] FileManager: Script folder C:\Users\Rubynator\AppData\Local\Temp\Rubynator\tmp-906484839.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:\

-- 
You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.