[Coco] Basic09 6309 version

[James Ross]

Got it bill ... 

I will too download the current "VCC-1.200b" /w NO changes -- as is -- and build it using VS2015 which is installed on my DELL W10 notebook.  I will test that and see how it goes.   I thought I had done this once already and I had the menu issue (perhaps I am mistaken) ... which that issue is not there in the binaries.  But I will do it again and double check everything. If what your saying is TRUE ... then I've got some funky stuff going on!!  

Let us know what your results are and I'll report on mine. 

Thanks for the reply's .... 

James

________________________________________
From: Coco <coco-bounces at maltedmedia.com> on behalf of Bill Pierce via Coco <coco at maltedmedia.com>
Sent: Friday, May 26, 2017 11:38 PM
To: coco at maltedmedia.com
Cc: Bill Pierce
Subject: Re: [Coco] Basic09 6309 version

James, just to clarify, the current release was built directly from the default branch "VCC-1.200b". No changes have been made to the code since that build. One thing to remember in VS2015, is to make sure you have the "Legacy Support" package (or what ever it's called), which adds support for WinXP & Vista (also DX9). I don't think much else is required othter than the standard C/C++ package.
When I get a chance, which won't be until monday, I will do a build and see what happens. I was swapping Windows versions for dual boot and haven't reinstalled VS2015 on my Win7 boot since then, so I have to do the install and won't be free to do it until sunday evening or monday (I run Karaoke in a bar on the weekends).





Bill Pierce
"Charlie stole the handle, and the train it won't stop going, no way to slow down!" - Ian Anderson - Jethro Tull

My Music from the Tandy/Radio Shack Color Computer 2 & 3
https://sites.google.com/site/dabarnstudio/
Co-Contributor, Co-Editor for CocoPedia
http://www.cocopedia.com/wiki/index.php/Main_Page

E-Mail: ooogalapasooo at aol.com





-----Original Message-----
From: Bill Pierce via Coco <coco at maltedmedia.com>
To: coco <coco at maltedmedia.com>
Cc: Bill Pierce <ooogalapasooo at aol.com>
Sent: Fri, May 26, 2017 7:23 pm
Subject: Re: [Coco] Basic09 6309 version

James, the release version of VCC is built from that branch (I built it), which I use all the time (over a year). I didn't build your sources, I downloaded the exec from the link you provided.The becker.dll works in the current release (default branch)  Bill Pierce"Charlie stole the handle, and the train it won't stop going, no way to slow down!" - Ian Anderson - Jethro TullMy Music from the Tandy/Radio Shack Color Computer 2 & 3https://sites.google.com/site/dabarnstudio/Co-Contributor, Co-Editor for CocoPediahttp://www.cocopedia.com/wiki/index.php/Main_PageE-Mail: ooogalapasooo at aol.com  -----Original Message-----From: James Ross <jrosslist at outlook.com>To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>Sent: Fri, May 26, 2017 3:31 pmSubject: Re: [Coco] Basic09 6309 versionBill Pierce Wrote:> James, just tried you build of VCC over one of my "regular" installations and > right off the bat, the "becker.dll" does not load. It reports "Invalid Module".Bummer … I had not tried loading the Becker DLL since I have not learned how to use and setup DriveWire.  I just tried loading the DLL through an MPI slot and sure enough, I get the same error. I just now quickly tried it under VS2013 in Debug mode and I get this error Unhandled exception at 0x10001F33 in VCC.exe: 0xC0000005: Access violation executing location 0x10001F33.So... Probably a stray pointer. > Which branch did you build this from?I started w/ the default branch. It’s the branch (VCC-1.200b) that comes up automatically when you go to https://github.com/VCCE/VCC. SO … if someone were to (I will late tonight) build that exact branch (just clone/download from that default branch) we should get the exact same error w/o any of my changes. That default branch and the code zip file (https://github.com/VCCE/VCC/archive/v2.0.1b-edit.zip) from the “VCC Color Computer 3 Emulator w/Becker Port v 2.0.1b (final [edit]) release” page are precisely the same (even though you have two different version #’s 1.200b &  v2.0.1b – I just figured that was done just to distinguish it as the new version) I was under the impression that this WAS the code that created the VCC.2.01b-final.zip release. But perhaps I am mistaken?? It appeared to me that all of the “recent” stuff was indeed there (keyboard changes, etc…) that I recall you talking about.   However, I do wonder if the code that created the current release executables is indeed NOT the current code that is there.  Did you compile/build those yourself Bill? For example I was also getting a problem where the drop down “insert” menu items would not bring the load file dialog window – which I fixed.  SO… the question is then – do you have the code that created the binaries in the current release (https://github.com/VCCE/VCC/releases/download/v2.0.1b-edit/VCC.2.01b-final.zip)If you do, could you send that to me? Or make downloadable from somewhere?  If not, I’ll just have the debug the problems w/ where I started from and go from there. I’ll figure out the Becker issue – but it would be nice to know that I was starting w/ the last good source of it. Thanks James-- Coco mailing listCoco at maltedmedia.comhttps://pairlist5.pair.net/mailman/listinfo/coco-- Coco mailing listCoco at maltedmedia.comhttps://pairlist5.pair.net/mailman/listinfo/coco

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