Macguvyer

Yes, I just did an over the top install, thinking this would work as well. No change. Goes to black screen for 2 seconds after I select a MAME game. Outside of GameEx, MAME works completely smooth. I've tried this with 64 bit MAME, 32 bit varients, and MAMEUIFX. This is coming from a guy who's been playing around with GameEx for 5 years. I'm totally baffled.

I've done a fair amount of tinkering and still no success with this 64 bit MAME version. Again, to be clear, it works fine on its own. In case it had to do with my ROMset being the wrong version, I now have a V160 split ROMset and I've updated the path correctly. Did an update list, still going to black screen after I try various MAME games. Attached is my log.txt, and GameEx.ini. Would love some further suggestions... Thanks! log.txt GameEx.ini

The issue was that I had installed MAMEUIFX in Program Files, and there were issues with permissions / admin rights that didn't work, no matter what I tried. Once I reinstalled it in C:/Emulators, it worked fine. The shader is absolutely fantastic! . I was blown away with the analogue feel. I'm curious though, I'm guessing that using MAMEUIFX with GameEx is always going to bring up the MAMEUI GUI? Is it difficult to set this shader up with vanilla MAME 160, instead?

Thanks Draco and DazzleHP. I did a pile of reading and I'm pretty clear on how this works with UAC, and how where you install matters. I do have kids using this machine and I think that UAC does make sense now that I understand it better. I simply re-installed mame64 into c:/emulators and BAM, it works fine, no UAC nonsense. Well, to clarify, MAME works on its own, I'm having trouble getting it to work with Gameex (black screen despite carefully checking the setup wizard), but I'll continue troubleshooting and report back on a new post.

Windows 7 64 bit user, trying to update from MAME 149 to 160. Getting some strange behavior that's driving me nuts. First of all, the previous 64bit verson of MAME 149 worked beautifully with Gameex. Installed in a directory named "MAME" in the Program Files directory. When I click on MAME64.exe in this directory, it just works. No UAC prompt, it just starts. When I tried installing MAME 160 into a directory named "MAME160" in the Program Files directory, I get different behavior. Let's forget about Gameex for a second, which only gives me a black screen now. The problem is in permissions or administrator rights or some damn thing. When I click on MAME64.exe in this directory, The UAC (User Account Control) screen comes up. Why does this new installation of MAME 64 require UAC when the old one did not? I think this UAC screen is what is stopping Gameex. Right clicking MAME64.exe and running as administrator still brings up the UAC screen. In fact, right clicking properties of MAME64.exe and checking the compatibility tab, the checkbox is in fact "run this program as an administrator". So why does the UAC screen come up? Strangely, the V149 installation which is the same /program files directory, does not have "run this program as an administrator" checked, but yet runs fine without a UAC screen. Any suggestions? I'm pretty baffled. I can install 160 in a directory on my desktop and avoid the UAC nonsense, but normally I would install a program where the rest of my 64 bit programs go, which is in c:program files. How did I get V149 installed in that directory before? Thanks for any advice.

Yes, Draco you were right as to the problem. I'm using Windows 7 and I'm logged in with the administrator account. I'm a bit confused why I can't get the 64 bit version to save, but it does work properly when I right click and "run as administrator". Shouldn't this normally work with admin rules because it was installed in the administrator account? Thanks U-man for the tip on the Open GL options, got it.

I`ve been playing around with MAMEUIFX64 V0.160.1, but it doesn`t seem to remember all the folders for ROMs, etc. So each time that I start it, I have to manually point it to all the folders. Any suggestions? The 32 bit version doesn't have this issue, so I'm using that for the time being. I'm also interested in where you enable OpenGL video mode. On the default game options tab, the OpenGL has all the options greyed out, so I can't enable GLSL in OpenGL options

Hi Lurker, I'm not the person to list all the benefits of WinUAE loader, but I can name a few. It's designed to make running huge piles of Amiga games much easier. First of all, it's possible to setup to load games almost instantaneously via the WHDload set which is a real treat. Secondly, you're able to very quickly setup a huge number of games right away with screencaptures (snaps) and settings, instead of manually setting up each one. I've never tried, but how difficult is it to setup let's say 100 Amiga games on Gamex using only WinUAE, without WinUAE loader?

