vice-emu-mail Mailing List for VICE

Hyho!

as usual, we will make a release at xmas - which is in roughly 7 weeks!

Please everyone check out the current trunk now, and do a couple basic checks:


- make sure it compiles, both SDL and GTK, on "your platform". If not, please 
fix :) (since we build all ports automatically on github this should be a non 
issue)

- while doing that, you might spot a few more warnings than there used to be -
feel free to try to fix some of these :) (this should also be a non issue for 
the most part)

- please take some time and update NEWS. i have not started with this yet, but 
feel free to do so :)

- have a look at the "howto" for your platform, and update it if needed

- perhaps skim through the documentation as well

- please look over the development wiki page at https://vice-emu.pokefinder.org/wiki/3.9.1 - there might be some small things left that can 
be fixed quickly before the release. In particular the remaining rendering 
related things would be nice to have, and there are a bunch of random macOS 
related TODOs too.

- have a look if there is any low hanging fruit left one the bugtracker and/or
patches tracker. in particular this "monitor window does not open properly" 
(apparently fixed on linux and windows, but still broken on macOS) and the 
"cbm font not registered at startup" (windows) is a bit annoying

- There are a bunch of scripts in the tree, some of which are very specific
and used by few people. If you are one of them, please check if the scripts
are all working and up to date.

Whatever you do, please do NOT commit "big" things anymore - from now on it
should be strictly small bugfixes, and other little things that will not break
anything no matter what :)

It might also be a good time to check #vice-dev more often :)

I will send another reminder in some weeks, which will then announce
the  "real" codefreeze before christmas.

Please really take the time to go through the above now - so we can make this
release as smooth as possible :)


Also Compyx, if you are reading this - please get in touch. We are missing you 
:)


-- 

http://hitmen.eu                 http://rr.pokefinder.org
http://vice-emu.sourceforge.net  http://magicdisk.untergrund.net

The best thing I did with my amiga, was probably to give it away :) 
<Jeff/Camelot>

Am 22. Oktober 2025 23:02:54 schrieb gpz via Vice-emu-mail 
<vic...@li...>:

> Am Mittwoch, 22. Oktober 2025, 22:52:18 Mitteleuropäische Sommerzeit schrieb
> A. Fachat via Vice-emu-mail:
>> Hi there,
>>
>> I am trying to find out if VICE supports the PC disk image formats on
>> the VC1571 emulation.
>>
>> I couldn't find it in the VICE docs, so I assume it does not, but maybe
>> you know more.
>>
>> Reason is I am trying to resurrect my BDOS program that can copy files
>> to/from PC floppies, which was once a project of the month in the German
>> 64er magazin.
>>
>> I already recovered the sources (because other than I assumed they
>> weren't on the web already...), now I am trying to run it again,
>> preferably in an emulator for better video capture (for my Youtube channel).
>
>
> Nope, it is not supported. (You can mostly trust the docs these days, other
> than back in the days, they are actually up to date and cover everything :))

What a pity.

How much is missing? Is it basically the 1770 emulation missing (plus 
resource infrastructure for file image handling)?

André

Am Mittwoch, 22. Oktober 2025, 22:52:18 Mitteleuropäische Sommerzeit schrieb 
A. Fachat via Vice-emu-mail:
> Hi there,
> 
> I am trying to find out if VICE supports the PC disk image formats on
> the VC1571 emulation.
> 
> I couldn't find it in the VICE docs, so I assume it does not, but maybe
> you know more.
> 
> Reason is I am trying to resurrect my BDOS program that can copy files
> to/from PC floppies, which was once a project of the month in the German
> 64er magazin.
> 
> I already recovered the sources (because other than I assumed they
> weren't on the web already...), now I am trying to run it again,
> preferably in an emulator for better video capture (for my Youtube channel).


Nope, it is not supported. (You can mostly trust the docs these days, other 
than back in the days, they are actually up to date and cover everything :))


-- 

http://hitmen.eu                 http://rr.pokefinder.org
http://vice-emu.sourceforge.net  http://magicdisk.untergrund.net

The trouble with quotes on the internet is that it's difficult to determine 
whether or not they're genuine 
<Joseph Goebbels>

Hi there,

I am trying to find out if VICE supports the PC disk image formats on 
the VC1571 emulation.

I couldn't find it in the VICE docs, so I assume it does not, but maybe 
you know more.

Reason is I am trying to resurrect my BDOS program that can copy files 
to/from PC floppies, which was once a project of the month in the German 
64er magazin.

I already recovered the sources (because other than I assumed they 
weren't on the web already...), now I am trying to run it again, 
preferably in an emulator for better video capture (for my Youtube channel).

Any help appreciated!

Thanks

André

Hello List :)

