Setup docs need to be more specific were ROM files are concerned

[Deadweasel]

Thanks very much for the effort put into this project! I'd like to contribute some feedback on a documentation issue I ran into, and doubtless will cause headaches for other newbies like myself who wander in hopefully.

There is confusion regarding file extensions.

• The emulator kept throwing start errors at me, no matter what I tried to plop into the appropriate folder. The docs talk about "ROMs", the files provided by most sites actually have a ".bin" extension, and while the screenshot in the docs is technically accurate, showing no file extensions, most Windows users are running with the default setting that hides file extensions, so they'll never actually see what's going wrong. I only realized my error when I checked on a separate installation of VICE and discovered all the ROM files are sitting there ready to go, no file extensions at all.

Understood, there are legalities to steer clear of when referring to others' works, but users need specifics for those ROMS when they go out looking.

• For example, will a combined BASIC and KERNAL ROM suffice, as was used in the 64c, or do those need to be the older, segregated versions? Which kernal of the 3 revisions for the C64 will be the most reliable?
• Would it be crossing a legal line to recommend installing VICE on a desktop system and using the ROMs from that, instead? Could save a lot of hassle, questions and headaches if that were an option. "Install VICE, go to this folder, copy this this and that file to the matching folder on the SDcard. Bam, done.

Minor point regarding the ROMs for the various Commodore drives out there

• Not your fault, but may bear mentioning somewhere in the docs: Most of the drive ROMs will be named "dosxxxx", but the 1541-II ROM, for some reason, is named only d1541II. I kept re-naming the file to "dos1541ii" and getting nowhere, until I compared with the VICE defaults on my desktop.

[Digital-Monk]

I would like to second this, but with a specific focus on the BMPET ROMs. These seem to be the most complicated, due to the variety of PET machines and ROM configurations that are supported by the emulator. I am able to use VIC20, 64, 128, and Plus4 emulators, but have not yet been able to get the PET emulator to start.

Things I have tried:

• Copying ROMs from a working VICE installation (no renaming)
• Copying ROMs from the VICE 3.6 tarball that is linked to on the BMPET page (no renaming)
• Attempting to find an appropriate ROM from the VICE 3.6 tarball and rename it to match each name listed on the BMPET page (renaming for short names, leaving names alone for long names). Names and extensions matched as given, so short names had no extension, long names retained the .bin extension.

I would very much like to get this working. I have a project where I am 3D printing a PET-inspired case so that I can have a retro computer that runs all of the old Commodore machines. I had originally thought to do this with a full Raspberry Pi OS setup and some shell scripts along the lines of go64, govic, gopet, etc. But I love the BMC64 project! Awesome work! I just need a little more specific help.

The other option, which might be better all around if possible, would be to have the emulators state which ROM file they were unable to locate (or was the wrong size, or whatever). Doing so would require a better color combination on the failure screen, though, because dark blue on black is extremely hard to read.

Thank you for all the amazing work here!

[randyrossi]

The dark blue text is a bug I need to fix.

Copying the files from any VICE archive (vice-3.6.1/data/PET) has always worked for me. Can you paste a dir listing of what you have inside the top level PET dir?

On Tue, Feb 1, 2022 at 9:33 AM Digital-Monk @.***> wrote:

I would like to second this, but with a specific focus on the BMPET ROMs. These seem to be the most complicated, due to the variety of PET machines and ROM configurations that are supported by the emulator. I am able to use VIC20, 64, 128, and Plus4 emulators, but have not yet been able to get the PET emulator to start.

Things I have tried:

• Copying ROMs from a working VICE installation (no renaming)
• Copying ROMs from the VICE 3.6 tarball that is linked to on the BMPET page (no renaming)
• Attempting to find an appropriate ROM from the VICE 3.6 tarball and rename it to match each name listed on the BMPET page (renaming for short names, leaving names alone for long names). Names and extensions matched as given, so short names had no extension, long names retained the .bin extension.

I would very much like to get this working. I have a project where I am 3D printing a PET-inspired case so that I can have a retro computer that runs all of the old Commodore machines. I had originally thought to do this with a full Raspberry Pi OS setup and some shell scripts along the lines of go64, govic, gopet, etc. But I love the BMC64 project! Awesome work! I just need a little more specific help.

