Run full-blown vice on the Mini/Maxi/VIC-20

clindsa1
BASIC

Posts: 1

Run full-blown vice on the Mini/Maxi/VIC-20 Jul 28, 2021 14:52:45 GMT

Quote

Post by clindsa1 on Jul 28, 2021 14:52:45 GMT

This is amazing. Epic props to you.

I have been trying to compile the v2.4 code myself, because I am trying to enable MIDI support. I have failed miserably several times.

Would you be able to post the set of steps you used for compiling? I'm pretty sure my issues are a missing requirement or some addition to the configure or make command I just don't know about.

Thank you for any assistance.

jj0
THEC64 Developer

Manic Miner rules!

Posts: 1,020
Member is Online

Run full-blown vice on the Mini/Maxi/VIC-20 Jul 29, 2021 8:47:31 GMT

Quote

Post by jj0 on Jul 29, 2021 8:47:31 GMT

Jul 28, 2021 14:52:45 GMT clindsa1 said:

This is amazing. Epic props to you.

I have been trying to compile the v2.4 code myself, because I am trying to enable MIDI support. I have failed miserably several times.

Would you be able to post the set of steps you used for compiling? I'm pretty sure my issues are a missing requirement or some addition to the configure or make command I just don't know about.

Thank you for any assistance.

Thanks.

I've found it easisest to avoid all cross compiling and as the Ubuntu Xenial environment matches THE64 glibc environment I chroot into an armhf Armbian Xenial rootfs on my Linux PC and do my compiling from there. Though for Vice I think I did it in an XWM rootfs (which is Debian jessie) but it works in Xenial just as well. You do need to install the 'qemu-user-static' package on the main Linux OS to it emulate the arm SoC and mount bind the PC's /dev directory to the Armbian rootfs dev directory.

For vice (2.4) I used (you might need to change this a bit depending on exactly which 2.4 version you use):

./configure --prefix=/usr --enable-sdlui --enable-fullscreen --disable-gnomeui --enable-rs232 --disable-midi --disable-lame --disable-nls --disable-dingoo --disable-dingux --disable-ffmpeg --disable-quicktime --enable-ethernet --disable-ipv6 --disable-parsid --disable-bundle --disable-editline --disable-wiz --disable-static-lame --disable-hidmgr --disable-hidutils --with-alsa --without-pulse --without-sdlsound --without-oss --without-png --without-picasso96 --without-cocoa --without-x --no-create --no-recursion --with-residfp --with-resid

And then installed any missing xxxx-dev libraries that it complained about. I haven't kept a list of those. After that it's just 'make'.

spannernick
THEC64 Administrator

PCUAE Creator.. :)

Posts: 2,829

Run full-blown vice on the Mini/Maxi/VIC-20 Jul 29, 2021 11:18:47 GMT

Quote

Post by spannernick on Jul 29, 2021 11:18:47 GMT

You will need the latest version of Ubuntu too 21.04, if you use 20.04 then it will use a older version of 'qemu-user-static' package and will not work, so you can not use Linux Mint cause it use a older version to that don't work with Armbian rootfs, its a bug in 'qemu-user-static' and if you use a Armbian rootfs as chroot.

Last Edit: Jul 29, 2021 11:19:41 GMT by spannernick

1

knightfire BASIC Posts: 1	Run full-blown vice on the Mini/Maxi/VIC-20 Oct 5, 2021 4:21:02 GMT Quote Select Post Deselect Post Link to Post Member Give Gift Back to Top Post by knightfire on Oct 5, 2021 4:21:02 GMT I'm interested in the PET 4032 (40x25) might you replace the SuperPET mode with it? Also will it display correctly at HD resolution?

jj0
THEC64 Developer

Manic Miner rules!

Posts: 1,020
Member is Online

Run full-blown vice on the Mini/Maxi/VIC-20 Oct 5, 2021 11:57:27 GMT

Quote

Post by jj0 on Oct 5, 2021 11:57:27 GMT

Oct 5, 2021 4:21:02 GMT knightfire said:

I'm interested in the PET 4032 (40x25) might you replace the SuperPET mode with it? Also will it display correctly at HD resolution?

I think you can do that by going into the emulator menu and change the machine type - all pet types are emulated by the same emulator. Not sure how it will display, I suggest you check it out and report back what it looks like.

spannernick
THEC64 Administrator

PCUAE Creator.. :)

Posts: 2,829

Run full-blown vice on the Mini/Maxi/VIC-20 Oct 8, 2021 14:04:35 GMT

Quote

Post by spannernick on Oct 8, 2021 14:04:35 GMT

Oct 5, 2021 4:21:02 GMT knightfire said:

I'm interested in the PET 4032 (40x25) might you replace the SuperPET mode with it? Also will it display correctly at HD resolution?

I already changed PET in VICE Mode in PCUAE to PET 4032, Press CTRL-F3 in PCUAE Mode(on the carousel Screen or Classic Screen) and select VICE Mode in the Mode Changer Menu and then press CTRL-1 to start up PET, I changed it cause thats the PET I used in 1983 before I got a C64...

This is what it looks like on the C64 Maxi, could not remove the screen shadow on the right of the screen.

Last Edit: Oct 8, 2021 14:07:55 GMT by spannernick

1

andromeda1968 BASIC Posts: 7	Run full-blown vice on the Mini/Maxi/VIC-20 Jan 15, 2022 16:58:10 GMT Quote Select Post Deselect Post Link to Post Member Give Gift Back to Top Post by andromeda1968 on Jan 15, 2022 16:58:10 GMT fantastic job thanks...yur are great!! there is a possibility for a new version with vice 3.6

spannernick THEC64 Administrator PCUAE Creator.. :) Posts: 2,829	Run full-blown vice on the Mini/Maxi/VIC-20 Jan 15, 2022 17:12:11 GMT andromeda1968 likes this Quote Select Post Deselect Post Link to Post Member Give Gift Back to Top Post by spannernick on Jan 15, 2022 17:12:11 GMT I think we tried a newer version of VICE but it was to slow, frame rate was low.
	1

jj0
THEC64 Developer

Manic Miner rules!

Posts: 1,020
Member is Online

Run full-blown vice on the Mini/Maxi/VIC-20 Jan 16, 2022 21:13:06 GMT andromeda1968 likes this

Quote

Post by jj0 on Jan 16, 2022 21:13:06 GMT

Jan 15, 2022 16:58:10 GMT andromeda1968 said:

fantastic job thanks...yur are great!!

there is a possibility for a new version with vice 3.6

This is a compiled version of x64 v3.6 (goes into the bin folder) and the additonal libraries (goes into the lib folder). You need to experiment with running it form the commandline (via the UART), I haven't been able to get it to show something on the screen. If it does run it will be pretty slow I think.

andromeda1968 BASIC Posts: 7	Run full-blown vice on the Mini/Maxi/VIC-20 Jan 17, 2022 10:52:01 GMT Quote Select Post Deselect Post Link to Post Member Give Gift Back to Top Post by andromeda1968 on Jan 17, 2022 10:52:01 GMT thanks but can you create for me a bin file for update my C64 maxi?? with 3.6 vice?

jj0
THEC64 Developer

Manic Miner rules!

Posts: 1,020
Member is Online

Run full-blown vice on the Mini/Maxi/VIC-20 Jan 17, 2022 10:59:25 GMT andromeda1968 likes this

Quote

Post by jj0 on Jan 17, 2022 10:59:25 GMT

Jan 17, 2022 10:52:01 GMT andromeda1968 said:

thanks but can you create for me a bin file for update my C64 maxi?? with 3.6 vice?

No I can't as as I mentioned I didn't get it to run properly on the Maxi. So it's just for experimental purposes for anyone who wants to try to get it to work.

turrican9
PCUAE Supporter

Posts: 38

Run full-blown vice on the Mini/Maxi/VIC-20 Dec 4, 2022 15:05:03 GMT

Quote

Post by turrican9 on Dec 4, 2022 15:05:03 GMT

So I couldn't get this working. In the end I found that the issue was that this package is not compatible with my USB to DB9 joystick adapter. It has the 4 menu buttons built in aswell, and is built to work with C64 mini/TheC64 and TheVIC20, but did not work with this VICE package. When I plugged in my original TheC64 joystick everything was working okay.

I tried I few games and noticed I didn't get smooth scrolling.

To me it seems that the hardware used in C64mini, TheC64/TheVIC20 is not up to the task of running much else than the standard firmware. As soon as I experiment with stuff like this or Project carousel it seems like there is always some kind of problem. Like slowdowns, not smooth scrolling, lockups or things not working correctly.

