Nologic

Well generally your better off getting it locally. Any place that sales motherboards & hard drives should also carry OEM copies. This applies anywhere at any store...and as I said before you need to make some sort of required part purchase...other wise the OEM price point doesn't apply. If you want web sites...try newegg & frys. Newegg hmm maybe prices have gone up...or maybe newegg is grabbing some extra funds...anyways enjoy

Okay give this a shot...when importing the INI make sure the Launch Before\After look like so: "C:\Program Files\DAEMON Tools\daemon.exe" -mount 0,"[RomPath]\[RomFile]" "C:\Program Files\DAEMON Tools\daemon.exe" -unmount 0 As some times double quotes get stripped. Update Stu has since taken over this build so browse his posts...attachment removed.

Okay I'll get you setup with Daemon...hehe but in trade if I recall you had figured out how to do button combinations with Xpadder...please share that info. Well I think it was you...been a while and a lot of things didn't get moved over to the new forum.

Well nullDC seems to work with the following formats (gdi, cdi, mds, nrg)...also DC games are picky as hell.

Well if you haven't bought a shiny new hard drive for your jukebox I'd suggest going to any ma & pa shop and buying one and while in the process pick up a OEM copy of XP, tho I'd suggest getting Pro...should run you about $80-90 for a full version. If you don't need a hard drive...then I HIGHLY suggest you buy a power cord for your power supply should run $8 and will allow you to buy a OEM copy of XP at the $80-90 price point. Basically any required part for a computer will quality you to be able to get an OEM copy of XP. This is straight out of a couple of MS reps at a Small Systems Builders meeting...which buy the way if MS ever has one in your neck of the woods go to it....costed $40 to cover their lunch costs, but in return they gave me a free copy of MCE 2005...plus I won a server software package...basically I traded $40 for $3000 Hehe not a bad trade...and the 6 hour meeting wasn't bad ether...the MS reps where fairly entertaining, and very informative...so $40 was well spent just to be able to hang out there...all the software was an added bonus.

I'll install purevideo later tonight and see if there are any issues...if there are none I'll be pointing lots of fingers at tinyxp.

Maybe use AutoIt... Doom 2 (Doomsday engine) RunWait ( @ScriptDir & '\jdoom.exe -bd & _ M:\Giochi\Emulatori\Doomsday\ & _ -mem 512m -sfxchan 32 -b 32 -wh 800 600 -g & _ M:\Giochi\Emulatori\Doomsday\bin\jDoom.dll -d & _ M:\Giochi\Emulatori\Doomsday\defs\jDoom\jDoom.ded & _ M:\Giochi\Emulatori\Doomsday\defs\jdoom\doomdata.ded -f & _ M:\Giochi\Emulatori\Doomsday\Wads\DOOM2.WAD & _ M:\Giochi\Emulatori\Doomsday\Wads\DOOM2.gwa & _ M:\Giochi\Emulatori\Doomsday\data\jDoom\doomdata.pk3 & _ M:\Giochi\Emulatori\Doomsday\data\jDoom\doomdata1.pk3 & _ -vtxar -novtxar -r & _ M:\Giochi\Emulatori\Doomsday\Bin\drOpenGL.dll' ) Doom Sony Playstation Edition (Doomsday Engine) RunWait ( @ScriptDir & '\jdoom.exe -bd & _ M:\Giochi\Emulatori\Doomsday\ & _ -mem 512m -sfxchan 32 -b 32 -wh 800 600 -g & _ M:\Giochi\Emulatori\Doomsday\bin\jdoom.dll -d & _ M:\Giochi\Emulatori\Doomsday\defs\cdoom\cdoom.ded -f & _ M:\Giochi\Emulatori\Doomsday\Wads\DOOM2.WAD & _ M:\Giochi\Emulatori\Doomsday\Wads\DOOM2.gwa & _ M:\Giochi\Emulatori\Doomsday\Wads\cdoom.gwa & _ M:\Giochi\Emulatori\Doomsday\Wads\cdoom.wad & _ M:\Giochi\Emulatori\Doomsday\Wads\cdoommus.wad & _ -vtxar -novtxar -nohightex -nohighpat -nohudmod & _ -nomonstermod -noplayermod -nogweaponmod & _ -noitemmod -nofxmod -nodecormod -r & _ M:\Giochi\Emulatori\Doomsday\Bin\drOpenGL.dll' ) Heretic: Shadow Of the Serpent Riders (Doomsday Engine) RunWait ( @ScriptDir & '\jdoom.exe -bd & _ M:\Giochi\Emulatori\Doomsday\ & _ -mem 512m -sfxchan 32 -b 32 -wh 800 600 -g & _ M:\Giochi\Emulatori\Doomsday\bin\jHeretic.dll -d & _ M:\Giochi\Emulatori\Doomsday\defs\jHeretic\jHeretic.ded -f & _ M:\Giochi\Emulatori\Doomsday\Wads\HERETIC.WAD & _ M:\Giochi\Emulatori\Doomsday\Wads\HERETIC.gwa & _ M:\Giochi\Emulatori\Doomsday\data\jHeretic\hereticdata.pk3 & _ -vtxar -novtxar -r & _ M:\Giochi\Emulatori\Doomsday\Bin\drOpenGL.dll' )

