mckafka99
-
Content Count
1,152 -
Joined
-
Last visited
Posts posted by mckafka99
-
-
Check the permissions/ownership on the various folders related to your coolcv setup.I'm trying to get coolcv running on a RPi2 using RetroPi 3.1 and have done what mckafka99 has said to do - added the system lines to es_systems.cfg and put coolcv_pi into a coolcv folder at cd /opt/retropie/emulators/coolcv. Even put a ColecoVision BIOS in the bios folder. When I try to open a game, I get a permission denied error. Any idea what I'm doing wrong?
If you go to /opt/retropie/emulators and do a ls -l the list of folders (including coolcv) will be listed with permissions.The coolcv user/group owner needs to be set to root like all the others and the permissions need to be set like the other emulator folders.
The same applies to the folder where you put your Colecovision roms. If they are in /home/pi/RetroPie/roms/Colecovision, goto /home/pi/RetroPie/roms and do the ls -l command to see the owner/permissions on the Colecovision roms folder (or whatever name you gave the folder). The user/group owner should be pi. Permissions should be set like the others as well.
To change these I would suggest changing to 'SuperUser first' (sudo su) but be aware that as the su user you can do just about anything to your system so be careful that you dont delete anything you dont intend to.
As the SU user, goto each of those directories and check the owner/permissions.
To change ownership, you use the 'chown' command. For example to change ownership on a directory called 'test' to a user called 'user', you would run the following two commands:
chown user test
chown :user test
To change the permissions on a directory called 'test' to match most of those you should see for the other folder you can run the following:
chmod 775 test
Hope this helps.
-
For setup/install in RetroPI, does one just need to copy over the inclued rpi version and then setup the config files apprprotately or do you still have to go through all of the additional Linux Instructions for libSDL2? If so, does that have any effects on the rest of the RetroPi install?
I've learned that none of those extra linux steps for libSDL2 on my RPi2 with RetroPi 3.1 are required. Last thing to work out is whether or not controller remapping is possible in RetroPie with this. I'd like to use joy3 rather than joy0 or add some mappings to joy0 (joy0 for me is a SuperNintendo looking joypad and joy3 is an A2600 joystick connected via a Stelladaptor).
Thanks again for this awesome emulator! One more system I can now take out of the living room (making wife happy) and move to a game room upstairs.
-
If you want integred coolcv to retropie you need first copy your coolcv at cd /opt/retropie/emulators/coolcv and add this lines at nano /etc/emulationstation/es_systems.cfg:
<system>
<name>colecovision</name>
<fullname>ColecoVision</fullname>
<path>~/RetroPie/roms/colecovision</path>
<extension>.rom .ROM .col .COL</extension>
<command>/opt/retropie/emulators/coolcv/coolcv_pi %ROM% </command>
<platform>colecovision</platform>
<theme>colecovision</theme>
</system>
And don't forget this line finish with:</systemList>
This way work great for coolcv on retropie
keyboard works
joystick works.
Good pleasure!
Just wanted to add the .zip and .ZIP can be added to the extension list as those work as well.
-
1
-
-
I'm interested in a completed version of one of these whenever the are ready (hope they havent all been claimed).
-
For setup/install in RetroPI, does one just need to copy over the inclued rpi version and then setup the config files apprprotately or do you still have to go through all of the additional Linux Instructions for libSDL2? If so, does that have any effects on the rest of the RetroPi install?
-
Hi,
Found this topic just now, so apologies for bumping such an old issue. Did you ever manage to solve the issue of missing pixels? I had the same on my box and it is definitely related to the RAM chips. I found them on ebay, replaced them - all the pixels are available again. In fact, finding the sockets for the RAM chips was the hardest part, as they are wider than normal ICs...
regards,
flip
Fauxscot fixed two of my units and I donated a 3rd to him for whatever experiements he saw fit to put it through. It's been a while since he has been around though. The main thread for most things RCA SII (at least recently) is here:
-
-
-
Admittedly not in the best of formats, but check your PMs.I received my UltiMulti Cart Ver 2.00 yesterday and spent all night with it. Ken (kenzre) did a wonderful job and I'm very happy to have it. I have a question about the cart for someone that owns it. I wrote Ken but he has been slow to reply so I'll ask it publicly. Also, this may be useful to others who have or will have this multi-cart.
Does anyone who owns the cart have a listing/matrix of the DIP switch settings for Ver 2.00? Ken included a printout of his Ver 1.5.1 cart (the same available here on BallyAlley). Is there an updated version for the 2.00 to include War and Crazy Climber? He didn't include the switch settings for the new game additions in any of the paperwork he included.
War is 01010100
Crazy Climber is 00110100
-
After playing this version many times, I'm beginning to miss the ability to move in one direction and fire in another as with the Intellivision version...
Would it be possible to have one of the A7800 button fire in the same direction as the joystick is moved while the other button is used for the opposite direction? Perhaps have this option as well as the option to swap which button did which direction?
-
hmmm.. that's one way to do it it appears. Perhaps a hot air gun would do the trick also if one isn't feeling confident with an Soldering Iron and desoldering wick?
-
it's funny, only .a78 that I can't get pokey audio to work on is commando. besides that and a few freeze-ups, the Concerto cart is a lot of fun. getting that Pokey out of my spare Ball Blazer was hard as hell though!! excited to play all of Bob's homebrews now on real hardware! having the complete 7800 and 2600 libraries on one cart is amazing.
Is removing the POKEY from Ballblazer typically a challenge?
-
If you have a working system, I highly recommend getting on the list for e5frog's MultiCart - it is awesome to have and may be the only way (unless you are rich) you'd get a chance to play some of the later releases. The inclusion of the PacMan port alone makes it a worthy purchase.
-
1
-
-
I am very interested in one if available.
-
You can put the hackfile anywhere you would like, you just have to have the correct path listed in the proper emulators.cfg file. As an example, I put my hackfile in /opt/retropie/emulators/jzintv/bin (this is the path to the actual jzintv emulator (at least in the latest RetroPie). If you look in /opt/retropie/configs/intellivision you should see an emulators.cfg file which is what actually launches the emulator. In that file, you need to add the kbdhackfile flag to the command in that file and point it to location of your hackfile. I've attached a photo of what my emulators.cfg file (for the Intellivision) looks like which probably demonstrates better what I have described.Is anyone else having problems running Retropie 3.1 on a Pi1 B+ with the flashback Intellivision controllers using VisionDapters? I remember earlier version of Retropie working out of the box with the controllers, but I can't seem to find those older versions of Retropie either. I have the old hackfile.cfg, but I'm not sure where to put it in this latest version and then exactly how to change es_systems.cfg to recognize it. Earlier posts refer to earlier versions of Retropie..and things have changed enough that I can't figure out what I'm doing wrong. Any ideas? Am I missing something obvious....again?
One of the things to get used to with the new version of RetroPie is that, the direct launch commands for the individual emulators are no longer in the es_systems.cfg file; the es_systems.cfg file (see 2nd photo) now typically calls /opt/retropie/supplementary/runcommand/runcommand.sh for each emulator and it is within that script that individual emulators will be called by looking for emulators.cfg files. I've looked at the runcommand.sh file to try to understand a little bit but promptly realized that it was probably best to stay out of it.
I should add that this is how things work on my RPi2 Model B.
-
@ $22 for a Special Edition, I'm in for one. If the SE isnt available, I'm still in for one of the regular ones.
-
1
-
-
I will investigate this for you.
..Al
Awesome, thanks!
-
That will be my next purchase without hesitation.

Ditto this. I need to renew my AA subscription as well but the invoice link I received no longer works.
-
Great scores rolling in! I knew it was just matter of time before the 'million' plus scores started showing up. Someday I may get there but I don't think it will be this round.
-
I'd gladly donate towards a compiled RetroPi version of this emulator!
-
Pm sent for 5200 trackball
-
844,826 - I think this is my best since the game launch (starting from level 0); even got to try out the 3rd bonus level style which I may have only seen once or twice before. I dont recall ever making it to rainbow level before though. I couldnt figure out how to kill the spinny heads on this level; hitting them straight in the middle didnt seem to kill them (split occasionally, but never kill) - thus I lost my last 3 lives here.
-
If there is a Jag Pro Controller in there that you're willing to part with for a reasonable price, I'd love to grab it.
-
1
-
-

CoolCV emulator for Mac OS X, Linux, Windows and Raspberry
in ColecoVision / Adam
Posted
I believe when running ES and launching games you are running as the PI user. If you drop out of ES to the command prompt you will be dropped as the PI user I believe. Changing the ownership and permissions as I described has always resolved those permissions errors I have received in the past when trying to launch other games/emulators. I am also running the latest version of coolcv. I would double check the folders and make sure owner/permission match those of other emulators you are able to launch. Also might have to check the owner/permissions on the coolcv_pi file itself.