I've just got the Mega65. After some tests the freeze menu stopped working. When I press the restore key the screen fills with random characters and crashes
How can I fix it?
freeze menu stopped working
-
- Problem!
- fabrimarvel
- Thread is marked as Resolved.
-
-
I've just got the Mega65. After some tests the freeze menu stopped working. When I press the restore key the screen fills with random characters and crashes
How can I fix it?I have experienced the same and I assume we need to be a little patient and await a newer version As far as I know the entire freezer is being rewritten.
-
Not sure if I should open a new thread, but I'll just recycle this one for now.
I have similar symptoms with my Mega65. I'm running ROM 920377, which is the latest AFAIK.
When booting from the internal SD-Card that came with my Mega65, the freezer menu works. Well, most of the time, that is.
Now, I use an external MicroSD-Card, where I copied the files from the original card to. Like MEGA65.ROM, the FREEZER.M65, all those D81 images plus a few other things like D64 images to use with the C64 Modes. The Mega65 does boot, but freezer does not even start. Pressing RESTORE has no effect. RUN STOP/RESTORE works however.
Also I cannot disable the CRT Emulation in the Setup menu. The menu shows it disabled, blatantly lying to me.
I mean, I can remove the external SD-Card, boot the Mega65 from the internal one and then reinsert the external SD-Card as a workaround, but I'd prefer not having to fiddle with this fingernail in the back of the computer all the time...
Any hints? Does the size matter? My MicroSD is of 64 GB capacity.
-
-
Any hints? Does the size matter? My MicroSD is of 64 GB capacity.
64GB is to big. You need a SDHC card, max. 32GB. See also userguide page 23....
-
As a matter of fact, no, I did partition and format it on my Linux box. I did not think it would matter. I will try this though.
I wonder however, what the difference is when I let the Mega65 handle it? Does it add some "secret ingredient" to the filesystem, e.g. raise a special flag?
Well, let's see, but first I have to backup the stuff already on the SD-Card.
-
Any hints? Does the size matter? My MicroSD is of 64 GB capacity.
64GB is to big. You need a SDHC card, max. 32GB. See also userguide page 23....
What, me having to read a manual? Woe is me!
What puzzles me though is that other than those hickups I mentioned, the 64 GB seems to work fine. But okee, I wanted to get a bunch of SD-Cards for my Raspis, so I'll go shopping tomorrow.
I'll report back, once I got hold of a 32 GB MicroSD-Card.
Thank you both for your help so far!
-
As a matter of fact, no, I did partition and format it on my Linux box. I did not think it would matter. I will try this though.
I wonder however, what the difference is when I let the Mega65 handle it? Does it add some "secret ingredient" to the filesystem, e.g. raise a special flag?
From the MEGA65 Welcome Guide (https://dansanderson.com/mega65/welcome/setting-up-microsd-card.html):
Preparing the microSD memory card
To use an SD card with the MEGA65, it must be formatted (erased and prepared) using the MEGA65. The SD card works like a regular storage drive when connected to your PC, but it contains additional data not visible to the PC that is used by MEGA65.
-
From the MEGA65 Welcome Guide (https://dansanderson.com/mega65/welcome/setting-up-microsd-card.html):
Preparing the microSD memory card
To use an SD card with the MEGA65, it must be formatted (erased and prepared) using the MEGA65. The SD card works like a regular storage drive when connected to your PC, but it contains additional data not visible to the PC that is used by MEGA65.
I see. Actually, the additional data is (kind of) visible, if you use Linux.
It is a second partition of a very weird type:
root@stallion:~# fdisk -l /dev/sdc
Disk /dev/sdc: 59.63 GiB, 64021856256 bytes, 125042688 sectors
Disk model: STORAGE DEVICE
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xa6cb7d83
Device Boot Start End Sectors Size Id Type
/dev/sdc1 2048 120848381 120846334 57.6G c W95 FAT32 (LBA)
/dev/sdc2 120848382 125042685 4194304 2G 41 PPC PReP Boot
Could not yet mount it however, but eventually my kernel just lacks the appropriate driver.
And yes, now that I prepared the card according to the manuals and guides, everything works! Sometimes, all you need is a nice RTFM slapped in your face.
Thank you so much everybody!