I appreciate all the nice work done but for me it seems like it's best to stick to the standard firmware and setup.

1410

lasttape
Creatures

Posts: 25

Run full-blown vice on the Mini/Maxi/VIC-20 Jun 4, 2023 18:45:37 GMT

Quote

Post by lasttape on Jun 4, 2023 18:45:37 GMT

Jul 29, 2021 8:47:31 GMT jj0 said:

Jul 28, 2021 14:52:45 GMT clindsa1 said:

This is amazing. Epic props to you.

I have been trying to compile the v2.4 code myself, because I am trying to enable MIDI support. I have failed miserably several times.

Would you be able to post the set of steps you used for compiling? I'm pretty sure my issues are a missing requirement or some addition to the configure or make command I just don't know about.

Thank you for any assistance.

Thanks.

I've found it easisest to avoid all cross compiling and as the Ubuntu Xenial environment matches THE64 glibc environment I chroot into an armhf Armbian Xenial rootfs on my Linux PC and do my compiling from there. Though for Vice I think I did it in an XWM rootfs (which is Debian jessie) but it works in Xenial just as well. You do need to install the 'qemu-user-static' package on the main Linux OS to it emulate the arm SoC and mount bind the PC's /dev directory to the Armbian rootfs dev directory.

For vice (2.4) I used (you might need to change this a bit depending on exactly which 2.4 version you use):

./configure --prefix=/usr --enable-sdlui --enable-fullscreen --disable-gnomeui --enable-rs232 --disable-midi --disable-lame --disable-nls --disable-dingoo --disable-dingux --disable-ffmpeg --disable-quicktime --enable-ethernet --disable-ipv6 --disable-parsid --disable-bundle --disable-editline --disable-wiz --disable-static-lame --disable-hidmgr --disable-hidutils --with-alsa --without-pulse --without-sdlsound --without-oss --without-png --without-picasso96 --without-cocoa --without-x --no-create --no-recursion --with-residfp --with-resid

And then installed any missing xxxx-dev libraries that it complained about. I haven't kept a list of those. After that it's just 'make'.

when I build vice2 I got a hardcoded error

#include "/home/chris/src/the64-hardware/firmware/src/videoarch.h"

could any one help me with this file?

unknown storage on my system

2283

jj0
THEC64 Developer

Manic Miner rules!

Posts: 1,020
Member is Online

Run full-blown vice on the Mini/Maxi/VIC-20 Jun 5, 2023 11:40:40 GMT

Quote

Post by jj0 on Jun 5, 2023 11:40:40 GMT

Jun 4, 2023 18:45:37 GMT lasttape said:

Jul 29, 2021 8:47:31 GMT jj0 said:

Thanks.

I've found it easisest to avoid all cross compiling and as the Ubuntu Xenial environment matches THE64 glibc environment I chroot into an armhf Armbian Xenial rootfs on my Linux PC and do my compiling from there. Though for Vice I think I did it in an XWM rootfs (which is Debian jessie) but it works in Xenial just as well. You do need to install the 'qemu-user-static' package on the main Linux OS to it emulate the arm SoC and mount bind the PC's /dev directory to the Armbian rootfs dev directory.

For vice (2.4) I used (you might need to change this a bit depending on exactly which 2.4 version you use):

./configure --prefix=/usr --enable-sdlui --enable-fullscreen --disable-gnomeui --enable-rs232 --disable-midi --disable-lame --disable-nls --disable-dingoo --disable-dingux --disable-ffmpeg --disable-quicktime --enable-ethernet --disable-ipv6 --disable-parsid --disable-bundle --disable-editline --disable-wiz --disable-static-lame --disable-hidmgr --disable-hidutils --with-alsa --without-pulse --without-sdlsound --without-oss --without-png --without-picasso96 --without-cocoa --without-x --no-create --no-recursion --with-residfp --with-resid

And then installed any missing xxxx-dev libraries that it complained about. I haven't kept a list of those. After that it's just 'make'.

when I build vice2 I got a hardcoded error

#include "/home/chris/src/the64-hardware/firmware/src/videoarch.h"

could any one help me with this file?

unknown storage on my system

The instructions for compiling in this thread are for compiling vice 2.4 from the official source. If you have '/home/chris' somewhere the I assume you are trying to compile vice 2.4 from the sources from RGL? At the minimum you probably need to do a 'make clean' and a new './configure .....'. But as far as I know RGL doesn't use the actual vice (x64) binary but creates some kind of library out of it that they use with the Carousel. Check out this thread where there's more info about building those.

lasttape
Creatures

Posts: 25

Run full-blown vice on the Mini/Maxi/VIC-20 Jun 6, 2023 10:27:07 GMT

Quote

Post by lasttape on Jun 6, 2023 10:27:07 GMT

Jun 5, 2023 11:40:40 GMT jj0 said:

Jun 4, 2023 18:45:37 GMT lasttape said:

when I build vice2 I got a hardcoded error

#include "/home/chris/src/the64-hardware/firmware/src/videoarch.h"

could any one help me with this file?

unknown storage on my system

The instructions for compiling in this thread are for compiling vice 2.4 from the official source. If you have '/home/chris' somewhere the I assume you are trying to compile vice 2.4 from the sources from RGL? At the minimum you probably need to do a 'make clean' and a new './configure .....'. But as far as I know RGL doesn't use the actual vice (x64) binary but creates some kind of library out of it that they use with the Carousel. Check out this thread where there's more info about building those.

the base system that I want to use for compiling: git clone github.com/armbian/build.git armbian

it's configurable build from source

ill try the following

sudo apt install pkg-config libasound2-dev libjpeg-dev libpng*-dev bison flex g++ dpkg-dev gcc make gcc-aarch64-linux-gnu* binutils-aarch64-linux-gnu binutils-multiarch arm-linux-gnueabi-g++-10 readline*-dev
dpkg --add-architecture armhf
sudo apt-get update && sudo apt-get install libudev-dev:armhf
git clone github.com/retro-games-ltd/redquark-sixtyfour.git
cd redquark-sixtyfour/src/
git clone github.com/retro-games-ltd/vice-2.4.git vice2
cd vice2 && chmod +x the64_configure
./the64_configure --prefix=/usr --enable-sdlui --enable-fullscreen --disable-gnomeui --enable-rs232 --disable-midi --disable-lame --disable-nls --disable-dingoo --disable-dingux --disable-ffmpeg --disable-quicktime --enable-ethernet --disable-ipv6 --disable-parsid --disable-bundle --disable-editline --disable-wiz --disable-static-lame --disable-hidmgr --disable-hidutils --with-alsa --without-pulse --without-sdlsound --without-oss --without-png --without-picasso96 --without-cocoa --without-x --no-create --no-recursion --with-residfp --with-resid --host=aarch64-linux-gnu CC=arm-linux-gnueabi-gcc-10

cd ../../../
./configure --host=aarch64-linux-gnu CC=arm-linux-gnueabi-gcc-10 CFLAGS="-lreadline"
make

with following result:

