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 becoming a contibuting member by either clicking this text or the Patreon link on the right.

Patreon

Nologic

Basic Member
  • Posts

    1360
  • Joined

  • Last visited

Everything posted by Nologic

  1. Maybe try Mednafen...been actually thinking of going on a spree of doing up a bunch of configs for this great Emu
  2. Thanks Tom for the update...tho I'm lagging 6+ versions behind.
  3. >huh...I'm using build 3.51 not sure if thats current or not...you do have your BIOS correctly configured in the Emu correct? > >Under Options you don't have Disable Key Shortcuts correct? > >Under Country you have AutoDetect selected correct? > >I'm other wise I'm generally clueless this is more Adultery's baby than mine. Hehe good deal
  4. hehe nope that should have done it....I'll take another look and see if I missed some thing else. *Update* redownload and try again...more cruder code...but ideally it'll work. --Okay redid the code some more should be cleaner...for some odd reason AutoIt wasn't grabbing the class name for Fusion correctly.
  5. Probably the sendkey code I'm using isn't working with fullscreen fusion...I'll browse through it some more. Okay redownload the file...hehe I guess it would help if I sent CTRL+B and not ALT+B which is incorrect.
  6. Okay you know the drill. You could combine Genesis & CD and rename the group Sega CDX or you could combine Genesis & 32X and create the group Sega Neptune Hehe to bad Sega never created a Genesis + CD + 32X system.
  7. Well looks like I'll be adding a few lines...things aren't as clean cut as they where with the Magic Engine...Fusion has great CLI except when it comes to booting directly from the CD...which is probably the only lacking feature via CLI.
  8. I could probably edit the current to work with Fusion...might as well get started making your ini's with the prior app. It should only be editing one line & deleting another...so at some point it'll be posted here. How ever you may want to look into part of Tom's suggestion where you mix two or more setups together...in your case TG16 Hucard & TG16 CD then just rename the grouping to Turbo Duo
  9. I'll look into it tomorrow. You do have the Emu set to by its self to access the correct drive correct? Also you do have a system card image placed in the same folder as the emu executable...and its named correctly in the _settings.ini file? If all thats good...then I'll have to burn a disc and try things out my self...we'll get it.
  10. Oh forgot to mention you'll probably need to edit the _settings.ini for the loader.
  11. Extract the attached file to the location where Magic Engine is installed Copy "[Console] NEC TurboGrafx CD (MagicEngine).ini" from "*\Support\Import\" to "C:\Program Files\GameEx\CONFIG\EMULATORS\IMPORT-EXPORT\" Copy all the "[Mapping Off] Exit *.ini" from "*\Support\Import\" to "C:\Program Files\GameEx\CONFIG\EMULATORS\" Fire up "Advanced Configuration" Press "Next Page" till you come to your TG16 CD listing then click that button From the drop down menu for "Import Emulator:" select "[Console] NEC TurboGrafx CD (MagicEngine)" Press the "Import" button Press "OK" on the overwrite dialog box Correct directory pathing if required Press "Save" Press "Exit" Notes: Rom pathing should be to where the *.ini's for the CD's are This is expected to work...but not positive.
  12. Actually its been rather nice up here for a change...not the normal gray and rain. When its nice in Seattle its extremely beautiful...but most the time its a depressing shit hole.
  13. damn now that was a fast reply...okay...my next post should contain the loader required.
  14. Well the next step is probably largely dependent on which Emu you are using...I could write something basic...but you would have to have a little idea of coding & autoit...not much but I'm not always up for crash courses. Any ways let me know what Emu and we'll go from there....tho don't be to slow to reply I'm suppose to be leaving town here shortly and will have not Net access.
  15. I know on most if not all Mame32 builds you can select what monitor mame renders to.
  16. Nologic

    Typhoon 2001

    There was a thread some where on here that listed cool PC games to run on your cab...I couldn't find it...but some one should link to this in that thread if it wasn't already. Typhoon 2001
  17. Well I'm not feeling all that excited about tackling a quicker way...shouldn't be much code but I'm still waking up. You can use the following autoit code to grab the label and serial for a given disc. $var1 = DriveGetSerial( "j:\" ) MsgBox(4096, "Serial Number: ", $var1) $var2 = DriveGetLabel( "j:\" ) MsgBox(4096,"Volume Label: ",$var2) Of course editing it to match your actual drive. Really should only need the serial...ideally you could write a simple program that would check what the current serial of the disc in the drive then prompt you for a name...this could then write a simple ini file per disc that could be used by a loader to prompt you if serials don't match...and then when they do...fire up the Emu. My thoughts tho *Update* Okay I've attached an executable and source code that will create your ini files as I suggested.
  18. Yeah both Tom and Ben do great jobs of keeping things in order. Also I think the general age of most the active forum members tends to be older than some forums...which lends its self to being more peaceful. That and if someone gets out of line we tend to pounce on him like rabid dogs....J\K ...I was going to post something other than brown nosing Tom & Ben...but I've forgotten what it was...blah
  19. Well from my general testing it doesn't look like its the loaders fault and CLI won't likely make things better...just cleaner. Basically it looks like the internal CD image plugin vomits all over its self every so often...or fairly often, depending on disc image and where the moon is in the sky. Tho I'm running a beta of xpadder right now so maybe thats influencing my testing. However things seem to work fine with the virtual drive loader if using Alcohol 52% or 100%
  20. No idea really. Just make sure that the loader and nullDC can run with admin rights is the best I can suggest...but since both are generally in a beta state your system admin may hunt you down and bludgeon you to death if s\he finds out. Best I can suggest is to troll the AutoIt forums and see if they have some thing to shed some light on things. I have no real intent to support Vista...if some thing I make works on it...bonus.
  21. Your welcome...oh and don't let that bit under my avatar fool you...I screw up plenty as you've seen thus far. So far the actual cleanest way for different ePSXe executables is to use Delta as the mini FE instead of ePSXecutor. Tho honestly I don't know how many games are required to run on an older build...or how many older builds are required. I know Delta handles 1 older with ease...past that it's likely an issue just like ePSXecutor. So if its only 1 older build being used and only a handful of games...its a non issue really...I'm just looking at the fact there where 1200 games for the US alone. Well I'm thinking on it...but the more input I get from you and others the easier it is for me to decide the correct way to go about things.
  22. Doh! screw up on my part...redownload the file.
  23. loader.exe "file location\name with extension" loader.exe "C:\games\fubar.cdi"
  24. This should do the bulk of what you want...still haven't added a way to run two different builds of ePSXe...I'll look into finishing that off tomorrow. Extract the attached folder to "C:\Emulation\" Copy "[Console] Sony Playstation (ePSXe).ini" from "C:\Emulation\Playstation\Support\Import\" to "C:\Program Files\GameEx\CONFIG\EMULATORS\IMPORT-EXPORT\" Copy all the "[Mapping Off] Exit *.ini" from "C:\Emulation\Playstation\Support\Import\" to "C:\Program Files\GameEx\CONFIG\EMULATORS\" Fire up "Advanced Configuration" Press "Next Page" till you come to your PlayStation listing then click that button From the drop down menu for "Import Emulator:" select "[Console] Sony Playstation (ePSXe)" Press the "Import" button Press "OK" on the overwrite dialog box Correct directory pathing if required (shouldn't be for you) Press "Save" Press "Exit" Important Notes: The "Rom Path" should actually be the folder where the CD images are...not using shortcut links any more. smile.gif Make sure all your ePSXeCutor profiles match the name of the CD image it for...minus file extension of course. Oh when using the Emu pressing the Dpad to the upper left and pressing buttons 4, 5 & 6 all at the same time will exit the emu.
  25. Nologic

    NullDC Loader

    Hehe be careful I may end up taking you up on that offer.
×
×
  • Create New...