@nintendoboy96 glad you got it going! For future reference, googling a md5 checksum will almost always get you to the file you need. Checksums use one of many algorithms to add up the 1s and 0s in a file making duplicate sums hard to come across. This is why a lot of software distribution platforms use it for verification. MD5 is long enough for it to be very effective with search algorithms.

@mitu it seems that in Debian (LXQT) this issue is not present. I think i'll just switch to it. I assume that this bug is related to the GNOME desktop environment

@nintendoboy96 said in Ms Pac-Man/Galaga:

Where do I get the full rom? I also want to mention that I am using mame2003.

Please read carefully the forum rules again - no asking for ROMs here.

I have been several different websites and I keep getting the file name 20pacgal.zip.

Yes, that's correct.

I also want to mention that I am using mame2003.

Make sure you have the right ROMset collection for Mame2003, it's all explained in the documentation page that @Ashpool posted.

@retropieuser555 yeah that's most certainly an option, but from what I've seen on the standalone, it isn't much different from the libretro core where you just go and manually load up the next disc, right? Disc Control > Eject Disk > Load disc.

That seems to work fine, I was just surprise to see the m3u format didn't want to pre-load the disc images.

@mitu thanks

It's been a while since I took another look into this, but I have a lead that this forum could possibly help with. On a side note, the Arduino forum was not very helpful at all. The only thing that I could think of was if the Arduino was being driven too much power (or if the power is inconsistent somehow), and the switched I have in the dance mat are acting as capacitors and letting some current through. I haven't done any measurements or math to look into this, but it seems very unlikely to me.

Asking chatgpt, I got lead to check permissions of the usb device, and even giving the decide all permissions does not help. However, I decided to check the dmesg log, and noticed something. I am transcribing this from a photo I took of the text on a CRC tv, so I apologize if there's errors.

[ 153.053753] usb 1-1.1.3 New USB device strings Mfr=1, Product=2 SerialNumber=3 [ 153.053758] usb 1-1.1.3 Product: Arduino Leonardo [ 153.053763] usb 1-1.1.3 Manufacturer: Arduino LLC [ 153.053768] usb 1-1.1.3 SerialNumber: HIDAF [ 153.067997] input: Arduino LLC Arduino Leonardo as /devices/platform/scb/61500000.pcie/pci0000:00/0000:00:00.0/usb1/1-1/1-1.1/1-1.1.3/1-1.1.3:1.2/0003:2341:0036.0003/input/input4 [ 153.068204] hid-generic: 0003:2341:8036.0003: input.hidraw2: USB HID v1.01 joystick (Arduino LLC Arduino Leonardo) on usb-0000:01:00.0-1.1.3/input2 [ 154.009506] cdc_acm 1-1.1.3:1.0: ttyACM0: USB ACM device [ 154.092227] usbcore: registered new interface driver cdc_acm [ 154.092232] cdc_acm: USB Abstract Control Model driver for USB *[illegible]* and USB adapter

A couple things I noticed here: The arduino is being read as an input into input 4, and it is being read as a HID joystick into input 2, and it is being read as an ACM device. Do any of you think that being registered as multiple inputs/systems could cause the issues I am seeing? And if so, how can I make Debian only recognize the arduino as one device? I am not linux savvy enough to know how to do that.

Thanks!

@signtoo Here is a Pi5 version of RGBPi OS4 https://github.com/forkymcforkface/RGBPi-Bookworm

@Folly Sure, once I have this Pi 5 set up so I can run 0265.

Please add some description to your issue and the system info as requested in https://retropie.org.uk/forum/topic/3/read-this-first.

This error is most common when you don't have write permissions for the specified location. The core is unable to write to or even create the system directory.

User read/write permissions, or login as root user. Also, make sure the sd card isn't set to read only.

For what it's worth, I bought one of these SJ@JX controllers on alix, and it wasn't detecting as a USB gamepad (or wasn't working at all).

I download and ran the .exe that @bryantjblair shared and it's now working and detecting as I'd expect.

@gargoyle73 said in Vertical Screen Rotation on RP4 400 HELP:

SO what interface do I use to read and alter MAME configs? Can you walk me through steps?

Start the 'File Manager' (mc - Midnight Commander) from the RetroPie system. It has an interface similar to the old Norton Commander, which allows you to browse the filesystem and operate on files/folders. Go to the folder where the retroarch.cfg is located (/opt/retropie/configs/all/) and modify the file by selecting it and pressing F4. This will start an editor, from which you can modify the file and save it afterwords.

There are lots of links with documentation/videos on how to use Midnight Commander - see for instance https://www.tecmint.com/midnight-commander-a-console-based-file-manager-for-linux/ or https://www.linode.com/docs/guides/how-to-install-midnight-commander/.

4.5.1 is really old and I don't think it's supported anymore - i.e. there are no more binary packages to download for the Raspbian version on which it was based. You may try installing reicast from source to get it back.

I got it to work by researching kernel. I ran lr-parral64 and edited a line in retroarch config. Thank you for your help!

@mitu Thanks for the reply to both of you.

It turns out, I had set my ui settings to detailed. I switched it over to video and made sure the theme I was using supported video and... bingo. all set.

By the way, I found the solution of this problem. You must edit ~/.config/eduke32/eduke32.cfg. You must use there ScreenMode = 0, ScreenHeight = 576 and ScreenWidth = 720 (you can play with ScreenHeight and ScreenWidth to fit the picture to the screen).

I ended up fixing the problem on my own.

The issue was that Drastic and Retroarch were trying to render the resolution at 640W x 480H, which would cause squishing issues.

By adding in:

hdmi_cvt 480 640 60

Into the config.txt, I was able to give drastic another resolution to render at, solving the issue. For retroarch, I made the auto fullscreens resolution the 480W x 640H that the display was native to, which also solved the squishing.