checking for aarch64-linux-gnu-g++... aarch64-linux-gnu-g++
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether aarch64-linux-gnu-g++ accepts -g... yes
checking for aarch64-linux-gnu-gcc... arm-linux-gnueabi-gcc-10
checking whether we are using the GNU C compiler... yes
checking whether arm-linux-gnueabi-gcc-10 accepts -g... yes
checking for arm-linux-gnueabi-gcc-10 option to accept ISO C89... none needed
checking how to run the C preprocessor... arm-linux-gnueabi-gcc-10 -E
checking for aarch64-linux-gnu-ar... aarch64-linux-gnu-ar
checking the archiver (aarch64-linux-gnu-ar) interface... ar
checking for aarch64-linux-gnu-strip... aarch64-linux-gnu-strip
checking for aarch64-linux-gnu-pkg-config... /usr/bin/aarch64-linux-gnu-pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for alsa... yes
checking for libjpeg... yes
checking for libpng16... yes
checking for zlib... yes
checking for libgcrypt-config... libgcrypt-config
./configure: line 4243: libgcrypt-config: command not found
./configure: line 4244: libgcrypt-config: command not found
checking for getopt... yes
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... no
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking whether getopt is declared... yes
checking whether getsubopt is declared... yes
checking whether getopt_long is declared... no
checking for getopt_long... yes
checking for getsubopt... yes
checking for logf... no
checking for expf... no
checking if the logf prototype is present... yes
checking if the expf prototype is present... yes
configure: creating ./config.status
config.status: creating src/vice2/src/resid-fp/siddefs-fp.h
configure: creating ./config.status
config.status: creating src/vice2/src/resid-fp/siddefs-fp.h
config.status: creating Makefile
config.status: creating release.mk
config.status: creating src/viceport/Makefile
config.status: creating src/vbuild/Makefile.libc64cart
config.status: creating src/vbuild/Makefile.libc64cartsystem
config.status: creating src/vbuild/Makefile.libc64commoncart
config.status: creating src/vbuild/Makefile.libc64
config.status: creating src/vbuild/Makefile.libvic20
config.status: creating src/vbuild/Makefile.libvic20cart
config.status: creating src/vbuild/Makefile.libcore
config.status: creating src/vbuild/Makefile.libdiskimage
config.status: creating src/vbuild/Makefile.libdriveiecc64exp
config.status: creating src/vbuild/Makefile.libdriveiecieee
config.status: creating src/vbuild/Makefile.libdriveiec
config.status: creating src/vbuild/Makefile.libdriveieee
config.status: creating src/vbuild/Makefile.libdrive
config.status: creating src/vbuild/Makefile.libfileio
config.status: creating src/vbuild/Makefile.libfsdevice
config.status: creating src/vbuild/Makefile.libgfxoutputdrv
config.status: creating src/vbuild/Makefile.libiecbus
config.status: creating src/vbuild/Makefile.libimagecontents
config.status: creating src/vbuild/Makefile.libmonitor
config.status: creating src/vbuild/Makefile.libp64
config.status: creating src/vbuild/Makefile.libparallel
config.status: creating src/vbuild/Makefile.libplatform
config.status: creating src/vbuild/Makefile.libprinterdrv
config.status: creating src/vbuild/Makefile.libraster
config.status: creating src/vbuild/Makefile.libresidfp
config.status: creating src/vbuild/Makefile.libresid
config.status: creating src/vbuild/Makefile.librs232drv
config.status: creating src/vbuild/Makefile.librtc
config.status: creating src/vbuild/Makefile.libserial
config.status: creating src/vbuild/Makefile.libsid
config.status: creating src/vbuild/Makefile.libsounddrv
config.status: creating src/vbuild/Makefile.libtape
config.status: creating src/vbuild/Makefile.libuserport
config.status: creating src/vbuild/Makefile.libvdrive
config.status: creating src/vbuild/Makefile.libvicemain
config.status: creating src/vbuild/Makefile.libvicii
config.status: creating src/vbuild/Makefile.libvideo
config.status: creating src/vbuild/Makefile
config.status: creating src/c64emu/Makefile
config.status: creating src/vic20emu/Makefile
root@debian:~/redquark-sixtyfour# make
make[1]: Entering directory '/root/redquark-sixtyfour/src'
make[2]: Entering directory '/root/redquark-sixtyfour/src/viceport'
Building the64 vice bridge

Done
make[2]: Leaving directory '/root/redquark-sixtyfour/src/viceport'
make[2]: Entering directory '/root/redquark-sixtyfour/src/vbuild'
make -f Makefile.libc64
make[3]: Entering directory '/root/redquark-sixtyfour/src/vbuild'
Building Vice C64 library

Done
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vbuild'
make -f Makefile.libc64cart
make[3]: Entering directory '/root/redquark-sixtyfour/src/vbuild'
Building Vice C64 cartridge library

Done
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vbuild'
make -f Makefile.libc64cartsystem
make[3]: Entering directory '/root/redquark-sixtyfour/src/vbuild'
Building Vice C64 cartridge system library

Done
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vbuild'
make -f Makefile.libc64commoncart
make[3]: Entering directory '/root/redquark-sixtyfour/src/vbuild'
Building Vice common cart library

Done
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vbuild'
make -f Makefile.libcore
make[3]: Entering directory '/root/redquark-sixtyfour/src/vbuild'
Building Vice core library

Done
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vbuild'
make -f Makefile.libdiskimage
make[3]: Entering directory '/root/redquark-sixtyfour/src/vbuild'
Building Vice C64 disk image library

Done
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vbuild'
make -f Makefile.libdrive
make[3]: Entering directory '/root/redquark-sixtyfour/src/vbuild'
Building Vice drive IEEE library

Done
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vbuild'
make -f Makefile.libdriveiec
make[3]: Entering directory '/root/redquark-sixtyfour/src/vbuild'
Building Vice drive IEC library

Done
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vbuild'
make -f Makefile.libdriveiecc64exp
make[3]: Entering directory '/root/redquark-sixtyfour/src/vbuild'
Building Vice drive IEEE library

Done
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vbuild'
make -f Makefile.libdriveiecieee
make[3]: Entering directory '/root/redquark-sixtyfour/src/vbuild'
Building Vice drive IEC IEEE library

Done
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vbuild'
make -f Makefile.libdriveieee
make[3]: Entering directory '/root/redquark-sixtyfour/src/vbuild'
Building Vice drive IEEE library

Done
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vbuild'
make -f Makefile.libfileio
make[3]: Entering directory '/root/redquark-sixtyfour/src/vbuild'
Building Vice C64 file IO library

Done
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vbuild'
make -f Makefile.libfsdevice
make[3]: Entering directory '/root/redquark-sixtyfour/src/vbuild'
Building Vice FS device library

Done
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vbuild'
make -f Makefile.libgfxoutputdrv
make[3]: Entering directory '/root/redquark-sixtyfour/src/vbuild'
Building Vice graphics output driver library

Done
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vbuild'
make -f Makefile.libiecbus
make[3]: Entering directory '/root/redquark-sixtyfour/src/vbuild'
Building Vice IEC bus library

Done
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vbuild'
make -f Makefile.libimagecontents
make[3]: Entering directory '/root/redquark-sixtyfour/src/vbuild'
Building Vice C64 image contents library

Done
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vbuild'
make -f Makefile.libmonitor
make[3]: Entering directory '/root/redquark-sixtyfour/src/vbuild'
Building Vice C64 monitor library

Done
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vbuild'
make -f Makefile.libp64
make[3]: Entering directory '/root/redquark-sixtyfour/src/vbuild'
Building Vice P64 library

Done
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vbuild'
make -f Makefile.libparallel
make[3]: Entering directory '/root/redquark-sixtyfour/src/vbuild'
Building Vice parallel library

Done
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vbuild'
make -f Makefile.libplatform
make[3]: Entering directory '/root/redquark-sixtyfour/src/vbuild'
Building Vice platform library

Done
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vbuild'
make -f Makefile.libprinterdrv
make[3]: Entering directory '/root/redquark-sixtyfour/src/vbuild'
Building Vice C64 printer driver library

Done
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vbuild'
make -f Makefile.libraster
make[3]: Entering directory '/root/redquark-sixtyfour/src/vbuild'
Building Vice C64 raster library

Done
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vbuild'
make -f Makefile.libresid
make[3]: Entering directory '/root/redquark-sixtyfour/src/vbuild'
Building RESID library

Done
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vbuild'
make -f Makefile.libresidfp
make[3]: Entering directory '/root/redquark-sixtyfour/src/vbuild'
Building RESID-FP library

Done
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vbuild'
make -f Makefile.librs232drv
make[3]: Entering directory '/root/redquark-sixtyfour/src/vbuild'
Building Vice RS232 Driver library

Done
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vbuild'
make -f Makefile.librtc
make[3]: Entering directory '/root/redquark-sixtyfour/src/vbuild'
Building Vice C64 RTC library

Done
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vbuild'
make -f Makefile.libserial
make[3]: Entering directory '/root/redquark-sixtyfour/src/vbuild'
Building Vice C64 serial library

Done
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vbuild'
make -f Makefile.libsid
make[3]: Entering directory '/root/redquark-sixtyfour/src/vbuild'
Building Vice SID library

