Jump to content

theoakade

Platinum Member
  • Content Count

    17
  • Joined

  • Last visited

Community Reputation

2 Neutral

About theoakade

  • Rank
    Member

Converted

  • Location
    Austin USA
  1. OK. Final post. Here is how I installed everything. There are 5 wires connecting the front power button to the motherboard in a Dell 790 SFF Optiplex. I spliced the YELLOW and BLACK wires to the arcade buttons. BLUE, RED and ORANGE stayed going to the motherboard. I don't get LED functionality but I will survive. No alert message. Boots right up.
  2. The hornets net... Windows boots!! Blue light is back on the comp... But here's my new problem. The green arcade light stays on when the computer is off. Turns off when computer is on. Basically opposite of what I want.
  3. I took off the front power button. Clearly red and blue (as I have them) are meant for an LED of some sort. On the other side black, yellow and orange are grouped. I currently have black and yellow going to the button with orange being free. What I'm going to do is splice the front panel button wires into the mix and reattach orange.
  4. I'ma go ahead and do that... 1) Front panel BLK, Y, R and B spliced with original motherboard BLK, Y, R and B and speaker wire that leads to button. 2) Front panel orange to motherboard orange. See what happens. Front panel will get original signal and button in the middle will hopefully still work without setting off an alert message.
  5. Would splicing the original front panel wires back into the mix help? So basically from the button.... BLK, Y, R and B spliced into the speaker wire that is already spliced with the motherboard wire, that then heads out to the button. The orange wire simply reattach to itself. That would basically be the original signal loop, with the arcade button in the middle. The button should still work, and the power/signal from the motherboard to the front panel would reach each other and vice versa.
  6. OK. Here we go. This is where the front panel power button cable connected to on the motherboard. Six-pin housing with five wires. BLK, R, Y, B and O. I cut the cable. I added wire to each line to give me length to work with and added a labeled tag to each. After a little trial and error I found that BLK and Y powered on the computer as the button used to. I also saw that R and B together acted as the LED- coming on when the computer did so, going off when the computer shuts down. I did not see how it acted in SLEEP mode so I'm not sure if it blinks. That leaves Orange as the odd wire out. I just put some tape on the end and let it be free. I took some PCI covers off the back of the case. Took 4 speaker wires and connected them appropriately. Here is how I hooked up to the button. Remember, Orange is loose wire. Any ideas? I can't find out what each color represents cause Dell thinks it's some top secret shit. Any ideas?
  7. Hey. I just looked at the cable that connected the motherboard to the power button. I saw there were 5 wires. The LED button has 4. Trial and error got it up and working. One Orange wire was left out of the mix. I'd love to know how to bypass this message.
  8. Hey guys. Been trying to figure this out. Today I hacked an LED arcade button to power up my Dell 790 Optiplex SFF. Success. The button acts just as a power button would do. Press it to boot computer, press to go into hibernate and hold down to power off.   Only problem I have is a Dell diagnostic program giving me a message .... "Alert. Power Button Cable failure." Here is the message...   When I press F2 it takes me to the BIOS. Here is a pic with all the settings opened...     More settings...     Here is what I get when I press F5. It's Dell's ePSA program. Self diagnostics. It spots a difference in the power cable I hacked.   And another...   The Dell front power button had 5 wires. BLK, R, Y, B and O. I noticed on the MOBO which colors sat across from each other. The microswitch has BLK on the bottom and Y in the middle. The LED has R and B hooked up to it, leaving O free from anything.   The computer boots up. The Dell POST screen splashes. And then I'm hit with the "Alert!" message.  How do I get around this? Can I skip the cable test in ePSA? Should I reset CMOS battery? Reset BIOS? Update BIOS? Any ideas would be greatly appreciated. Once this is done, the Hyperspin cabinet is 100% complete!!!!
  9. OK. My cab is 100% ready to go with MAME, Atari 5200, NES, SNES and Genesis. Everything I want. However, I'm playing around with the idea of adding some kind of pinball into the mix. I don't want to do a full-fledged HyperPin, I just want to do a decent 16:9 pinball setup and add it to the existing wheel. I know of FX2 and Arcade Pinball. I don't have Steam. What are my (free) options to add some kind of pinball to my cab? Can anybody point me in the right direction? Tutorial?
  10. Thanks to all. Y'all def cleared a few things up. And hell yeah I built the cab first. If I woulda screwed around with HyperSpin first I prolly woulda just given up! But now I'm too far in. Thanks again. I think my next step is determining what MAME games I want, using a tool to make a new XML, secure my roms, and determine whether I want to download game media personally or figure out HyperSync. If any of this sounds wrong stop me now. And any more tips always appreciated. Thanks again.
  11. OK. I built a sweet friggin cab. Time for computer side of things. Newly imaged i3 desktop and went ahead and got lifetime membership to HyperSpin and Emumovies. Here I go..... I followed ghutch's install guide and I feel great. RocketLauncher and HyperSpin are working together. I'm mastering MAME before I move on. RL test window plays my copy of 88 Games. HyperSpin can launch and play same copy as well. YAY! So glad I even got this far. I'll worry about controls later. Before I get too deep, I want to completely understand a few things. 1) An XML file is essentially a list of games HyperSpin is going to read and then project to me on the respective emulator wheel, correct? The XML file shows the name of the game, genre, year, yada yada. In RocketLauncherUI I set the rom path and tell Rocket Launcher where exactly the rom folder is. It worked because HyperSpin launched 88 Games perfectly. My question is what file can show me exactly what the rom needs to be named? Not the XML file cause there is no rom path info on that file. So what file will show me that RL/HS wants 88 Games to be "C:\Emulators\MAME\roms\88games.zip" 2) An INI file is the wheel setting file for each emulator wheel (or, am I supposed to say module?), correct? The INI file shows what video, what artwork, how the wheel is laid out, etc. Correct? Nothing more? 3) What in the hell is an AHK file? I'm completely stumped. And furthermore... 4) If you were me, and you want to narrow down the game list for MAME, you use HyperTools to eliminate crap and keep what you want. HyperTools then spits out a new XML file that you then need to overwrite in both RL and HS database folders, correct? Anything else? 5) And once you have the game list you want, then what? Start gathering my game copies? HyperSync after that? Which leads me back to question 1- How do I know exactly what the rom needs to be named? Or is everything these days pretty pre-configured/named? LOL, jeez. I feel like an idiot. It's gonna be a long road but if somebody can see where I'm at on the HyperSpin road and has a few lines of wisdom and recommendations, I'd greatly appreciate it. Thanks in advance. Hope to be an involved member at some point.
×
×
  • Create New...