SapphireSteel Forum
Welcome,
Guest
. Please
login
or
register
.
June 19, 2013, 05:24:34 AM
1 Hour
1 Day
1 Week
1 Month
Forever
Login with username, password and session length
Search:
Advanced search
Welcome to the SapphireSteel forum - for discussion of the Sapphire and Amethyst IDEs
3893
Posts in
803
Topics by
672
Members
Latest Member:
davib
SapphireSteel Forum
General
Sapphire / Ruby In Steel
Trouble: Can't run any ruby file!
« previous
next »
Pages:
[
1
]
Author
Topic: Trouble: Can't run any ruby file! (Read 2777 times)
lisapan
Newbie
Posts: 2
Trouble: Can't run any ruby file!
«
on:
August 04, 2009, 03:38:22 AM »
Hi,
I just start trying out RIS today. So far, everytime I try to run a ruby file, an error shows up saying "StartRubyProcess failed: CreateProcess failed: 123".
What's wrong w/t this?
Logged
Huw Collingbourne
Administrator
Hero Member
Posts: 937
Re: Trouble: Can't run any ruby file!
«
Reply #1 on:
August 04, 2009, 04:01:33 AM »
You are creating projects, are you? Remember that Visual Studio only works with projects not with single source code files. There is a short tutorial to get you started in the PDF manual supplied with the software. If you follow that do you get any errors?
Also, which version of Ruby In Steel are you using?
best wishes
Huw
Logged
lisapan
Newbie
Posts: 2
Re: Trouble: Can't run any ruby file!
«
Reply #2 on:
August 04, 2009, 05:07:56 PM »
Huw, thanks for the reply.
I've already tried it and it didn't work.
I also installed it from scratch (even uninstalling all versions of .Net Framework with Aaron Stebner's .NET Framework Cleanup Too and it didn't work either.
I'm using PE.
Logged
Dermot
Administrator
Hero Member
Posts: 1006
Re: Trouble: Can't run any ruby file!
«
Reply #3 on:
August 05, 2009, 04:58:07 AM »
The '123' is a WinAPI error code returned by CreateProcess: 'The filename, directory name, or volume label syntax is incorrect.'
So I would guess that something like the path to the Ruby Interpreter is invalid or the Working Directory is invalid in some way.
It also may be the case that the system environment variable ComSpec (which points to the command line process, cmd.exe) is screwed up - I have seen that once before.
So the first thing is to check the Working Directory and Ruby Interpreter properties (they are under Project Properties|Build) to see if they exist.
You can check ComSpec by opening a command prompt (aka DOS box) any typing set ComSpec.
Dermot
Logged
Pages:
[
1
]
« previous
next »
Jump to:
Please select a destination:
-----------------------------
General
-----------------------------
=> News and Announcements
=> Amethyst
=> Sapphire / Ruby In Steel
=> Ruby Programming
=> The Snug Bar