xpet virtual devices has no UI setting
Versatile Commodore Emulator
Brought to you by:
blackystardust,
gpz
Menu
▾
▴
#1212 xpet virtual devices has no UI setting
I tried to access the host filesystem directory directly, using the "device type: filesystem" in the drive settings tab. However, I was unable to access the filesystem.
Only when I enable "-virtualdev" on the command line I could use "device type: filesystem" to access the host's filesystem.
I did not find any kind of UI setting in the Linux Gtk3 port that sets this setting.
Note: xpet does not use "traps" to communicate with the host's filesystem, it uses the virtual IEEE488 bus. So there is (rightly) no "traps" setting in xpet.
Note: same may be true for CBM-II / CBM500
any idea what resource that is related to? to me "virtualdev" means "device traps" (on x64 it certainly is)
it's the same "virtualdev" setting as in the other emus (in traps.c). However, the xpet (and xcbm2) don't use traps to tap into the IEEE488 traffic, that is what the virtual IEEE488 bus is for.
In fact you can use true drive emulation on unit8 and filesystem virtual drive on unit 11 at the same time. You can also use all these with other operating systems in the PET, as no traps are used (Actually I'm still proud of this).
Looking at it this way, virtualdev could be enabled in xpet/xcbm2 by default anyway.
Look on the "Emulator" pane in the Settings dialog.
Last edit: Greg King 2020-04-16
seems that you implemented the virtual devices for IEEE in the way i wish they were implemented for IEC also :) indeed, enabling them by default is no problem in that case - which is why i did now in r37633
closing this, the setting is indeed there (perhaps not at the most optimal place =P)
I've moved the 'virtual devices' checkbutton to settings -> peripheral devices -> generic. Makes a little more sense, although we now have a 'settings page' with a single widget, but that could change.
As for enabling virtual devices by default in xpet/xcbm5x0/xcbm2, wouldn't that interfere with tape emulation? ie TAP vs T64?
good question :) i haven't seen either for the PET :)
You mean tap/t64's for the PET? Me neither, but I think the PET and perhaps CBM-II actually support two tape drives?
they do!
but no idea if t64 would work at all. or tap for that matter :)
Well, t64 should be on its way out, and I suppose we'll deal with TAPs for PET/CBM-II when it comes up (probably never).
Closing again.
It turns out that the change to enable virtual devices by default on a PET is the cause of bug #1250...
Pascal seems to have some loader routine which touches the I/O chips, and when this option is enabled, it crashes into the monitor.
Last edit: Olaf Seibert 2020-07-11
I vote for disabling it again then - such subtle bugs were the exact reason for disabling it by default
Quick reference to bug 1250, where I did find out what went wrong with the VirtualDevices.
I even have something close to a solution, but I don't have the exact conditions quite right yet. Maybe Andre can look it over.