[Coco] VCC 2.0.1b Released (New Thread)

[William Mikrut]

As Bill said... I see this a lot.

The current version of Visual Studio produces exe files that are not
compatible with earlier versions of windows.

I have this problem now... I have a Power Edge server running windows
server 2003.  For reasons I am keeping it that way for now.

My resolution was to run VirtualBox with a version of W7 on the 2003
machine.  So many things are just wrong about that... but it works.
On Oct 3, 2015 7:27 PM, "James Ross" <jrosslist at outlook.com> wrote:

> Valid points, Bill.
>
> However, I would say you are a little premature in thinking that a
> standard Win32 / DirectX app (as long as it doesn’t do undocumented calls)
> is NOT going to run on whatever the current version of Windows is anytime
> soon.
>
> Besides isn’t Windows 10 supposed to be the last version of Windows? And
> if this runs on 8.1, I am certain it will run on 10. (There is the matter
> of VCC writing to the .ini files in the Programs Files folder its installed
> in which is not supposed to be writable – that causes a glitch – but that
> is the reason I am actually against an install program for VCC in the first
> place – unzip and create a shortcut, what could be simpler?).
>
> Now the issue of the VS version that is a different matter.  I would not
> attempt to run VS6 on anything greater than XP.  I am all with you on
> having the project files there to build this thing using VS 2015 (and every
> version between that and VS6, for that matter) … I just believe that the
> generated program should continue to be compatible w/ XP. (Not necessarily
> Win 98 – but it would be cool.)
>
> You would never need separate builds for the different versions of
> Windows. You can program it in a manner that if it’s running on a newer
> version it can conditional execute whatever extra capabilities.
>
> How’s that expression “I’m making a mountain out of a molehill”?
>
> One last thing, converting the existing VCC code to be multi-platform is
> not going to be an easy task.  I would say that it would be simpler and
> easier just to start over from scratch and borrowing some of the CPU &
> Hardware emulation code from VCC where appropriate.
>
> Well, back to my cave … :)
>
> ----------------------------------------
> > Date: Sat, 3 Oct 2015 18:36:31 -0400
> > Subject: Re: [Coco] VCC 2.0.1b Released (New Thread)
> >
>
> ... snip ...
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
>