I was chatting with folks online about test equipment and someone
mentioned that the Vice Team could use some timing scans for the
commodore 128, specifically the traffic at the Vic-IIe socket.

I will have opportunity to do scans at VCFMW in a week or so and would
like to know what test programs the team would find most valuable for
single-cycle emulation.

The general plan is to get timing and state captures of chosen
test-suite programs on the c128, process them into data usable outside
of my analyzer, and send them to someone in the team that would find
them useful.

Let me know what you folks need, I'm happy to assist!

-jbev

Am Montag, 11. August 2025, 11:42:39 Mitteleuropäische Sommerzeit schrieb 
timothylegg:
> Hello,
> 
> I have been puzzled over the functionality of a couple particularly
> complicated software packages on the C64.  The chis command is pretty
> amazing and helpful, but I am greedy and want more.
> 
> Is there a way to have the emulator dump something equivalent to chis to a
> file, perhaps with an arbitrary number of instructions?  I'm not
> worried about disk space nor the performance of the emulator.  I'm also not
> afraid to modify source code, but if there is a shortcut to achieving this,
> I'd greatly appreciate the tip.

If you can build VICE yourself, configure with --enable-debug. You'll get some 
extra Menu items that let you log various things. WARNING this generates a LOT 
of output :)

-- 

http://hitmen.eu                 http://rr.pokefinder.org
http://vice-emu.sourceforge.net  http://magicdisk.untergrund.net

Wenn der Wind des Wandels weht, beginnen manche Mauern zu bauen. Andere bauen 
Windmühlen. 
<Chinesische Weisheit>

No not the same question, but for people in the future after lemon64 is
occupied by a domain squatter, the answer was:

x64sc -monlog -monlogname monitor.log

But that wasn't exactly what I was hoping for.  I can see how it would be
useful at times.  I ran the emulator for a couple seconds before quitting
and was hoping to find a log file that was a few hundred MB in size,
preferably seeing a first line starting similarly to:

.C:fce2  A2 FF       LDX #$FF ...

and whatever randomness the A, X and Y registers might be.  I honestly
don't know because I've never been able to press Alt-H that quickly.

Timothy D Legg

On Mon, Aug 11, 2025 at 12:37 PM Bacchus of fairLight <ba...@fa...>
wrote:

> Same question as this?
>
> https://www.lemon64.com/forum/viewtopic.php?t=81313
>
> /Pontus Berg
> +46 735 082860
>
> Den mån 11 aug. 2025 11:42timothylegg <tim...@gm...> skrev:
>
>> Hello,
>>
>> I have been puzzled over the functionality of a couple particularly
>> complicated software packages on the C64.  The chis command is pretty
>> amazing and helpful, but I am greedy and want more.
>>
>> Is there a way to have the emulator dump something equivalent to chis to
>> a file, perhaps with an arbitrary number of instructions?  I'm not
>> worried about disk space nor the performance of the emulator.  I'm also not
>> afraid to modify source code, but if there is a shortcut to achieving this,
>> I'd greatly appreciate the tip.
>>
>> Timothy Legg
>> _______________________________________________
>> Vice-emu-mail mailing list
>> Vic...@li...
>> https://lists.sourceforge.net/lists/listinfo/vice-emu-mail
>>
>

Same question as this?

https://www.lemon64.com/forum/viewtopic.php?t=81313

/Pontus Berg
+46 735 082860

Den mån 11 aug. 2025 11:42timothylegg <tim...@gm...> skrev:

> Hello,
>
> I have been puzzled over the functionality of a couple particularly
> complicated software packages on the C64.  The chis command is pretty
> amazing and helpful, but I am greedy and want more.
>
> Is there a way to have the emulator dump something equivalent to chis to a
> file, perhaps with an arbitrary number of instructions?  I'm not
> worried about disk space nor the performance of the emulator.  I'm also not
> afraid to modify source code, but if there is a shortcut to achieving this,
> I'd greatly appreciate the tip.
>
> Timothy Legg
> _______________________________________________
> Vice-emu-mail mailing list
> Vic...@li...
> https://lists.sourceforge.net/lists/listinfo/vice-emu-mail
>

Hello,

I have been puzzled over the functionality of a couple particularly
complicated software packages on the C64.  The chis command is pretty
amazing and helpful, but I am greedy and want more.

Is there a way to have the emulator dump something equivalent to chis to a
file, perhaps with an arbitrary number of instructions?  I'm not
worried about disk space nor the performance of the emulator.  I'm also not
afraid to modify source code, but if there is a shortcut to achieving this,
I'd greatly appreciate the tip.

