If you're frustrated with the installation but really want to try out Arc, http://tryarc.org/ provides a functional Arc REPL in your web browser. You could use it to go through the Arc tutorial [1] and otherwise experiment with the language until things are set up on your system. (Full disclosure: I created the site.)
You were probably following the brief installation instructions at [2], which tell you to download Arc 3.0. If you download Arc 3.1 instead (see [3]), then you have more flexibility about which version of mzscheme to use. In any case, once you have installed mzscheme and downloaded/untarred arc3.[0|1].tar, you cd into the arc3.[0|1]/ directory (where as.scm resides) and run "mzscheme -m -f as.scm" to launch an instance of the Arc REPL.
To be sure, which operating system are you running?
I did try the site for a bit, its quite cool. Was trying to learn some schema earlier on, but totally lost as to how to get arc to launch.
By cd, do you mean the windows command prompt? Haven't used that before. Tried to though, but it says that neither run nor mzscheme are recognised commands.
Well I'm glad I asked because the above instructions presume you're on a Unix-based system (Linux, Mac OS X) working from the command line.
Unfortunately, I'm not familiar with how to get Arc installed on Windows. Here's one guide on the topic [1], but I can't vouch for its accuracy. If you want to find more related resources, try using http://af.searchyc.com/ to search this forum for posts that mention "Windows".
By cd, do you mean the windows command prompt?
Yes. cd is a standard command on shells for both Windows and Unix to change the current directory.
3) Make a batch file that'll run an Arc REPL for me when I double-click it. Here's my batch file, with a boatload of comments to help you figure out what I'm doing: http://gist.github.com/576688 There's probably some room for improvement, but it's what I'm happily using at the moment. (Note that it crashes a bit if you close the terminal window while Racket 5.0.1 is running, instead of exiting via a Racket (exit) call or an Arc (quit) call. I think this is a Racket issue, since previous versions don't crash that way.)
4) Make some necessary changes to Arc so that it stops giving errors on Windows. There are two main issues here. For Arc to start at all, you'll need to fix 'setuid (http://arclanguage.org/item?id=10625). Then, if you also want to run web applications, you'll probably need to fix the system call to mkdir (http://arclanguage.org/item?id=4652), and I wouldn't be surprised if one of the other system calls breaks too.
If you've already installed Cygwin, the system call issues may not exist, but I'm not totally sure of that. I know I only encountered the mkdir issue on a Cygwin-free Windows computer after having used Arc on a Cygwin-ful Windows computer for quite a while... but I'm not sure I've ever actually tried to run Arc web applications on the Cygwin-ful computer.
Tip: At least for me (on a Mac), running Arc with "[racket|mzscheme] -f as.scm" and then hitting ctrl-C at some point will kill the whole process, instead of dropping to a [Racket|Scheme] prompt from which I can use (tl) to return to the arc> prompt. Replacing the command with "[racket|mzscheme] -i -f as.scm", -i for interactive, fixes this. Much better.
I used to have 'cd ~/Dropbox/arc3.1;' before the 'rlwrap ...' part; the aload function and all the Arc files that load other Arc files (libs.arc) assume that you're in the Arc directory. I worked around this by wrapping all the calls to 'aload in as.scm like this: