|
Post by MeneerJansen on Apr 28, 2020 9:49:45 GMT
I take it that starting this mod once to have a look at it is completely harmless because it dot not alter your firmware in any way what so ever (unless you do so yourself)?
|
|
|
Post by jj0 on Apr 28, 2020 11:02:42 GMT
I take it that starting this mod once to have a look at it is completely harmless because it dot not alter your firmware in any way what so ever (unless you do so yourself)? Yes. You have nothing to fear but what you do yourself. So always start off with a backup, and copy that backup somewhere else, don't just keep it on the USB-drive.
|
|
|
Post by MeneerJansen on Apr 28, 2020 13:59:37 GMT
I take it that starting this mod once to have a look at it is completely harmless because it dot not alter your firmware in any way what so ever (unless you do so yourself)? Yes. You have nothing to fear but what you do yourself. So always start off with a backup, and copy that backup somewhere else, don't just keep it on the USB-drive. I have a The C64 Maxi. But I don't know how to make a backup of what's in it. Or do you mean backup of the SD USB stick?
|
|
|
Post by jj0 on Apr 28, 2020 16:24:15 GMT
Yes. You have nothing to fear but what you do yourself. So always start off with a backup, and copy that backup somewhere else, don't just keep it on the USB-drive. I have a The C64 Maxi. But I don't know how to make a backup of what's in it. Or do you mean backup of the SD USB stick? See the first post: In addition there's an icon on the Desktop to backup the nand and the 'usr/shares/the64' files to the USB disk, to a backup directory. It creates new copies every time you run it. So you can make a backup first thing when you run the tool.
|
|
|
Post by MeneerJansen on Apr 29, 2020 10:02:40 GMT
I have a The C64 Maxi. But I don't know how to make a backup of what's in it. Or do you mean backup of the SD USB stick? See the first post: In addition there's an icon on the Desktop to backup the nand and the 'usr/shares/the64' files to the USB disk, to a backup directory. It creates new copies every time you run it. So you can make a backup first thing when you run the tool. Thanks for the reply! I get it now. But forgive me the following stupid question: how do I restore a backup of the NAND memory and the /usr/share/the64 directory to my The C64?
|
|
|
Post by spannernick on May 13, 2020 12:55:34 GMT
I wanted to ask.. Is there a version of Vice you could use thats compatible with the C64 Maxi that works from a shell, anyone tried it..?
|
|
|
Post by MeneerJansen on May 15, 2020 10:40:26 GMT
See the first post: So you can make a backup first thing when you run the tool. Thanks for the reply! I get it now. But forgive me the following stupid question: how do I restore a backup of the NAND memory and the /usr/share/the64 directory to my The C64? Bump. How to restore a backup? I think that one must start The C64 in "Linux X-Windows mode" again and manually overwrite the NAND etc. with the files from your backup directory. But that will not work, I think, if you did stupid things and your The C64 won't startup anymore?
|
|
|
Post by jj0 on May 15, 2020 13:39:36 GMT
Thanks for the reply! I get it now. But forgive me the following stupid question: how do I restore a backup of the NAND memory and the /usr/share/the64 directory to my The C64? Bump. How to restore a backup? I think that one must start The C64 in "Linux X-Windows mode" again and manually overwrite the NAND etc. with the files from your backup directory. But that will not work, I think, if you did stupid things and your The C64 won't startup anymore? If TheC64 won't startup anymore then it depends on which model you have: - TheC64 Mini: Either start in FEL mode or using an USB2UART converter in the initial ramdisk mode. Then (after doing the 'insmod /lib/modules/3.4.39/nand.ko' and 'mount /dev/sda1 /mnt' (assuming your backup is on the only USB disk that's inserted) you can use the command 'dd if=/mnt/nanda of=/dev/nanda' to restore nanda (usually not needed) or 'dd if=/mnt/nandb of=/dev/nandb'
- TheC64 Maxi: Using an USB2UART converter in the initial ramdisk mode. Then (after doing the 'insmod /lib/modules/3.4.39/nand.ko' and 'mount /dev/sda1 /mnt' (assuming your backup is on the only USB disk that's inserted) you can use the command 'dd if=/mnt/nanda of=/dev/nanda' to restore nanda (usually not needed) or 'dd if=/mnt/nandb of=/dev/nandb'
You can also use either of the above methods to first see if you can get them to work before making any drastic changes.
|
|
|
Post by MeneerJansen on May 16, 2020 11:19:28 GMT
Bump. How to restore a backup? I think that one must start The C64 in "Linux X-Windows mode" again and manually overwrite the NAND etc. with the files from your backup directory. But that will not work, I think, if you did stupid things and your The C64 won't startup anymore? If TheC64 won't startup anymore then it depends on which model you have: - TheC64 Mini: Either start in FEL mode or using an USB2UART converter in the initial ramdisk mode. Then (after doing the 'insmod /lib/modules/3.4.39/nand.ko' and 'mount /dev/sda1 /mnt' (assuming your backup is on the only USB disk that's inserted) you can use the command 'dd if=/mnt/nanda of=/dev/nanda' to restore nanda (usually not needed) or 'dd if=/mnt/nandb of=/dev/nandb'
- TheC64 Maxi: Using an USB2UART converter in the initial ramdisk mode. Then (after doing the 'insmod /lib/modules/3.4.39/nand.ko' and 'mount /dev/sda1 /mnt' (assuming your backup is on the only USB disk that's inserted) you can use the command 'dd if=/mnt/nanda of=/dev/nanda' to restore nanda (usually not needed) or 'dd if=/mnt/nandb of=/dev/nandb'
You can also use either of the above methods to first see if you can get them to work before making any drastic changes. Thank you for the instructions. It's certainly not easy to recover a TheC64 but it is possible.
|
|
|
Post by jj0 on May 16, 2020 16:38:02 GMT
If TheC64 won't startup anymore then it depends on which model you have: - TheC64 Mini: Either start in FEL mode or using an USB2UART converter in the initial ramdisk mode. Then (after doing the 'insmod /lib/modules/3.4.39/nand.ko' and 'mount /dev/sda1 /mnt' (assuming your backup is on the only USB disk that's inserted) you can use the command 'dd if=/mnt/nanda of=/dev/nanda' to restore nanda (usually not needed) or 'dd if=/mnt/nandb of=/dev/nandb'
- TheC64 Maxi: Using an USB2UART converter in the initial ramdisk mode. Then (after doing the 'insmod /lib/modules/3.4.39/nand.ko' and 'mount /dev/sda1 /mnt' (assuming your backup is on the only USB disk that's inserted) you can use the command 'dd if=/mnt/nanda of=/dev/nanda' to restore nanda (usually not needed) or 'dd if=/mnt/nandb of=/dev/nandb'
You can also use either of the above methods to first see if you can get them to work before making any drastic changes. Thank you for the instructions. It's certainly not easy to recover a TheC64 but it is possible. Well, once you've done it a couple of times it will come naturally to you. Fluitje van een cent! 😁
|
|
|
Post by spannernick on Jun 9, 2020 19:13:12 GMT
I was wondering if you could get this to read the file system from the SD Card, If I run this on TheC64 Maxi PI, I can't access its file system on it cause it looking for a Nand, can get this to look in 2 places for the file system, the Nand and the SD card..?
|
|
|
Post by jj0 on Jun 10, 2020 7:12:58 GMT
I was wondering if you could get this to read the file system from the SD Card, If I run this on TheC64 Maxi PI, I can't access its file system on it cause it looking for a Nand, can get this to look in 2 places for the file system, the Nand and the SD card..? In the start.sh there's the following: mkdir -p /tmp/chroot/mnt/nandb mount /dev/nandb /tmp/chroot/mnt/nandb mkdir -p /tmp/chroot/media/the64 mount --bind /tmp/chroot/mnt/nandb/usr/share/the64 /tmp/chroot/media/the64
If you change 'nandb' to whatever the right partition on your SD-card is (mmcblk0p2 ?) then it will use the SD-card.
|
|
|
Post by knipser2001 on Jun 17, 2020 4:05:18 GMT
This is a fantastic mod. What I would like to do is use this to replace the gamecontrollerdb.txt file so I can finally tell the C64 Mini to remap my Speedlink Competion Pro Anniversary Edition and to put the Menu button on the Top Right triangle button. I have enhanced the gamecontrollerdb.txt file already. As I have no experience in scripting what would be the command to add in the start.sh that exchanges the gamecontrollerdb.txt in the C64 Mini with the one I have in the root of the USB stick. Maybe also a command to save the gamscontrollerdb.txt from the C64 Mini as gamecontrollerdb.txt backup on the USB in case something goes wrong. Is that doable? It would be great if someone could help me out here. Thank you very much
|
|
|
Post by jj0 on Jun 27, 2020 11:49:59 GMT
Guys, I have small problem. A few years ago, I had one of my bread bins die on me. Though, sad I still had a working 64c so I let the pain pass. The 64c still works today. I found a tutorial for using a Keyrah to hook up and existing C64 keyboard to a RaspberryPi running Vice. I set it up and it worked, but I didn't like all the menus in Vice and I just wanted something for casual games since I still had the 64c for serious stuff. I eventually took the RPi out and used it for another project. Then the mini came out and the priced dropped. Since I like the mini interface, I stuck it in the bread bin and I had an instant Maxi..almost. They keys are still mapped to a Windows style keyboard no matter if I switch the Keyrah or change between US and UK keyboards on the C64mini. I posted this problem on another board a while back, and someone suggested I copy a keyboard map from Vice and replace the C64mini keyboard map file with it since it is running a version Vice. The person was vague on how to do it, so I never persued it. But now, since customizing the carousel is a thing, I am more interested. Does anyone know how to replace the keyboard map file on the mini? I am picturing a custom C64 with proper joystick ports, a carousel full of games I love, and HDMI out. BTW-I do have a Maxi and it is great, but I am looking to recapture that old-school keyboard feel and the maxi just doesn't do it for me. Keymapping on the Keyrah can be found here-http://wiki.icomp.de/wiki/Keyrah_V2#C64_key_mapping spannernick maybe move this post to your THEC64 MAXi Pi (DIY Version) thread? That's where you explain about the edits you did to /usr/lib/vice/theC64-sym-COMMON.vkm so it works withe the Keyrah.
|
|
|
Post by spannernick on Jul 2, 2020 15:27:57 GMT
I was wondering, I am using THEC64 Maxi PI(Orange PI PC H3) so it has a network card, would there be to hard to get it working on this, Jerome, the light are on.....? Got to have a laugh once in a while..
|
|
|
Post by spannernick on Jul 2, 2020 16:24:58 GMT
I was wondering if you could get this to read the file system from the SD Card, If I run this on TheC64 Maxi PI, I can't access its file system on it cause it looking for a Nand, can get this to look in 2 places for the file system, the Nand and the SD card..? In the start.sh there's the following: mkdir -p /tmp/chroot/mnt/nandb mount /dev/nandb /tmp/chroot/mnt/nandb mkdir -p /tmp/chroot/media/the64 mount --bind /tmp/chroot/mnt/nandb/usr/share/the64 /tmp/chroot/media/the64
If you change 'nandb' to whatever the right partition on your SD-card is (mmcblk0p2 ?) then it will use the SD-card. I did try this and it still can't find the SD card on THEC64 Maxi PI, I tried "mmcblk0p1" and "mmcblk0p2" none worked, have you still got your OPI PC H3, maybe you could look in to it for me when you have the time, no rush and work it out, no luck for me so far. You can see "mmcblk0p1" and "mmcblk0p2" in the dev folder so SD card is there, the nanda and nandb is not there but they wouldn't be. This is what I changed...
|
|
|
Post by jj0 on Jul 2, 2020 19:29:08 GMT
In the start.sh there's the following: mkdir -p /tmp/chroot/mnt/nandb mount /dev/nandb /tmp/chroot/mnt/nandb mkdir -p /tmp/chroot/media/the64 mount --bind /tmp/chroot/mnt/nandb/usr/share/the64 /tmp/chroot/media/the64
If you change 'nandb' to whatever the right partition on your SD-card is (mmcblk0p2 ?) then it will use the SD-card. I did try this and it still can't find the SD card on THEC64 Maxi PI, I tried "mmcblk0p1" and "mmcblk0p2" none worked, have you still got your OPI PC H3, maybe you could look in to it for me when you have the time, no rush and work it out, no luck for me so far. You can see "mmcblk0p1" and "mmcblk0p2" in the dev folder so SD card is there, the nanda and nandb is not there but they wouldn't be. This is what I changed... What is the output of the mount commands if you try them manually?
|
|
|
Post by spannernick on Jul 2, 2020 19:34:20 GMT
I have a look..
|
|
|
Post by spannernick on Jul 2, 2020 23:15:54 GMT
sorted its working now, it now has 4 folders bookmarked.. 2 for the64 folder and nandb folder and 2 more for the64 sd folder and SD card root.
|
|
|
Post by jj0 on Jul 3, 2020 7:11:53 GMT
sorted its working now, it now has 4 folders bookmarked.. 2 for the64 folder and nandb folder and 2 more for the64 sd folder and SD card root. So what was the issue?
|
|
|
Post by spannernick on Jul 14, 2020 9:07:42 GMT
Added a brief description in the first post on DIY adding stuff to the package. Had a idea... X-Windows Mod loads from a OS image don't it, its a bit like the image is its SD card.. , so why can't you use a image of RetrOrangePi that's a OS image, and load it up on THEC64 Maxi, it would have to be the H3 version so it would not work on THEC64 Mini...? unless there is a version for a A20. What you think Jerome..? www.retrorangepi.org/download/
|
|
|
Post by jj0 on Jul 14, 2020 9:23:34 GMT
Added a brief description in the first post on DIY adding stuff to the package. Had a idea... X-Windows Mod loads from a OS image don't it, its a bit like the image is its SD card.. , so why can't you use a image of RetrOrangePi that's a OS image, and load it up on THEC64 Maxi, it would have to be the H3 version so it would not work on THEC64 Mini...? unless there is a version for a A20. What you think Jerome..? www.retrorangepi.org/download/It could work but it depends on what the image needs/expects in terms of kernel features, graphics support and what the proper startup command is. With the X-Windows nod you are not booting the actual OS, but only starting up the graphical shell (via startx). In theory you could even remove a lot of stuff from the .img file to make it smaller as a lot of stuff is probably not used. So you could try the same for RetrOrangePi.
|
|
|
Post by spannernick on Jul 14, 2020 9:32:59 GMT
Had a idea... X-Windows Mod loads from a OS image don't it, its a bit like the image is its sd card.. , so why can't you use a image of RetrOrangePi that's a OS image, and load it up on THEC64 Maxi, it would have to be the H3 version so it would not work on THEC64 Mini...? What you Jerome..? It could work but it depends on what the image needs/expects in terms of kernel features, graphics support and what the proper startup command is. With the X-Windows nod you are not booting the actual OS, but only starting up the graphical shell (via startx). In theory you could even remove a lot of stuff from the .img file to make it smaller as a lot of stuff is probably not used. So you could try the same for RetrOrangePi. Would you mind taking a look, cause you know what your doing and I don't.. I only know bits about Linux, And you know what your looking for and what you need, do it when you have time of core.. I don't see why It wouldn't work, it works on a Orange PI PC H3, I have tested it on mine THEC64 Maxi PI, I guess it would depends on as well what OS it uses to boot it too. RetrOrangePi do have a forum... retrorangepi.download/forum/forumdisplay.php?fid=41And the emulators in RetrOrangePi are controlled by command line or run in a shell so you might be able to just use the emulators in thec64 Maxi..??
|
|
|
Post by jj0 on Jul 20, 2020 13:19:32 GMT
|
|
|
Post by spannernick on Jul 20, 2020 20:59:30 GMT
I added a link so you can download it from One Drive, I done it for you.. I left the Mega link there too.
|
|
|
Post by gurce on Jul 26, 2020 14:37:11 GMT
Wow, I gave this a try tonight for my TheC64-maxi, installed it along with PCU+XWM, works great! Thanks for making this! So great to navigate in Linux via the Maxi's keyboard!
...and now I'm wondering, controlling the mouse pointer via the joystick...
I get a sneaky feeling somebody asked about this already, so I'll have a search
Maybe this "xserver-xorg-input-joystick" package mentioned in this thread?
|
|
|
Post by MeneerJansen on Aug 19, 2020 17:00:46 GMT
Can I use this to alter things so that an ordinary USB joypad that is connected to TheC64 can use button 1 to fire instead of its shoulder button? Because if I connect a SNES like USB controller to my The64 (Maxi) then I must use the shoulder button to fire in a game. I'd like to connect my old Atari 2600 joystick the The64 (via an DB9 to USB converter). But that one has only one fire button.
|
|
|
Post by jj0 on Aug 20, 2020 10:49:17 GMT
Can I use this to alter things so that an ordinary USB joypad that is connected to TheC64 can use button 1 to fire instead of its shoulder button? Because if I connect a SNES like USB controller to my The64 (Maxi) then I must use the shoulder button to fire in a game. I'd like to connect my old Atari 2600 joystick the The64 (via an DB9 to USB converter). But that one has only one fire button. Yes, with XWM you have access to the all the files on the nandb so you can edit the gamecontrollerdb.txt to change buttons for your joytstick or even add it if it isn't in there already. Instructions on how to add/edit joysticks/controllers are elsewhere on the forum, probably easiest is to search for joystick and gamecontrollerdb.txt. While in XWM you should be able to investigate how the joystick/gamecontroller presents itself to the system (e.g.'dmesg') to gather what you need to add/change in gamecontrollerdb.txt. If you use PCU then you should make the changes to the gamecontrollerdb,txt on the PCU USB stick (if you use that feature) which is probably also an easy way to test them. As a starting point, this is the original text I wrote on adding joysticks, but there are other guides on the forum as well:
|
|
|
Post by MeneerJansen on Aug 26, 2020 14:05:49 GMT
Can I use this to alter things so that an ordinary USB joypad that is connected to TheC64 can use button 1 to fire instead of its shoulder button? Because if I connect a SNES like USB controller to my The64 (Maxi) then I must use the shoulder button to fire in a game. I'd like to connect my old Atari 2600 joystick the The64 (via an DB9 to USB converter). But that one has only one fire button. Yes, with XWM you have access to the all the files on the nandb so you can edit the gamecontrollerdb.txt to change buttons for your joytstick or even add it if it isn't in there already. Instructions on how to add/edit joysticks/controllers are elsewhere on the forum, probably easiest is to search for joystick and gamecontrollerdb.txt. While in XWM you should be able to investigate how the joystick/gamecontroller presents itself to the system (e.g.'dmesg') to gather what you need to add/change in gamecontrollerdb.txt. If you use PCU then you should make the changes to the gamecontrollerdb,txt on the PCU USB stick (if you use that feature) which is probably also an easy way to test them. As a starting point, this is the original text I wrote on adding joysticks, but there are other guides on the forum as well: Thank you very much for your kind and fast reply! I didn't get a mail to notify me of your reply so I'm kinda late in replying. Anyway, I did what you advised. I have a DB9 to USB dongle/adapter from Monster Joystics ( link). A DB9 plug is the one used in the 80's for the joysticks from the Atari 2600, Commodore etc. The adapter works fine on my Linux PC: I don't even have to configure anything. However, for the life of me I can't get it to work on The C64 Maxi. I booted my The C64 Maxi with the brilliant X-Windows Mod (easy peasy! boots really super fast!). And the Monster Joystick is recognized! When I double click on the joystick icon on the desktop the application evtest-qt starts and all buttons and axis' work. So The C64 really does "see" the joystick. One has to add said joystick/dongle to the text file called /usr/share/the64/ui/data/gamecontrollerdb.txt. This is because, as far as I can tell, the Monster Joystick is not yet "officially" added to the SDL2 database of joysticks. This "database" actually is the file gamecontrollerdb.txt (as far as I can tell). So I added the following line to it: 03000000C0160000DC27000001010000,Monster Joysticks MJ2DB9,a:b1,b:b4,back:b6,leftx:a0,lefty:a1,leftshoulder:b0,rightshoulder:b5,start:b7,x:b3,y:b2,platform:Linux,
I determined the ID w/ dmesg and tried different descriptions for the axis etc. Won't work. As far as I know one must describe the axis of a digital joystick as "dpdown:+a1,dpleft:-a0" or "leftx:a0,lefty:a1". It doesn't seem to matter much which you use because I changed them for my USB iBuffalo SNES controller clone (which actually does have a default entry in gamecontrollerdb.txt) and it works. For the iBuffalo I even could change the fire button from its default (shoulder button) to the A button! Very nice. So I am editing the proper text file, but the Monster Joystick converter with my Atari 2600 joystick just wont work. The Monster Joystick is recognized by dmesg as: hid-generic 0003:16C0:27DC.000D: input,hidraw5: USB HID v1.01 Joystick [Monster Joysticks MJ2DB9]
So the 32 number ID 3000000C0160000DC27000001010000 must be right? Or isn't it? Did I maybe make a typo in gamecontrollerdb.txt as fas as y'all can tell? I "constructed" the ID as follows. I changed the hexadecimal codes from dmesg into lowbyte/highbyte form. So for instance 16C0 becomes C016. Take the first 3 hexadecimal ID's from dmesg and append the HID version number (v. 1.01 = 0101) at the end like so: 0003 16C0 27DC 0101
Now reverse the (2-byte) order of each number (i.e. set it to lowbyte/highbyte) like so: 0300 C016 DC27 0101 Now add four zero's after each number like so: 0300 0000 C016 0000 DC27 0000 0101 0000
Finally remove spaces and paste into gamecontrollerdb.txt: 03000000C0160000DC27000001010000
Check if it's 32 numbers in length. It's right, aint it?
|
|
|
Post by jj0 on Aug 26, 2020 15:10:45 GMT
Finally remove spaces and paste into gamecontrollerdb.txt: 03000000C0160000DC27000001010000
Check if it's 32 numbers in length. It's right, aint it? It looks fine to me except that it's in uppercase. Not sure if that matters though.
|
|