Timothy Legg

That is very interesting and this is the first I have heard about this.  I
had no idea that the VIC-II has the capability to suspend CPU activity, as
least what is visible to the user via the chis tool in the monitor.  It has
been such a long time (early 1990s) since I heard/read about DMA on a
Commodore product.  I had to read up on DMA as well.

On Sun, Aug 10, 2025 at 1:26 PM gpz via Vice-emu-mail <
vic...@li...> wrote:

> Am Sonntag, 10. August 2025, 13:09:36 Mitteleuropäische Sommerzeit schrieb
> timothylegg:
> > I am using x64sc 3.9 (GTK3 3.24.41, GLib 2.80.0, Cairo 1.18.0, Pango
> > 1.52.1) which I'm pretty certain is compiled from source.
> >
> >
> > Last week, I used chis for the cpu_history and I noticed something
> > peculiar...
> >
> > C:c402  A9 10       LDA #$10       A:0e X:6f Y:00 SP:d8 .V-..I.C
> >  191041395
> > .C:c404  9D 00 C0    STA $C000,X    A:10 X:6f Y:00 SP:d8 .V-..I.C
> >  191041397
> > .C:c083  48          PHA            A:10 X:6f Y:00 SP:d5 .V-..I.C
> >  191041452
> > .C:c084  AD 18 C0    LDA $C018      A:10 X:6f Y:00 SP:d4 .V-..I.C
> >  191041455
> > .C:c087  4A          LSR A          A:0e X:6f Y:00 SP:d4 .V-..I.C
> >  191041459
> >
> > Does anyone know why the STA (9D) take 55 clock cycles?  From the MOS
> > datasheet, I see that it should be 5.  Is this a bug in the emulator or
> is
> > there something quirky with the C64 hardware that I don't know about yet?
>
> My guess would be that there was DMA going on ("badline" and/or sprites)
>
>
> --
>
> http://hitmen.eu                 http://rr.pokefinder.org
> http://vice-emu.sourceforge.net  http://magicdisk.untergrund.net
>
> Americans always do the right thing, once they have exhausted all other
> possibilities.
> <Winston Churchill>
>
>
>
>
>
>
> _______________________________________________
> Vice-emu-mail mailing list
> Vic...@li...
> https://lists.sourceforge.net/lists/listinfo/vice-emu-mail
>

Am Sonntag, 10. August 2025, 13:09:36 Mitteleuropäische Sommerzeit schrieb 
timothylegg:
> I am using x64sc 3.9 (GTK3 3.24.41, GLib 2.80.0, Cairo 1.18.0, Pango
> 1.52.1) which I'm pretty certain is compiled from source.
> 
> 
> Last week, I used chis for the cpu_history and I noticed something
> peculiar...
> 
> C:c402  A9 10       LDA #$10       A:0e X:6f Y:00 SP:d8 .V-..I.C
>  191041395
> .C:c404  9D 00 C0    STA $C000,X    A:10 X:6f Y:00 SP:d8 .V-..I.C
>  191041397
> .C:c083  48          PHA            A:10 X:6f Y:00 SP:d5 .V-..I.C
>  191041452
> .C:c084  AD 18 C0    LDA $C018      A:10 X:6f Y:00 SP:d4 .V-..I.C
>  191041455
> .C:c087  4A          LSR A          A:0e X:6f Y:00 SP:d4 .V-..I.C
>  191041459
> 
> Does anyone know why the STA (9D) take 55 clock cycles?  From the MOS
> datasheet, I see that it should be 5.  Is this a bug in the emulator or is
> there something quirky with the C64 hardware that I don't know about yet?

My guess would be that there was DMA going on ("badline" and/or sprites)


-- 

http://hitmen.eu                 http://rr.pokefinder.org
http://vice-emu.sourceforge.net  http://magicdisk.untergrund.net

Americans always do the right thing, once they have exhausted all other 
possibilities. 
<Winston Churchill>

I am using x64sc 3.9 (GTK3 3.24.41, GLib 2.80.0, Cairo 1.18.0, Pango
1.52.1) which I'm pretty certain is compiled from source.


Last week, I used chis for the cpu_history and I noticed something
peculiar...

C:c402  A9 10       LDA #$10       A:0e X:6f Y:00 SP:d8 .V-..I.C
 191041395
.C:c404  9D 00 C0    STA $C000,X    A:10 X:6f Y:00 SP:d8 .V-..I.C
 191041397
.C:c083  48          PHA            A:10 X:6f Y:00 SP:d5 .V-..I.C
 191041452
.C:c084  AD 18 C0    LDA $C018      A:10 X:6f Y:00 SP:d4 .V-..I.C
 191041455