The other option, which might be better all around if possible, would be to have the emulators state which ROM file they were unable to locate (or was the wrong size, or whatever). Doing so would require a better color combination on the failure screen, though, because dark blue on black is extremely hard to read.

Thank you for all the amazing work here!

— Reply to this email directly, view it on GitHub https://github.com/randyrossi/bmc64/issues/202#issuecomment-1026907836, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAI3HKHADXYGNFAQW54KIL3UY7VL7ANCNFSM5JNFSLCQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you are subscribed to this thread.Message ID: @.***>

-- Randy Rossi

• "There are only two things that are hard about computer science; Naming things, Cache Invalidation, and Off-by-one errors."

[Digital-Monk]

This is what I have presently:

total 384 drwxr-xr-x 2 mac mac 8192 Jan 31 15:04 ./ drwxr-xr-x 16 mac mac 16384 Dec 31 1969 ../ -rw-r--r-- 1 mac mac 151 Feb 17 2021 amber.vpl -rw-r--r-- 1 mac mac 8192 Feb 17 2021 basic-1.901439-09-05-02-06.bin -rw-r--r-- 1 mac mac 8192 Feb 17 2021 basic-2.901465-01-02.bin -rw-r--r-- 1 mac mac 12288 Feb 17 2021 basic-4.901465-23-20-21.bin -rw-r--r-- 1 mac mac 2048 Feb 17 2021 characters-2.901447-10.bin -rw-r--r-- 1 mac mac 4096 Feb 17 2021 characters.901640-01.bin -rw-r--r-- 1 mac mac 2048 Feb 17 2021 chargen.de -rw-r--r-- 1 mac mac 2048 Feb 17 2021 edit-1-n.901439-03.bin -rw-r--r-- 1 mac mac 2048 Feb 17 2021 edit-2-b.901474-01.bin -rw-r--r-- 1 mac mac 2048 Feb 17 2021 edit-2-n.901447-24.bin -rw-r--r-- 1 mac mac 2048 Feb 17 2021 edit-4-40-b-50Hz.ts.bin -rw-r--r-- 1 mac mac 2048 Feb 17 2021 edit-4-40-b-60Hz.ts.bin -rw-r--r-- 1 mac mac 2048 Feb 17 2021 edit-4-40-n-50Hz.901498-01.bin -rw-r--r-- 1 mac mac 2048 Feb 17 2021 edit-4-40-n-60Hz.901499-01.bin -rw-r--r-- 1 mac mac 2048 Feb 17 2021 edit-4-80-b-50Hz.901474-04.bin -rw-r--r-- 1 mac mac 2048 Feb 17 2021 edit-4-80-b-50Hz.901474-04_.bin -rw-r--r-- 1 mac mac 2048 Feb 17 2021 edit-4-80-b-60Hz.901474-03.bin -rw-r--r-- 1 mac mac 2048 Feb 17 2021 edit-4-b-noCRTC.901474-02.bin -rw-r--r-- 1 mac mac 151 Feb 17 2021 green.vpl -rw-r--r-- 1 mac mac 4096 Feb 17 2021 hre-9000.324992-02.bin -rw-r--r-- 1 mac mac 4096 Feb 17 2021 hre-a000.324993-02.bin -rw-r--r-- 1 mac mac 80 Feb 17 2021 hre.vrs -rw-r--r-- 1 mac mac 4096 Feb 17 2021 kernal-1.901439-04-07.bin -rw-r--r-- 1 mac mac 4096 Feb 17 2021 kernal-2.901465-03.bin -rw-r--r-- 1 mac mac 4096 Feb 17 2021 kernal-4.901465-22.bin -rw-r--r-- 1 mac mac 59 Jun 2 2021 PUT_ROMS_HERE -rw-r--r-- 1 mac mac 323 Feb 17 2021 rom1g.vrs -rw-r--r-- 1 mac mac 314 Feb 17 2021 rom2b.vrs -rw-r--r-- 1 mac mac 314 Feb 17 2021 rom2g.vrs -rw-r--r-- 1 mac mac 300 Feb 17 2021 rom4b40.vrs -rw-r--r-- 1 mac mac 308 Feb 17 2021 rom4b80.vrs -rw-r--r-- 1 mac mac 307 Feb 17 2021 rom4g40.vrs -rw-r--r-- 1 mac mac 570 Feb 17 2021 romsuperpet.vrs -rw-r--r-- 1 mac mac 2781 Jun 2 2021 rpi_buus_pos.vkm -rw-r--r-- 1 mac mac 5157 Jun 2 2021 rpi_buus_sym.vkm -rw-r--r-- 1 mac mac 2285 Jun 2 2021 rpi_grus_pos.vkm -rw-r--r-- 1 mac mac 4568 Jun 2 2021 rpi_grus_sym.vkm -rw-r--r-- 1 mac mac 4096 Feb 17 2021 waterloo-a000.901898-01.bin -rw-r--r-- 1 mac mac 4096 Feb 17 2021 waterloo-b000.901898-02.bin -rw-r--r-- 1 mac mac 4096 Feb 17 2021 waterloo-c000.901898-03.bin -rw-r--r-- 1 mac mac 4096 Feb 17 2021 waterloo-d000.901898-04.bin -rw-r--r-- 1 mac mac 2048 Feb 17 2021 waterloo-e000.901897-01.bin -rw-r--r-- 1 mac mac 4096 Feb 17 2021 waterloo-f000.901898-05.bin -rw-r--r-- 1 mac mac 143 Feb 17 2021 white.vpl

