[xd3l]

Sorry, I wasn’t trying to be a jerk, I was just surprised, and no, I guess I missed that part of the readme.

[xd3l]

I picked up an external 320Gb drive. Your kit installed from it without any issues, but…

…what was the point of installing it from USB? It didn’t install to USB. Bah!

I really really like what you’ve done with this, I tried to use the SD to USB tutorial on this, but I got lost as the guide is for a 3 in 1 boot and this is a 2 in 1. For what ever reason I could never get the SD to see the USB drive at boot time.

[xd3l]

I had it, then I decided I needed to get off SD and boot of USB, so I am on a new setup now.

I am trying to ./configure but am getting this error:

No working C++ compiler was found.
Please install a C++ compiler, such as GCC’s g++.
If you have a C++ compiler installed and openMSX did not detect it, please set the environment variable CXX to the name of your C++ compiler.
After you have corrected the situation, rerun “configure”.

[xd3l]

Yes, you are right, I forgot all about Fastab, it has been years!

Since I started this post, I found out that since I am over clocking my Pi 2, that I increase the chances of burning out my SD card, so I opted to only initiate the boot sequence from SD, and now host my OS on my USB stick, which of course in itself also solves this problem without the need to edit Fstab.

Thank you though, maybe this will come in handy for those who don’t share my SD phobias, or just that little extra speed boot, save money, or what have you.

[xd3l]

Here are the tools you will need.

Use Popstation to convert your single disc games. The reason for this is because Popstation is good at preserving the audio sound track.

For multi-disc games you will want to use PSX2PSP. With it you can see that it has a place to select multiple discs in Classic Mode. Fill up your cue, convert, and then configure the PSX emu to use buttons on your controller (which will work in conjunction with SELECT), to open the lid on your virtual PSX, load a different virtual CD (now contained within your PBP), and close the virtual lid to resume.

THe Save per Core and Save On Exit options need to be active in RGUI to do this.

[xd3l]

I got it! Well I got the guide I linked to work, I’ve not applied this to your package yet, though I am pretty well convinced that it would apply.

I did not bother with Part 3 of the tutorial as it seems to be rushed in that it leaves out a lot of explanation and just assumes you know what in the world he is talking about. So for now I just select my OS with a mouse, though I wish it would just boot into RetroPie everytime by default and then offer a script from within there to reboot into Kodi or Rapspain. Maybe I can work out a solution on my own and or with the help of the forums.

I am going to keep tinkering, then when I feel confident, I’ll probably back up all my partitions and have a go at what ever your lastest release may be at the time, because I got to admit, what I’ve seen in your Youtube video impressed me a lot, plus you changed the boot up screen into a video, which is something I wanted to do my self.

Thank you for the help and inspiration!

USB rules, SD drools! ;)

[xd3l]

I hear you man, I was up all night last night working on the Pi as per the pages I linked, and yes, it is not terribly hard, but very very very very time consuming! In fact I am still not done because by 8:30 AM in the morning, I realized I’d made a grave error and needed to adjust the guide a little bit to meet my needs.

When or if I make progress, I will post back and will hopefully have something useful to share in relation to how to get this working for 128Gb USB sticks and above, as we really don’t need to be depending up on SD cards since they are often slower, corrupt easier, and corrupt MUCH easier when we over clock our Pi’s… which is something I believe everyone and their grandma is going to want to do considering you need to be running at 1000Mhz in order to pull of PSX emulation as well as I’ve been able to.

[quote=106989]

xd3l wrote:

Nevermind, I believe I may have found the answer to all my woes in the following links. Gonna stay up all night and skip church to see how this goes down. Fingers crossed!!!

http://bobbyromeo.com/technology/triple-boot-raspberry-pi-on-usb-raspbianretropieopenelec-part-1/

http://bobbyromeo.com/technology/triple-boot-raspberry-pi-on-usb-raspbianretropieopenelec-part-2/

http://bobbyromeo.com/technology/triple-boot-raspberry-pi-on-usb-raspbianretropieopenelec-part-3/

Hmmm… Im a little confused with this guide you have linked. It seems that he has made the process harder than it should be, although maybe that is due to the fact its designed to run off a USB stick instead of SD card. I really don’t understand how the OS switching occurs though? I have only skimmed through to be fair, but from what I gather the script to switch OS is triggered via SSH? That, to me, seems a little… odd, and un-intuitive. Maybe I have read it wrong, however I think that having a script to select in each OS that can be run natively on the Pi is a much more user friendly approach.

