[Coco] Basic09 6309 version
Wayne Campbell
asa.rand at gmail.com
Sat Jun 3 01:33:46 EDT 2017
A very interesting update. I had just gotten home when I posted the last
message here, and had not yet ran VCC. When I did, I was surprised. It
remembered it's last size settings (which it never did before), and there
was no alert! I have restarted my computer and launched it again, and still
no alert! I tried full screen mode and it didn't mess with my other
windows. The aspect ratio was correct also. When I tried the maximize
button, though, it was stretched across the width of my screen, so the
aspect ratio still doesn't work correctly in maximized mode.
On Fri, Jun 2, 2017 at 9:06 PM, Wayne Campbell <asa.rand at gmail.com> wrote:
> I was never concerned about it containing viruses or malware. I just never
> had the system react to VCC that way before, and I was wondering what I
> could do to get that alert to stop being issued.
>
>
> On Thu, Jun 1, 2017 at 11:55 PM, James Ross <jrosslist at outlook.com> wrote:
>
>> You installed it right. It's either windows defender or some other
>> virus/malware program saying this simply because it’s not a known
>> file/program in their databases, and it’s not digitally signed.
>>
>> Well, I can guarantee that the files are safe. (Well, technically
>> speaking, safe from purposely harmful or privacy invading code, that is).
>> Most modern OS’s are generally safe from bugs – but there’s always that
>> disclaimer about bugs right?
>>
>> If it makes you (or anyone else) feel better, you can scan the whole zip
>> file or each individual file at virustotal.com (a subsidiary of Google)
>> which scans using all the major virus/malware checkers and then some. I
>> already checked to make sure there was not a false positive, which can
>> happen.
>>
>> I can look at getting (I think I'd have to buy it) a digital signature at
>> some point. Until then the only option would be to learn how to disable
>> that warning in this instance.
>>
>> > The first two times I ran it I got a small dialog box saying
>> > invalid module,
>>
>> Hmmm, that is interesting, and the fact that it stopped … I’m not getting
>> that. Bill didn’t mention getting that either. However, I wonder, if
>> you had the becker module being loaded before you tried it, in your *.ini
>> file, and it could be that after the second try the ini file got
>> overwritten w/o the becker module? (just a guess at this stage) because we
>> know for a fact that the Becker module is giving that error (which I am
>> working on figuring out)
>>
>> James
>>
>> ________________________________________
>> From: Coco <coco-bounces at maltedmedia.com> on behalf of Wayne Campbell <
>> asa.rand at gmail.com>
>> Subject: Re: [Coco] Basic09 6309 version
>>
>> I just installed the files. The MOD problem is definitely solved, but now
>> every time I launch VCC I get a notice that Windows stopped a program from
>> running because of unknown author and possibly unsafe. I have to override
>> it to continue. I never had to do this before with VCC. The first two
>> times
>> I ran it I got a small dialog box saying invalid module, but that stopped
>> after the second attempt. I don't know what caused it.
>>
>> I selected all of the files in the zip archive, copied them, and pasted
>> them into the VCC folder. The original files were overwritten, so none of
>> the original files (of the ones copied) exist in the folder.
>>
>>
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> https://pairlist5.pair.net/mailman/listinfo/coco
>>
>
>
>
> --
> Wayne
>
> The Structure of I-Code
> http://www.cocopedia.com/wiki/index.php/The_Structure_of_I-Code
>
> decode
> http://cococoding.com/wayne/
>
--
Wayne
The Structure of I-Code
http://www.cocopedia.com/wiki/index.php/The_Structure_of_I-Code
decode
http://cococoding.com/wayne/
More information about the Coco
mailing list