[Coco] VCC 2.0.2 with full 6309 emulation. Runs Nitros9 EOU 6309.

Mon Dec 9 00:00:33 EST 2019

Walter, the 1.0.2b was a typo LOL
Personally, I want to see VCC running with all the functionality as Mame. I hate Mame for it's EVER CHANGING versions where you get them to fix something and an arcade programmer breaks 3 more things. Anything they do for the 6809 arcade emus, affects the Coco emu directly.

There is no one but me working on VCC and I know very little C++ ( but I'm learning). I just mess around with the cosmetics more than anything. There are a couple of others who were working on it, and show up every-so-often and say they're going to do something, then disappear again.

Here's some thing that (to me) need to be done...
Fix the hsync so that Pop Star Pilot runs correctly.

Add a 2nd drive to harddisk.dll

Have each function that uses a load screen to have it's own file path saved in the ini (including individual drives). Currently, the last place you loaded a cass, is the next place you'll see when trying to load a disk and so on, and so on...

Add a "Keymap editor" to do custom keyboard layouts. I actually started this but have gotten no further than to design the dialog box. LOL

Fix the artifact colors so the gamers will stop complaining.

Oh, and as far as I know, there's no other dependencies that are needed once it's compiled. Just the VCC.exe and the plugin DLLs. I have never had any problems with that. I think by not including the XP compatibility, you're dropping some of the core dependencies. It WAS written that long ago LOL

-----Original Message-----
From: Walter Zambotti <zambotti at iinet.net.au>
To: 'CoCoList for Color Computer Enthusiasts' <coco at maltedmedia.com>
Sent: Sun, Dec 8, 2019 10:33 pm
Subject: Re: [Coco] VCC 2.0.2 with full 6309 emulation. Runs Nitros9 EOU 6309.

Bill

For my build I used the VCC2.01(B) source.

I did move the MemWrite32/MemRead32 functions from hd6309.c to tccmmu1014.c. however I have now moved them back into hd6309.c and for me it still works.

I placed the updated hd6309.c on the google drive.  Fingers crossed I haven't changed anything else.

As for the VCC 1.0.2b version that you mentioned.  I'm not familiar with that one so can't assist much.

The biggest problem I am having is I can't determine what library dependencies are required to correctly package VCC so that it will work on other PCs.

However I'm not sure I want to become the maintainer for VCC (or even some off shoot of it).  My exercise here was to try and deliver an updated 6309 cpu emulator to whoever is maintaining VCC so they could incorporate it.

Naturally I am willing to help to get it going.  

I am fairly certain we are all clever guys and together we can get the new 6309 component working in the official VCC.

If anyone has a working VCC dev environment that can create an installer setup exe, can you please look through your project/solution properties and identify what additional dependencies are required (and let me know).

Regards

Walter

-----Original Message-----
From: Coco [mailto:coco-bounces at maltedmedia.com] On Behalf Of Bill Pierce via Coco
Sent: Sunday, 8 December 2019 9:23 PM
To: coco at maltedmedia.com
Cc: Bill Pierce <ooogalapasooo at aol.com>
Subject: Re: [Coco] VCC 2.0.2 with full 6309 emulation. Runs Nitros9 EOU 6309.

Walter, that is not the case. I have VS2015 installed, and I still get no dialogs on disk, vhd, cass, & external rom loads.

Also, I just tried dropping your h6309.c & h6309.h into my 2.0.1b sln.
7 errors & 4 warnings.
Errors & warnings are all the same,
Error: "MemWrite32":identifier not found.
Warning: "=":conversion from 'short' to 'unsigned char', possible loss of data

You have definately changed something somewhere else to get this result. I did notice you commented out MemWrite32 in h6309.c, and I know that's used throughout VCC. Without knowing what's been done elsewhere, it can't be fixed.

You stated if having problems, build it on my system... How? the only source you provided was h6309.c. It WILL NOT work with 1.0.2b sources. I have 1.0.2b and it builds with no errors. Your changes are to vast to just drop h6309.c into it.

-----Original Message-----
From: Walter Zambotti <zambotti at iinet.net.au>
To: coco <coco at maltedmedia.com>
Sent: Sun, Dec 8, 2019 8:00 am
Subject: Re: [Coco] VCC 2.0.2 with full 6309 emulation. Runs Nitros9 EOU 6309.

I think I know what might be happening here with 2.0.2 not working on some systems.

It sounds like a missing dependency/library.

I suspect it is workingt for people who have visual studio installed.

I will try and make an installation package. That might help! The installer should identify all dependencies and included them in the package.

Hold tight!

Walter

>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> https://pairlist5.pair.net/mailman/listinfo/coco
>>
>

--
Coco mailing list
Coco at maltedmedia.com
https://pairlist5.pair.net/mailman/listinfo/coco

--
Coco mailing list
Coco at maltedmedia.com
https://pairlist5.pair.net/mailman/listinfo/coco

-- 
Coco mailing list
Coco at maltedmedia.com
https://pairlist5.pair.net/mailman/listinfo/coco