Can't Launch any program in Outlaw with the 2013.1135 SDK

Getting Started Newbie Questions
#1

Ok,

Very new to this, and I desperately want to get up and running but am being hit at the first hurdle.

Running Windows 8 (64 bit)

  1. Have downloaded and installed the SDK from the file CoronaSDK-2013.1135.msi into the following location : F:\Program Files (x86)\Corona Labs\Corona SDK

  2. I have download and installed Outlaw from the file Outlaw-Setup.exe into the following location : F:\Program Files (x86)\Outlaw

  3. I have registered for the products and paid for them also!

  4. Have fired up Outlaw, gone to preferences and set my path to the Corona Simulator.exe as shown below in SS

  5. I have Dropped in the tutorial project “Attack of the Cuteness” following the tutorials on the website, loaded up the main.lua file, followed the first video, selected Save then Launch and I just keep getting the error “Windows cannot find ‘F:\Program’.  Make sure you typed the name correctly, and then try again.” See SS below.

  6. I have tried uninstalling and reinstalling both the SDK and Simulator, tried re linking to the simulator in the preferences.  Tried changing the default install path of the SDK to one without spaces in the path name (this results in Outlaw finding the Corona Simulator.exe put then crashing).

  7. I have searched the forums and guides to try and help myself but at a loss.  Im hoping its something very simple, but right now im stuck on day one :frowning:

#2

Hi Craig

This doesn’t help your problem but I bought Outlaw as well and found it a bit klunky and then downloaded ZeroBrane Studio and everything worked first pop and its my IDE of choice now for Corona SDK.

Peace out

Peter
 

#3

I tried the default “Corona Project Manager” that ships with the SDK also, that also gave me the error.

It’s very frustrating as I want to learn and experiment over the weekend and then introduce my students to this on Monday.  I had set aside the week the play and tinker, this has kind of halted me before I started :frowning:

#4

I think the Corona Project Manager is an earlier version of Outlaw made by the same guy, try ZeroBrane once I set the SDK to Corona everything just worked and its free :slight_smile:

#5

Well I can tell people it was as simply as the fact that I installed to my F:\ drive partition and not C:\

As soon as I uninstalled the SDK and reinstalled to C:\ linking to the simulator then worked.

Crazy they don’t mention that somewhere.

#6

I’ll mention it somewhere now that I know – I’ve never installed CPM/Outlaw to an F: drive so I never ran into it.

Thanks for letting me know the problem/solution. I’ll see if it’s something I can fix, and if not (I have some limitations due to my dev environment) I’ll either warn people when installing or only allow installation to the C: drive.

 Jay

#7

Hi Craig

This doesn’t help your problem but I bought Outlaw as well and found it a bit klunky and then downloaded ZeroBrane Studio and everything worked first pop and its my IDE of choice now for Corona SDK.

Peace out

Peter
 

#8

I tried the default “Corona Project Manager” that ships with the SDK also, that also gave me the error.

It’s very frustrating as I want to learn and experiment over the weekend and then introduce my students to this on Monday.  I had set aside the week the play and tinker, this has kind of halted me before I started :frowning:

#9

I think the Corona Project Manager is an earlier version of Outlaw made by the same guy, try ZeroBrane once I set the SDK to Corona everything just worked and its free :slight_smile:

#10

Well I can tell people it was as simply as the fact that I installed to my F:\ drive partition and not C:\

As soon as I uninstalled the SDK and reinstalled to C:\ linking to the simulator then worked.

Crazy they don’t mention that somewhere.

#11

Hi guys,

Update: Never mind, figured it out.

#12

I’ll mention it somewhere now that I know – I’ve never installed CPM/Outlaw to an F: drive so I never ran into it.

Thanks for letting me know the problem/solution. I’ll see if it’s something I can fix, and if not (I have some limitations due to my dev environment) I’ll either warn people when installing or only allow installation to the C: drive.

 Jay

#13

Hi guys,

Update: Never mind, figured it out.