wOOt! just heard back...this will be getting added to Xpadder in a future release.

Last time I looked into this emulator I couldn't find a way to get it to play nice with GX...that said I could take a look at it again in a weeks time...as I got a lot of my plate right now. Really I'd suggest using FBA, Nebula, WinKawaks over using NeoRageX anyways...the newer builds of Mame typically play all the games anyways...so really unless your looking for NetPlay...Mame is generally fine. Maybe someone else can lend a hand...but more than likely its going to require a fairly tricky AutoIt script to make it work...and likely it won't be very clean.

Okay I think we are now on the same page. Heh shit no reason to be sorry, hell I'm in debt to you over the fine work you have done on the db's. Yeah the basic idea is to use very generic code in the scripts (AutoIt, Batch, AutoHotKey,...) to where all its required is for the end user to make sure that Xpadder has a valid value in App Paths with in the Registry. That way it limits the amount of trouble shooting involved, and the difficulty getting things setup right the first time. So basically picking peoples minds about what they thought of this method...along with digging for newer\better suggestions. I nearly have my basic Zinc loader written out with all the required support files...so I should be able to bang on this here in a bit to see how well things work when actually used with GX. heh after this is all worked out...then I'll be see about tackling the age old problem of dealing with OpenGL in a GX environment...get that solved and I'll be feeling rather studly...until bug reports come rolling in.

hmm think we got two different things going at the same time. Far as adding Xpadder to App's Path, I can write a script that searches the current directory for Xpadder and if found, make the required registry entry...if not found ask end user if its installed & if yes prompt end user for location...then make registry entry...if not installed fire up IE at users request and direct it to Xpadder home page. I don't really care where its installed on the system...only adding the pathing of Xpadder so that its known by the OS, so that I and others can script against it. So R:\some\messed\up\path\xpadder is just as good as C:\Program Files\xpadder So where ever its at...is fine by me...not looking to move it anywhere. As for ?Jonathon? hehe been awhile since I spoke to him...yeah he's not keen on installers...and an installer is not fully required here...as for the registry he seems to prefer keeping things portable...not that he's against the registry...just if it doesn't need to be in the registry...then it wont go into the registry. In this case he would likely add the registry entry as it kind of does need to be there to do whats desired. I posted about this to some degree on his forum...and have yet to hear yay or nay about it. Hehe T.Rex is going to be cool.

Yeah thats part of the over all work...looking to address as many concerns as possible...and make things as simple as possible. Anyways I'm fairly close...not a lot of code really...more just rethinking and refactoring what and how things should be done. This will in some ways spill over into other loaders...ideally for the better.

