Recently I updated my Vice emulator on Ubuntu 21.10 from the repository
to version 3.5. Now it doesn't work anymore. It complains that it cannot
find the (Commodore)kernel. That is however there where it belongs in /usr/lib/vice. How do I tell the program where to look for these
auxillary files?

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Tue, 8 Mar 2022 16:05:45 +0100, me@privacy.net wrote:

Recently I updated my Vice emulator on Ubuntu 21.10 from the
repository to version 3.5. Now it doesn't work anymore. It complains
that it cannot find the (Commodore)kernel. That is however there where
it belongs in /usr/lib/vice. How do I tell the program where to look
for these auxillary files?

Hah, had a similar problem.

VICE seems to have moved its config from ~/.vice/vicerc to ~/.config/vice/vicerc without copying the config of the old file. I
assume that also other settings are ignored?

If you know the path of your kernal (it will later also ask for the
chargen and basic), you can o the command line:

x64 -kernel /path/to/kernal -chargen /path/to/chargen -basic /path/to/basic

After the emulator initialized save the config. After that a simple "x64"
or click on the VICE up should work again.

[My problem]

After I realized that and that ~/.vice is no longer used, I put the
kernal, chargen and basic in there and told VICE were they are (see
above). But when I wanted to do the same for xvic (VIC-20) I realized the
three files for it have the same filenames as for the C64. Thus overwrite
them when copying over there.

On my old computer file locations are a mess. I for example have

/usr/lib/vice/C64/kernal

as well as

/usr/lib/vice/data/C64/kernal

But on the new machine /usr/lib/vice/ already exists, but is empty.

Am I supposed to create directories there to move the various kernal and
other files in there? Or is there a better location?

Short: Any Linux (preferred Debian-) user has x64, xvic and others
working, and then tell where the kernal and other files are located?
--
Andreas

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Andreas Kohlbach wrote:

On Tue, 8 Mar 2022 16:05:45 +0100, me@privacy.net wrote:

Recently I updated my Vice emulator on Ubuntu 21.10 from the
repository to version 3.5. Now it doesn't work anymore. It complains
that it cannot find the (Commodore)kernel. That is however there where
it belongs in /usr/lib/vice. How do I tell the program where to look
for these auxillary files?

Hah, had a similar problem.

VICE seems to have moved its config from ~/.vice/vicerc to ~/.config/vice/vicerc without copying the config of the old file. I
assume that also other settings are ignored?

If you know the path of your kernal (it will later also ask for the
chargen and basic), you can o the command line:

x64 -kernel /path/to/kernal -chargen /path/to/chargen -basic /path/to/basic

After the emulator initialized save the config. After that a simple "x64"
or click on the VICE up should work again.

[My problem]

After I realized that and that ~/.vice is no longer used, I put the
kernal, chargen and basic in there and told VICE were they are (see
above). But when I wanted to do the same for xvic (VIC-20) I realized the three files for it have the same filenames as for the C64. Thus overwrite them when copying over there.

On my old computer file locations are a mess. I for example have

/usr/lib/vice/C64/kernal

as well as

/usr/lib/vice/data/C64/kernal

But on the new machine /usr/lib/vice/ already exists, but is empty.

Am I supposed to create directories there to move the various kernal and other files in there? Or is there a better location?

Short: Any Linux (preferred Debian-) user has x64, xvic and others
working, and then tell where the kernal and other files are located?

Thank you for your reply. Telling frankly, I don't really like the above mentioned somewhat tedious solution. But now I have a better one :-)

I looked up the handbook. 405 poorly written pages! Fortunately on page
19 I found where Vice looks for all of its files. The first place is ~/.local/share so I copied /usr/lib/vice to that directory. It works now.

I'm fed up with Ubuntu :-(

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Thu, 10 Mar 2022 23:20:51 +0100, me@privacy.net wrote:

Andreas Kohlbach wrote:

[My problem]
After I realized that and that ~/.vice is no longer used, I put the
kernal, chargen and basic in there and told VICE were they are (see
above). But when I wanted to do the same for xvic (VIC-20) I realized the
three files for it have the same filenames as for the C64. Thus overwrite
them when copying over there.
On my old computer file locations are a mess. I for example have
/usr/lib/vice/C64/kernal
as well as
/usr/lib/vice/data/C64/kernal
But on the new machine /usr/lib/vice/ already exists, but is empty.
Am I supposed to create directories there to move the various kernal
and
other files in there? Or is there a better location?
Short: Any Linux (preferred Debian-) user has x64, xvic and others
working, and then tell where the kernal and other files are located?

