At sometime in the past when using 2008 I came across the OM command, but I don't remember where.  What this command does is as follows.  OM enter returns in the command line OFFSET DISTANCE if you enter a distance and then enter it reurns SELECT OBJECT TO OFFSET then you select an object and enter which returns SELECT SIDE once a side is selected and entered it will ask how many times entering a number and then enter will offset the object by the distance the number of times requested.  It is very handy and I use it a lot.  Again I do not remember where I came up with this.  For some reason this only works on my machine none of the other 14 in the office recognize the command, it worked on 2008 and when I upgraded to 2011 it still works, I am hoping that with the pending upgrade to 2013 or 2014 that it will continue.  I have searched appload and cannot see where I have ever loaded it.  Where does this command come from?  Where did I get it?
 
Thanks

Maybe it is a lisp routine?

John may be on to something.  Run a search on your system from the root directory for OM.LSP and see what you find.  If you do come up with a hit open the file with a word processor and have a look at it.  If only you have it then it's a file on your system in an AutoCAD common directory, so it won't matter what version you're using... it will still work.Dave.

I'm guessing the the OM is short for Offset Multiple.

Yes OM is Offset Multiple, but it seems to work different as I can select the object, enter the offset distance and them enter how many times to offset the object.  Kinda like a modified array. IMGrumpy2013-10-24 12:28:12

So did you search for OM.lsp on your hard drive?  Or just do a general search for all lisps routines as in many cases the file itself has a different name then the command used to invoke it.

For the time being you could use the Offset > Multiple option.  Every time you pick with your mouse another line is created offset from the last the distance specified.Command: OFFSETCurrent settings: Erase source=No  Layer=Source  OFFSETGAPTYPE=0Specify offset distance or [Through/Erase/Layer] <0.2500>: .5Select object to offset or [Exit/Undo] <Exit>:Specify point on side to offset or [Exit/Multiple/Undo] <Exit>: MSpecify point on side to offset or [Exit/Undo] <next object>:Specify point on side to offset or [Exit/Undo] <next object>:Specify point on side to offset or [Exit/Undo] <next object>:Specify point on side to offset or [Exit/Undo] <next object>:Specify point on side to offset or [Exit/Undo] <next object>:Specify point on side to offset or [Exit/Undo] <next object>:Specify point on side to offset or [Exit/Undo] <next object>:Specify point on side to offset or [Exit/Undo] <next object>:Specify point on side to offset or [Exit/Undo] <next object>:Specify point on side to offset or [Exit/Undo] <next object>:Specify point on side to offset or [Exit/Undo] <next object>:

Here is another option.  It is a custom lisp routine by Lee Mac called Dynamic Offset.  Check it out...http://lee-mac.com/dynamicoffset.html

>> ... Run a search on your system from the root directory for OM.LSP ....
 
It might not be a file called OM.lsp.  If it were me, I would probably call the file something like OffsetMultiple.lsp, so I'd know what it was about when looking at file names, with the command name defined inside it as OM for short.  But even that would only apply if it's defined in a file devoted to only the one command.  It might rather be in the acaddoc.lsp file, or some other .lsp file that contains definitions of multiple commands -- looking at the APPLOAD history will show the file name, but not the names of commands defined within it.
 
What you really should try to find is a file containing C:OM in it, because if it's an AutoLISP-(defun)'d command, that will necessarily be the command-name designation.  The basic Windows Explorer Search function won't search for content within .lsp files as it will in .txt or .doc or some other file types, but there may be a way to add that file type to those that it will search within, or other means of searching for content inside files.
 
Then there's also the possibility that it's in some kind of compiled file format, such as .arx or .fas, that may not be searchable in that way at all (I haven't tried such a thing).Kent Cooper2013-10-24 16:55:21