- Joined
- Jan 24, 2007
- Posts
- 8,152
Help me Obi-Wan, you're my only hope.
For the last month/2 months I've been trying to set up Groovymame on a PC so I can throw it in my cab using crt_emudriver. This is not turning out well. I'm getting stress headaches trying to decipher posts on other forums written by people that barely speak english.
I'm computer-literate, but I'm no means a master with this stuff, so any precise instructions would be VERY welcomed.
The problem:
I was given this GPU by a friend that had usede it in his own MAME rig. It was bought specfically for this because it was supposed to have the absolute best compatibility with crt_emudriver.
I have a compatible mobo, and hunted down a copy of WinXP, as I was told that I needed it.
Using this tutorial, I downloaded the crt_emudriver for my graphics card, the latest groovymame64, the latest mame64, anything else it said I needed and followed the installation instructions to the letter.
The big problem I'm coming up with is that the ATI drivers I keep finding for crt_emudriver (I downloaded it here) are giving me drivers for some "Mobility HD 4330" card. Now, the graphics card works, because I downloaded the latest drivers for it and everything runs fine. However, crt_emudriver doesn't work with the latest drivers, I need to use this Catalyst (9.3 because it supports my graphics card), VMMAKER, Arcade OSD stuff. Also, different installation instructions that I've seen all say NOT to update the graphics card.
WTF am I doing wrong? Everyone says how "Easy" this is to set up, but I'm about to throw this thing out the window and be done with it. I really don't want to join the BYOAC forums to ask Calamity (the one who made crt_emudriver) 1 or 2 questions and possibly not get an answer.
SYSTEM:
CPU: It's an AMD, don't remember the exact specs
GPU: VisionTek 4350 512mb VT Retail
OS: Win XP SP3 64-bit(fresh install)
-4GB RAM (Anything more seems a bit overkill for MAME)
-It's not connected to the internet, thats not what I want this for just yet (maybe fightcade later on), and I don't plan to connect it anytime soon.
For the last month/2 months I've been trying to set up Groovymame on a PC so I can throw it in my cab using crt_emudriver. This is not turning out well. I'm getting stress headaches trying to decipher posts on other forums written by people that barely speak english.
I'm computer-literate, but I'm no means a master with this stuff, so any precise instructions would be VERY welcomed.
The problem:
I was given this GPU by a friend that had usede it in his own MAME rig. It was bought specfically for this because it was supposed to have the absolute best compatibility with crt_emudriver.
I have a compatible mobo, and hunted down a copy of WinXP, as I was told that I needed it.
Using this tutorial, I downloaded the crt_emudriver for my graphics card, the latest groovymame64, the latest mame64, anything else it said I needed and followed the installation instructions to the letter.
The big problem I'm coming up with is that the ATI drivers I keep finding for crt_emudriver (I downloaded it here) are giving me drivers for some "Mobility HD 4330" card. Now, the graphics card works, because I downloaded the latest drivers for it and everything runs fine. However, crt_emudriver doesn't work with the latest drivers, I need to use this Catalyst (9.3 because it supports my graphics card), VMMAKER, Arcade OSD stuff. Also, different installation instructions that I've seen all say NOT to update the graphics card.
WTF am I doing wrong? Everyone says how "Easy" this is to set up, but I'm about to throw this thing out the window and be done with it. I really don't want to join the BYOAC forums to ask Calamity (the one who made crt_emudriver) 1 or 2 questions and possibly not get an answer.
SYSTEM:
CPU: It's an AMD, don't remember the exact specs
GPU: VisionTek 4350 512mb VT Retail
OS: Win XP SP3 64-bit(fresh install)
-4GB RAM (Anything more seems a bit overkill for MAME)
-It's not connected to the internet, thats not what I want this for just yet (maybe fightcade later on), and I don't plan to connect it anytime soon.