.C:c087  4A          LSR A          A:0e X:6f Y:00 SP:d4 .V-..I.C
 191041459

Does anyone know why the STA (9D) take 55 clock cycles?  From the MOS
datasheet, I see that it should be 5.  Is this a bug in the emulator or is
there something quirky with the C64 hardware that I don't know about yet?

Timothy Legg

Am Montag, 14. Juli 2025, 21:05:16 Mitteleuropäische Sommerzeit schrieb 
Torsten Kracke via Vice-emu-mail:
> Not sure where you can actually set NTSC in the settings. 

The setting was there until some releases ago, but i removed all of it, since 
it didn't make sense (and had no effect anyway).

You can also see the effective frame rate in the log file, btw, it will be 
printed every time the system needs to resync because something changed (eg at 
reset time when the registers are initialized)

-- 

http://hitmen.eu                 http://rr.pokefinder.org
http://vice-emu.sourceforge.net  http://magicdisk.untergrund.net

The weirder you are going to behave, the more normal you should look... When I 
see a kid with three or four rings in his nose, I know there is absolutely 
nothing extraordinary about that person. 
<P.J. O'Rourke>

Not sure where you can actually set NTSC in the settings. I only see the 
different models to choose from there. In the end all the older machines 
(before 4000/8000) use 60 Hz-monitors and only the later 
4000/8000-models have different Editor-ROMs with 50 or 60 Hz-modes. 
Actually for the 4000-series only the "fat" 12 inch-screens have the 
CRTC, the smaller 9-inch screens do not have the CRTC-chip and should 
all be 60 Hz.

See here on Zimmers:

https://www.zimmers.net/anonftp/pub/cbm/firmware/computers/pet/index.html

Look for the "edit-..."-ROMs down below. Also check this post on 
Stackexchange:

https://retrocomputing.stackexchange.com/questions/13034/did-all-integrated-commodore-pet-monitors-always-use-60-hz-refresh

If you want to check what your actual running VICE-emulator is using for 
the 4000/8000-models with CRTC, go into the Monitor (ALT+H) and type "io 
e880" - this will give information on the CRTC-controller (at $e880) and 
further down also show the timings. If you want to have a 60 Hz-machine 
you should use the accompanying editor-ROM from Zimmers and place it 
under "Machine - ROMS" in the Settings-menu.

Hope that helps,
tokra

Am 14.07.2025 um 19:20 schrieb KnightFire66--- via Vice-emu-mail:
> Hello,
>
>    I'm a big fan of the Commodore PETs/CBMs and I'm having issues with xpet.  My issues stem from NTSC (60Hz) / PAL (50Hz) parameters and default settings... they all seem to favor 50Hz, even when specifying the model and NTSC.  I have compiled both current versions under Mint Linux.  I own two 2001s, a fat 4032, and two 8032s; I obtained my ROMs from an older Vice release and even tried ROMs from MAME.
>    For me, in Canada, my assumption has been that the 2000, 4000, and 8000 series models should default to 60Hz, and only the 3000 models should default to 50Hz.
>
>    I wonder if this is an unintended side affect of http://sourceforge.net/p/vice-emu/45250
>

Hello, 

  I'm a big fan of the Commodore PETs/CBMs and I'm having issues with xpet.  My issues stem from NTSC (60Hz) / PAL (50Hz) parameters and default settings... they all seem to favor 50Hz, even when specifying the model and NTSC.  I have compiled both current versions under Mint Linux.  I own two 2001s, a fat 4032, and two 8032s; I obtained my ROMs from an older Vice release and even tried ROMs from MAME.
  For me, in Canada, my assumption has been that the 2000, 4000, and 8000 series models should default to 60Hz, and only the 3000 models should default to 50Hz. 

  I wonder if this is an unintended side affect of http://sourceforge.net/p/vice-emu/45250

-- 
Peace, 
Matt

I'm sorry, I wrote purpose but I intend suggest, propose

I'm not English.


Thanks


Il 03/04/2025 12:57, Luigi Russo ha scritto:
> Hi,
>
> I purpose to insert for audio leak session a slider volume regulation 
> or command line option, I would use it for emulate old crt sound and 
> now it's lov and I can't manage its volume.
>
>
> Thank you
>
>
> Gigi
>

Hi,

I purpose to insert for audio leak session a slider volume regulation or 
command line option, I would use it for emulate old crt sound and now 
it's lov and I can't manage its volume.


Thank you


Gigi