Thank you for your reply. Telling frankly, I don't really like the
above mentioned somewhat tedious solution. But now I have a better
one :-)

I looked up the handbook. 405 poorly written pages! Fortunately on
page 19 I found where Vice looks for all of its files. The first place
is ~/.local/share so I copied /usr/lib/vice to that directory. It
works now.

Can you please list the contents of your ~/.local/share and /usr/lib/vice
for me?

I'm fed up with Ubuntu :-(

Suppose it's not Ubuntu's fault. The "problem" might be that Windows'
VICE comes with kernal et al already in the right place after
installation, whereas Linux doesn't even have these files.

And - umm - why is that Windows had them? AFAIK both the Windows and
Linux version of VICE are freeware.
--
Andreas

http://www.ankman.de/commodore-64-sid-music/

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Andreas Kohlbach wrote:

On Thu, 10 Mar 2022 23:20:51 +0100, me@privacy.net wrote:

Andreas Kohlbach wrote:

[My problem]
After I realized that and that ~/.vice is no longer used, I put the
kernal, chargen and basic in there and told VICE were they are (see
above). But when I wanted to do the same for xvic (VIC-20) I realized the >>> three files for it have the same filenames as for the C64. Thus overwrite >>> them when copying over there.
On my old computer file locations are a mess. I for example have
/usr/lib/vice/C64/kernal
as well as
/usr/lib/vice/data/C64/kernal
But on the new machine /usr/lib/vice/ already exists, but is empty.
Am I supposed to create directories there to move the various kernal
and
other files in there? Or is there a better location?
Short: Any Linux (preferred Debian-) user has x64, xvic and others
working, and then tell where the kernal and other files are located?

Thank you for your reply. Telling frankly, I don't really like the
above mentioned somewhat tedious solution. But now I have a better
one :-)

I looked up the handbook. 405 poorly written pages! Fortunately on
page 19 I found where Vice looks for all of its files. The first place
is ~/.local/share so I copied /usr/lib/vice to that directory. It
works now.

Can you please list the contents of your ~/.local/share and /usr/lib/vice
for me?

/usr/lib/vice$ ls
C128 C64 C64DTV CBM-II DRIVES PET PLUS4 PRINTER SCPU64 VIC20

These are directories. Their content had been taken from from the source tarball or the Windows binary - I don't remember exactly. Anyway, I just
copied the directories over.

~/.local/share/vice$ ls
C128 C64 C64DTV CBM-II DRIVES PET PLUS4 PRINTER SCPU64 VIC20

I'm fed up with Ubuntu :-(

Suppose it's not Ubuntu's fault. The "problem" might be that Windows'
VICE comes with kernal et al already in the right place after
installation, whereas Linux doesn't even have these files.

Sure it's Ubuntu's fault! They are the ones who compile and at compile
time set the directory for auxillary files like ROM images and such.
What they've done is totally inconsistent with the handbook. They messed
up the place for the binaries and ROMS. According to the handbook there
should be 3 directories where Vice looks for the files. Only the first directory under .local/share works. They should have changed the place
for binaries AND files, instead they just changed the place for the
files, once again giving a shit about standards.

And - umm - why is that Windows had them? AFAIK both the Windows and
Linux version of VICE are freeware.

I don't understand it either.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sat, 12 Mar 2022 01:18:16 +0100, me@privacy.net wrote:

Andreas Kohlbach wrote:

On Thu, 10 Mar 2022 23:20:51 +0100, me@privacy.net wrote:

I looked up the handbook. 405 poorly written pages! Fortunately on
page 19 I found where Vice looks for all of its files. The first place
is ~/.local/share so I copied /usr/lib/vice to that directory. It
works now.

Can you please list the contents of your ~/.local/share and
/usr/lib/vice
for me?

/usr/lib/vice$ ls
C128 C64 C64DTV CBM-II DRIVES PET PLUS4 PRINTER SCPU64 VIC20

These are directories. Their content had been taken from from the
source tarball or the Windows binary - I don't remember
exactly. Anyway, I just copied the directories over.

~/.local/share/vice$ ls
C128 C64 C64DTV CBM-II DRIVES PET PLUS4 PRINTER SCPU64 VIC20

Interesting. This seems to be a mirror of some kind.

But helpful. I will put kernal, basic and cargen files there. Hoping VICE
will look there.

Thank you.
--
Andreas

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)