CC /root/redquark-sixtyfour/src/vice2/src/sid/resid.cc
cc1plus: error: unknown value ‘armv7-a’ for ‘-march’
cc1plus: note: valid arguments are: armv8-a armv8.1-a armv8.2-a armv8.3-a armv8.4-a armv8.5-a armv8.6-a native; did you mean ‘armv8-a’?
cc1plus: error: unknown value ‘cortex-a7’ for ‘-mtune’
cc1plus: note: valid arguments are: cortex-a34 cortex-a35 cortex-a53 cortex-a57 cortex-a72 cortex-a73 thunderx thunderxt88p1 thunderxt88 octeontx octeontx81 octeontx83 thunderxt81 thunderxt83 emag xgene1 falkor qdf24xx exynos-m1 phecda thunderx2t99p1 vulcan thunderx2t99 cortex-a55 cortex-a75 cortex-a76 cortex-a76ae cortex-a77 cortex-a65 cortex-a65ae ares neoverse-n1 neoverse-e1 octeontx2 octeontx2t98 octeontx2t96 octeontx2t93 octeontx2f95 octeontx2f95n octeontx2f95mm a64fx tsv110 thunderx3t110 zeus neoverse-v1 saphira neoverse-n2 cortex-a57.cortex-a53 cortex-a72.cortex-a53 cortex-a73.cortex-a35 cortex-a73.cortex-a53 cortex-a75.cortex-a55 cortex-a76.cortex-a55 generic; did you mean ‘cortex-a57’?
make[3]: *** [Makefile.libsid:95: obj/sid/resid.cc.o] Error 1
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vbuild'
make[2]: *** [Makefile:36: all] Error 2
make[2]: Leaving directory '/root/redquark-sixtyfour/src/vbuild'
make[1]: *** [Makefile:15: build] Error 2
make[1]: Leaving directory '/root/redquark-sixtyfour/src'
make: *** [Makefile:18: build] Error 2

root@debian:~/redquark-sixtyfour# cd src/vice2/
root@debian:~/redquark-sixtyfour/src/vice2# make
Making all in po
Making all in src
make[1]: Entering directory '/root/redquark-sixtyfour/src/vice2/src'
make all-recursive
make[2]: Entering directory '/root/redquark-sixtyfour/src/vice2/src'
Making all in resid
make[3]: Entering directory '/root/redquark-sixtyfour/src/vice2/src/resid'
make all-am
make[4]: Entering directory '/root/redquark-sixtyfour/src/vice2/src/resid'
make[4]: Nothing to be done for 'all-am'.
make[4]: Leaving directory '/root/redquark-sixtyfour/src/vice2/src/resid'
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vice2/src/resid'
Making all in resid-fp
make[3]: Entering directory '/root/redquark-sixtyfour/src/vice2/src/resid-fp'
aarch64-linux-gnu-g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"resid\" -DVERSION=\"0.16vice\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DSIZEOF_INT=4 -DHAVE_LOGF=1 -DHAVE_EXPF=1 -I. -g -Wall -O3 -ffast-math -fno-exceptions -fno-pic -MT sid.o -MD -MP -MF .deps/sid.Tpo -c -o sid.o sid.cc
mv -f .deps/sid.Tpo .deps/sid.Po
aarch64-linux-gnu-g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"resid\" -DVERSION=\"0.16vice\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DSIZEOF_INT=4 -DHAVE_LOGF=1 -DHAVE_EXPF=1 -I. -g -Wall -O3 -ffast-math -fno-exceptions -fno-pic -MT voice.o -MD -MP -MF .deps/voice.Tpo -c -o voice.o voice.cc
mv -f .deps/voice.Tpo .deps/voice.Po
aarch64-linux-gnu-g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"resid\" -DVERSION=\"0.16vice\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DSIZEOF_INT=4 -DHAVE_LOGF=1 -DHAVE_EXPF=1 -I. -g -Wall -O3 -ffast-math -fno-exceptions -fno-pic -MT wave.o -MD -MP -MF .deps/wave.Tpo -c -o wave.o wave.cc
mv -f .deps/wave.Tpo .deps/wave.Po
aarch64-linux-gnu-g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"resid\" -DVERSION=\"0.16vice\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DSIZEOF_INT=4 -DHAVE_LOGF=1 -DHAVE_EXPF=1 -I. -g -Wall -O3 -ffast-math -fno-exceptions -fno-pic -MT envelope.o -MD -MP -MF .deps/envelope.Tpo -c -o envelope.o envelope.cc
mv -f .deps/envelope.Tpo .deps/envelope.Po
aarch64-linux-gnu-g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"resid\" -DVERSION=\"0.16vice\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DSIZEOF_INT=4 -DHAVE_LOGF=1 -DHAVE_EXPF=1 -I. -g -Wall -O3 -ffast-math -fno-exceptions -fno-pic -MT filter.o -MD -MP -MF .deps/filter.Tpo -c -o filter.o filter.cc
mv -f .deps/filter.Tpo .deps/filter.Po
aarch64-linux-gnu-g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"resid\" -DVERSION=\"0.16vice\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DSIZEOF_INT=4 -DHAVE_LOGF=1 -DHAVE_EXPF=1 -I. -g -Wall -O3 -ffast-math -fno-exceptions -fno-pic -MT extfilt.o -MD -MP -MF .deps/extfilt.Tpo -c -o extfilt.o extfilt.cc
mv -f .deps/extfilt.Tpo .deps/extfilt.Po
aarch64-linux-gnu-g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"resid\" -DVERSION=\"0.16vice\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DSIZEOF_INT=4 -DHAVE_LOGF=1 -DHAVE_EXPF=1 -I. -g -Wall -O3 -ffast-math -fno-exceptions -fno-pic -MT pot.o -MD -MP -MF .deps/pot.Tpo -c -o pot.o pot.cc
mv -f .deps/pot.Tpo .deps/pot.Po
aarch64-linux-gnu-g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"resid\" -DVERSION=\"0.16vice\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DSIZEOF_INT=4 -DHAVE_LOGF=1 -DHAVE_EXPF=1 -I. -g -Wall -O3 -ffast-math -fno-exceptions -fno-pic -MT version.o -MD -MP -MF .deps/version.Tpo -c -o version.o version.cc
mv -f .deps/version.Tpo .deps/version.Po
rm -f libresidfp.a
ar cru libresidfp.a sid.o voice.o wave.o envelope.o filter.o extfilt.o pot.o version.o convolve.o
ar: `u' modifier ignored since `D' is the default (see `U')
aarch64-linux-gnu-ranlib libresidfp.a
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vice2/src/resid-fp'
Making all in resid-dtv
make[3]: Entering directory '/root/redquark-sixtyfour/src/vice2/src/resid-dtv'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vice2/src/resid-dtv'
Making all in sounddrv
make[3]: Entering directory '/root/redquark-sixtyfour/src/vice2/src/sounddrv'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vice2/src/sounddrv'
Making all in drive
make[3]: Entering directory '/root/redquark-sixtyfour/src/vice2/src/drive'
Making all in iec
make[4]: Entering directory '/root/redquark-sixtyfour/src/vice2/src/drive/iec'
Making all in c64exp
make[5]: Entering directory '/root/redquark-sixtyfour/src/vice2/src/drive/iec/c64exp'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/root/redquark-sixtyfour/src/vice2/src/drive/iec/c64exp'
Making all in plus4exp
make[5]: Entering directory '/root/redquark-sixtyfour/src/vice2/src/drive/iec/plus4exp'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/root/redquark-sixtyfour/src/vice2/src/drive/iec/plus4exp'
make[5]: Entering directory '/root/redquark-sixtyfour/src/vice2/src/drive/iec'
make[5]: Nothing to be done for 'all-am'.
make[5]: Leaving directory '/root/redquark-sixtyfour/src/vice2/src/drive/iec'
make[4]: Leaving directory '/root/redquark-sixtyfour/src/vice2/src/drive/iec'
Making all in iec128dcr
make[4]: Entering directory '/root/redquark-sixtyfour/src/vice2/src/drive/iec128dcr'
make[4]: Nothing to be done for 'all'.
make[4]: Leaving directory '/root/redquark-sixtyfour/src/vice2/src/drive/iec128dcr'
Making all in iecieee
make[4]: Entering directory '/root/redquark-sixtyfour/src/vice2/src/drive/iecieee'
make[4]: Nothing to be done for 'all'.
make[4]: Leaving directory '/root/redquark-sixtyfour/src/vice2/src/drive/iecieee'
Making all in ieee
make[4]: Entering directory '/root/redquark-sixtyfour/src/vice2/src/drive/ieee'
make[4]: Nothing to be done for 'all'.
make[4]: Leaving directory '/root/redquark-sixtyfour/src/vice2/src/drive/ieee'
Making all in tcbm
make[4]: Entering directory '/root/redquark-sixtyfour/src/vice2/src/drive/tcbm'
make[4]: Nothing to be done for 'all'.
make[4]: Leaving directory '/root/redquark-sixtyfour/src/vice2/src/drive/tcbm'
make[4]: Entering directory '/root/redquark-sixtyfour/src/vice2/src/drive'
make[4]: Nothing to be done for 'all-am'.
make[4]: Leaving directory '/root/redquark-sixtyfour/src/vice2/src/drive'
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vice2/src/drive'
Making all in vdrive
make[3]: Entering directory '/root/redquark-sixtyfour/src/vice2/src/vdrive'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vice2/src/vdrive'
Making all in fsdevice
make[3]: Entering directory '/root/redquark-sixtyfour/src/vice2/src/fsdevice'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vice2/src/fsdevice'
Making all in diskimage
make[3]: Entering directory '/root/redquark-sixtyfour/src/vice2/src/diskimage'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vice2/src/diskimage'
Making all in iecbus
make[3]: Entering directory '/root/redquark-sixtyfour/src/vice2/src/iecbus'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vice2/src/iecbus'
Making all in serial
make[3]: Entering directory '/root/redquark-sixtyfour/src/vice2/src/serial'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vice2/src/serial'
Making all in parallel
make[3]: Entering directory '/root/redquark-sixtyfour/src/vice2/src/parallel'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vice2/src/parallel'
Making all in tape
make[3]: Entering directory '/root/redquark-sixtyfour/src/vice2/src/tape'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vice2/src/tape'
Making all in imagecontents
make[3]: Entering directory '/root/redquark-sixtyfour/src/vice2/src/imagecontents'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vice2/src/imagecontents'
Making all in fileio
make[3]: Entering directory '/root/redquark-sixtyfour/src/vice2/src/fileio'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vice2/src/fileio'
Making all in video
make[3]: Entering directory '/root/redquark-sixtyfour/src/vice2/src/video'
aarch64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../../src -I../../src/arch/unix -I../../src -I../../src -I../../src/raster -lreadline -MT video-canvas.o -MD -MP -MF .deps/video-canvas.Tpo -c -o video-canvas.o video-canvas.c
In file included from video-canvas.c:48:
../../src/arch/unix/videoarch.h:3:2: error: #error "Unix videoarch.h"
3 | #error "Unix videoarch.h"
| ^~~~~
../../src/arch/unix/videoarch.h:5:10: fatal error: /home/chris/src/the64-hardware/firmware/src/videoarch.h: No such file or directory
5 | #include "/home/chris/src/the64-hardware/firmware/src/videoarch.h" // CDS
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[3]: *** [Makefile:569: video-canvas.o] Error 1
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vice2/src/video'
make[2]: *** [Makefile:1828: all-recursive] Error 1
make[2]: Leaving directory '/root/redquark-sixtyfour/src/vice2/src'
make[1]: *** [Makefile:1582: all] Error 2
make[1]: Leaving directory '/root/redquark-sixtyfour/src/vice2/src'
make: *** [Makefile:560: all-recursive] Error 1

