Jump to content

All my products and services are free. All my costs are met by donations I receive from my users. If you enjoy using any of my products, please donate to support me. My bare hosting costs are currently not met so please consider donating by either clicking this text or the Patreon link on the right.

Patreon

tthurman

Admin
  • Posts

    6884
  • Joined

  • Last visited

  • Days Won

    209

Everything posted by tthurman

  1. FYI this is what I was reading: "What folder are you attempting to extract to? If it's at the root of a drive, or one of the protected folders (\Program Files, ProgramData, \Windows), then yes, you need admin access to do this. If it's a profile folder (like your desktop or documents), that wouldn't make sense unless 7zip is doing something "bad" when launching (for what it's worth, I've been using WinRAR without problems on Windows 8, but I've not tried 7zip yet)." http://www.eightforums.com/software-apps/9003-7-zip-administrator-rights-problem.html After reading the quoted post, and seeing how the target directory is "C:\MinGW" per the directions, it stands to reason it would apply to 7 too, perhaps Vista as well, with it's overblown UAC. So many of our industrial UPS units and mechanical systems require the run as administrator thing, I've pretty much acclimated to doing it all the time now.
  2. Cool! I was just coming back to suggest right click and run as administrator for 7zip in windows 8. Then just extract using file manager. Apparently it's a problem for some, but I don't know your OS. fingers crossed!!!
  3. This has to be some compatibility problem between 7zip, and this .exe. I just downloaded it again, and extracted it using nothing, just let windows 7 do it's thing. This is on a completely different machine than I compiled on above. Can you bypass 7zip? Perhaps right click and run it as administrator, or configure 7zip to not associate with .exe files, just until you get this succesfully extracted? I've verified everything you have, file size, etc. and I believe you've found your problem for sure, and it's not the file, it's just not jivin' with 7zip for some reason.
  4. Early upon my return to GameEx I felt the wait would be timed nearly perfect with my build. As things progressed I found myself becoming more Impatient, but ended up loading 13.26 at the recommendation of many here. I realize this doesn't apply to the original poster in any way, but to me this was a whole new ballgame from the frontend I messed around with so briefly five or so years ago. Going with the current version has been a good move for me, as it has given me the oppoturnity to familiarize myself with configuration screens, which I assume will retain a similar feel with Evolution. That said, I am eager and excited about the release of Evolution, but imagine a huge amount of effort is being taken on to ensure a polished release. On the other sites I frequent, I see others posting about the release too, and expect to see activity here increase dramitcally on launch, and the continuing support to keep them coming back.
  5. Wow, I thought I was a packrat! Bid is up to 50K!
  6. That..., is a good point! Captian Obvious voice: ".NET 2.0 Runtime, you don't need it right now!"
  7. One other thing, have you confirmed you have .NET 2.0 Runtime?
  8. Hmm, well the seller responded at the 11th hour with a "I'll refund the money" post, and no details. They shipped this 2 day priority for 24 bucks, and so I thought ground back would be less. WRONG! My focus is non-existent here as of late, I should have thought this through better, instead of focusing on being pissed over the crap packaging. After shipping I'll net about 25, then I suppose gamble its a power supply in my old one for 20. If I'm wrong, I've got an power supply I don't need, and now I'm out 45. At $49 I beleive your plan to part it out for repair is the only logical solution, and call it a day!
  9. I'm posting pics for the paths, so it's easier to grasp. In my case I didn't need minigw 32, but I just left everything intact.
  10. If you already haven't done so, at this point I would recommend deleting your miniGW directory and starting over. Often when I dive into something that is bombing left and right on me, I just make things worse by trying to fix, instead of start over, perhaps you're stuck in a similar loop here. Note that I didn't use MAME UI, and when extracting MAME 0153 that I renamed that folder from mame0153s to mame0153. Also inside of Mame0153 I extracted mame.zip, and trashed the zip file once done.
  11. I was gonna welcome you the old farts club, but you're not there yet Happy Birthday!
  12. Man this is a looooong thread! There is some amazing work here! This has to be the most complete theme, EVER! Hands down, the ideal theme for the "The Completist" ! Great work!!!
  13. Recently it came to my attention that my brand new fresh install of 8.1 had some errors. These looked more of the trival sort, but I like things to be right. My install was as clean as possible, as in brand new, with nothing additional installed, which leads me believe this may be a result of 8.1 update (1). from an elevated command prompt you can check to see if you have any issues. sfc/scannow takes a little while, and if it finds anything, reboot and run it again. It may take sevaral reboot and runs to clean it up, if your lucky. For me this never got all of it, but the following did. Again, from an elevated command prompt. Dism /Online /Cleanup-Image /RestoreHealth This found and repaired an error in the component store. Following this I ran sfc/scannow again, and got an all clear message. Anyway, I thought some here might find this information of value.
      • 1
      • Like
  14. Here's my directory structure root directory on C C:\MiniGW inside minigw64-w32 minigq32-w64 patches (only file in patches is hi_153.txt) source (source path goes a little deeper) MAME0153 (which has two folders in it, mame and src) You don't seem to have the MiniGW files in the MiniGW root directory why don't you have the src folder? Are you absolutely sure you got the source code, and not a regualar release?
  15. Cool, thanks! Pretty much a rom in the roms folder, and the compressed hard disk in a subfolder of the roms folder. /mame/roms/area51.zip /mame/roms/area51/<area51chdfiles> I'll be looking into what chd's are worth testing for sure, I'd rather not clutter up the directory with a bunch of non-working titles.
  16. After kicking the tires for a little while, I've got Joust and Daphne running without issue. I thnk Joust was just something flaky, Daphne was a path issue.
  17. Yep, they are both the 0.153 flavor. I'm more concerned that I got a netframework error while updateing the mame list. The Joust thing is probably a PEBCAC.
  18. Once I set the correct paths for the MAME roms, as soon as I was back in GameEX it went through a rather lengthy process of adding them. At about 65% complete I had to step away, and so locked my workstation while I was out. When I came back and unlocked it I was greeted to a netframework error that I didn't bother to note, as I figured it would be logged, but I cannot find it. I am able to browse MAME games and succesfully launched pac man, but Joust hung at "resetting to factory settings", so I don't know if that is related to the error, of if the Joust rom just isn't working for some reason. Also, I've never used the CHD's before, where should they reside in the MAME directory structure? I don't see a specific folder to point to in the config setup. Daphne cannot find my laser disc images, but I believe this is related to the DDL. I previously used the downloader to pull all the images down, and I archived the entire folder, which it sees, but I get errors that the files cannot be found. Since I don't currently have my DL available, and so I tried Cobra Command and got the same error. Is this because I used the daphne downloader? thanks!
  19. When you extract the mame source, it creates Mame0153, with a sub folder of mame. Are you pointing to this mame sub folder, or the parent Mame0153 folder? That could be all it is, as I noticed this wasn't exactly detailed on HK's instructions, as it's possibly some subtle change that was made in the souce codes directory structure since the directions where written. C:\MinGW\source\Mame0147u3 is how the directions detail it, in our case it is C:\MinGW\source\Mame0153\mame This is what immediatley comes to mind, as I had an error too before I corrected this. As soon as I started looking at it I realized if twas looking for mame in the wrong place.
  20. I don't know how much trouble it would be to try your suggestions, but I think they are good. Sort of a less is more type thinking! Note: the graphis thing isn't something I'm skilled at, so this is my ignorance showing! stiglzer, I'm partial to the Tempest marquee, as far as game marquees go. What do you plan to do with nine different marquees, rotate them? On a side note: I finally watched Promethous, just tonight
  21. Never mind, the mame 64 executible is there bigger than life in the folder!
  22. Yeah, that's what years of experience gets you Wonder how cold all of that brushed aluminum would keep your beer?
  23. Okay, been a while since I did this, but I believe everything went well. Followed the HK steps, omitting the MAMEUI part, so the build is vanilla. C:\MiniGW C:\MiniGW\source\mame0152\mame C:\MiniGW\patches\high_153txt 20 min 12 sec on my Q9550, and when finished it opened the "mame" folder in the above path, with what I suppose is my newly compiled version of MAME 0.153, which for all intents and purposes is nothing more than a compiled version with the high score feature added. Sound correct? Why is the target OS Win 32 with MAME compiler 64? What is the source version, 32 or 64 bit? I thought there was some advantage to running 64 bit.
  24. You just got a new smartphone, and now you want what!
×
×
  • Create New...