I intend to document my build process, in fact I have already started, but it will take a while til its finished. :/ To be fair its not a hard process that I follow, just very time consuming due to the fact I need to leave things in their ‘standard’ form all the time, so if I need to test then I need to go through the whole process every time from scratch – create the tarballs for each OS, copy to SD / USB, install, configure, test… takes a great deal of time! Especially when an error is found, small as it may be. Means that the process needs to be started over from scratch again. :/

[/quote]

[xd3l]

Your project is brilliant, and works great if done from an SD card, and probably a small USB stick. The benefit from running from USB stick of course is potential increased speeds, and ditching the risk of frying your SD card when overclocked.

Sadly though, it would seem that any large USB stick or drive that I have, do not auto mount under USB*, but need to be mounted manually instead. So I presume NOOBS is working in much the same way, detecting the drive, but not mounting it, thus not seeing the OS folder.

With that in mind, I tried another tutorial that has you flash the Retropie image to USB, then copy over some files to an SD, modify a file, and you are set to go with full access to the entire USB drive!

As it stands though, I want my cake, with frosting, and the ability to eat it too, so I kept searching and that is when I found the guide I linked.
I am starting from part 1, so I can learn how to make my own NOOBS like you did, but without the custom tweaks added into each distro.
I am currently transferring partitions from my SD to my USB, which is a tedious process. Once this is done, I go on to the last few steps, and I should have a working Triple booter. If so I will most likely go back to your work, start at step 2 of the tutorial I linked, and see if I can transfer an SD install of your work, to a USB and use it as my main drive.
This should be the solution I believe.

[xd3l]

Nevermind, I believe I may have found the answer to all my woes in the following links. Gonna stay up all night and skip church to see how this goes down. Fingers crossed!!!

Triple Boot Raspberry Pi on USB (Raspbian / RetroPie / OpenELEC) – Part 1

Triple Boot Raspberry Pi on USB (Raspbian / RetroPie / OpenELEC) – Part 2

Triple Boot Raspberry Pi on USB (Raspbian / RetroPie / OpenELEC) – Part 3

[xd3l]

I am at a loss here. I put the OS folder on my Fat32 formatted 128Gb USB stick. I put the other contents of the NOOBS folder on the MicroSO.

I plugged both into my system, unplugged the network cable, and NOOBS does not see any OS’ to install but insists that I need to connect to the inet first.

When I do get this working, is this going to install this to my USB and leave my SD there to boot from?

[xd3l]

Awesome, thank you for doing this! This is one of those things I was wanting to figure out how to do on my own as running Kodi from within a RetroPie boot isn’t nearly as reliable as running it from the OpenElec distro.

I’m downloading now, thanks for the huge time saver!

[xd3l]

And “sudo fdisk -l” reveals that my tiny little Sandisk USB stick is in fact showing up as /dev/sdb1

Probably because sda1 is in use by my 4Tb drive. I formatted it in NTFS format and it is not auto mounting under USB, why not?

[xd3l]

I am trying to follow this guide:

http://linuxconfig.org/automatically-mount-usb-external-drive-with-autofs

replacing “udevinfo -a -p /sys/block/sdc/ | grep model” with “udevadm info -a -n /dev/sda1”

I get down to:

# /etc/init.d/udev restart
Stopping the hotplug events dispatcher: udevd.
Starting the hotplug events dispatcher: udevd.

Plug in external USB and your new base name is:

ls -l /dev/Iomega*
lrwxrwxrwx 1 root root 3 2011-02-23 12:36 /dev/Iomega -> sdc
lrwxrwxrwx 1 root root 12 2011-02-23 12:36 /dev/Iomega0 -> bsg/14:0:0:0
lrwxrwxrwx 1 root root 4 2011-02-23 12:36 /dev/Iomega1 -> sdc1
lrwxrwxrwx 1 root root 3 2011-02-23 12:36 /dev/Iomega3 -> sg3

Please note that /dev/Iomega1 points to a /dev/sdc1, which is exactly the partition we are interested in and we use it next to configure autofs.

——–

And I do not have the custom directory in /dev/

As a work around I updated to xbmc.sh script to read:

#!/bin/bash
sudo mount /dev/sda1 /mnt && kodi

Though I’d prefer if ALL of my drives auto mounted.

[xd3l]

Stupid mistake, I forgot to close Emustation.

So can I delete all the lists and images from the .Emulationstation folder in HOME/Pi now?

[xd3l]

THank you, I did manage to get the correct file and extract it to where it needed to be this time, but…

…after resetting Emulation Station, nothing is different. I presume I have to move the list and image files to their proper directories in /home/pi/.emulationsation first?

[xd3l]

So it’s confirmed then? The DOOM engine in every shape and form, needs to be a part of RetroPi 4! :)

[xd3l]

Weird, in some emulators Select plus X gets me into RGUI… others not so much.

Also Start and Select get me out of most emulators, but in FBA it is the top two Shoulder buttons.

[xd3l]

Thank you, I am in RGUI, but I am using a PS2 controller with USB adapter.

[xd3l]

I managed to get things worked out. In one place there was a typo, in the other places I do not know what was up, but I re-typed out the lines for the games that the info and image were not showing up in and now they work.
All I need now is to figure out how to get around the dating issue.

To speed things up though, I might be interested in getting the alternative Scraping tool working if someone can help me where the guide seems to be falling short.

[xd3l]

I can’t even get that guide to work. I just want to know how to do this manually.

[xd3l]

And just after I post, I figured at least part of it out.

<releasedate>19940719T000000</releasedate>

The first four numbers are of course the year it was released (1994).

The next two are the month (07)

Followed by the day (19)

And then the T which stands for time, and then (Hour,Minute,Seconds).

I can leave the Time as pure zeros and it is fine with that, but what I want to know is how to get this to accept if I do not know the month or day either?

Also, some game art and info just don’t show up even though my links are 100% correct. (not reflected in the example given).

[xd3l]

Thank you, I’m trying to follow it now, all is well but there is no “/home/pi/.openMSX/” folder.

[xd3l]

I compiled Odamex, everything compiles but Odalaunch which we don’t need anyhow.

Problem is that it does not want to communicate with the keyboard. Strange.

[xd3l]

The Pi will not be running DOOM 3 let alone the Dark MOD, sorry to say.

[xd3l]

Hmmm… actually now that I installed the depends… nothing will launch. everything on my Pi is now getting this error.

I did a chmod775 on the ZDoom directory and the .sh files. Might that have caused it? By why all the other programs on the Pi as well, I didn’t chmod them.

[xd3l]

Well I tried to run Brutal Freedoom but got this instead:

brutal_freedoom2.sh permission denied

[xd3l]

Thank you very much! I’d have compiled this my self, but I had issues with the dependencies, though I can’t recall what they were right now.
I’ll give this a go, and if I have problems I’ll post them here in hopes that someone will have the time to guide me even further.

Excited!!!

[xd3l]

Got it, I copied the Base3 directory to the ports folder in roms, the went into the folder and…

pi@retropie ~/RetroPie/roms/ports/baseq3 $ sudo cp *.* /opt/retropie/ports/quake3/baseq3/

works.

[xd3l]

As would I, thanks I’m going to PM you!

[xd3l]

OK, well hopefully I can talk the Retroarch guys into supporting more than one button to trigger this feature… not all of us are using XBOX 360 controllers with a spare button after all.

In the mean time, since I am using PSX controllers, I’ll assign it to Right Analog Down, and change discs with Right Analog left and right.

So if I turn all my multi disc games into one file using PSX2PSP, they will work when I get to that point right?

Does someone have a save game I can test this with to be sure?

[xd3l]

[quote=101491]Works great. Thank you very much.
But if you just edit it inside the rom it wont save it, so that you have to configure it every time you start a game.

So here are the commands for it. Write them to your specific controller config at /opt/retropie/emulators/retroarch/configs/ and write your prefered button inside the “”.

input_disk_eject_toggle_btn = ""
input_disk_next_btn = ""
input_disk_prev_btn = ""

[/quote]

So how would I enter this if I want my Disc Eject toggle to be more than one key, I.E. Select, L1 and L2?

[xd3l]

“Open Rgui and select:
– Settings
– Input Settings
– Scroll down until „Disk eject toggle“, setup a key or button for it.
– The same for „Disk next“ and „Disk prev“”

There is nothing there called Input Settings.

[Author]

Posts