Hi Evilforces. WinUAE loader is currently only designed to be used withGameBase Amiga, SPS and WHDLoad game sets. . I actually wasn't aware of the "no intro" set, and I can see the appeal if you're a purist and want the 100% original Amiga game experience. The downsides would be the load time and occasional manual code protections. Personally, the almost instant starting of games via WHDLoad makes this the clear winner in my books. Many of the WHDLoad ROMs don't have intros, anyway.

Not sure which set you were referring to when you read that they might not be supported. However if you have the WHDLoad set working outside of GameEx, then it shouldn't be too difficult to get it working inside. WinUAELoader works with 3 sets: WHDLoad, SPS and Gamebase Amiga. So in theory you can have all 3 of those sets working in GameEx by using WinUAE Loader. (You can also set up the Gamebase Amiga set directly in GameEx, which I found easier to set up for the Gamebase Amiga set) There are a number of benefits to using WINUAELoader compared to Gamebase. Easy setup of the WHDLoad set is the most important which means lighting quick game starts, followed by the ability to use video snapshots, among other things. The advantage of using Gamebase is the fact that GameBase is basically a complete set of every single game and has absolutely everything, plus it's easy to setup in GameEx. But the games load slowly. If you need detailed instructions of how to setup the WHDLoad rom set in GameEx via WinUAE Loader, check out the following: http://www.gameex.info/forums/topic/14158-resolved-gameex-and-winuae-amiga-games-in-gameex/?hl=whdload#entry119823 Gamebase Amiga files are located here: http://gbamiga.elowar.com/#Download I don't understand what's going on with bu22.com. Hopefully it's temporary?

There are a number of benefits to using WinUAE loader with Gameex, but the most awesome is that you are able to easily set up to use WHDload versions of Amiga games. This is a massive plus because WHDload versions load almost instantaneously, like a cartridge. Once you try this, you'll never go back to standard game ROMs. Another way to easily set up a massive pile of instant Amiga games instead of using WinUAEloader is to import Gamebase Amiga. This works easily and is worth trying, although you end up with a list of thousands of games and it has a huge drawback of not allowing video snaps in your Gameex menu. Instead you can only have still images which makes the Amiga games feel lifeless and old in your Gameex collection. With WinUAE loader however, you can easily replace boring old still snaps with high quality video snaps, alongside your favorite MAME, SNES, etc games. The Amiga game library is so massive with some real standouts and it's well worth the effort of setting up on GameEx.