Well I'm trying to avoid the use of an INI file just store the location of where Xpadder is...and the dozens of ini files required to store that value. Setting the Apps Path value for Xpadder not only makes it simple to use Xpadder with Zinc but also nulDC & whatever else...basically its a single point of failure or success. The current GX Zinc loader doesn't use JoyToKey...but my current Zinc loader does...this allows you to play the CHD games supported by Zinc...and thats not fully correct. The bases of my Loader is to by default use WinterBlast's JoyStick Controller plugin for Zinc so that you have better responsiveness from your controls, compared to Keyboard mapping. The problem is the JoyStick plugin doesn't work with the CHD games...so you have to revert to the Keyboard plugin in this case we are looking to make things appear seemless rather than fucked up like they are. So we use some sort of Joystick to Keyboard mapper application...which prior to Xpadder, JoyToKey was the popular pick so things where coded to that....which was an ugly hack. The current GX Zinc loader doesn't appear to map any keys to gamepads...nor show any way of doing so....so from my point of view the current GX loader is broken. Now I certainly could be wrong about a number of things...if so I'm gladly open to being enlightened. Anyways Zinc is sort of off topic even tho its what spurred this discussion.

Well this applies to work being done on a loader that would replace GX's.

Yeah I've done that before...but looking to make it far more simplistic for the end user...thus easier to get GX up and running. With the above Apps Path value set I can then use ether of these bits of autoit code to perform the same thing as the batch script. Run(@ComSpec & ' /c start xpadder "' & @WorkingDir & '\Player 1" "' & @WorkingDir & '\Player 2" /M' ) #Include <Process.au3> _RunDos ( 'start xpadder "' & @WorkingDir & '\Player 1" "' & @WorkingDir & '\Player 2" /M' ) Basically it removes the need to edit half a doze ini files...by just setting one registry value.

Well I'm not sure Xpadder needs to run a installation routine...tho I have put forth a feature request that it checks the "Applications Path" in the registry to see if there is a value..and if its correct...and to automatically inject itself into the registry or the correct value. Followed by a secondary request to allow the end user to added Xpadder to the environment paths. Well not really looking to retrieve the value...but to invoke the value. App Paths start xpadder "%cd%\Player 1" "%cd%\Player 2" The above actually works in a batch script...provided there is the Apps Path value entered into the registry.

Okay in my fumbling around working on a rewrite of my Zinc loader...which entails switching from JoyToKey to Xpadder for very clear reasons...I've been mildly annoyed at not being able to count on where Xpadder will be located on a given persons system. It being placed with in "Program Files" is simple enough: start %PROGRAMFILES%\Xpadder\Xpadder.exe "%cd%\Player 1" "%cd%\Player 2" It being placed in the "Windows" folder is also simple: start %WINDIR%\Xpadder.exe "%cd%\Player 1" "%cd%\Player 2" or start %PATH%\Xpadder.exe "%cd%\Player 1" "%cd%\Player 2" It being placed in the "System32" folder is also simple: start %PATH%\Xpadder.exe "%cd%\Player 1" "%cd%\Player 2" or Xpadder.exe "%cd%\Player 1" "%cd%\Player 2" However I strongly feel that Xpadder should never be in the Windows or System32 folder...as its just making a mess. Placing it in "Program Files" is proper but not portable. Heh yeah I'm being anal. Now we could add Xpadder to the Application Paths; Example using "Program Files": [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\Xpadder.exe] @="C:\\Program Files\\Xpadder\\Xpadder.exe" Doing the above then makes Xpadder portable to some degree...tho ideally Xpadder is on something like Z:\ drive. Anyways then coding for it is simply: start xpadder "%cd%\Player 1" "%cd%\Player 2" heh plus you can also start the Run Box (Win+R) and type "Xpadder" and it'll fire up Xpadder. Now we can take it another step further...and generally viewed as improper...but less so than dumping stuff into Windows & System32 folders...and thats to add Xpadder's path to the environment variables paths; Example using "Program Files": [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment] "Path"=...;C:\Program Files\Xpadder\ That can also be done from the AutoExec.bat...but I'm suffering from OldTimers..hehe so not recalling how right now. Anyways then we can code for it like so: xpadder "%cd%\Player 1" "%cd%\Player 2" Well looking for the thoughts of others as to what should be done...as I can write scripts to automate adding the required registry entries based on where Xpadder is currently. Or am I simply having one of those blond moments and over thinking the simplest of things?

