Build Your Own Arcade Controls Forum
Main => Everything Else => Topic started by: KevinFlynn on June 30, 2014, 10:18:59 am
-
Now that I have my Mame cab pretty much operational without the use of a keyboard, I want to make a general operational instruction manual to accompany it in case others wanted to boot it up and play. At the moment, just thinking of even turning it on makes most folks heads spin, even though it couldn't be easier.
I figure others have already written their own manuals though I've searched the web extensively and I cant find a single one. I realize I would have to customize any one else's guide but it would be better than reinventing the wheel.
Thanks!!
-
You might be the first. Seem like Uncle T had a book. Or at least someone that was doing a build at the same time he was doing the driving game.
Good luck. I would suggest taking a look at the wiki. That should be a good jumping off point.
It would be interesting, although, it would probably be suited to a slant d 3 ring binder, tab dividers and sheet protectors.
Considering that the Mame machine is an amalgamation of COTS (commercial off the shelf) hardware and some software, it would need to be specific to each category.
Takes me back to the days of having a Theory Manual, Operators Manual, Schematics and Illustrated Parts Break Down manual.
-
In addition to the manual, have you considered making a bezel sticker or laminated quick-start instruction card?
It should cover how to:
1. Power on the system.
2. Navigate the front end.
3. Select a game.
4. Exit a game.
5. Properly power down the system.
For the manual, you can go as in-depth as you like, but you might as well start from scratch by creating an outline of topics such as:
- Safety warnings (found in most arcade manuals)
- Electrical specs (as accurate as possible, both overall and for individual components)
- Basic operation (Similar to the instruction sheet above, but more in-depth)
- Software listing (MAME, LEDBlinky, etc. include version #s) and support utilities (WinIPac, KADE Loader, etc)
- Periodic maintenance (joystick lube, cleaning trackball rollers, dusting off CPU cooler)
- Parts listing (including vendors/order options selected i.e. 5v LEDs or 12v LEDs, regular or ultra-bright) and manufacturer's exploded view with part numbers for sticks/trackball
- Basic troubleshooting (joystick sticking, buttons not working)
- Wiring diagrams and/or block diagrams with operating voltages and signal flow
Bonus points if you include a software disk with all programs and support utilities and an image/back-up your HDD with a bootable restore disk . . . for just, I say, for just such an emergency. [/Foghorn Leghorn]
Scott
-
My 2 cents. Don't do it.
Playing games is fun, reading instructions and doing what you are told is "hard and boring" according to the mouth breathers of the world. People won't do what you say/write and then your cab will potentially get screwed up... you should be around whenever the cabinet is in operation.
From my tech support days I've learned never to underestimate the stupidity of a user.
-
My 2 cents. Don't do it.
Playing games is fun, reading instructions and doing what you are told is "hard and boring" according to the mouth breathers of the world. People won't do what you say/write and then your cab will potentially get screwed up... you should be around whenever the cabinet is in operation.
From my tech support days I've learned never to underestimate the stupidity of a user.
+1 -- Even if you take the time to write it all out in specific detail covering every possible scenario -- they will either not read it or find some way of messing it up you didn't cover so you'll be answering jaust as many if not more questions than you think you are going to avoid by writing one up ! (ie. when was the last time you actually read ( this means the entire manual not just the quick start guide or looking at a picture or 2 !!) a manual for a piece of equipment you purchased.
-
I figured the bezel sticker/instruction card was for others and the manual was for him. :dunno
Scott
-
Thanks everyone!
I have already composed an information sticker, of which I will eventually put on the bezel. There are several reasons why a manual would be good...
First, I totally get what most of you are saying, no one ever really reads a manual but to be honest, most of them that come with electronics or whatever are filled with a ton of useless info that no one would ever need, even if they needed some technical assistance. Most of the info in them is totally useless. Mine, written by me, would be much more pertinent useful, and specific to this build.
Which brings me to my second point... If years go by, I may forget some info and thus, having this guide could in turn help me out to remember some of the build, the front end, the emu's, etc. It's all fresh up there right now but as memory goes...I'm not getting younger - as he said in 'Dazed and Confused', "I get older, and they stay the same age..."
Also, and least important, if I ever went to sell the thing, having a guide might help a little bit with the sale. I can see some being totally intimidated where having a manual might ease their concerns. Also, it's something to say - I'm not your 24/7 tech desk, that's what the manual is for.
I guess, it would add an element of completion. But, again, I hear you all - is it really worth it.
More thoughts??
-
If you want to do it for yourself to use as future reference, go for it. I know I have forgotten things about my cab setup over the years... But if you expect the casual gamer to read it or care about it, you are fooling yourself. Anyone that will use your cab will just want to know what PL1 suggested for the bezel sticker.
-
But if you expect the casual gamer to read it or care about it, you are fooling yourself.
You know, you're absolutely right on that one. I used to get hung up on making things totally perfect or specific to friends, knowing they were coming over or whatever.
No longer do I ever spend any time on any part of this for others. They simply don't appreciate any of it, and if you find they actually do, you're extremely lucky. Everything in/on my cab was done for me (now at 41, and for the 80's me, age 8-18.)
So, I will better consider exactly who this manual would be for. It's for me and the lucky individual who inherits it when I kick the curb, I guess :)
-
Mine, written by me, would be much more pertinent useful, and specific to this build.
And this is exactly what everyone that has written all of those other manuals you refer to thought when they wrote the ones they did ! -- as mentioned if it is an exercise for yourself to remember what you did later that's one thing since you'll most likely remember what you meant when you wrote it (though may not) and might even remember that you wrote it down but if for others chances are they'll never read it or understand why you went into detail about certain parts and left all the relevant info they are looking for completely out !
-
Mine, written by me, would be much more pertinent useful, and specific to this build.
...but if for others chances are they'll never read it or understand why you went into detail about certain parts and left all the relevant info they are looking for completely out !
No doubt, LOL!
-
I write a manual for every one I sell--how to turn it on, adjust the volume, navigate the menu etc. I show people at first but you know they might forget and it saves them having to email me: "how do I turn the volume down??" It doesn't help when they totally F the machine up--but it gets them through the easy stuff.
I also suggest games to try--1 player, 2 player head to head, 2 player same joystick etc. I did this after I got one guy saying pacman was broke cause player 2 had to use player 1's joystick.... :dizzy:
-
I am making a simple page by page layout of each emulator on my machine that just shows which button does what.
Like: snes----- Y X L
B A R
NES----- B A -
- - -
dreamcast-- X Y L
A B R
Just for people (my wife) to understand that they are all different.
-
Thanks for the input!!