Am Mittwoch, 2. April 2025, 17:46:07 Mitteleuropäische Sommerzeit schrieb mac:
> Hi folks,
> 
> I code music for the 1541 floppy, or rather for its step motor.
> 
> To protect the good old retro hardware , I use a 1541 Ultimate2
> cartridge. That´s ok for ONE drive, but it can´t do sound for more than one.
> 
> So my question is: Could you import the stepmotor sounds from the
> Ultimate into WinVice?
> 
> The drive sound in WinVice isn´t "doing right" - just a constant
> creaking instead of the different step motor sounds.
> 
> Maybe the following data could be helpful?
> 
> 1541 ULTIMATE:
> 
> - format of the sound file in the sounds.bin files that you can find on
> the device:  They are at a sampling rate of 22050 Hz, stored raw in
> signed 8-bit samples. Location of the segments:
> 
> HUM: $0000 (Len: 4410)
> SLIP: $1200 (Len: 4410)
> TrackIn: $2400 (Len: 2048)
> TrackOut: $2C00 (Len: 2176)
> Head Bang: $3480 (Len: 2176)
> Insert: $3D00 (Len: 16256)
> Remove $7D00 (Len: 14336)
> 
> 
> Looking forward to your answer.

The samples are not the problem here (1541U used the same samples that VICE 
used last time i checked) - it's the implementation of the drive sounds 
itself. Its just a simple sample player right now, and will not work with 
"drive music".

So basically, it needs someone to step up and fix that. It's very low priority 
for us right now.

-- 

http://hitmen.eu                 http://rr.pokefinder.org
http://vice-emu.sourceforge.net  http://magicdisk.untergrund.net

Wer im Glashaus sitzt hat immer frische Gurken.

Hi folks,

I code music for the 1541 floppy, or rather for its step motor.

To protect the good old retro hardware , I use a 1541 Ultimate2
cartridge. That´s ok for ONE drive, but it can´t do sound for more than one.

So my question is: Could you import the stepmotor sounds from the
Ultimate into WinVice?

The drive sound in WinVice isn´t "doing right" - just a constant
creaking instead of the different step motor sounds.

Maybe the following data could be helpful?

1541 ULTIMATE:

- format of the sound file in the sounds.bin files that you can find on
the device:  They are at a sampling rate of 22050 Hz, stored raw in
signed 8-bit samples. Location of the segments:

HUM: $0000 (Len: 4410)
SLIP: $1200 (Len: 4410)
TrackIn: $2400 (Len: 2048)
TrackOut: $2C00 (Len: 2176)
Head Bang: $3480 (Len: 2176)
Insert: $3D00 (Len: 16256)
Remove $7D00 (Len: 14336)


Looking forward to your answer.

Best regards,
Sebastian

Am Freitag, 31. Januar 2025, 17:10:09 Mitteleuropäische Normalzeit schrieb 
Boris Steinmetz:
> I have a question which I need a little bit support with.
> I have VICE running on a Raspberry Pi 5 (Raspbian OS). Now I'm looking for
> a way to control 8 GPIOs from the Raspberry Pi from within the VICE
> emulated C64. On these GPIOs I have hooked up some LEDs. This works fine,
> but since I'm not a professional software developer I'm not sure if my
> approach is really good. Maybe you have a better proposal.
> 
> On the Raspbian side, with the GNU debugger (gdb) and some Python scripts,
> I was able to find the memory addresses used in the Raspbian OS for the
> VICE C64 memory location $C000 - $C007 and also the memory range used for
> the C64 screen memory.
> But for some reason I can't find the memory locations $DD00 and upwards
> which is to control the CIA2 for the user port. I did same way as I did to
> look up $0400 and $C000 by putting a pattern of some values in it which I
> was then looking for with a python script. As mentioned, it did work fine
> for $0400 and $C000 but not for $DD00 and upwards.
> 
> Do you know how I can find this memory locations or do have a better
> proposal for me to emulate the userport on my raspberry pi from within VICE?
> 
> Thanks a lot for a helpful advice!!
> Have a nice day.

First of all - use a recent VICE release (the last one, 3.9)

now look at src/userport/userport_io_sim.c

at the top uncomment #define HOST_HARDWARE_IO

then scroll down to "userport_io_hw_store_pbx" (and following) functions, 
there you can add the gpio handling code

-- 

http://hitmen.eu                 http://rr.pokefinder.org
http://vice-emu.sourceforge.net  http://magicdisk.untergrund.net

Every program has at least one bug and can be shortened by at least one 
instruction --- from which, by induction, one can deduce that every program 
can be reduced to one instruction which doesn't work.

