Yes it is still available, just update Kodi first in RetroPie-Setup before downgrading.

0_1510744328164_Screenshot from 2017-11-15 11-09-55.png

Update Kodi first in RetroPie-Setup, than you can downgrade.

@proxycell Thanks mate. I sent you another reply lol

@shayne66 OK so I have no experience with that chipset. However, a quick Google around revealed that Foxconn refuses to play nicely with Linux back when this board was in use. Foxconn is a large OEM motherboard manufacturer, but according to a thread on the Ubuntu Forums, they refuse to support Linux. There is a bug in one of their DSDT tables for their BIOS that's causing installation and lock up issues. Now this was years ago but since you have an old board, if it's BIOS is original then maybe you are experiencing the hell that many did years ago. If you have played a ROM and now you cannot, then it probably points to an installation problem. I have never heard of a rom working and then not working unless configs and/or the emulator was changed via the runcommand.

Ok, Thanks for your help!

never mind.... i'm dumb.... i choosed a wrong romset from my archive... doh! Vectrex works... :)

I've had some success...

So, for anyone else having similar issues, i added the line:

input_player1_joypad_index = 1

to the psx-specific retroarch.cfg. Knowing it was "1" was a bit of luck. My next challenge is to correctly map X and O :-)

Hope this helps someone.

@kaz69 No, only one OS boots at a time. Nothing additional is running in the background from the other installations. Not sure if PINN asks or allows you to set the partition sizes but obviously it would be handy to have larger partitions for those OSes that need it.

@meleu Yeah, I saw it when I was checking your script. Ok, I'll take a look into it and see if I can do something with it. ;)

@tomaz I ran the ES update from binary last night. I didn't have a ton of time to mess with it, but I scrolled through several system gamelists and it did not crash.

There was a delay where everything froze for a 3 or 4 seconds and I thought it was going to crash, but then it started moving along again. It could have been something loading in the background or a gamelist.xml being scanned perhaps?

I'll spend more time with it this weekend. Thank you everyone for all your work and help. I was dreading that I might have to start over again.

@jonnykesh said in Error formatting 64Gb USB:

@landyvlad Windows is a pain the the ass. Use a third party tool like this https://www.sdcard.org/downloads/pls/index.html or this https://www.easeus.com/partition-master/best-fat32-format-tool.html

The former didn't give me any options and formatted the usb stick (which it said was an sd card) as ex-FAT rather than FAT32.

The second easeus worked fine and quickly. Cheers

thanks!!!! i missed this.... :) PS: i had spaces in rom's name.... removing spaces they works. now seeing the story of cfg mapping :)

@monkeydisco don’t give up on heat sinks. They can help a lot (they do in my setup). But use a thermal compound instead of mystery tape.

Ok. Thanks for the answer !
Wasn't sure if you needed that driver for any on/off switch hooked up to the pins.

@lostless

Try it again later (if you have not done so already). Had the same issue and just worked on another system and went back to it the next day

Fixed with last commit update to SDLPoP
https://github.com/NagyD/SDLPoP/pull/141

@pacmanlives this is fixed in RetroPie if you update. It deletes the broken repo.

@thomen Normally, I would suggest checking RUNCOMMAND, but you mentioned you are using Attract Mode. I would have expected Attract Mode you to be explicit about which emulator gets used, meaning, you would know what emulator because you had to set it up that way.

Perhaps someone more familiar with Attract Mode can add a better answer.

Yea I've played around with it a fair bit though so it could be related to something non standard. Just wanted to set the retropie menu view to Basic and everything else to auto in ES and thought this was a way...