Thank you for the very quick response!

[randyrossi]

Here is what I have. Maybe you did copy . ? It seems you are missing the files without extensions (like basic1, basic2, etc)

12/21/2019 11:17 AM 8,192 basic1 12/21/2019 11:17 AM 8,192 basic2 12/21/2019 11:17 AM 12,288 basic4 12/21/2019 11:17 AM 4,096 characters.901640-01.bin 12/21/2019 11:17 AM 2,048 chargen 12/22/2019 03:11 AM 16,384 dos1001 12/22/2019 03:11 AM 16,384 dos1540 12/22/2019 03:11 AM 16,384 dos1541 12/22/2019 03:11 AM 16,384 dos1551 12/22/2019 03:11 AM 32,768 dos1570 12/22/2019 03:11 AM 32,768 dos1571 12/22/2019 03:11 AM 32,768 dos1581 12/22/2019 03:11 AM 16,384 dos2031 12/22/2019 03:11 AM 8,192 dos2040 12/22/2019 03:11 AM 12,288 dos3040 12/22/2019 03:11 AM 12,288 dos4040 12/21/2019 11:17 AM 2,048 edit1g 12/21/2019 11:17 AM 2,048 edit2b 12/21/2019 11:17 AM 2,048 edit2g 12/21/2019 11:17 AM 2,048 edit4b40 12/21/2019 11:17 AM 2,048 edit4b80 12/21/2019 11:17 AM 2,048 edit4g40 12/21/2019 11:17 AM 4,096 hre-9000.324992-02.bin 12/21/2019 11:17 AM 4,096 hre-a000.324993-02.bin 12/21/2019 11:17 AM 80 hre.vrs 12/21/2019 11:17 AM 4,096 kernal1 12/21/2019 11:17 AM 4,096 kernal2 12/21/2019 11:17 AM 4,096 kernal4 12/28/2019 09:43 AM 59 PUT_ROMS_HERE 12/21/2019 11:17 AM 246 rom1g.vrs 12/21/2019 11:17 AM 246 rom2b.vrs 12/21/2019 11:17 AM 246 rom2g.vrs 12/21/2019 11:17 AM 230 rom4b40.vrs 12/21/2019 11:17 AM 230 rom4b80.vrs 12/21/2019 11:17 AM 230 rom4g40.vrs 12/21/2019 11:17 AM 511 romsuperpet.vrs 12/28/2019 09:43 AM 2,781 rpi_buus_pos.vkm 12/28/2019 09:43 AM 5,157 rpi_buus_sym.vkm 12/28/2019 09:43 AM 2,285 rpi_grus_pos.vkm 12/28/2019 09:43 AM 4,568 rpi_grus_sym.vkm 12/21/2019 11:17 AM 4,096 waterloo-a000.901898-01.bin 12/21/2019 11:17 AM 4,096 waterloo-b000.901898-02.bin 12/21/2019 11:17 AM 4,096 waterloo-c000.901898-03.bin 12/21/2019 11:17 AM 4,096 waterloo-d000.901898-04.bin 12/21/2019 11:17 AM 2,048 waterloo-e000.901897-01.bin 12/21/2019 11:17 AM 4,096 waterloo-f000.901898-05.bin

