Mame issue osd_init failed? *first cab*

[mudmonkey]

I’m not quick to post a question because I know that lots of times within a few hours of posting I find the answer (or figure it out) on my own. But I think this time I’m going to have to ask for some help.

I’m setting up my first cabinet. I have no formal training with software…I’m just a guy who likes arcade machines.

Some background before I get to my question:
I’m using a computer that is comprised of free parts that were given to me. It’s a HP Vectra VL400 DT. The video card is integrated into the motherboard (I have a sneaking suspicion that this may be my problem…).

I wanted to build a cab that I could hide windows and use the joystick/buttons for navigation. The reading I did led me to believe that Mame Windows + Mamewah would be best to use. Again, I know little about computers…so this is a challenge. After getting many errors (mostly “Unable to initialize Direct3D”) I decided to give up and go to Mame32.

It had similar problems. I went into the options for one game and changed the display setting from Direct3D to GDI. Now that game works.

My Question: Is there a way to change the Mame.ini file so that all games would be GDI rather than Direct3D? I should explain that I have no idea what GDI means…but that change was the one that fixed my problem (like I said above I like to try to figure things out for myself). I read everything I could find about the Mame Command Line Options…but I can’t see anything that has to do with GDI.

I tried some of what is in this post: http://forum.arcadecontrols.com/index.php?topic=59283.0

…no effect.

Any suggestions would be greatly appreciated.

[mudmonkey]

okay...i figured it out...sorry...this is why reading is much better than posting.

found the info here: http://www.mameworld.net/maws/mamesrc/docs/windows.txt
(for anyone who finds this post while having the same problem)

now i have to solve my new error: "error creating DirectSound:"
it's a never ending road paved with errors.

[Silver]

I would suggest tracking down the latest software for your motherboard.

Or just find out what the integrated chipset is (e.g. an intel one) and download the latest drivers from the manufacturers website (e.g intel.com).

Do the same for your onboard sound.

Then go to windowsupdate.com, and install the latest version of DirectX.

You may find this solves your sound/graphic problems.

[mudmonkey]

Okay…I did all of that. I downloaded Aida32 and wrote down all the info. I then hunted the web for all the drivers I could find. After installing them all I have fixed the graphics problems, however the audio drivers I’ve found so far haven’t stopped the “error creating DirectSound: 88780078 osd_init failed” message.

I’ve searched for info on this error and have found others with similar errors, but really, most of the replies are just not helpful (most are insulting).

I can get Mame Windows to run with a command prompt that has “-nosound”…but really, it’s a short term fix…I’d like to have some sound on my cab.

Anyone have any idea at all what could be the problem?
Aida32 says I have the “AC’97 Audio Controller” I downloaded the drivers for that and installed them, but it doesn’t seem to have made any difference at all (yes, I restarted the machine).

Help?

I swear that when I’m old and gray (and know what I’m doing) I will answer stupid noobie questions on this forum.

[mudmonkey]

I decided to change the title of this post rather than start a new one. This new title is more to the point of the issues that I’m having.

I installed Mame Windows on a HP Vectra LV400 (Pentium III 800MHz) running Windows 98SE.

First error was “Unable to initialize Direct3D osd_init failed”
I fixed that by editing Mame.ini with “GDI rather than D3D”
I’m not at all happy with that fix. I’ve read enough to know that this will slow things down.

Second error (after changing to GDI) was “Error creating DirectSound: 88780087 osd_init failed”
This too I was able to get around by editing Mame.ini so that the sound is turned off.

SO, I have a slow mame program with no sound. Not what I was envisioning. 

I’ve downloaded many many drivers but none have fixed the problem. When I turn back to “D3D” same error comes back.

Grrrr…

I decided to switch to my back-up machine... Compaq Desktop Pentium III 550 MHz (that’s why it’s the backup). This time I started with all the drivers. Installed Mame again. Same problem. Really? Yes really. 

Okay…so is this something that might be fixed by an earlier version of Mame? Or is this something wrong with the way I’ve installed win 98se? 

I seriously could use some help. I’ll be your best friend?

[mudmonkey]

okay...going on 2 days of working on this.

i downloaded every single audio driver i could find for both machines and installed them all... one from each set worked. Each of the ones that fixed the problem asked me to put the win 98se CD back in. Not sure why that happened.

Anyhoo. Now i have sound. But, i still haven't figured out the d3d problem. Still running in GDI...it bogs down a little (causing the sound to do strange things).

Guess i'll work on tackling the d3d issue now.
COuld this be a problem with the version of MAME i'm using?