windows xp woes!!!!!!!!!!!!!!!!!!!1 :(

Archive of the old message board

Moderator: Chad

Locked
Game Guru

windows xp woes!!!!!!!!!!!!!!!!!!!1 :(

Post by Game Guru »

Hi
<p>

I run DOS mame with arcade at home...

<p>

When I install the new version (57) I get no sound and no joystick control even though I can see the options have been selected on the command line?

<p>

If I go back to mame 56 it works fine?

<p>

If I select my 1024 card in the command line line it just goes back to the arcade@home menu, however, it works fine on 56??

<p>

Any idea?

<p>

Also, how do u remove that blur effect on winmame?

<p>

Thanks in advance!

<p>

GG

--
virtualinsanity@blueyonder.co.uk
Chad

Post by Chad »

are you talking about how mamew looks "smooth" around the pixels? i
noticed that too, it didn't really bother me much since i figured it
was just my new computer monitor and video card, but you have this
same problem, it it would be nice to douse it to nice square sharp
pixels like i'm used to. I still can't get any dos mame to work with
my xp setup, but i haven't yet tried the arcade at home, will try
some this weekend hopefully.

--
churritz@crash.cts.com
Barry Rodewald

Post by Barry Rodewald »

WinXP is not really designed to run DOS apps such as MAME, but you
could try using VDMSound. It's a SB16 emulator that works with DOS
apps under WinNT4/2K/XP.

<p>

As for removing the blurring, you can disable the hardware stretching
with the -nohws switch. The blurring is done by your video card
drivers, so there isn't a lot that can be done about.

--
bsr@hnpl.net
Chad

Post by Chad »

ahhhh, square pixesl again, actually with my old ati all in wonder
mamew streched the pixels pretty square, but the geforce3 seems to
strech them with blurriness, eh i can deal with out exact
perspectives to see nice square pixels, thanks barry.

<p>

supposedly arcade at home will run dos mame under xp, mame56 anyway,
i'm going to try it one of these hours, hopefully, and try to figure
out how it does it, since i sure can't run on it by itself, must be
some special pif setting.

--
chad
Locked