You should be able to find all the required files and help here. The above link has rom images (legally distributed) named to match the names used by the OverLays...so you only need to make a map file so that every thing humanly readable.

Yes donating is worth it. However the over sized lettering is not really welcome...bold would be good enough. Anyways I think both of those options are available without having to donate...I could be wrong tho. Mouse Emulation...well frankly I haven't tried this aspect of GameEx...but you should be able to try this your self. The quote about $20 is correct...until recently...Xpadder can do this and generally better and its free....BUT there are some KEY features to GameEx's controller mapping that have yet to be duplicated in Xpadder...so I generally use both to obtain the best end result. There are a lot of nice features for those that donate...however generally those are not the reason most donate...ether its out of love for the software...or to get rid of the time delay imposed on running it without having registered it. Originally I planned on donating...but the delay pushed me into doing so a LOT quicker than planned. I just figured my time was worth more than my money...so we parted ways. I would suggest you donate...save your valuable time, and support Tom who is always making updates to this software...there are a lot of cool things coming our way both from Tom and the community surrounding it. Anyways I'm a piss poor sales rep...course thats probably why I'm not one. *Update* Damn I'm getting slow.

Yes some folks know it. I use it for CD32...haven't setup anything else tho. I'm also stretched a little to thin right now to lend a hand....I got half a dozen projects going and none of them seem to be getting done any time soon. I'm sure in time someone will be around to aid...so hold tight...remember this is all volunteer...no one is getting paid to help anyone.

They should be the same files...well far as Mame. Typically if you do multiple systems each system goes into its own folder.

There currently is no way...BUT...and its a big BUT at that. There is a new build of Xpadder in the works code named T.Rex...which will solve this problem and a host of others once its done. It will be creating virtual gamepad\keyboard\mouse\... all at the driver level...so far as Mame knows...its getting raw data. This also opens up the door for controller combining...which has some corner cases where its nice to do. Anyways the keyboard driver is functional and may make a beta appearance in the next week or two...others will likely quickly follow...once the keyboard is finalized.

Yeah it can be done with AutoIt...and I'm working on it now...just trying to make sure every thing is clean and simple...not rewriting this again.

bkenobi - Hehe I would say thats spot on...I'm proud of you. hehe

Well I'd suggest using HyerSnap myself...then maybe use Xpadder to send the required key combo to trigger the capture of the active window...as other wise it is a pain in the ass...mainly if your trying to grab filtering...when the app doesn't support it...I don't know if Mame does or not...heh haven't taken a screenshot till now. Adultery would it be possible to tag these pic's so that they stand out just a little bit better when digging through a theme...ala [Mame] Fighting Games.png [Mame] ... I need to find out if one can alter a theme so that GameEx looks for images not using the default naming for GameEx's own icon's, but tagged icons...basically more attempts to bring theme folders more under control so one can fairly easily find stuff without being some sort of theme guru. [GameEx] Control.png [GameEx] DVD.png [GameEx] DVD Disc.png [GameEx] ... I've done a few & made some changes to the PSD...I lowered the opacity of the Reflection layer...I've shuffled all the layers around to make better room for titles...then added title names layers...I think I got them all...but don't quote me and be sure to double check. I used a dark navy blue for the stroke around the title text...figured its fairly close to black...but far enough to where we won't need to shift colors around to prevent holes from being shot into the title text.