On Tue, Feb 1, 2022 at 11:02 AM Digital-Monk @.***> wrote:

This is what I have presently:

total 384 drwxr-xr-x 2 mac mac 8192 Jan 31 15:04 ./ drwxr-xr-x 16 mac mac 16384 Dec 31 1969 ../ -rw-r--r-- 1 mac mac 151 Feb 17 2021 amber.vpl -rw-r--r-- 1 mac mac 8192 Feb 17 2021 basic-1.901439-09-05-02-06.bin -rw-r--r-- 1 mac mac 8192 Feb 17 2021 basic-2.901465-01-02.bin -rw-r--r-- 1 mac mac 12288 Feb 17 2021 basic-4.901465-23-20-21.bin -rw-r--r-- 1 mac mac 2048 Feb 17 2021 characters-2.901447-10.bin -rw-r--r-- 1 mac mac 4096 Feb 17 2021 characters.901640-01.bin -rw-r--r-- 1 mac mac 2048 Feb 17 2021 chargen.de -rw-r--r-- 1 mac mac 2048 Feb 17 2021 edit-1-n.901439-03.bin -rw-r--r-- 1 mac mac 2048 Feb 17 2021 edit-2-b.901474-01.bin -rw-r--r-- 1 mac mac 2048 Feb 17 2021 edit-2-n.901447-24.bin -rw-r--r-- 1 mac mac 2048 Feb 17 2021 edit-4-40-b-50Hz.ts.bin -rw-r--r-- 1 mac mac 2048 Feb 17 2021 edit-4-40-b-60Hz.ts.bin -rw-r--r-- 1 mac mac 2048 Feb 17 2021 edit-4-40-n-50Hz.901498-01.bin -rw-r--r-- 1 mac mac 2048 Feb 17 2021 edit-4-40-n-60Hz.901499-01.bin -rw-r--r-- 1 mac mac 2048 Feb 17 2021 edit-4-80-b-50Hz.901474-04.bin -rw-r--r-- 1 mac mac 2048 Feb 17 2021 edit-4-80-b-50Hz.901474-04_.bin -rw-r--r-- 1 mac mac 2048 Feb 17 2021 edit-4-80-b-60Hz.901474-03.bin -rw-r--r-- 1 mac mac 2048 Feb 17 2021 edit-4-b-noCRTC.901474-02.bin -rw-r--r-- 1 mac mac 151 Feb 17 2021 green.vpl -rw-r--r-- 1 mac mac 4096 Feb 17 2021 hre-9000.324992-02.bin -rw-r--r-- 1 mac mac 4096 Feb 17 2021 hre-a000.324993-02.bin -rw-r--r-- 1 mac mac 80 Feb 17 2021 hre.vrs -rw-r--r-- 1 mac mac 4096 Feb 17 2021 kernal-1.901439-04-07.bin -rw-r--r-- 1 mac mac 4096 Feb 17 2021 kernal-2.901465-03.bin -rw-r--r-- 1 mac mac 4096 Feb 17 2021 kernal-4.901465-22.bin -rw-r--r-- 1 mac mac 59 Jun 2 2021 PUT_ROMS_HERE -rw-r--r-- 1 mac mac 323 Feb 17 2021 rom1g.vrs -rw-r--r-- 1 mac mac 314 Feb 17 2021 rom2b.vrs -rw-r--r-- 1 mac mac 314 Feb 17 2021 rom2g.vrs -rw-r--r-- 1 mac mac 300 Feb 17 2021 rom4b40.vrs -rw-r--r-- 1 mac mac 308 Feb 17 2021 rom4b80.vrs -rw-r--r-- 1 mac mac 307 Feb 17 2021 rom4g40.vrs -rw-r--r-- 1 mac mac 570 Feb 17 2021 romsuperpet.vrs -rw-r--r-- 1 mac mac 2781 Jun 2 2021 rpi_buus_pos.vkm -rw-r--r-- 1 mac mac 5157 Jun 2 2021 rpi_buus_sym.vkm -rw-r--r-- 1 mac mac 2285 Jun 2 2021 rpi_grus_pos.vkm -rw-r--r-- 1 mac mac 4568 Jun 2 2021 rpi_grus_sym.vkm -rw-r--r-- 1 mac mac 4096 Feb 17 2021 waterloo-a000.901898-01.bin -rw-r--r-- 1 mac mac 4096 Feb 17 2021 waterloo-b000.901898-02.bin -rw-r--r-- 1 mac mac 4096 Feb 17 2021 waterloo-c000.901898-03.bin -rw-r--r-- 1 mac mac 4096 Feb 17 2021 waterloo-d000.901898-04.bin -rw-r--r-- 1 mac mac 2048 Feb 17 2021 waterloo-e000.901897-01.bin -rw-r--r-- 1 mac mac 4096 Feb 17 2021 waterloo-f000.901898-05.bin -rw-r--r-- 1 mac mac 143 Feb 17 2021 white.vpl