I've got the SPS and WHDLoad sets working smoothly in GameEx with your great program, Headkaze. I also have 2711 out of 4953 games working in the Gamebase set, via the "Run ROM" feature, but only directly in WinUAE Loader. (Let's ignore why they don't all show up for a moment, even though I'm using a complete V1.6 Gamebase ROMset.) The trouble I am having now is that I can't get the Gamebase set to run via GameEx and WinUAE Loader. The window opens, it says it is going to run the game, and then flash, the GameEx screen returns. Any suggestions? I have double checked that the paths are correct in GameEx. I don't understand because it is working fine in WinUAE Loader. (I do have the Gamebase set working quite nicely in the direct usage (not via WinUAE Loader) in GameEx quite nicely, so I know it should work. What exactly is the difference / benefit between running the Amiga Gamebase in GameEx with or without WInUAE Loader? Thanks!

Thanks for the clarification on topic titles guys. Was happy to take a few minutes and document the steps I took. It's been a fun puzzle.

I have to admit that I don't know how to change the topic title! Is this only possible for the person who started the topic?

More details. Finally got the Amiga SPS ROMset to work correctly with WinUAE Loader. It was a bit tricky. There are two naming schemes for the SPS ROMs. One collection has the following naming system: 0001_Wizard Warz.zip 0002_Commando.zip 0003_Cybernoid II- The Revenge.zip. This is the only set that I could get to work correctly with WinUAE Loader. It's hard to find on the net. (Read important note below about the MAP file fix which I needed to adjust) The other SPS ROM set which is more readily available is located inside the giant 31.6 Gig Commodore Amiga TOSEC v2012-04-10. Unfortunately I could not get these SPS ROMs to work with WinUAE loader and if other people have tried this it's probably driving them crazy. Here is how they are named in the TOSEC package: 1st Division Manager (1992)(Codemasters)[1800].zip Commando (1989)(Elite)[0002].zip I'm sure there is a way to map the TOSEC ROMset but I do not know how to do it. So you need the SPS set with the other naming scheme! However, there was one important final step that I needed to adjust before it worked completely smooth in Gamex. There is something wrong with the Mapfile that WinUAE Loader creates, at least on my system. I think this is because the first SPS ROM appears to have a blank name when you open it in WinUAE Loader (my set did, at least). This made the SPS Map file completely fizzle in GameEx. So what I did is I loaded this map file into Wordpad and simply deleted that one entry. Then I moved it over to the correct place in GameEx and voila, all of the SPS games work fine now (for the first time!) Here are very specific instructions, which are only necessary if you get the message in GameEx (No SPS Roms found, or something like that, when you try to Run SPS games) - Run WinUAE Loader. On the settings tab, press the button marked "Generate Map Files" under GameEx Options. - This creates a map file called [PC] Commodore Amiga (SPS).map (ignore the other map files, this fix is specific for SPS ROMs) - On my machine the file was located in C:\Program Files (x86)\WinUAELoader\Data\GameEx\MAP FILES - Click on this file and open it in Wordpad. - Delete the first line which is "1151_Slam Tilt - The Pinball Game (AGA)_Disk1.zip|" - Save this Map file. - Copy this Map file into the correct location in GameEx. On my machine is C:\GameEx\MAP FILES - Save this Map file here, and overwrite if necessary. - Enjoy the SPS ROMset. Remember you need to locate SPS ROMs which are labelled with the numbers in front, like "0001_Wizard Warz.zip" One last bit of info. The WHDLoad Set is great because of the speed that the ROMs load. However the SPS set is unique in that it contains only retail versions of games, without crack screens etc. So for the purist these are actually quite nice and the reality is that these unaltered versions are actually extremely rare. They do take longer than the WHDLoad Set but it's nice to have both sets. Hope this is helpful for someone else. I was not going to let a full Amiga setup beat me! MacGuyver.

After doing a split second "print screen" keypress the moment the shell appeared, I was able to finally see the error which was "WinUAELoader.exe" is not recognized as an internal or external recognized command, operable program or batch file. This made me realize that there was somehow a paths problem. It turned out when I reinstalled "WinUAE Loader", by dragging the .ini files from its setup to GameEx, it reset the working directory to C:\Program Files (x86)\WinUAE\WinUAE Loader instead of C:\Program Files (x86)\WinUAE Loader which was where I had installed it on my machine. They were so similar that I didn't recognize that it had changed. My apologies, I have the WHD set working fine again now with WinUae Loader. Will keep troubleshooting the other WinUae Loader ROMsets, there might be something unique (resetting the paths correctly didn't fix those, but I'm not one to give up) Thanks for the assistance, earlier. MacGuyver

Alas, the suggestion of deleting the cache files did not solve the problem. Still appear to have some sort of corruption. Any other ideas? I'm working in debug mode - there appears to be an error just after the emulator tries to run the game but the shell screen closes instantly so I can't see the message.

Thanks for the tip, guys. I'll try that tonight, and report back.

Hi there, I am having a strange new problem with GameEx and I'm having a heck of a time trying to figure out what is causing it. Recently I set up WinUAE Loader and it was working like a dream. There were 3 ROMsets that I was playing around with. SPS, Gamebase, and WHDLOAD. One of the features in WinUAE Loader is a "check ROMs" feature which allows you to confirm that you've set it up correctly and all the ROMs are there. You can also test ROMs via this method. I noticed that it was indicating that some of the ROMsets weren't complete, so I located alternate ROMs and rechecked, and WinUAE Loader indicated that I had in fact solved the issues and 100% of the ROMs were working for the SPS and WHDLoad sets. (Gamebase wasn't 100% but let's ignore that for now) Since I had created new directories with the corrected ROM sets, I had to tell GameEx where the new ROMs were since the directory changed so I did that with the Setup Wizard. (The games emulate just fine via the WINUAE Loader ROM test so everything seemed great) Only problem is, now in GameEx, not a single game will run in the via WinUAE Loader from either of the 3 ROMsets. In fact, now it says that none of the SPS ROMs are even showing up, and the games in the WHDLoad section appear corrupted (Game list is fine, but clicking on a game brings up a list of random words in GameEx). I have double checked that the paths are correct in the Setup Wizard profile. I'm totally stabbing in the dark here that somehow some file permissions got messed up, and GameEx is having trouble accessing certain files, but it's a total guess. Also in the GameEx log file I see the following: Restoring Emulator Database From Cache: 122:05:13.2 13/03/2014: Index was outside the bounds of the array.22:05:13.2 13/03/2014: at GameEx.GameEx.MainForm.b(Int32 A_0, Int32 A_1, Boolean A_2)22:05:13.2 13/03/2014: No Database Data: 222:05:13.3 13/03/2014: No Database Data: 3What's strange is that I've copied new versions of the database files from the WinUAE Loader setup to replace the old ones in the GameEx directory, and this does not seem to help. I would love any suggestions because I'm pretty stumped. I had it working so nicely, too! Thank you, MacGuyver PC Commodore Amiga (GameBase).ini PC Commodore Amiga (SPS).ini PC Commodore Amiga (WHDLoad).ini GameEx.ini log.txt

Welcome and have fun! Good job on sleuthing out solutions on the forums, too.

I noticed that by default when I set up Gamebase Vic20, that the VICE emulator default set up means that pressing ESC does not end the program, but rather is mapped to the "Run/stop" key on the Vic20 keyboard. So it was a real pain to get back to the GameEx menu after I had played a Vic game. It's fairly simple to change the keyboard map on Vice. Attached is a modified Vic20 keyboard layout which allows the ESC key to behave normally. (The Caps lock key also works as the Vic Run/Stop key if you need that functionality in the emulator still) This file needs to go into VICE install directory, in the VIC20 subdirectory.. You will see other .KVM files which are other Keyboard maps. One you have saved the new keyboard map file here, run xvice.exe and choose the settings menu, then keyboard settings and select the Escape Quit.vkm file I've attached below. Now you can have normal ESC functionality, and easily leave Vic20 emulation and go back to the GameEx menu. If you want more instructions about editing Keymaps with VICE, the following page is helpful: http://www.lemon64.com/forum/viewtopic.php?t=49551&sid=a1176d014db7049e6c60e432845c9fe9 Edit: I had trouble attaching my file (you aren't permitted to upload that kind of file is the message), so I've pasted the keyboard file text below. Simply copy and paste with a text editor like Notepad a .KVM extension and follow the instructions above. # VICE keyboard mapping file which allows normal ESC function## A Keyboard map is read in as patch to the current map.## File format:# - comment lines start with '#'# - keyword lines start with '!keyword'# - normal line has 'keysym/scancode row column shiftflag'## Keywords and their lines are:# '!CLEAR' clear whole table# '!INCLUDE filename' read file as mapping file# '!LSHIFT row col' left shift keyboard row/column# '!RSHIFT row col' right shift keyboard row/column# '!VSHIFT shiftkey' virtual shift key (RSHIFT or LSHIFT)# '!UNDEF keysym' remove keysym from table## Shiftflag can have the values:# 0 key is not shifted for this keysym/scancode# 1 key is shifted for this keysym/scancode# 2 left shift# 4 right shift# 8 key can be shifted or not with this keysym/scancode# 16 deshift key for this keysym/scancode# 32 another definition for this keysym/scancode follows## Negative row values:# 'keysym -1 n' joystick #1, direction n# 'keysym -2 n' joystick #2, direction n# 'keysym -3 0' first RESTORE key# 'keysym -3 1' second RESTORE key# 'keysym -4 0' 40/80 column key# 'keysym -4 1' CAPS (ASCII/DIN) key# !CLEAR!LSHIFT 1 3!RSHIFT 6 4!VSHIFT RSHIFT #0 -1 -1 0 /* (no key) */1 0 3 8 /* ESC -> Run/Stop */2 0 0 8 /* 1 -> 1 */3 0 7 8 /* 2 -> 2 */4 1 0 8 /* 3 -> 3 */5 1 7 8 /* 4 -> 4 */6 2 0 8 /* 5 -> 5 */7 2 7 8 /* 6 -> 6 */8 3 0 8 /* 7 -> 7 */9 3 7 8 /* 8 -> 8 */10 4 0 8 /* 9 -> 9 */11 4 7 8 /* 0 -> 0 */12 5 0 8 /* Minus -> Plus */13 5 7 8 /* Equal -> Minus */14 7 0 8 /* Backspace -> Del */15 0 2 8 /* TAB -> Ctrl */16 0 6 8 /* Q -> Q */17 1 1 8 /* W -> W */18 1 6 8 /* E -> E */19 2 1 8 /* R -> R */20 2 6 8 /* T -> T */21 3 1 8 /* Y -> Y */22 3 6 8 /* U -> U */23 4 1 8 /* I -> I */24 4 6 8 /* O -> O */25 5 1 8 /* p -> P */26 5 6 8 /* [ -> @ */27 6 1 8 /* ] -> * */28 7 1 8 /* Return -> Return */29 0 5 8 /* Left Ctrl -> CBM */30 1 2 8 /* A -> A */31 1 5 8 /* S -> S */32 2 2 8 /* D -> D */33 2 5 8 /* F -> F */34 3 2 8 /* G -> G */35 3 5 8 /* H -> H */36 4 2 8 /* J -> J */37 4 5 8 /* K -> K */38 5 2 8 /* L -> L */39 5 5 8 /* ; -> : */40 6 2 8 /* ' -> ; */41 0 1 8 /* ` -> Left Arrow */42 1 3 2 /* Left Shift -> Left Shift */43 6 5 8 /* \ -> = */44 1 4 8 /* Z -> Z */45 2 3 8 /* X -> X */46 2 4 8 /* C -> C */47 3 3 8 /* V -> V */48 3 4 8 /* B -> B */49 4 3 8 /* N -> N */50 4 4 8 /* M -> M */51 5 3 8 /* , -> , */52 5 4 8 /* . -> . */53 6 3 8 /* / -> / */54 6 4 4 /* Right Shift -> Right Shift */55 6 1 8 /* Grey * -> * */#56 -1 -1 0 /* Left Alt -> (no key) */57 0 4 8 /* Space -> Space */58 0 3 8 /* Caps Lock -> Run/Stop */59 7 4 8 /* F1 -> F1 */60 7 4 1 /* F2 -> F2 */61 7 5 8 /* F3 -> F3 */62 7 5 1 /* F4 -> F4 */63 7 6 8 /* F5 -> F5 */64 7 6 1 /* F6 -> F6 */65 7 7 8 /* F7 -> F7 */66 7 7 1 /* F8 -> F8 */#67 -1 -1 0 /* F9 -> (no key) */#68 -1 -1 0 /* F10 -> (no key) */#69 -1 -1 0 /* Num Lock -> (no key) */#70 -1 -1 0 /* Scroll Lock -> (no key) */#71 -1 -1 0 /* Numpad 7 -> (no key) */#72 -1 -1 0 /* Numpad 8 -> (no key) */#73 -1 -1 0 /* Numpad 9 -> (no key) */#74 -1 -1 0 /* Numpad - -> (no key) */#75 -1 -1 0 /* Numpad 4 -> (no key) */#76 -1 -1 0 /* Numpad 5 -> (no key) */#77 -1 -1 0 /* Numpad 6 -> (no key) */#78 -1 -1 0 /* Numpad + -> (no key) */#79 -1 -1 0 /* Numpad 1 -> (no key) */#80 -1 -1 0 /* Numpad 2 -> (no key) */#81 -1 -1 0 /* Numpad 3 -> (no key) */#82 -1 -1 0 /* Numpad 0 -> (no key) */#83 -1 -1 0 /* Numpad . -> (no key) */#84 -1 -1 0 /* SysReq -> (no key) */#85 -1 -1 0 /* 85 -> (no key) */#86 -1 -1 0 /* 86 -> (no key) */#87 -1 -1 0 /* F11 -> (no key) */#88 -1 -1 0 /* F12 -> (no key) */89 6 7 8 /* Home -> CLR/HOME */90 7 3 1 /* Up -> CRSR UP */#91 -1 -1 0 /* PgUp -> (no key) */92 7 2 1 /* Left -> CRSR LEFT */93 7 2 8 /* Right -> CRSR RIGHT */#94 -1 -1 0 /* End -> (no key) */95 7 3 8 /* Down -> CRSR DOWN */#96 -1 -1 0 /* PgDown -> (no key) */97 6 0 8 /* Ins -> Pound */98 6 6 8 /* Del -> Up Arrow */#99 -1 -1 0 /* Numpad Enter -> (no key) */#100 -1 -1 0 /* Right Ctrl -> (no key) */#101 -1 -1 0 /* Pause -> (no key) */#102 -1 -1 0 /* PrtScr -> (no key) */#103 -1 -1 0 /* Numpad / -> (no key) */#104 -1 -1 0 /* Right Alt -> (no key) */#105 -1 -1 0 /* Break -> (no key) */#106 -1 -1 0 /* Left Win95 -> (no key) */#107 -1 -1 0 /* Right Win95 -> (no key) */ ## Joystick 1##KP_0 -1 0#KP_1 -1 1#KP_2 -1 2#KP_3 -1 3#KP_4 -1 4#KP_5 -1 5#KP_6 -1 6#KP_7 -1 7#KP_8 -1 8#KP_9 -1 9 ## Joystick 2##w -2 7#e -2 8#r -2 9#s -2 4#d -2 5#f -2 6#x -2 1#c -2 2#v -2 3#space -2 0 # Restore key mappings91 -3 0 /* PgUp -> RESTORE */

I'm trying to link the Vic20 and Commodore 64 video snaps from emumovies to the Gamebase setup that I have set up so nicely in GameEx. I'm hoping Tom that there is some straightforward method that you're about to implement, perhaps if someone created a map file to connect the video snap file name to the Gamebase ROM name, which would allow the Gamebase to over-ride the still snaps and defer to the video snap when available. This wouldn't be too crazy and it would be so nice to have the Gamebases working with video snaps!

Glad to help! There are some wonderful games on that system, I hope more people go for it.

NicolasRaphael, Don't give up on Amiga Integration, you're missing out! I'm happy to give you a hand. Right now I've got Amiga working wonderfully. The instructions I used were located here which were provided by stigzler: http://www.gameex.info/forums/topic/12876-amiga-winuae-setup/?hl=amiga I did not need to use any command line methods. WinUAE loader is an incredible tool that works very well with Gameex and I found it to be seamless once I set it up. I highly recommend using the WDHLoad ROMs becauase they start almost instantly, like a cartridge (I recommend registering to eliminate the nag screen). I also have put some time into the other Amiga ROM sets such as the Gamebases which you may end up setting up for important ROMs which are not in the WHDLoad set and that you're willing to wait 1-2 minutes to load like the good old days. (I'm sure someone has come up with an easy way to trigger the hyper load speeds in WinUAE and then turn this off when the game starts but I don't know how to do this) Below are stigzler's instructions which I am reposting below. I've filled in a few more details which may clarify some steps: 1. Go through the GameEx setup and install the WinUAE emulator. (I'm using WinUAE V2.6.1. You can download via GameEx or you can set up yourself) 2. Go to this page : http://headsoft.com.au/index.php?category=winuaeloader 3. Read through the notes on the above page carefully, they are pretty straightforward, but there are a few steps to complete. You will need to move some files into specific GameEx folders. Check your work carefullly. 4. Download and install WinUAE Loader from this page (Latest is V1.78) 5. You'll need some bios files - install as instructed (see step 3. Details are on the WinUAE Loader page above) 6. Use the GameEx setup Wizard to properly integrate WinUAE Loader into GameEx. This is done on the Emulator selection screen and is pretty straightforward. Choose "Commodore Amiga (WHDLoad)" to start and enable with a checkmark on the left. You should also choose "Commodore Amiga (SPS),Commodore Amiga (Gamebase) and Commodore Amiga (Demobase) although keep in mind you will need to setup these romsets for these to work correctly of course. If you don't see these option in the list on the right, then you didn't do step 3 correctly. 7. (Power tip#1) if you want your Amiga game names in GameEx to look cleaner, use the "create mapfile" function by running WinUAE Loader.exe separately from Gameex once all the ROMs are set up. It will generate a .map file in the location WinUAELoader/data/gameex for the appropriate ROM set. You need to locate this file and move it to the correct Gamex folder where it looks for Maps. On my machine this was C:GameEx/Map files. 9. Under advance emu config - point to the mapfile you just moved to the GameEx map folder. (I don't think I needed to do this step - it happened automatically I think - but check for sure). The result will be a very clean list of Game names. 10. Go to Emumovies and download the Amiga snaps (stills) and the videos so that your games show up in all their glory properly in GameEx. 11. Profit! A big thanks to all the coders behind WHDLoader, WinUAE Loader, and of course GameEx. It really does take all the hard work out of the process and makes it seamless. Let me know if you have any questions.

That did it. Sorry for the delayed thanks, I've been caught up with real life for a few days. I really appreciate the help.