404 error on compile run
- SinisterSoft
- Posts: 77
- Joined: Sun Apr 06, 2014 11:41 pm
- Location: Preston, UK
- Contact:
Re: 2.31 final: 404 error on compile run
It creates the spiderbasic._compileation0.html in the source dire too, here are the options in the source code:
; IDE Options = SpiderBasic 2.31 (Windows - x86)
; CursorPosition = 915
; FirstLine = 2258
; Folding = ---------
; WindowTheme = flat
; GadgetTheme = flat
; WebAppName = ReportComplete
; WebAppIcon = ..\Images\liveicon.png
; HtmlFilename = interface.html
; JavaScriptFilename = interface.js
; JavaScriptPath = libraries/javascript
; CopyJavaScriptLibrary
; iOSAppOrientation = 0
; AndroidAppOrientation = 0
; EnableXP
; CompileSourceDirectory
; EnableUnicode
; IDE Options = SpiderBasic 2.31 (Windows - x86)
; CursorPosition = 915
; FirstLine = 2258
; Folding = ---------
; WindowTheme = flat
; GadgetTheme = flat
; WebAppName = ReportComplete
; WebAppIcon = ..\Images\liveicon.png
; HtmlFilename = interface.html
; JavaScriptFilename = interface.js
; JavaScriptPath = libraries/javascript
; CopyJavaScriptLibrary
; iOSAppOrientation = 0
; AndroidAppOrientation = 0
; EnableXP
; CompileSourceDirectory
; EnableUnicode
Re: 2.31 final: 404 error on compile run
I think I found the issue, I will upload a new version in a minute
- SinisterSoft
- Posts: 77
- Joined: Sun Apr 06, 2014 11:41 pm
- Location: Preston, UK
- Contact:
Re: 2.31 final: 404 error on compile run
Could you try to download the final version again ?
- SinisterSoft
- Posts: 77
- Joined: Sun Apr 06, 2014 11:41 pm
- Location: Preston, UK
- Contact:
- SinisterSoft
- Posts: 77
- Joined: Sun Apr 06, 2014 11:41 pm
- Location: Preston, UK
- Contact:
- SinisterSoft
- Posts: 77
- Joined: Sun Apr 06, 2014 11:41 pm
- Location: Preston, UK
- Contact:
Re: 2.31 final: 404 error on compile run
btw, the sb examples don't work either. They worked the first time I tried them, now they no longer work - same as my program.
Re: 2.31 final: 404 error on compile run
Do you remember if you had the OptimizeJS checked ?
Did you installed the beta 2 or did you used the beta 1 ?
I can't find any relevant change between beta 2 and final version, so I'm wondering.
Does anybody else have the same issue ? (on Windows)
Did you installed the beta 2 or did you used the beta 1 ?
I can't find any relevant change between beta 2 and final version, so I'm wondering.
Does anybody else have the same issue ? (on Windows)
- SinisterSoft
- Posts: 77
- Joined: Sun Apr 06, 2014 11:41 pm
- Location: Preston, UK
- Contact:
Re: 2.31 final: 404 error on compile run
I re-installed 2.30 from the museum. My program worked and the examples didn't. Optimisation is turned off.
But I noticed that the ports were different:
http://127.0.0.1:9081/SpiderBasic_Compilation0.html <-- works with port 9081 (my code)
http://127.0.0.1:9080/SpiderBasic_Compilation0.html <-- 404 on port 9080 (the examples)
When I went back to 2.31 it was like this:
http://127.0.0.1:9080/SpiderBasic_Compilation0.html <-- 404 on port 9080 (my code)
http://127.0.0.1:9081/SpiderBasic_Compilation0.html <-- works on port 9081 (the examples)
Maybe this can help you figure what's going on?
But I noticed that the ports were different:
http://127.0.0.1:9081/SpiderBasic_Compilation0.html <-- works with port 9081 (my code)
http://127.0.0.1:9080/SpiderBasic_Compilation0.html <-- 404 on port 9080 (the examples)
When I went back to 2.31 it was like this:
http://127.0.0.1:9080/SpiderBasic_Compilation0.html <-- 404 on port 9080 (my code)
http://127.0.0.1:9081/SpiderBasic_Compilation0.html <-- works on port 9081 (the examples)
Maybe this can help you figure what's going on?
- SinisterSoft
- Posts: 77
- Joined: Sun Apr 06, 2014 11:41 pm
- Location: Preston, UK
- Contact:
Re: 2.31 final: 404 error on compile run
It looks like port 9080 is being used by Logitech for their gaming software.
Disabling the Logitech software fixed the SpiderBasic issue.
This will affect anyone who uses Logitech's new gaming hub.
Maybe SpiderBasic should have a way of specifying the port range used for testing?
Disabling the Logitech software fixed the SpiderBasic issue.
This will affect anyone who uses Logitech's new gaming hub.
Maybe SpiderBasic should have a way of specifying the port range used for testing?