Commodore OS Vision 2.0 Forum

Vic20 and C16 tap and CRT files won't load.

It seems to flash up then crash, trying to load a t64 and not tap according to the echo statements.

D64 load OK

Could you look at the RunCommodore script please?

Thank you.

Have you installed the ROMs?
I am revamping the whole emulation launch to make it configurable for every emulator.
Ask yourself how I would know if a CRT or TAP file belongs to a C64 or a C16 or a Vic20?
IIRC it will probably try to launch a C64 emulator.
The next script will have to utilise folder names as hints.
But it's gonna take some time.

Hi Leo,

Thanks for the reply and for the Commodore OS, runs very nicely on a Toshiba Satellite Z930 10X from years back.

I have the roms installed and all the emulators work.

I can launch the emulator and load the files from the included software manually but when I use the Commodore symbol and select from the folder I have:

C64 - T64, CRT, D64 and RP9 work fine

Vic20 - D64 works but TAP and CRT seem to crash out - maybe I need to edit RunVIC20Keys

C16 - D64 works but PRG does not even respond to a double click - maybe not assoicated with RunC16Keys?

C128 - D64 works fine

Should I be editing the keys scripts in usr/share/commodoreos/scripts? or the RunCommodore in usr/share/commodoreos/config or both?

I am a bit new to Linux but will have a go as I worked with Spanner on PCUAE. I will share the result when working.

You can edit the script if you want. It's all there.
You can't associate file types to two different scripts though and it is clear that it is calling the wrong script (i,e. the C64 one for the VIC).
But recognise that they're going to be deprecated in favour of a new universal runemu command in development.
As I stated before, when the file extensions/types are the same for two machines the only way to differentiate between them is via the folder structure.
runemu will use the folder name as hint as to which emulator to run, and it needn't necessarily be under the provided Commodore folder structure.
I might also mention that what the Commodore logo in the dock will launch in the next version will be an actual system game launcher, negating the need for scripts and script associations.

Hi,

I managed to edit the script to deal with the Vic20 CRT files.

The Vic20 is tricky as there are 5 options for cartridges to load to.

For the moment I have .CRT files loading the majority of $A000 located carts with xvic -crtA. No file renaming needed.

For the Scott Adams Adventures they load at $4000, I renamed these 5 files to .CR4 and load these with xvic -cart4

One other cart is at $6000 so i renames it to .CR6 and load it with xvic -cart6.

The other options are at $2000 and $B000 with -cart2 and -cartB respectively.

I might change these to not needing renaming by using a pattern search in the filename but renaming 6 files was quick last night.

I am working on getting the Vic20 tapes to load next, for some reason these are bombing out and I cannot clearly see why yet.

I think clicking the .tap is loading the RunCommodore script which launches the RunVic20key script but I am not sure as .T64 flashes onto the screen before the crash.

Some sorting of Vic20 games will be needed as there are 3 distinct memory needs of Unexpanded, +3k and the group +8k, +16k +24k, +27k which will all run as full memory expansion.

More later.

Best regards,
Vic20-Ian

I don't think you're understanding me.
Even modifying the VIC script won't help, as the file extension is associated to the C64 script.
You're modifying a script that won't be launched. The CRT association is going to the C64 script.
You would have to detect that(via folder name) in the C64 script and then call the VIC-20 script.

I also think you may be going down the rabbit hole in regard to cartridge memory mapping. Surely that shouldn't matter.

You have brought up an interesting issue however.
Will some VIC-20 cartridges fail on VICE because the system configuration isn't set for the required memory expansion?

Admin: I think this should actually be under the emulation section so I'm moving it.

I have it working.

The Vic20-tap files are now associated with RunCommodore instead of RunC64 and this works. This does not affect the C64 as it is using .T64 files.

The Vic20 CRT files all work using my modified script.

Regarding the memory allocation - you have to understand the Vic20 and VICE more:

If you have an unexpanded game it will not run with 3k, 8k or 16k or more expansion.

If you have a 3k game it won't run on unexpanded, or 8k or more expansion.

If you have an 8k or more expanded game it will run on any configuration with more than 8k.

Regarding the cartidges, they are different to C64. $A000 cartridges are autostart games and need -crtA to load. $4000 games are Scott Adams 5 adventures and need -crt4 to load then Sys32592 to start. The wrong cart setting will not load a cart and be able to run on a Vic20.

I have been running the Vic20 for 40 years, it was a little more complicated than the C64.

I will send you a full script over the weekend, it makes it work nicely from the Commodore menu now. C16 next.

Vic20Ian

Thanks for that. I look forward to seeing what you've come up with.
I learned something new.

I have it working with Grep queries to load:

1. All tapes unexpanded, 3k, 8k, 16k, 24k, 35k

2. All disks 3k, 8k, 16k, 24k, 35k

3. All Cartridages at $2000, $4000, $6000, $A000, $B000

provided the filename containes these strings.

I am testing the odd case that does not load e.g. the Catapult type in game which loads with ,8,1 and it needs to be ,8 then it works.