(Solved) Races through first cycle upon first start up. Fine afterwards.

When a sentence starts with "Again," it functions as a conjunctive adverb, requiring a comma immediately after it to separate it from the rest of the sentence. This usage is grammatically correct and can effectively add emphasis to repetition, the return to a previous point, or a second example.

Google -> "In CNC, MEM mode, or Memory mode (sometimes called Auto mode), is the operating mode where the controller executes a complete G-code program stored in its internal MEMORY, allowing the machine to perform automated machining cycles for production."

After being piled on by a pack of folks, that can only be described as: Deliberately obtuse.
I think I'm just going to the smart thing and just never mind.

You all have a nice day. Take care now. Bye-bye then.

WOW, you made 3 posts, quite long at that, justifying yourself being obtuse from the start, instead of replying to questions, or even more importantly, making a normal post to begin with, with normal questions and at least some info to go on with, so now we have a mess that absolutely helps no one, nor does it contain any info about your machine/software/use case/what the issue is.
And you call us being ....
And since you got stuck to it, "again" was aimed at you not giving us any useful info, but hey feel free to write essays about it, as long as it keeps you from giving us any info about your "miracle" machine that you "invented".

I come from an industrial background, this is our only linuxcnc controlled machine. If I use a description that is common in other machines we use daily and you don't, then ask. I'd be more than happy to explain what I mean and happy to learn the "correct" description used by linux users. If you don't want to ask. Heck, Google it. It's free. 

No. Instead I get this snark comment from you:

"Despite reading almost every post on this forum, i have no idea what that means."

Guess what, that's not a question. But I explained what MEM mode was anyways. Again, google is free. 

Another person here felt it necessary be insulting as though I don't know what system I'm using... Sorry, I don't know your "linuxcnc" lingo.
THIS is how you people conduct yourselves here and act appalled by my response? 

Then you said "Again, does the machine move at G0 speeds or just the gcode preview on LinuxCNC screen?"

This was explained CLEARLY in the first text:

"And it'll race through the g code like the entire program was full of G0 commands. If I had a part in the machine it would have crashed.  It's like it ignored every G1 command."

No where in the post did I even mention "preview" of any kind. No Idea where you got that. I said if a part was in it that it would have crashed. Know what that means? That means the machine was moving....  I can't make it any clearer. I can't understand it for you. 

Now if you'll excuse me, I have an issue to figure out. 

I thought I was being quite helpful, like my esteemed colleagues I was confused about MEM.
Playing the victim, the use of the phrase "folks", the mini lecture on the use of the word again, whilst missing the comma you used to add emphasis as noted in the mini lecture and finally quoting google as to drive home the point that those that queried the whole MEM thing were plebs makes me wonder if the OP has had any oil, dirt or grease ever touch their hands.

But then again I'm a paranoid bastard that trusts no one.

Just read your post prior to mine.

Your still to provide the information I ask for to diagnose your situation.

See sometimes as issue can arise that none have seen before, there was a recent one regarding MDI pins. Until one user had used a particular setup it had never occurred. Fortunately the user supplied the information particular to their usage and the code was quickly fixed and merged into the code base.
If that user had of reacted as you did nothing would have been resolved.
Now old Tommy has a great deal of experience deploying Linuxcnc based equipment as a commercial endeavour, so he is no Johnny come lately. PCW is the Mesa presence on the forum, very helpful, very knowledgeable and quick to respond to users requests for custom firmware. Very respected, will even endeavour to help when the mesa firmware is being deployed on non Mesa Spartan 6 platforms. Also has been generous enough to supply schematics to his products when asked.
So I would my two esteemed colleagues conduct themselves in a manner that has earned them the utmost of respect.
So I think it would be a good time for you the reassess your comments, look through the forum and read the replies they have given other users. Then it would be an idea to offer an apology cool down and supply the information requested so this issue can be resolved .

So what version of Linuxcnc are you using, what is the underlying OS, are you able to attach the config files ? Also what hardware is being used to control the machine, is it parallel port based, Mesa based or some other hardware based step direction system ?
Diagnosis requires the collection of information and that is the reason for request.

It's quite possible it is a gcode issue, mayhaps the cam is in metric units and the machine is setup in imperial units and no g21 was given in the preamble.

Another possibility is whoever setup the machine gave the overrides quite a large postivie range and the feed override is set at max.

And just for clarity Linuxcnc loads the gcode from the filesystem, ie from disk, not from "Internal memory", for those that are familiar with computers there is a distinction between memory (being ram/rom) and disk. As many things getting terms incorrect can cause confusion.
Look for all we know you could be using a custom interface with a MEM button implemented to make the machine more familiar. If that is the case it would be no wonder there has been confusion. Reading through the documentation for the various interfaces supplied with Linuxcnc there is no mention of a MEM button. I mention this as the frustration of the OP seems to be the questioning of a MEM button being implemented in Linuxcnc to retrieve gcode from "internal memory".