Am Montag, 3. Februar 2025, 23:14:33 Mitteleuropäische Normalzeit schrieb 
Fabbo via Vice-emu-mail:
> Il 03-02-2025 17:17, gpz via Vice-emu-mail ha scritto:
> >> * It (x64sc) couldn't find the kernel ROM.  I ran it again with the
> >> parameter -directory/path/to/ROMS where the ./C64/, ./DRIVES/ and
> >> ./PRINTERS/ are located and it launched normally.  Interestingly, this
> >> path
> >> has been stored somewhere because x64sc found the ROMs without the
> >> -directory parameter the next time I ran it.  The -directory/PATH/
> >> parameter is very important for people to know about.  I remember once in
> >> the past, I had the damndest time figuring what the default ROM path was
> >> and I couldn't access a Settings window to define the path immediately
> >> after installation.  Maybe in future just have the screen emulation be a
> >> black rectangle with a VICE logo in place of the emulation and then a
> >> novice can click Settings and correct the issues with missing ROMs and
> >> config files?
> > 
> > Well, you shouldnt have to do this when VICE was installed correctly.
> > Using - directory and then saving the path into the config really isn't a
> > good idea at all, since that means whenever you will use "reset
> > settings", you end up with a non working emulator. The right way to fix
> > this problem is: install VICE correctly 🙂
> 
> Another thing that works is the -directory command-line switch, followed
> by the path of the data directory (the one that has subdirectories C64,
> DRIVES etc.). Absolute path is recommended, so it will work no matter
> where you launch the emulator from. When the emulator is running, save
> the settings so they will be remembered

That however has the same problem - using "reset settings" results in a non 
working emulator

-- 

http://hitmen.eu                 http://rr.pokefinder.org
http://vice-emu.sourceforge.net  http://magicdisk.untergrund.net

...the harm was done: the topic became known as "computer science"---which, 
actually, is like referring to surgery as "knife science"---and it was firmly 
implanted in people's minds that computing science is about machines and their 
peripheral equipment. 
<Edsgar Dijkstra>

Il 03-02-2025 17:17, gpz via Vice-emu-mail ha scritto:
>> * It (x64sc) couldn't find the kernel ROM.  I ran it again with the
>> parameter -directory/path/to/ROMS where the ./C64/, ./DRIVES/ and
>> ./PRINTERS/ are located and it launched normally.  Interestingly, this path
>> has been stored somewhere because x64sc found the ROMs without the
>> -directory parameter the next time I ran it.  The -directory/PATH/
>> parameter is very important for people to know about.  I remember once in
>> the past, I had the damndest time figuring what the default ROM path was
>> and I couldn't access a Settings window to define the path immediately
>> after installation.  Maybe in future just have the screen emulation be a
>> black rectangle with a VICE logo in place of the emulation and then a
>> novice can click Settings and correct the issues with missing ROMs and
>> config files?
> Well, you shouldnt have to do this when VICE was installed correctly. Using -
> directory and then saving the path into the config really isn't a good idea at
> all, since that means whenever you will use "reset settings", you end up with
> a non working emulator. The right way to fix this problem is: install VICE
> correctly 🙂

Another thing that works is the -directory command-line switch, followed 
by the path of the data directory (the one that has subdirectories C64, 
DRIVES etc.). Absolute path is recommended, so it will work no matter 
where you launch the emulator from. When the emulator is running, save 
the settings so they will be remembered

Am Samstag, 1. Februar 2025, 22:26:36 Mitteleuropäische Normalzeit schrieb 
timothylegg:
> I noticed a few odd things right away after running the executable the
> first time.
> 
> * It (x64sc) couldn't find the kernel ROM.  I ran it again with the
> parameter -directory /path/to/ROMS where the ./C64/, ./DRIVES/ and
> ./PRINTERS/ are located and it launched normally.  Interestingly, this path
> has been stored somewhere because x64sc found the ROMs without the
> -directory parameter the next time I ran it.  The -directory /PATH/
> parameter is very important for people to know about.  I remember once in
> the past, I had the damndest time figuring what the default ROM path was
> and I couldn't access a Settings window to define the path immediately
> after installation.  Maybe in future just have the screen emulation be a
> black rectangle with a VICE logo in place of the emulation and then a
> novice can click Settings and correct the issues with missing ROMs and
> config files?

Well, you shouldnt have to do this when VICE was installed correctly. Using -
directory and then saving the path into the config really isn't a good idea at 
all, since that means whenever you will use "reset settings", you end up with 
a non working emulator. The right way to fix this problem is: install VICE 
correctly :)

> * On my host computer, which is a Lenovo T440p with a German key layout, I
> have the QWERTZ keyboard.  I pressed the Z-key on my laptop and a 'Z'
> appeared in the emulator.  This is notable because in settings, the default
> of North American host system keyboard is still set.  I thought I would see
> a 'Y' in the emulation.  I actually looked to see if there existed a German
> chargen ROM or kernel that was set by default.  So in settings I specified
> a German host keyboard.  I didn't observe any change in behavior - good.

