technomonkey76

I think this works in the Mac OS X terminal as well. Go ahead and run that command.

Re: Wont Open Not sure if trolling or arrogant. A "bash file" is nothing more than a plaintext file headed with a "shebang line" (yes, it's the common term for it), which is the line that tells the computer with what to interpret the file. If you've seen a Python script, you've seen a shebang line. (Bash scripts use #!/bin/bash as the first line.) A more appropriate term for this kind of file is a "shell script." The Bourne-Again SHell (bash) offers additional interpretable characters that do not appear in the form of external executables, for purposes such as creating loops and conditional statements. As for an "opening command," one can often execute either bash or (if bash is the user's default shell [see also: chsh]) sh with the file as an argument to run the commands in the script. However, it's probably better to give the shell script executable permissions (see also: chmod) (755 [-rwxr-xr-x] is usually a decent choice for permissions), and invoke it without bash. To invoke a shell script without explicitly specifying the program that will handle it (to run it without passing it as an argument to the shell executable), however, the file must either be in a directory specified in the PATH environment variable or it must be prefixed with a "./", which will tell the shell invoking the file to search for it in the current directory. The shebang line, if typed properly, will instruct the computer to use bash to parse the script. Often, a shell script is given an extension such as ".sh", but if you're using one, you're likely on a Unix-based OS (including Linux-based OSs), and you shouldn't care about file extensions much. Ja, men lojban är det bästa språket.

I'm sorry to hear that you've been having issues, Snowsdan. I also regret that these guys have been trolling you. Your issue is likely rooted in the fact that they're all lying, though Lear85 has some valid points. He is correct that Technic requires 33.5 bobs; no more, no less, and that an instrument is required to successfully launch the "Technic luncher." Windows tends to give programs only 32 bobs, and to fix this, you must rename C:\Windows\System32 to C:\Windows\System33.5. Your computer will likely ask for administrative permissions. Grant them, and reboot your computer before trying to run the "Technic luncher" again. It should work now. EDIT: Oh, by the way, you must have a microphone and you'll need to play a 5C, tuned to be sharp by 23 cents exactly, on any string instrument while booting Windows, or Windows won't be happy using 33.5 bobs instead of 32.