Last Edit: Jun 6, 2023 13:44:45 GMT by lasttape

2283

jj0
THEC64 Developer

Manic Miner rules!

Posts: 1,020
Member is Online

Run full-blown vice on the Mini/Maxi/VIC-20 Jun 6, 2023 14:28:57 GMT

Quote

Post by jj0 on Jun 6, 2023 14:28:57 GMT

Jun 6, 2023 10:27:07 GMT lasttape said:

Jun 5, 2023 11:40:40 GMT jj0 said:

The instructions for compiling in this thread are for compiling vice 2.4 from the official source. If you have '/home/chris' somewhere the I assume you are trying to compile vice 2.4 from the sources from RGL? At the minimum you probably need to do a 'make clean' and a new './configure .....'. But as far as I know RGL doesn't use the actual vice (x64) binary but creates some kind of library out of it that they use with the Carousel. Check out this thread where there's more info about building those.

the base system that I want to use for compiling: git clone github.com/armbian/build.git armbian

it's configurable build from source

Is that an armhf system compatible with THE64 libraries etc? The thread I referred to specifically uses the ancient XWM rootfs as that is mostly library-compatible with THE64 and also has been used for a successful build by gurce so demonstratably works

ll try the following

<snip>
./configure --host=aarch64-linux-gnu CC=arm-linux-gnueabi-gcc-10 CFLAGS="-lreadline"
make

<snip>

CC /root/redquark-sixtyfour/src/vice2/src/sid/resid.cc
cc1plus: error: unknown value ‘armv7-a’ for ‘-march’
cc1plus: note: valid arguments are: armv8-a armv8.1-a armv8.2-a armv8.3-a armv8.4-a armv8.5-a armv8.6-a native; did you mean ‘armv8-a’?
cc1plus: error: unknown value ‘cortex-a7’ for ‘-mtune’
cc1plus: note: valid arguments are: cortex-a34 cortex-a35 cortex-a53 cortex-a57 cortex-a72 cortex-a73 thunderx thunderxt88p1 thunderxt88 octeontx octeontx81 octeontx83 thunderxt81 thunderxt83 emag xgene1 falkor qdf24xx exynos-m1 phecda thunderx2t99p1 vulcan thunderx2t99 cortex-a55 cortex-a75 cortex-a76 cortex-a76ae cortex-a77 cortex-a65 cortex-a65ae ares neoverse-n1 neoverse-e1 octeontx2 octeontx2t98 octeontx2t96 octeontx2t93 octeontx2f95 octeontx2f95n octeontx2f95mm a64fx tsv110 thunderx3t110 zeus neoverse-v1 saphira neoverse-n2 cortex-a57.cortex-a53 cortex-a72.cortex-a53 cortex-a73.cortex-a35 cortex-a73.cortex-a53 cortex-a75.cortex-a55 cortex-a76.cortex-a55 generic; did you mean ‘cortex-a57’?
make[3]: *** [Makefile.libsid:95: obj/sid/resid.cc.o] Error 1
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vbuild'
make[2]: *** [Makefile:36: all] Error 2
make[2]: Leaving directory '/root/redquark-sixtyfour/src/vbuild'
make[1]: *** [Makefile:15: build] Error 2
make[1]: Leaving directory '/root/redquark-sixtyfour/src'
make: *** [Makefile:18: build] Error 2

I think this error is due to using aarch64-linux-gnu instead of arm-linux-gnueabihf

<snip>

In file included from video-canvas.c:48:
../../src/arch/unix/videoarch.h:3:2: error: #error "Unix videoarch.h"
3 | #error "Unix videoarch.h"
| ^~~~~
../../src/arch/unix/videoarch.h:5:10: fatal error: /home/chris/src/the64-hardware/firmware/src/videoarch.h: No such file or directory
5 | #include "/home/chris/src/the64-hardware/firmware/src/videoarch.h" // CDS
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[3]: *** [Makefile:569: video-canvas.o] Error 1
make[3]: Leaving directory '/root/redquark-sixtyfour/src/vice2/src/video'
make[2]: *** [Makefile:1828: all-recursive] Error 1
make[2]: Leaving directory '/root/redquark-sixtyfour/src/vice2/src'
make[1]: *** [Makefile:1582: all] Error 2
make[1]: Leaving directory '/root/redquark-sixtyfour/src/vice2/src'
make: *** [Makefile:560: all-recursive] Error 1

I hoped that this would have been cleared up by a make clean - did you do a make clean?

lasttape
Creatures

Posts: 25

Run full-blown vice on the Mini/Maxi/VIC-20 Jun 6, 2023 16:05:46 GMT

Quote

Post by lasttape on Jun 6, 2023 16:05:46 GMT

hmm : I think this error is due to using aarch64-linux-gnu instead of arm-linux-gnueabihf
this is the host machine ... ill cross compile the binary

yes make clean && make

cc1plus: error: unknown value ‘armv7-a’ for ‘-march’
cc1plus: note: valid arguments are: armv8-a armv8.1-a armv8.2-a armv8.3-a armv8.4-a armv8.5-a armv8.6-a native; did you mean ‘armv8-a’?
cc1plus: error: unknown value ‘cortex-a7’ for ‘-mtune’
cc1plus: note: valid arguments are: cortex-a34 cortex-a35 cortex-a53 cortex-a57 cortex-a72 cortex-a73 thunderx thunderxt88p1 thunderxt88 octeontx octeontx81 octeontx83 thunderxt81 thunderxt83 emag xgene1 falkor qdf24xx exynos-m1 phecda thunderx2t99p1 vulcan thunderx2t99 cortex-a55 cortex-a75 cortex-a76 cortex-a76ae cortex-a77 cortex-a65 cortex-a65ae ares neoverse-n1 neoverse-e1 octeontx2 octeontx2t98 octeontx2t96 octeontx2t93 octeontx2f95 octeontx2f95n octeontx2f95mm a64fx tsv110 thunderx3t110 zeus neoverse-v1 saphira neoverse-n2 cortex-a57.cortex-a53 cortex-a72.cortex-a53 cortex-a73.cortex-a35 cortex-a73.cortex-a53 cortex-a75.cortex-a55 cortex-a76.cortex-a55 generic; did you mean ‘cortex-a57’?