This happens because "symbolic" mapping is the default - many keys will just 
work, regardless of the host layout

> + I went to a friend's house with a working C64 and found the keys behaving
> completely differently than I remembered from the 1990s.  Wow, it's pretty
> odd by today's standards, but I vaguely remember it was quite a learning
> curve to adapt to a 101-key keyboard back in the mid 1990s.  I was
> absolutely certain that CTRL + Letter Keys produced PETSCII glyph shapes,
> but that was in fact C= and the shift key.  No, CTRL+Q does CURSOR-DOWN,
> CTRL-E does WHITE, and other obscure, potentially undefined behaviors.  So
> this has been a Nelson Mandela moment for me and I probably would have lost
> a 50€ bet over this. I don't think I can become accustomed to Symbolic
> mapping again now that I realize what is happening - the host TAB being the
> emulated C= is unnatural.
> 
> I printed out a picture of a C64 keyboard with a bunch of notes and slid it
> into a plastic sleeve.  There will come a time that I'll write my own vkm
> file, but it probably won't be until next week.  I absolutely love these
> config files.  This has been a really fun learning experience for me and am
> really grateful for this mailing list.  If you end up in the Nürnberg area,
> hit me up and I'll buy you dinner somewhere nice.

Did you look at the manual? There are pictures of the provided layouts, both 
symbolic and positional. The later will try to reproduce the C64 layout. 


-- 

http://hitmen.eu                 http://rr.pokefinder.org
http://vice-emu.sourceforge.net  http://magicdisk.untergrund.net

C makes it easy to shoot yourself in the foot; C++ makes it harder, but when 
you do it blows your whole leg off. 
<Bjarne Stroustrup>

GMail makes it maddeningly easy to accidentally -NOT- reply to list.  Every
reply is an awkward procedure.  Thanks for forwarding the previous message.

I installed the GTK3 variant from source and the doc you cited is
wonderfully well-written, concise, exacting and complete.  Great job!
Compiling from source is how it all started for me when I switched from C64
to UN*X in 1996, so it's still second nature to me.  However, great
documentation doesn't come by luck or chance.  Now I want to read through
the source and customize my build.

I noticed a few odd things right away after running the executable the
first time.

* It (x64sc) couldn't find the kernel ROM.  I ran it again with the
parameter -directory /path/to/ROMS where the ./C64/, ./DRIVES/ and
./PRINTERS/ are located and it launched normally.  Interestingly, this path
has been stored somewhere because x64sc found the ROMs without the
-directory parameter the next time I ran it.  The -directory /PATH/
parameter is very important for people to know about.  I remember once in
the past, I had the damndest time figuring what the default ROM path was
and I couldn't access a Settings window to define the path immediately
after installation.  Maybe in future just have the screen emulation be a
black rectangle with a VICE logo in place of the emulation and then a
novice can click Settings and correct the issues with missing ROMs and
config files?

* On my host computer, which is a Lenovo T440p with a German key layout, I
have the QWERTZ keyboard.  I pressed the Z-key on my laptop and a 'Z'
appeared in the emulator.  This is notable because in settings, the default
of North American host system keyboard is still set.  I thought I would see
a 'Y' in the emulation.  I actually looked to see if there existed a German
chargen ROM or kernel that was set by default.  So in settings I specified
a German host keyboard.  I didn't observe any change in behavior - good.

+ I went to a friend's house with a working C64 and found the keys behaving
completely differently than I remembered from the 1990s.  Wow, it's pretty
odd by today's standards, but I vaguely remember it was quite a learning
curve to adapt to a 101-key keyboard back in the mid 1990s.  I was
absolutely certain that CTRL + Letter Keys produced PETSCII glyph shapes,
but that was in fact C= and the shift key.  No, CTRL+Q does CURSOR-DOWN,
CTRL-E does WHITE, and other obscure, potentially undefined behaviors.  So
this has been a Nelson Mandela moment for me and I probably would have lost
a 50€ bet over this. I don't think I can become accustomed to Symbolic
mapping again now that I realize what is happening - the host TAB being the
emulated C= is unnatural.

I printed out a picture of a C64 keyboard with a bunch of notes and slid it
into a plastic sleeve.  There will come a time that I'll write my own vkm
file, but it probably won't be until next week.  I absolutely love these
config files.  This has been a really fun learning experience for me and am
really grateful for this mailing list.  If you end up in the Nürnberg area,
hit me up and I'll buy you dinner somewhere nice.

Timothy Legg

