Main Restorations Software Audio/Jukebox/MP3 Everything Else Buy/Sell/Trade
Project Announcements Monitor/Video GroovyMAME Merit/JVL Touchscreen Meet Up Retail Vendors
Driving & Racing Woodworking Software Support Forums Consoles Project Arcade Reviews
Automated Projects Artwork Frontend Support Forums Pinball Forum Discussion Old Boards
Raspberry Pi & Dev Board controls.dat Linux Miscellaneous Arcade Wiki Discussion Old Archives
Lightguns Arcade1Up Try the site in https mode Site News

Unread posts | New Replies | Recent posts | Rules | Chatroom | Wiki | File Repository | RSS | Submit news

  

Author Topic: MAME - Access Violating when disabling HWSTRETCH?  (Read 873 times)

0 Members and 1 Guest are viewing this topic.

sofakng

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 646
  • Last login:February 18, 2021, 04:19:21 pm
MAME - Access Violating when disabling HWSTRETCH?
« on: June 20, 2008, 09:22:59 am »
I'm trying to achieve the best possible output on my television but I'm getting an access violating when I disable hwstretch.  I've tried using DirectDraw and Direct3D (along with nohwstretch) but I keep getting an access violation.  When I enable hwstretch then it works fine.

I'm using the latest version of MAME and a fresh install of Windows XP SP2 all patched but without .NET installed.

Here is the exact message I'm receiving:

Quote
-----------------------------------------------------
Exception at EIP=009413BF: ACCESS VIOLATION
While attempting to read memory at 00000028
-----------------------------------------------------
EAX=00000000 EBX=0022FC28 ECX=00000001 EDX=0022FC28
ESI=00000000 EDI=00000000 EBP=0022F778 ESP=0022F760

Minwah

  • Trade Count: (+3)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 7662
  • Last login:January 18, 2019, 05:03:20 am
    • MAMEWAH
Re: MAME - Access Violating when disabling HWSTRETCH?
« Reply #1 on: June 20, 2008, 12:24:20 pm »
I've had this a few times with v0.125u6...DirectDraw enabled.

Strangely I had the error, and then run the same commandline again, and it worked OK. Had this happen a day or two ago, but I can't say I spent any time trying to figure out why  ???