this error comes form native Makefile instruction ... native is arm64 ... hosted on macOS with UTM Virtual Machine "Debian arm64"

vice2/src:

.deps/                   render2x2.c              renderscale2x.o
Makefile                 render2x2crt.c           renderyuv.c
Makefile.am              render2x2crt.h           renderyuv.h
Makefile.in              render2x2crt.o           renderyuv.o
render1x1.c              render2x2.h              video-canvas.c
render1x1_dingoo.h       render2x2ntsc.c          video-canvas.h
render1x1.h              render2x2ntsc.h          video-cmdline-options.c
render1x1ntsc.c          render2x2ntsc.o          video-color.c
render1x1ntsc.h          render2x2.o              video-color.h
render1x1ntsc.o          render2x2pal.c           video-render-1x2.c
render1x1.o              render2x2pal.h           video-render-2x2.c
render1x1pal.c           render2x2pal.o           video-render.c
render1x1pal.h           render2x4.c              video-render-crt.c
render1x1pal.o           render2x4crt.c           video-render.h
render1x2.c              render2x4crt.h           video-render-pal.c
render1x2crt.c           render2x4crt.o           video-resources.c
render1x2crt.h           render2x4.h              video-resources.h
render1x2crt.o           render2x4.o              video-sound.c
render1x2.h              renderscale2x.c          video-sound.h
render1x2.o              renderscale2x.h          video-viewport.c

root@debian:~/redquark-sixtyfour/src/vice2/src/video# cat ../../src/arch/unix/videoarch.h
#include "vice.h"

#error "Unix videoarch.h"

#include "/home/chris/src/the64-hardware/firmware/src/videoarch.h" // CDS

#if 0 // CDS

#if defined(GP2X) || defined(WIZ)
#include "gp2x/videoarch.h"
#else
#ifdef USE_GNOMEUI
#include "x11/gnome/videoarch.h"
#else
#ifdef VMS
#include "x11xawvideoarch.h"
#else
#ifdef MACOSX_COCOA
#include "macosx/cocoa/videoarch.h"
#else
#include "x11/xaw/videoarch.h"
#endif
#endif
#endif
#endif

#endif

here is the error

2283

lasttape
Creatures

Posts: 25

Run full-blown vice on the Mini/Maxi/VIC-20 Jun 6, 2023 17:03:31 GMT

Quote

Post by lasttape on Jun 6, 2023 17:03:31 GMT

i removed the include file switch

root@debian:~/redquark-sixtyfour/src/vice2/src/arch/unix# cat videoarch.h 
#include "vice.h"

#if defined(GP2X) || defined(WIZ)
#include "gp2x/videoarch.h"
#else
#ifdef USE_GNOMEUI
#include "x11/gnome/videoarch.h"
#else
#ifdef VMS
#include "x11xawvideoarch.h"
#else
#ifdef MACOSX_COCOA
#include "macosx/cocoa/videoarch.h"
#else
#include "x11/xaw/videoarch.h"
#endif
#endif
#endif
#endif

run:

cd red... 
./configure --host=aarch64-linux-gnu CC=arm-linux-gnueabi-gcc-10 CXX=arm-linux-gnueabi-g++-10 AR=arm-linux-gnueabi-ar CFLAGS="-lreadline"
make

Building Vice C64 Emulater Module

CC	c64emu.c
In file included from /root/redquark-sixtyfour/src/vice2/src/vice.h:44,
                 from /root/redquark-sixtyfour/src/viceport/types.h:21,
                 from /root/redquark-sixtyfour/src/vice2/src/machine.h:31,
                 from c64emu.c:24:
/root/redquark-sixtyfour/src/vice2/src/config.h:702: warning: "PACKAGE_BUGREPORT" redefined
  702 | #define PACKAGE_BUGREPORT ""
      | 
<command-line>: note: this is the location of the previous definition
In file included from /root/redquark-sixtyfour/src/vice2/src/vice.h:44,
                 from /root/redquark-sixtyfour/src/viceport/types.h:21,
                 from /root/redquark-sixtyfour/src/vice2/src/machine.h:31,
                 from c64emu.c:24:
/root/redquark-sixtyfour/src/vice2/src/config.h:705: warning: "PACKAGE_NAME" redefined
  705 | #define PACKAGE_NAME ""
      | 
<command-line>: note: this is the location of the previous definition
In file included from /root/redquark-sixtyfour/src/vice2/src/vice.h:44,
                 from /root/redquark-sixtyfour/src/viceport/types.h:21,
                 from /root/redquark-sixtyfour/src/vice2/src/machine.h:31,
                 from c64emu.c:24:
/root/redquark-sixtyfour/src/vice2/src/config.h:708: warning: "PACKAGE_STRING" redefined
  708 | #define PACKAGE_STRING ""
      | 
<command-line>: note: this is the location of the previous definition
In file included from /root/redquark-sixtyfour/src/vice2/src/vice.h:44,
                 from /root/redquark-sixtyfour/src/viceport/types.h:21,
                 from /root/redquark-sixtyfour/src/vice2/src/machine.h:31,
                 from c64emu.c:24:
/root/redquark-sixtyfour/src/vice2/src/config.h:711: warning: "PACKAGE_TARNAME" redefined
  711 | #define PACKAGE_TARNAME ""
      | 
<command-line>: note: this is the location of the previous definition
In file included from /root/redquark-sixtyfour/src/vice2/src/vice.h:44,
                 from /root/redquark-sixtyfour/src/viceport/types.h:21,
                 from /root/redquark-sixtyfour/src/vice2/src/machine.h:31,
                 from c64emu.c:24:
/root/redquark-sixtyfour/src/vice2/src/config.h:717: warning: "PACKAGE_VERSION" redefined
  717 | #define PACKAGE_VERSION ""
      | 
<command-line>: note: this is the location of the previous definition
c64emu.c:54:8: warning: #warning NTSC Output [-Wcpp]
   54 | #      warning NTSC Output
      |        ^~~~~~~
c64emu.c: In function ‘emu_attach_default_storage’:
c64emu.c:565:13: warning: implicit declaration of function ‘sync’ [-Wimplicit-function-declaration]
  565 |             sync();
      |             ^~~~
Creating shared library c64emu.rgl
LD	c64emu.rgl
/usr/lib/gcc-cross/arm-linux-gnueabi/10/../../../../arm-linux-gnueabi/bin/ld: cannot find -lasound
/usr/lib/gcc-cross/arm-linux-gnueabi/10/../../../../arm-linux-gnueabi/bin/ld: cannot find -lz
/usr/lib/gcc-cross/arm-linux-gnueabi/10/../../../../arm-linux-gnueabi/bin/ld: cannot find -lpng16
/usr/lib/gcc-cross/arm-linux-gnueabi/10/../../../../arm-linux-gnueabi/bin/ld: cannot find -lz
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:499: c64emu.rgl] Error 1
make[2]: Leaving directory '/root/redquark-sixtyfour/src/c64emu'
make[1]: *** [Makefile:16: build] Error 2
make[1]: Leaving directory '/root/redquark-sixtyfour/src'
make: *** [Makefile:18: build] Error 2

for the moment run fine ... except the linker error

Last Edit: Jun 6, 2023 17:09:00 GMT by lasttape

2283

lasttape
Creatures

Posts: 25

Run full-blown vice on the Mini/Maxi/VIC-20 Jun 6, 2023 18:16:35 GMT

Quote

Post by lasttape on Jun 6, 2023 18:16:35 GMT

./configure --host=aarch64-linux-gnu CC=arm-linux-gnueabi-gcc-10 CXX=arm-linux-gnueabi-g++-10 AR=arm-linux-gnueabi-ar STRIP=arm-linux-gnueabi-strip CFLAGS="-lreadline -lz -lasound -lpng16" LFLAGS="-L /usr/lib" IFLAGS="-I /usr/include" LD=arm-linux-gnueabi-ld

and I run make clean && command above && make

2283

jj0
THEC64 Developer

Manic Miner rules!

Posts: 1,020
Member is Online

Run full-blown vice on the Mini/Maxi/VIC-20 Jun 7, 2023 12:26:33 GMT

Quote

Post by jj0 on Jun 7, 2023 12:26:33 GMT

Jun 6, 2023 18:16:35 GMT lasttape said:

./configure --host=aarch64-linux-gnu CC=arm-linux-gnueabi-gcc-10 CXX=arm-linux-gnueabi-g++-10 AR=arm-linux-gnueabi-ar STRIP=arm-linux-gnueabi-strip CFLAGS="-lreadline -lz -lasound -lpng16" LFLAGS="-L /usr/lib" IFLAGS="-I /usr/include" LD=arm-linux-gnueabi-ld

and I run make clean && command above && make

Ok, so you only have the linker error left?

Those could maybe be due to missing libasound-dev / libasound2-dev and libz-dev and libpng-dev?

lasttape
Creatures

Posts: 25

Run full-blown vice on the Mini/Maxi/VIC-20 Jun 7, 2023 13:47:39 GMT

Quote

Post by lasttape on Jun 7, 2023 13:47:39 GMT

Jun 7, 2023 12:26:33 GMT jj0 said:

Jun 6, 2023 18:16:35 GMT lasttape said:

./configure --host=aarch64-linux-gnu CC=arm-linux-gnueabi-gcc-10 CXX=arm-linux-gnueabi-g++-10 AR=arm-linux-gnueabi-ar STRIP=arm-linux-gnueabi-strip CFLAGS="-lreadline -lz -lasound -lpng16" LFLAGS="-L /usr/lib" IFLAGS="-I /usr/include" LD=arm-linux-gnueabi-ld

and I run make clean && command above && make

Ok, so you only have the linker error left?

Those could maybe be due to missing libasound-dev / libasound2-dev and libz-dev and libpng-dev?

ill tested out with lib*-dev:armhf and lib*-dev
both give the same error

and yes only the linker error

found now the libs but do not helps ... same error

./configure --host=aarch64-linux-gnu CC=arm-linux-gnueabi-gcc-10 CXX=arm-linux-gnueabi-g++-10 AR=arm-linux-gnueabi-ar STRIP=arm-linux-gnueabi-strip CFLAGS="-lreadline -lz -lasound -lpng16 -L /usr/lib/arm-linux-gnueabihf/ -I /usr/include" LD=arm-linux-gnueabi-ld

Last Edit: Jun 7, 2023 16:05:56 GMT by lasttape

2283

jj0
THEC64 Developer

Manic Miner rules!

Posts: 1,020
Member is Online

Run full-blown vice on the Mini/Maxi/VIC-20 Jun 8, 2023 13:22:26 GMT

Quote

Post by jj0 on Jun 8, 2023 13:22:26 GMT

Jun 7, 2023 13:47:39 GMT lasttape said:

Jun 7, 2023 12:26:33 GMT jj0 said:

Ok, so you only have the linker error left?

Those could maybe be due to missing libasound-dev / libasound2-dev and libz-dev and libpng-dev?

ill tested out with lib*-dev:armhf and lib*-dev
both give the same error

and yes only the linker error

found now the libs but do not helps ... same error

./configure --host=aarch64-linux-gnu CC=arm-linux-gnueabi-gcc-10 CXX=arm-linux-gnueabi-g++-10 AR=arm-linux-gnueabi-ar STRIP=arm-linux-gnueabi-strip CFLAGS="-lreadline -lz -lasound -lpng16 -L /usr/lib/arm-linux-gnueabihf/ -I /usr/include" LD=arm-linux-gnueabi-ld

You could add: '--without-alsa --without-png --without-zlib' when you run ./configure, I don't think those features are required.

lasttape
Creatures

Posts: 25

Run full-blown vice on the Mini/Maxi/VIC-20 Jun 8, 2023 14:18:27 GMT

Quote

Post by lasttape on Jun 8, 2023 14:18:27 GMT

Jun 8, 2023 13:22:26 GMT jj0 said:

Jun 7, 2023 13:47:39 GMT lasttape said:

ill tested out with lib*-dev:armhf and lib*-dev
both give the same error

and yes only the linker error

found now the libs but do not helps ... same error

./configure --host=aarch64-linux-gnu CC=arm-linux-gnueabi-gcc-10 CXX=arm-linux-gnueabi-g++-10 AR=arm-linux-gnueabi-ar STRIP=arm-linux-gnueabi-strip CFLAGS="-lreadline -lz -lasound -lpng16 -L /usr/lib/arm-linux-gnueabihf/ -I /usr/include" LD=arm-linux-gnueabi-ld

You could add: '--without-alsa --without-png --without-zlib' when you run ./configure, I don't think those features are required.

configure: WARNING: unrecognized options: --without-alsa, --without-png, --without-zlib

2283

lasttape
Creatures

Posts: 25

Run full-blown vice on the Mini/Maxi/VIC-20 Jun 9, 2023 10:53:18 GMT

Quote

Post by lasttape on Jun 9, 2023 10:53:18 GMT

my fail ... I had used the wrong compiler

now:

./configure --host=aarch64-linux-gnu CC=arm-linux-gnueabihf-gcc-10 CXX=arm-linux-gnueabihf-g++-10 AR=arm-linux-gnueabihf-ar STRIP=arm-linux-gnueabihf-strip CFLAGS="-lreadline -lz -lasound -lpng16 -L /usr/lib/arm-linux-gnueabihf/ -I /usr/include" LD=arm-linux-gnueabihf-ld --target=armhf-linux-gnu

Building Vice C64 Emulater Module

CC	c64emu.c
In file included from /root/redquark-sixtyfour/src/vice2/src/vice.h:44,
                 from /root/redquark-sixtyfour/src/viceport/types.h:21,
                 from /root/redquark-sixtyfour/src/vice2/src/machine.h:31,
                 from c64emu.c:24:
/root/redquark-sixtyfour/src/vice2/src/config.h:702: warning: "PACKAGE_BUGREPORT" redefined
  702 | #define PACKAGE_BUGREPORT ""
      | 
<command-line>: note: this is the location of the previous definition
In file included from /root/redquark-sixtyfour/src/vice2/src/vice.h:44,
                 from /root/redquark-sixtyfour/src/viceport/types.h:21,
                 from /root/redquark-sixtyfour/src/vice2/src/machine.h:31,
                 from c64emu.c:24:
/root/redquark-sixtyfour/src/vice2/src/config.h:705: warning: "PACKAGE_NAME" redefined
  705 | #define PACKAGE_NAME ""
      | 
<command-line>: note: this is the location of the previous definition
In file included from /root/redquark-sixtyfour/src/vice2/src/vice.h:44,
                 from /root/redquark-sixtyfour/src/viceport/types.h:21,
                 from /root/redquark-sixtyfour/src/vice2/src/machine.h:31,
                 from c64emu.c:24:
/root/redquark-sixtyfour/src/vice2/src/config.h:708: warning: "PACKAGE_STRING" redefined
  708 | #define PACKAGE_STRING ""
      | 
<command-line>: note: this is the location of the previous definition
In file included from /root/redquark-sixtyfour/src/vice2/src/vice.h:44,
                 from /root/redquark-sixtyfour/src/viceport/types.h:21,
                 from /root/redquark-sixtyfour/src/vice2/src/machine.h:31,
                 from c64emu.c:24:
/root/redquark-sixtyfour/src/vice2/src/config.h:711: warning: "PACKAGE_TARNAME" redefined
  711 | #define PACKAGE_TARNAME ""
      | 
<command-line>: note: this is the location of the previous definition
In file included from /root/redquark-sixtyfour/src/vice2/src/vice.h:44,
                 from /root/redquark-sixtyfour/src/viceport/types.h:21,
                 from /root/redquark-sixtyfour/src/vice2/src/machine.h:31,
                 from c64emu.c:24:
/root/redquark-sixtyfour/src/vice2/src/config.h:717: warning: "PACKAGE_VERSION" redefined
  717 | #define PACKAGE_VERSION ""
      | 
<command-line>: note: this is the location of the previous definition
c64emu.c:54:8: warning: #warning NTSC Output [-Wcpp]
   54 | #      warning NTSC Output
      |        ^~~~~~~
c64emu.c: In function ‘emu_attach_default_storage’:
c64emu.c:565:13: warning: implicit declaration of function ‘sync’ [-Wimplicit-function-declaration]
  565 |             sync();
      |             ^~~~