On Tue, Jan 28, 2025 at 9:54 PM gpz via Vice-emu-mail <
vic...@li...> wrote:

> (please reply to the list, not me :))
>
> Perhaps you have mixed up keymaps from different versions? Hard to say
>
> as for that "8 bit style settings" - you have built the SDL version then,
> you
> probably want the GTK version instead (see the howto in /docs/)
>
>
> Am Dienstag, 28. Januar 2025, 21:42:51 Mitteleuropäische Normalzeit
> schrieb
> timothylegg:
> > How can this be a problem outside of vice?
> >
> > I did:
> > sudo apt remove vice
> > sudo apt install vice
> > and recovered the exact same roms from a tar of /usr/share/vice/
> >
> > Now CTRL-9 and CTRL-0 work normally.  Unfortunately, I can't reproduce
> this
> > now.  Uninstalling and installing fixed it.
> >
> > Until I find a deb file for libflac8 for Ubuntu 24.04, I'll be staying at
> > 3.7.  I've compiled from source but utterly despise the 8-bit style
> > settings configuration interface.  I strongly prefer the Settings being
> > access from a box launched from a pulldown menu surrounding the
> application.
> >
> > On Mon, Jan 27, 2025 at 6:38 PM gpz via Vice-emu-mail <
> >
> > vic...@li...> wrote:
> > > Am Montag, 27. Januar 2025, 18:31:49 Mitteleuropäische Normalzeit
> schrieb
> > >
> > > timothylegg:
> > > > I tried that and remembered why I don't use positional mapping.  I
> hit
> > > > my
> > > > °/^ key to the left of my 1, and I get a '6' instead of a back arrow.
> > > >
> > > > What strikes me funny with this is that the three keys CTRL, 9 and 0
> > > > each
> > > > work independently to each other, but not in combination.  It's
> almost
> > > > as
> > > > if a ROM is corrupted - but this is software and just can't be.  If I
> > > > was
> > > > on my C-64, I'd be checking for bad capacitors or screwy voltages
> right
> > > > about now.  In 1992, I would cycle the power a few times.  This is
> 2025
> > >
> > > and
> > >
> > > > I restarted the emulator three times and it persists.  I am
> absolutely
> > > > certain that CTRL-9 and CTRL-0 toggled reverse with this binary just
> a
> > >
> > > week
> > >
> > > > ago.
> > >
> > > Really sounds like the problem is somewhere else than VICE - as said in
> > > the
> > > other way, it works for me, using either positional or symbolic keymap
> > >
> > >
> > > --
> > >
> > > http://hitmen.eu                 http://rr.pokefinder.org
> > > http://vice-emu.sourceforge.net  http://magicdisk.untergrund.net
> > >
> > > Vorsicht: Lesen gefährdet die Dummheit!
> > >
> > >
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > Vice-emu-mail mailing list
> > > Vic...@li...
> > > https://lists.sourceforge.net/lists/listinfo/vice-emu-mail
>
>
> --
>
> http://hitmen.eu                 http://rr.pokefinder.org
> http://vice-emu.sourceforge.net  http://magicdisk.untergrund.net
>
> No matter what the anticipated result, there will always be someone eager
> to
> (a) misinterpret it, (b) fake it, or (c) believe it happened according to
> his
> own pet theory.
>
>
>
>
>
>
> _______________________________________________
> Vice-emu-mail mailing list
> Vic...@li...
> https://lists.sourceforge.net/lists/listinfo/vice-emu-mail
>

Hello

Thanks a lot for this amazing emulator!!

I have a question which I need a little bit support with.
I have VICE running on a Raspberry Pi 5 (Raspbian OS). Now I'm looking for
a way to control 8 GPIOs from the Raspberry Pi from within the VICE
emulated C64. On these GPIOs I have hooked up some LEDs. This works fine,
but since I'm not a professional software developer I'm not sure if my
approach is really good. Maybe you have a better proposal.

On the Raspbian side, with the GNU debugger (gdb) and some Python scripts,
I was able to find the memory addresses used in the Raspbian OS for the
VICE C64 memory location $C000 - $C007 and also the memory range used for
the C64 screen memory.
But for some reason I can't find the memory locations $DD00 and upwards
which is to control the CIA2 for the user port. I did same way as I did to
look up $0400 and $C000 by putting a pattern of some values in it which I
was then looking for with a python script. As mentioned, it did work fine
for $0400 and $C000 but not for $DD00 and upwards.

Do you know how I can find this memory locations or do have a better
proposal for me to emulate the userport on my raspberry pi from within VICE?

Thanks a lot for a helpful advice!!
Have a nice day.

BR
Boris Steinmetz