|
|
Post by vic2020ian on Feb 9, 2021 11:32:31 GMT
Hi everyone, I had checked out the Project Carousel USB on my c64 mini and it seemed to have borked the controls on a couple of games - particularly Bomberman. Is there a way to reset or uninstall it and see if this fixes it? I appreciate any help because I am stuck at this point. Just power off, remove the USB and power it back on - PCUAE is now not running. |
|
|
|
Post by technofox on Feb 9, 2021 11:58:53 GMT
Hi everyone, I had checked out the Project Carousel USB on my c64 mini and it seemed to have borked the controls on a couple of games - particularly Bomberman. Is there a way to reset or uninstall it and see if this fixes it? I appreciate any help because I am stuck at this point. Just power off, remove the USB and power it back on - PCUAE is now not running. I just did that and I cannot seem to reflash any of my firmware in attempt to reset my mini back to it's prePCUAE state. Is there some other way to fix this? |
|
|
|
Post by vic2020ian on Feb 9, 2021 12:17:58 GMT
Just power off, remove the USB and power it back on - PCUAE is now not running. I just did that and I cannot seem to reflash any of my firmware in attempt to reset my mini back to it's prePCUAE state. Is there some other way to fix this? Was your mini firmware custom flashed or the nand games edited with Game Manager? PCUAE does not change the firmware it intercepts the startup and runs from usb. Removing the USB should put it back how it was before. What state is your mini in when you boot it up without USB fitted? What is it doing? What firmware are you running 1.5.2? |
|
|
|
Post by jj0 on Feb 9, 2021 12:21:45 GMT
Just power off, remove the USB and power it back on - PCUAE is now not running. I just did that and I cannot seem to reflash any of my firmware in attempt to reset my mini back to it's prePCUAE state. Is there some other way to fix this? PCUAE doesn't affect you firmware. What firmware version is your Mini on and how are you trying to reflash it? |
|
|
|
Post by technofox on Feb 9, 2021 12:46:34 GMT
I just did that and I cannot seem to reflash any of my firmware in attempt to reset my mini back to it's prePCUAE state. Is there some other way to fix this? PCUAE doesn't affect you firmware. What firmware version is your Mini on and how are you trying to reflash it? I appreciate your help on this. I am on 1.5.2 and was attempting to reflash using the very same upgrade firmware from Retrogames.biz for the c64 mini using the UI. It doesn't detect the update. I have even tried using the C64 Maxi Tool firmware that had worked prior to using PCUAE and still no dice. It's like the built-in updater is broken or something. |
|
|
|
Post by vic2020ian on Feb 9, 2021 13:01:23 GMT
You cannot reflash 1.5.2 on top of 1.5.2 - there is no need to either - you are already running current firmware and back to stock unless you edited the Nand.
|
|
|
|
Post by kugelblitz on Feb 9, 2021 13:26:14 GMT
Regarding "I want to reflash to stock firmware". The firmware updates provided by the manufacturer are UPDATES. They are not complete firmware files. They only update the files that are "new" or changed and they won't revert to earlier versions. If you think you firmware has been meddled with you need to go the complicated "restore NANDB" route. There are instructions for this in the forum but it is not for the faint of heart. If you only used PCU (and not the X-Mod or other tools that access NANDB) you should NOT have any changes in the firmware (but one single change for autostarting PCU).
|
|
|
|
Post by technofox on Feb 9, 2021 14:22:10 GMT
Regarding "I want to reflash to stock firmware". The firmware updates provided by the manufacturer are UPDATES. They are not complete firmware files. They only update the files that are "new" or changed and they won't revert to earlier versions. If you think you firmware has been meddled with you need to go the complicated "restore NANDB" route. There are instructions for this in the forum but it is not for the faint of heart. If you only used PCU (and not the X-Mod or other tools that access NANDB) you should NOT have any changes in the firmware (but one single change for autostarting PCU). I got it fixed. I just renamed the firmware update from Retrogames to theC64-9_9_90.bin and performed an update. It fixed the problem completely. I have no idea what happened but this worked. I appreciate everyone's help :-) |
|
|
|
Post by jj0 on Feb 9, 2021 15:57:25 GMT
Regarding "I want to reflash to stock firmware". The firmware updates provided by the manufacturer are UPDATES. They are not complete firmware files. They only update the files that are "new" or changed and they won't revert to earlier versions. If you think you firmware has been meddled with you need to go the complicated "restore NANDB" route. There are instructions for this in the forum but it is not for the faint of heart. If you only used PCU (and not the X-Mod or other tools that access NANDB) you should NOT have any changes in the firmware (but one single change for autostarting PCU). I got it fixed. I just renamed the firmware update from Retrogames to theC64-9_9_90.bin and performed an update. It fixed the problem completely. I have no idea what happened but this worked. I appreciate everyone's help :-) Nice trick! So there must have been something missing/broken on the internal storage. |
|
|
|
Post by vic2020ian on Feb 9, 2021 16:37:36 GMT
Nice trick! So there must have been something missing/broken on the internal storage. Not if it was already 1.5.2 ? What was broken that needed a reflash after removing PCUAE usb stick? PCUAE would not cause a change.... unless there was some poking in the nand with X Windows ;-) |
|
|
|
Post by spannernick on Feb 10, 2021 12:24:57 GMT
I am having a big problem with Dialog and its not working, I think it might be that PCUAE don't use `/mnt/` and uses `/tmp/pcu/` and a loop device, cause when I point it to the script that works, it show nothing, and don't run it, it's acting like its no there, when it is, I will have to test it on `/mnt/` and it could be that PCUAE is not booting from a update too, its booting itself so that could be the problem too, but its boot up the shell fine.
|
|
|
|
Post by spannernick on Feb 10, 2021 12:34:41 GMT
I named the fake update `theC64-9_9_9 0.bin` added a `0` to its name cause I was going to make a fake update that only worked with PCU only, just in case you wounded why...  |
|
|
|
Post by jj0 on Feb 11, 2021 7:34:28 GMT
If you want to add more controllers in the gamecontrollerdb.txt files, I have two additions for great DB9 adapters: 03000000828200000132000001010000,DB9-2-USB by Gary Methetingham,a:b4,b:b5,back:b6,lefttrigger:b0,leftx:a0,lefty:a1,righttrigger:b1,start:b7,x:b3,y:b2,platform:Linux, 030000001008000001e5000010010000,Retronic Design BD9 Adapter,lefttrigger:b6,leftx:a0,lefty:a1,righttrigger:b9,dpdown:+a1,dpleft:-a0,dpright:+a0,dpup:-a1,platform:Linux, Would save some of us some updating with every new version
Thank you, i will check it out asap
hmmm, still 1942 no joystick action(Carousel 1.4.2), joystick swapping with the new firmware is not implemented yet i guess.
Ctrl < does not do anything over here  Now even the TheVIC20 joystick does not work in the game 1942 so something has changed.....
1942 is joystick port 2 > no joystick action Alleycat is joystick port 2 > joystick ok Track and Field is joystick port 2 > joystick ok Arkanoid is joystick port 1 > joystick fire button not working, directions ok
Confusing......
Hi - if it helps you can use anykey-64.prg (24.84 KB) to check joystick/key presses in C64 mode. I haven't found something similar for VIC-20 though. |
|
|
|
Post by ginger on Feb 11, 2021 9:25:14 GMT
been using carousel project no problems.since the new update still fine only problem when using c64 mini in normal mode and side loading games from usb sound is very choppy and intermittent making the mini unuseable can anybody help.Is there a way to downgrade to last update?
|
|
|
|
Post by spannernick on Feb 11, 2021 11:53:12 GMT
when will you release pcuea 1.3.2 ? Will be soon, need to test it on THEC64 Mini and finish the Bios Menu. |
|
|
|
Post by technofox on Feb 11, 2021 12:04:34 GMT
I got it fixed. I just renamed the firmware update from Retrogames to theC64-9_9_90.bin and performed an update. It fixed the problem completely. I have no idea what happened but this worked. I appreciate everyone's help :-) Nice trick! So there must have been something missing/broken on the internal storage. Thank you my friend. I figured that since the PCUAE uses that same filename for a fake update, that this trick would work. Thankfully it did. I don't know what got borked but I don't think it was PCUAE (actually I think PCUAE's fake update feature and renaming of the 1.5.2 update to theC64-9_9_90.bin allowed me to perform the update to fix the problem. So PCUAE actually saved the day. My best guess is that the update from the C64 Maxi Tool prior to using the PCUAE did not play nice with each other. Some of the evidence to support this idea, is that no one else really had this issue with PCUAE and the only difference is that I was not working with an actual stock c64 mini unit. |
|
|
|
Post by technofox on Feb 11, 2021 12:08:06 GMT
when will you release pcuea 1.3.2 ? Will be soon, need to test it on THEC64 Mini. Hi Spannernick, I just read your signature. I just want to let you know that my prior post explains that it was your tool that helped fix my issue with the firmware and allowed to force an update to fix the problem. I think the C64 Maxi Tool that I have been using had borked something with your tool. I am not sure if you can confirm this assumption but this is my best guess based upon my research and observation of the issue between the joystick drivers failing in certain games and PCUAE. It's a pretty bizarre issue and I am not sure if I can replicate it. |
|
|
|
Post by spannernick on Feb 11, 2021 12:12:28 GMT
Nice trick! So there must have been something missing/broken on the internal storage. Thank you my friend. I figured that since the PCUAE uses that same filename for a fake update, that this trick would work. Thankfully it did. I don't know what got borked but I don't think it was PCUAE (actually I think PCUAE's fake update feature and renaming of the 1.5.2 update to theC64-9_9_90.bin allowed me to perform the update to fix the problem. So PCUAE actually saved the day. My best guess is that the update from the C64 Maxi Tool prior to using the PCUAE did not play nice with each other. Some of the evidence to support this idea, is that no one else really had this issue with PCUAE and the only difference is that I was not working with an actual stock c64 mini unit. So if you can do that with the latest update, you should be able to do it with a older update, if you want to downgrade it say v1.4.2, and rename it from thec64-1.4.2.bin to thec64-9.9.9.bin, I have not tested it, I don't know if it will work, just an idea. |
|
|
|
Post by spannernick on Feb 11, 2021 12:24:34 GMT
Will be soon, need to test it on THEC64 Mini. Hi Spannernick, I just read your signature. I just want to let you know that my prior post explains that it was your tool that helped fix my issue with the firmware and allowed to force an update to fix the problem. I think the C64 Maxi Tool that I have been using had borked something with your tool. I am not sure if you can confirm this assumption but this is my best guess based upon my research and observation of the issue between the joystick drivers failing in certain games and PCUAE. It's a pretty bizarre issue and I am not sure if I can replicate it. When you run the update the first time, it might of not updated properly, that's why you might of had the problem. |
|
|
|
Post by kugelblitz on Feb 11, 2021 13:24:22 GMT
DO NOT TRY "DOWNGRADING"! The updates only replace certain files, not the full NANDB. If you "downgrade" by faking version numbers you will put the system in an undefined state. Actually, if all is well written, nothing will change because older files should not replace newer ones, but then the downgrade does... nothing at all. That is the best possible outcome. The worst one is a mix of old and new files that is instable.
|
|
|
|
Post by max2007 on Feb 12, 2021 8:52:23 GMT
Hi I got The Vic-20 I put the project Carousel USB 1.3.1 I noticed that the section 6_VIC20_S_to_Z is not displayed help?!. For the rest everything seems ok.
|
|
|
|
Post by vic2020ian on Feb 12, 2021 9:39:58 GMT
Hi I got The Vic-20 I put the project Carousel USB 1.3.1 I noticed that the section 6_VIC20_S_to_Z is not displayed help?!. For the rest everything seems ok. Try scrolling down while in the left most column of the Carousel Choice menu. C64Fav C64-1 C64-2 C64-3 Vic-1 Vic-2 v X - X - Cannot scroll from here if the boxes below are empty due to no folders to displayVic-3 |
|
|
|
Post by max2007 on Feb 12, 2021 10:24:40 GMT
Hello nothing but if I change the carousel and put 1.4.2 now check.
|
|
|
|
Post by spannernick on Feb 12, 2021 10:45:30 GMT
Make sure the red box is on Favourites then pull down on joystick until you see 6_VIC20_S_to_Z and the red box is over the top of it then press fire to load that screen.
|
|
|
|
Post by vic2020ian on Feb 12, 2021 10:45:38 GMT
Hello nothing but if I change the carousel and put 1.4.2 now check. I can switch to carousel 1.4.2 and select Vic20 StoZ, Switch to 1.3.2 and do the same and back to 1.4.2 and it still works. I just make sure the red box highlights the left most column on CTRL+f7 menu and scroll down from there. |
|
|
|
Post by max2007 on Feb 12, 2021 17:17:39 GMT
Yes, only in this way it always works thanks.
|
|
|
|
Post by spannernick on Feb 12, 2021 21:38:16 GMT
Just put the C64 Mini Carousel v1.5.2 with Classic Mode and THEVIC20 Carousel V1.5.2 under CTRL-F5 so when you switch to it, it will detect what machine your on and load that carousel, if your using THEC64 Mini than it will load the Carousel v1.5.2 for that and if you on THEC64 Maxi or THEVIC20 it will load the Carousel v1.5.2 from the THEVIC20.
Sort out the boot menu now and made a new menu for Vice too using dialog.
|
|
|
|
Post by spannernick on Feb 13, 2021 12:42:57 GMT
Hacked TheCarousel's v1.5.2 to show 255 games now with HxD Hex Editor... Can someone test for me if you can see 255 games in TheCarousel's, you can do it with PCU Game Manager, you need to put in 255 games into one of the Carousel Gamelist Folders....? Someone said you could only see 226 games but I guess that was now a lie cause I put 240 games in TheCarousel v1.3.2 and you can see them, when doing this, remember what the last game is in the list, then if you see it in TheCarousel then it can hold 255 games in each Carousel Gamelist Screen. |
|
|
|
Post by vic2020ian on Feb 13, 2021 13:41:35 GMT
Hacked TheCarousel's v1.5.2 to show 255 games now with HxD Hex Editor... Can someone test for me if you can see 255 games in TheCarousel's, you can do it with PCU Game Manager, you need to put in 255 games into one of the Carousel Gamelist Folders....? Someone said you could only see 226 games but I guess that was now a lie cause I put 240 games in TheCarousel v1.3.2 and you can see them, when doing this, remember what the last game is in the list, then if you see it in TheCarousel then it can hold 255 games in each Carousel Gamelist Screen. I just copied your 0-G and H-R directories to a new Directory called Limit. This loaded fine from the CTRL+F7 menu and displayed 0-G plus 17 games from H-R starting with Hacker and ending at Highway Encounter. I counted and have 255 entries (I think that included the 0-G and H-R items) This was on TheVic20 firmware 1.5.2 and PCUAE latest version 1.3.1 |
|
|
|
Post by stainy on Feb 13, 2021 14:10:17 GMT
I also think that the idea of the simple carousel is the whole point. If additional options can be set in some files like the start.sh or other "config files", I am all happy. Adding menus during startup would make things more complicated at every startup and not so simple for my 4-year old daughter that now run the C64mini by her self with the carousel. I second that - very similar thoughts in the poll thread. I would have a setting to set the preferred boot next time. e.g. I am in Vic20 classic mode and press CTRL+8 to set that mode for next boot. Flash up a quick confirm message like for Autoboot. I have one of Gary`s DB9 adapters Also almost finished with my 3d printed case design for it. |
|