Thank you for the very quick response!

— Reply to this email directly, view it on GitHub https://github.com/randyrossi/bmc64/issues/202#issuecomment-1027005291, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAI3HKCUB6IJ3OB2LTTKUQTUY77Z5ANCNFSM5JNFSLCQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you commented.Message ID: @.***>

-- Randy Rossi

• "There are only two things that are hard about computer science; Naming things, Cache Invalidation, and Off-by-one errors."

[Digital-Monk]

Hmmm... What version of VICE is BMPET based on? My installed VICE is v3.5 (I need to update), and it's using the long filenames for everything:

*** VICE Version 3.5 ***

Welcome to xpet, the free portable PET Emulator.

Current VICE team members: Martin Pottendorfer, Marco van den Heuvel, Fabrizio Gennari, Groepaz, Errol Smith, Ingo Korb, Olaf Seibert, Marcus Sutton, Kajtar Zsolt, AreaScout, Bas Wassink, Michael C. Martin, Christopher Phillips, David Hogan, Empathic Qubit, Roberto Muscedere.

This is free software with ABSOLUTELY NO WARRANTY. See the "About VICE" command for more info.

Loading system file /usr/local/share/vice/PET/characters-2.901447-10.bin'. Loading system file /usr/local/share/vice/PET/basic-4.901465-23-20-21.bin'. Loading system file /usr/local/share/vice/PET/kernal-4.901465-22.bin'. PETMEM: Identified Kernal 4 ROM by checksum. Loading system file /usr/local/share/vice/PET/edit-4-40-n-50Hz.901498-01.bin'. PETMEM: Identified 40 columns editor by checksum. PETMEM: ROM screen width is 40. Loading system file /usr/local/share/vice/PET/waterloo-a000.901898-01.bin'. Loading system file /usr/local/share/vice/PET/waterloo-b000.901898-02.bin'. Loading system file /usr/local/share/vice/PET/waterloo-c000.901898-03.bin'. Loading system file /usr/local/share/vice/PET/waterloo-d000.901898-04.bin'. Loading system file /usr/local/share/vice/PET/waterloo-e000.901897-01.bin'. Loading system file /usr/local/share/vice/PET/waterloo-f000.901898-05.bin'. PET: Initializing IEEE488 bus... Loading system file /usr/local/share/vice/PRINTER/mps803'. Palette: Loading palette /usr/local/share/vice/PRINTER/mps803.vpl'. Loading system file /usr/local/share/vice/PRINTER/nl10-cbm'. Palette: Loading palette /usr/local/share/vice/PRINTER/nl10.vpl'. NL10: Printer driver initialized. Palette: Loading palette /usr/local/share/vice/PRINTER/1520.vpl'. Loading system file /usr/local/share/vice/DRIVES/dos2031'. Loading system file /usr/local/share/vice/DRIVES/dos2040'. Loading system file /usr/local/share/vice/DRIVES/dos3040'. Loading system file /usr/local/share/vice/DRIVES/dos4040'. Loading system file /usr/local/share/vice/DRIVES/dos1001'. Loading system file `/usr/local/share/vice/DRIVES/dos9000'. Drive: Finished loading ROM images.

[randyrossi]

Try the 3.3 VICE archive. Maybe the files changed?

On Tue, Feb 1, 2022 at 11:28 AM Digital-Monk @.***> wrote:

Hmmm... What version of VICE is BMPET based on? My installed VICE is v3.5 (I need to update), and it's using the long filenames for everything:

*** VICE Version 3.5 ***

Welcome to xpet, the free portable PET Emulator.

Current VICE team members: Martin Pottendorfer, Marco van den Heuvel, Fabrizio Gennari, Groepaz, Errol Smith, Ingo Korb, Olaf Seibert, Marcus Sutton, Kajtar Zsolt, AreaScout, Bas Wassink, Michael C. Martin, Christopher Phillips, David Hogan, Empathic Qubit, Roberto Muscedere.

This is free software with ABSOLUTELY NO WARRANTY. See the "About VICE" command for more info.

Loading system file /usr/local/share/vice/PET/characters-2.901447-10.bin'. Loading system file /usr/local/share/vice/PET/basic-4.901465-23-20-21.bin'. Loading system file /usr/local/share/vice/PET/kernal-4.901465-22.bin'. PETMEM: Identified Kernal 4 ROM by checksum. Loading system file /usr/local/share/vice/PET/edit-4-40-n-50Hz.901498-01.bin'. PETMEM: Identified 40 columns editor by checksum. PETMEM: ROM screen width is 40. Loading system file /usr/local/share/vice/PET/waterloo-a000.901898-01.bin'. Loading system file /usr/local/share/vice/PET/waterloo-b000.901898-02.bin'. Loading system file /usr/local/share/vice/PET/waterloo-c000.901898-03.bin'. Loading system file /usr/local/share/vice/PET/waterloo-d000.901898-04.bin'. Loading system file /usr/local/share/vice/PET/waterloo-e000.901897-01.bin'. Loading system file /usr/local/share/vice/PET/waterloo-f000.901898-05.bin'. PET: Initializing IEEE488 bus... Loading system file /usr/local/share/vice/PRINTER/mps803'. Palette: Loading palette /usr/local/share/vice/PRINTER/mps803.vpl'. Loading system file /usr/local/share/vice/PRINTER/nl10-cbm'. Palette: Loading palette /usr/local/share/vice/PRINTER/nl10.vpl'. NL10: Printer driver initialized. Palette: Loading palette /usr/local/share/vice/PRINTER/1520.vpl'. Loading system file /usr/local/share/vice/DRIVES/dos2031'. Loading system file /usr/local/share/vice/DRIVES/dos2040'. Loading system file /usr/local/share/vice/DRIVES/dos3040'. Loading system file /usr/local/share/vice/DRIVES/dos4040'. Loading system file /usr/local/share/vice/DRIVES/dos1001'. Loading system file `/usr/local/share/vice/DRIVES/dos9000'. Drive: Finished loading ROM images.

— Reply to this email directly, view it on GitHub https://github.com/randyrossi/bmc64/issues/202#issuecomment-1027033022, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAI3HKESR3Q276P55GPTK7DUZAC2ZANCNFSM5JNFSLCQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you commented.Message ID: @.***>

-- Randy Rossi

• "There are only two things that are hard about computer science; Naming things, Cache Invalidation, and Off-by-one errors."

[Digital-Monk]

That fixed it. Here's a permanent wayback/archive link to the .7z archive I pulled ROMs from:

https://web.archive.org/web/*/http://www.zimmers.net/anonftp/pub/cbm/crossplatform/emulators/VICE/GTK3VICE-3.3-win32.7z

The full archive is for Win32, but the ROMs are the same for all platforms, of course, so it works fine.