Creating shared library c64emu.rgl
LD	c64emu.rgl
/usr/lib/gcc-cross/arm-linux-gnueabihf/10/../../../../arm-linux-gnueabihf/bin/ld: error: c64emu.rgl uses VFP register arguments, ./shared/dynlib.o does not
/usr/lib/gcc-cross/arm-linux-gnueabihf/10/../../../../arm-linux-gnueabihf/bin/ld: failed to merge target specific data of file ./shared/dynlib.o
/usr/lib/gcc-cross/arm-linux-gnueabihf/10/../../../../arm-linux-gnueabihf/bin/ld: error: c64emu.rgl uses VFP register arguments, ./shared/blockdev.o does not
/usr/lib/gcc-cross/arm-linux-gnueabihf/10/../../../../arm-linux-gnueabihf/bin/ld: failed to merge target specific data of file ./shared/blockdev.o
/usr/lib/gcc-cross/arm-linux-gnueabihf/10/../../../../arm-linux-gnueabihf/bin/ld: error: c64emu.rgl uses VFP register arguments, ./shared/signals.o does not
/usr/lib/gcc-cross/arm-linux-gnueabihf/10/../../../../arm-linux-gnueabihf/bin/ld: failed to merge target specific data of file ./shared/signals.o
/usr/lib/gcc-cross/arm-linux-gnueabihf/10/../../../../arm-linux-gnueabihf/bin/ld: error: c64emu.rgl uses VFP register arguments, ./shared/archdep.o does not
/usr/lib/gcc-cross/arm-linux-gnueabihf/10/../../../../arm-linux-gnueabihf/bin/ld: failed to merge target specific data of file ./shared/archdep.o
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:499: c64emu.rgl] Error 1
make[2]: Leaving directory '/root/redquark-sixtyfour/src/c64emu'
make[1]: *** [Makefile:16: build] Error 2
make[1]: Leaving directory '/root/redquark-sixtyfour/src'
make: *** [Makefile:18: build] Error 2

2283

jj0 THEC64 Developer Manic Miner rules! Posts: 1,020 Member is Online	Run full-blown vice on the Mini/Maxi/VIC-20 Jun 12, 2023 15:11:45 GMT Quote Select Post Deselect Post Link to Post Member Give Gift Back to Top Post by jj0 on Jun 12, 2023 15:11:45 GMT Sorry, I don't know. Google thinks it's a mixup between softfloat and hardfloat - are the ./shared/*.o recompiled after the change to 'CC=arm-linux-gnueabihf-gcc-10'?

lasttape Creatures Posts: 25	Run full-blown vice on the Mini/Maxi/VIC-20 Jun 12, 2023 18:57:34 GMT Quote Select Post Deselect Post Link to Post Member Give Gift Back to Top Post by lasttape on Jun 12, 2023 18:57:34 GMT yes ... deleted and recompiled
	2283

b0wman
BASIC

Posts: 3

Run full-blown vice on the Mini/Maxi/VIC-20 Jul 9, 2023 20:39:29 GMT

Quote

Post by b0wman on Jul 9, 2023 20:39:29 GMT

Hi. I tried to flash it but without luck. I have already flashed the official firmwares, as well as custom firmwares (fake firmware with alternative carousel games). That had worked so far. This fake firmware is displayed in the settings, but if you try to flash, the usual animation (flash process) does not occur, but the device resets immediately and goes back to the Carousel. There is also no VICE etc. I have tried various USB pendrives (which I know work with TheC64). What could be the reason for this? Maybe I have the wrong "Bios" data (Basic, Kernal, Chargen etc.) or is something else? I would appreciate your help.

Last Edit: Jul 9, 2023 20:47:36 GMT by b0wman

jj0
THEC64 Developer

Manic Miner rules!

Posts: 1,020
Member is Online

Run full-blown vice on the Mini/Maxi/VIC-20 Jul 10, 2023 12:55:05 GMT

Quote

Post by jj0 on Jul 10, 2023 12:55:05 GMT

Jul 9, 2023 20:39:29 GMT b0wman said:

Hi. I tried to flash it but without luck. I have already flashed the official firmwares, as well as custom firmwares (fake firmware with alternative carousel games). That had worked so far. This fake firmware is displayed in the settings, but if you try to flash, the usual animation (flash process) does not occur, but the device resets immediately and goes back to the Carousel. There is also no VICE etc. I have tried various USB pendrives (which I know work with TheC64). What could be the reason for this? Maybe I have the wrong "Bios" data (Basic, Kernal, Chargen etc.) or is something else? I would appreciate your help.

It's hard to say, can you replace the /vice/run_vice.sh file with the one attached? That one should log error messages from running vice to a vice-message.txt on the USB-drive so you can see if there are any error messages.

Attachments:

run_vice.sh (3.23 KB)

b0wman
BASIC

Posts: 3

Run full-blown vice on the Mini/Maxi/VIC-20 Jul 10, 2023 13:18:24 GMT

Quote

Post by b0wman on Jul 10, 2023 13:18:24 GMT

Thank you. I tried that and found this in the "vice-message.txt":

C64MEM: Error - Couldn't load kernal ROM `kernal'.
Error - Machine initialization failed.

I put these files in Vice/Vice/C64:

basic-901226-01.bin
chargen-901225-01.bin
chargen-906143-02.bin
kernal-251104-04.bin
kernal-390852-01.bin
kernal-901227-01.bin
kernal-901227-02.bin
kernal-901227-03.bin
kernal-901246-01.bin
kernal-906145-02.bin

got these from the Vice3.7 Win32 release.

jj0
THEC64 Developer

Manic Miner rules!

Posts: 1,020
Member is Online

Run full-blown vice on the Mini/Maxi/VIC-20 Jul 10, 2023 15:11:40 GMT via mobile

Quote

Post by jj0 on Jul 10, 2023 15:11:40 GMT

Jul 10, 2023 13:18:24 GMT b0wman said:

Thank you. I tried that and found this in the "vice-message.txt":

C64MEM: Error - Couldn't load kernal ROM `kernal'.
Error - Machine initialization failed.

I put these files in Vice/Vice/C64:

basic-901226-01.bin
chargen-901225-01.bin
chargen-906143-02.bin
kernal-251104-04.bin
kernal-390852-01.bin
kernal-901227-01.bin
kernal-901227-02.bin
kernal-901227-03.bin
kernal-901246-01.bin
kernal-906145-02.bin

got these from the Vice3.7 Win32 release.

You need to have a 'kernal', 'chargen' and 'basic' file without the dates/versions in the name. Then it should run OK.

Gallery Title:
Image URL:
Image Title:
Comment:
Tick this box if you would like to allow other members to add images to your gallery.Add Image

Gallery Title:
Image URL:
Image Title:
Comment:
Tick this box if you would like to allow other members to add images to your gallery.Add Image

title

title

Run full-blown vice on the Mini/Maxi/VIC-20

Post by clindsa1 on Jul 28, 2021 14:52:45 GMT

Post by jj0 on Jul 29, 2021 8:47:31 GMT

Post by spannernick on Jul 29, 2021 11:18:47 GMT

Post by knightfire on Oct 5, 2021 4:21:02 GMT

Post by jj0 on Oct 5, 2021 11:57:27 GMT

Post by spannernick on Oct 8, 2021 14:04:35 GMT

Post by andromeda1968 on Jan 15, 2022 16:58:10 GMT

Post by spannernick on Jan 15, 2022 17:12:11 GMT

Post by jj0 on Jan 16, 2022 21:13:06 GMT

Post by andromeda1968 on Jan 17, 2022 10:52:01 GMT

Post by jj0 on Jan 17, 2022 10:59:25 GMT

Post by turrican9 on Dec 4, 2022 15:05:03 GMT

Post by lasttape on Jun 4, 2023 18:45:37 GMT

Post by jj0 on Jun 5, 2023 11:40:40 GMT

Post by lasttape on Jun 6, 2023 10:27:07 GMT

Post by jj0 on Jun 6, 2023 14:28:57 GMT

Post by lasttape on Jun 6, 2023 16:05:46 GMT

Post by lasttape on Jun 6, 2023 17:03:31 GMT

Post by lasttape on Jun 6, 2023 18:16:35 GMT

Post by jj0 on Jun 7, 2023 12:26:33 GMT

Post by lasttape on Jun 7, 2023 13:47:39 GMT

Post by jj0 on Jun 8, 2023 13:22:26 GMT

Post by lasttape on Jun 8, 2023 14:18:27 GMT

Post by lasttape on Jun 9, 2023 10:53:18 GMT

Post by jj0 on Jun 12, 2023 15:11:45 GMT

Post by lasttape on Jun 12, 2023 18:57:34 GMT

Post by b0wman on Jul 9, 2023 20:39:29 GMT

Post by jj0 on Jul 10, 2023 12:55:05 GMT

Post by b0wman on Jul 10, 2023 13:18:24 GMT

Post by jj0 on Jul 10, 2023 15:11:40 GMT

Shoutbox