COS 3.0 Emulator Config Help Needed

[LeoNigro]

Then it must be something directly related to the beta 6. I'll check it out soon.

[Ushgarak]

I'm sorry- this one is on me, though in my defence I wouldn't have previously thought it was an issue!

Looking at the logs suggested the issue was the file wasn't being found properly by the loader. Turns out that's my fault. I created a shortcut straight to my c64 games to stop me having to navigate back to the folder each time. But opening the t64 games from the shortcut route seems to confuse the loader! When I go in through 'Commodore's Home', the t64 files run fine. I don't know why that only affects t64 files, though the logs suggest that the way the files are found for t64 and d64 files is different.

Sorry about that.

[LeoNigro]

if you look at the home folder, which is the default folder where most emulators will send you, there is already a symbolic link called "ClassicSystem".
I removed the space from COS2 because some emulators where having a conniption over the space.
Also, don't include a "." (period) in any folders in your path to a ROM, or the universal emulation launcher will likely fail.
Currently all Commodore emulation is covered by the universal emulation launcher triggered by the LOAD command.
I hope to extend this to other emulators, but you will have to associate their extension to the LOAD command.
Obviously if I've missed a Commodore file extension, you should associate it with the LOAD command.
There may be an issue running some VIC-20 ROMs....with a fix someone made not having been implemented yet.
The status of the Universal ROM Launcher can followed in the first post of this thread.

The above script gets updated every COS update automatically, so if you make a change to support a different emulator post it here and I'll include it for everyone's benefit.