VCC 201 will not run on a WinXP 32 bit system

[BGPierce]

I was informed today that the compiled version I have of VCC 2.0.1 will not run on a WinXP 32 bit system. I have a feeling it was compiled for a 64 bit system only. Since I have yet to update my Win Vista 64 bit system to something Win 7 or beyond, I cannot yet recompile VCC to see if I can resolve the issue.

So Joseph, Gary or David, if you see this, could you compile a copy of the 1.200b branch, making sure it's 32 bit compatible and send me a copy?

[ursine]

Recommenting here for ease of more info on this issue:

I checked the configuration manager to see what platform the solution is targeted for, and it is x86, not x64. So, that is likely fine. My hypothesis would be that the runtime library is missing.

https://www.microsoft.com/en-us/download/details.aspx?id=48145

It could be built into the package and run via the installer.

[BGPierce]

Gary, the binary in question was compiled by Joseph, so the settings in your system wouldn't be the problem. That's why I would like another compile. Could you send me a copy of your compile?

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 Global Moderator for TRS-80/Tandy Color Computer Forums http://www.tandycoco.com/forum/

E-Mail: ooogalapasooo@aol.com

-----Original Message----- From: Gary Coulbourne notifications@github.com To: VCCE/VCC VCC@noreply.github.com Cc: Bill Pierce ooogalapasooo@aol.com Sent: Fri, Oct 2, 2015 8:17 am Subject: Re: [VCC] VCC 201 will not run on a WinXP 32 bit system (#9)

Recommenting here for ease of more info on this issue: I checked the configuration manager to see what platform the solution is targeted for, and it is x86, not x64. So, that is likely fine. My hypothesis would be that the runtime library is missing. https://www.microsoft.com/en-us/download/details.aspx?id=48145 It could be built into the package and run via the installer. — Reply to this email directly or view it on GitHub.

[RobertGault]

I'll try the url for the redist later today. However I do have MS VC++ 2010 x86 Redist KB2565063 installed on my system. That suggests the mentioned above redist may not help.

By the way, VCC2.0.1 is 6 times larger than VCC1.43 already. It will get larger still if you add the redist for VC++. Is this increase really required? How much has been added to the program?

[ursine]

I am at work. I'll try to get a build / binary to you this evening when I am home.

As for the size, I suspect it was compiled in debug rather than release mode so it still has symbols in the build for debugging.

[BGPierce]

Robert, the VCC PDF manual is included in the installer so that's part of the size. As far as the actual binary, the 1.42 binary was 524k, the 2.01 binary is 3.14meg... so it has grown, but only due to the developemnt platform change as nothing new was added... in fact, the becker port code was removed and moved to a DLL module. It's built from 'almost' the exact same sources as 1.42, but in a new developement platform. The MS C++ runtime will only add about 3-7 meg to the package (7 if both 32 & 64 bit are included).

It will probably grow even more as we actually start to add things and make things even more geared to the newer systems. If it's to grow, it has to happen.

The real key will be to get this thing out from under MS Visual Studio and DirectX into a cross-compilable environment and I think it will shrink when we leave MS's 'bloat' behind.

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 Global Moderator for TRS-80/Tandy Color Computer Forums http://www.tandycoco.com/forum/

E-Mail: ooogalapasooo@aol.com

-----Original Message----- From: RobertGault notifications@github.com To: VCCE/VCC VCC@noreply.github.com Cc: Bill Pierce ooogalapasooo@aol.com Sent: Fri, Oct 2, 2015 9:21 am Subject: Re: [VCC] VCC 201 will not run on a WinXP 32 bit system (#9)

I'll try the url for the redist later today. However I do have MS VC++ 2010 x86 Redist KB2565063 installed on my system. That suggests the mentioned above redist may not help. By the way, VCC2.0.1 is 6 times larger than VCC1.43 already. It will get larger still if you add the redist for VC++. Is this increase really required? How much has been added to the program? — Reply to this email directly or view it on GitHub.

[BGPierce]

I just got Gary's build and it runs fine. It also resolves the mouse issue in full screen mode... still no F10 statusbar toggle yet. Robert, I'll send a copy of this build and I'll include the C++ runtime in the zip. And yes, there is a big difference in C++ runtimes for 2010 to 2015... in fact, I bet I've updated both 6 or 7 times each for software that used different SPs of each of them.

[RobertGault]

I installed the redist package referenced above ( VC++ 2015 14.0.23026) and it made no difference at all. Hardly a surprise as the error did not indicate missing dlls but rather not a Win32 application.

[BGPierce]

Gary, Robert tried the build you linked me and it doesn't run under WinXP either or at least on his machine, so we're back to square one then. I will try to download MS VS2015 tonight on my wife's laptop as she's running Win 8. I have to wait until after 2AM as my bandwidth is limited and I get free time from 2AM to 7AM (sucks), and VS2015 is pretty large. Once I get it up and running and get oriented to the interface, I'll llook around and see what I can find. I Also remembered I have an old WinXP laptop that I quit using because the display went out. It has VGA out, so I can hook it to a spare monitor and I'll have a test machine. My only hopes is that it was upgraded to SP3 at some point as it originally was not hooked to the internet. The last usage was my wife using it to play World of Warcraft, so I expect I updated it, or WoW would not have run. VCC should work in WinXp and I see no reason why not, there has to be some setting that is off If all else fails, I can make a VC6 version with all the new changes (very few) just for WinXP. In time VCC will probably outgrow this method, but it's a quick fix for now.

[drencorxeen]

​Also if the new version is anything like how the old one did compiling there were CPU feature options you could turn on and off. Not sure if 2015 has any special CPU options turned on by default.

Also other thing I was thinking, which is only speculation, is that the newer compilers might be set to prevent EXE's from running on the older OS's to force people to upgrade off of their discontinued OS's? I know that is crazy, but just a off the wall idea I was thinking.​

+----------+ |David Ladd| +----------+

On Fri, Oct 2, 2015 at 8:26 PM, Bill Pierce notifications@github.com wrote:

Gary, Robert tried the build you linked me and it doesn't run under WinXP either or at least on his machine, so we're back to square one then. I will try to download MS VS2015 tonight on my wife's laptop as she's running Win 8. I have to wait until after 2AM as my bandwidth is limited and I get free time from 2AM to 7AM (sucks), and VS2015 is pretty large. Once I get it up and running and get oriented to the interface, I'll llook around and see what I can find. I Also remembered I have an old WinXP laptop that I quit using because the display went out. It has VGA out, so I can hook it to a spare monitor and I'll have a test machine. My only hopes is that it was upgraded to SP3 at some point as it originally was not hooked to the internet. The last usage was my wife using it to play World of Warcraft, so I expect I updated it, or WoW would not have run. VCC should work in WinXp and I see no reason why not, there has to be some setting that is off If all else fails, I can make a VC6 version with all the new changes (very few) just for WinXP. In time VCC will probably outgrow this method, but it's a quick fix for now.

— Reply to this email directly or view it on GitHub https://github.com/VCCE/VCC/issues/9#issuecomment-145191598.

[ursine]

Found a blog post addressing this issue. Appears after vs2012. Basically, the old OS support is deprecated and need to specifically set as the toolset.

http://blogs.msdn.com/b/vcblog/archive/2012/06/15/10320645.aspx

[RobertGault]

Gary, That article does seem to be critical but may not be the full story. It implies that if a user installed Visual Studio 2010, then the WinXP user could run programs created with VS 2012. Well I have installed the VC++ redistributables 2005, 2010, and 2015 which ought to take care of the problem but does not. A test would be to compile VCC with VS 2010 or get the latest VS with enhanced multi-targeting to compile VCC.

[BGPierce]

Robert, the problem with what you suggest is opening a bigger can of MS worms. Almost no code written for one version of their MS VS series (which became the .net series), will move to another version without major overhaul. This has been a major complaint ever since they introduced the VS ".net" series. If I'm not mistaken, the "MS VS 2015 Community" release is actually an effort on MS's part to be able to move all the old software forward with less trouble. Also... MS VS 2003 - 2012 (all versions) are VERY expensive software packages. The free "Express' versions were limited in what they could actually do, though they "may" be able to handle the VCC code. BUT... dropping back to one of those compilers, again, would be moving backwards and not forward. The idea was to bring VCC "up to date" with modern machines as problems were starting to appear.

The real question here would be: Do we want to move to another programming platform (which may or already has lost support) to support WinXP (which is no longer supported)...

Or do we move forward, eventually completely alienating WinXp and lower. Do we want to become the next emulator like Jeff Vavasour's or David Keil's that can only be run on an antique machine or in a VM running an antique OS?

Or do we maintain a '2nd' series of VCC with legacy compatibility? I still have MS VC6 and can still compile the original... but how long will my 'newer' machines support MS VS6? I already get warnings that it 'may not run' when I install VS6 on Win Vista... it seems I got an even stronger warning on my wife's Win 8 laptop. Eventually it will respond "This software requires an older version of Windows and can not be run on this system". I have many programs now that give that response and have lost them.

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

[vcc6809]

By default vs2015 doesn't have the toolset to build xp binaries. Theres a way to add it and im working on it now.

On Oct 3, 2015, at 6:05 PM, Bill Pierce notifications@github.com wrote:

Robert, the problem with what you suggest is opening a bigger can of MS worms. Almost no code written for one version of their MS VS series (which became the .net series), will move to another version without major overhaul. This has been a major complaint ever since they introduced the VS ".net" series. If I'm not mistaken, the "MS VS 2015 Community" release is actually an effort on MS's part to be able to move all the old software forward with less trouble. Also... MS VS 2003 - 2012 (all versions) are VERY expensive software packages. The free "Express' versions were limited in what they could actually do, though they "may" be able to handle the VCC code. BUT... dropping back to one of those compilers, again, would be moving backwards and not forward. The idea was to bring VCC "up to date" with modern machines as problems were starting to appear.

The real question here would be: Do we want to move to another programming platform (which may or already has lost support) to support WinXP (which is no longer supported)...

Or do we move forward, eventually completely alienating WinXp and lower. Do we want to become the next emulator like Jeff Vavasour's or David Keil's that can only be run on an antique machine or in a VM running an antique OS?

Or do we maintain a '2nd' series of VCC with legacy compatibility? I still have MS VC6 and can still compile the original... but how long will my 'newer' machines support MS VS6? I already get warnings that it 'may not run' when I install VS6 on Win Vista... it seems I got an even stronger warning on my wife's Win 8 laptop. Eventually it will respond "This software requires an older version of Windows and can not be run on this system". I have many programs now that give that response and have lost them.

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

— Reply to this email directly or view it on GitHub.

[vcc6809]

Got it! I'll post instruction tomorrow how to fix it. I just need to test what i did from a clean machine as i might have certain sdks installed on my normal computer that most people dont have.

On Oct 3, 2015, at 6:05 PM, Bill Pierce notifications@github.com wrote:

Robert, the problem with what you suggest is opening a bigger can of MS worms. Almost no code written for one version of their MS VS series (which became the .net series), will move to another version without major overhaul. This has been a major complaint ever since they introduced the VS ".net" series. If I'm not mistaken, the "MS VS 2015 Community" release is actually an effort on MS's part to be able to move all the old software forward with less trouble. Also... MS VS 2003 - 2012 (all versions) are VERY expensive software packages. The free "Express' versions were limited in what they could actually do, though they "may" be able to handle the VCC code. BUT... dropping back to one of those compilers, again, would be moving backwards and not forward. The idea was to bring VCC "up to date" with modern machines as problems were starting to appear.

The real question here would be: Do we want to move to another programming platform (which may or already has lost support) to support WinXP (which is no longer supported)...

Or do we move forward, eventually completely alienating WinXp and lower. Do we want to become the next emulator like Jeff Vavasour's or David Keil's that can only be run on an antique machine or in a VM running an antique OS?

Or do we maintain a '2nd' series of VCC with legacy compatibility? I still have MS VC6 and can still compile the original... but how long will my 'newer' machines support MS VS6? I already get warnings that it 'may not run' when I install VS6 on Win Vista... it seems I got an even stronger warning on my wife's Win 8 laptop. Eventually it will respond "This software requires an older version of Windows and can not be run on this system". I have many programs now that give that response and have lost them.

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

— Reply to this email directly or view it on GitHub.

[BGPierce]

Joseph, still waiting for a post on your fix for WinXP. If you send me a set of binaries, I can put together a new release package.

[BGPierce]

I've just tried Vcc 2.01b (the binaries Joe sent me last week), on a WinXP SP3 Gateway laptop running a 1.791ghz AMD and so far, it seems to run fine. This same build was crashing on Robert Gault's WinXP. I haven't moved any Coco disks or anything to that computer yet so I can't fully test, but I will in a couple of hours.

[RobertGault]

Bill, Joe sent me a more recent build which in essence works perfectly on my WinXP SP3 32-bit system. The only problem is a minor cosmetic one in the floppy menu when you Eject a disk. You get trash characters after Empty: There is a problem with DW4 access unrelated to the change to VS 2015 and this problem was present in the 1.43 build.

[BGPierce]

Robert, could you send me a copy of that build? I've just moved my VHD images over to the WinXP machine and now that I'm running the normal way I would on my main computer, I'm seeing a slight (but irritating) jitter (maybe waves) on the screen in the menus as well as anything above a 32 column screen. NitrOS9 80 col with black text on white background shows this jitter clearly. I may need to do some updating on my DirectX runtimes. I'll do some checking and see what I find. I'll be running this thing through the ringer tonight.

And Robert, I had no problem with DW4. I'm running DW4 v 4.3.3o. It booted NitrOS9 from my HDBDOS drive, and NOS9 is running fine. I'm running MShell at the moment testing out some things

[BGPierce]

I just tested Joe's new build that he had sent Robert. It works perfectly on WinXP and the 'jitters' seemed to have gone away. The Coco mouse now has full travel again. I added Gary's "fd502.dll" to the binaries and "Overclock Disk Drive" stays persistant from one run to the next. Gary's "fd502.dll" does still suffer the 'jitters', but once Joe merges his changes into branch 2.001b, I have a feeling this will go away as it's not present in Joes new build of that module. The statusbar does still seem to have a little flicker on WinXp, but not on Vista. Since it's updating itself rapidly, this could be a video card issue on my WinXP machine.

Robert, NOS9 is booting fine from an HDBDOS drive. I still can't replicate your problem there. It's booting on both WinXP and Vista.

[vcc6809]

I'll be uploading all my changes tomorrow. Just testing now.

On Oct 13, 2015, at 3:57 AM, Bill Pierce notifications@github.com wrote:

I just tested Joe's new build that he had sent Robert. It works perfectly on WinXP and the 'jitters' seemed to have gone away. The Coco mouse now has full travel again. I added Gary's "fd502.dll" to the binaries and "Overclock Disk Drive" stays persistant from one run to the next. Gary's "fd502.dll" does still suffer the 'jitters', but once Joe merges his changes into branch 2.001b, I have a feeling this will go away as it's not present in Joes new build of that module. The statusbar does still seem to have a little flicker on WinXp, but not on Vista. Since it's updating itself rapidly, this could be a video card issue on my WinXP machine.

Robert, NOS9 is booting fine from an HDBDOS drive. I still can't replicate your problem there. It's booting on both WinXP and Vista.

— Reply to this email directly or view it on GitHub.

[BGPierce]

Joe, I noticed you uploaded your changes. Could you link me a set of binaries. I'll run it through the gauntlet and if all is well, I'll put together the release package. I should have VS2015 installed in the next day or so. I started the download last night, but because of it's size, my limited bandwidth, and slow connection, it will be a day or two before I have the complete package.

[RobertGault]

I think we can close this bug! Joe's latest build works just fine on WinXP 32-bit SSE only. The strange behavior with a .vhd on DW4 where VCC 2.01 failed in some cases but MESS worked was a bad OS9Boot file which I though was good.

[BGPierce]

Robert, I will probably close it today. I tested it on my WinXP laptop... right before I broke the laptop :-( It was running fine and I saw no problems. Then I decide since the laptop's display was busted (I'm using an external LCD), and having the laptop open, the display panel get's in the way of the monitor. So I decided that I would just remove the display... and anyone who has ever done anything internal to a laptop knows to do something simple, you must disassemble the whole thing (50 or 60+ tiny screws). To unplug the display, I had to get to and remove the keyboard. In removing the keyboard, the clip holding the ribbon connector broke. After removing the display & reassembling it, I thought I had the clip back in place, but once I turned the laptop back on, everything worked but the keyboard. Now I have to take it back appart and see if I can repair that ribbon cable clip. I may superglue that sucker in there :-)

But yeah, I'll close this later when I get a chance.

Also... for Joe... What packages did you download for VS 2015? I got it downloaded last night, but I'm not sure if I got all I needed. I'm pretty sure I can update it to what I need, but want to make sure I got it all. I've yet to run it as it's on my wife's computer and she's using it, so it will be tonight before I can try compiling Vcc. Also, is there any external files needed for compilation? Like libraries, DX stuff etc...

[BGPierce]

One more thing... before making a release package of the binaries, Joe mentioned that he forgot to "grey out" the selection for new "hi-res mouse"... which is not working at the moment (experimental). Should we do another build with that greyed out first before releasing? It will save a lot of "This doesn't work" complaints. If so, please recompile and send me a link to the binaries.

[BGPierce]

As Robert stated, I think this issue has been resolved, WinXP support now works, so I am closing it.

[writeson]

Hi, Hope someone is still checking this. :) I'm trying to run the VCC 2.0.1b version on Windows 10, which is a guest OS running in VirtualBox on my Mac Sierra OS. The emulator opens up and as far as I can tell is running, but the screen is completely black. No setting I can change in the configs seems to affect this. I've tried going back to the 1.42 version (which I had running on a Windows guest running in Parallels on a different Mac), but it fails as well.

Any hints how to get it running with screen display in my rather wacky configuration?

Thanks, Doug

[drencorxeen]

On Sun, Apr 30, 2017 at 5:17 PM, Doug Farrell notifications@github.com wrote:

Hi, Hope someone is still checking this. :) I'm trying to run the VCC 2.0.1b version on Windows 10, which is a guest OS running in VirtualBox on my Mac Sierra OS. The emulator opens up and as far as I can tell is running, but the screen is completely black. No setting I can change in the configs seems to affect this. I've tried going back to the 1.42 version (which I had running on a Windows guest running in Parallels on a different Mac), but it fails as well.

​Have you tried using Barry's Wine wrapped VCC bundle that seems to work well on Mac?

Otherwise running VCC inside of Virtual Box with the Guest OS being Windows 10 I think you have to make sure ALL directX components are installed. I can't test this myself as the Mac's I have are old enough where the Intel CPU's do not support Virtualization.

I believe there is a webdirectx setup utility that should still be able to install all the missing DirectX components that are needed by older games.​

Any hints how to get it running with screen display in my rather wacky configuration?

Thanks, Doug

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/VCCE/VCC/issues/9#issuecomment-298261039, or mute the thread https://github.com/notifications/unsubscribe-auth/ANXIiy0Bt9umfC9HN2Ubkuju3cIu6UUJks5r1QiNgaJpZM4GHwM0 .

​

+-----------------------------------------------------------------------+	David Ladd a.k.a. PacoOtaktay a.k.a. Drencor		YouTube: http://www.youtube.com/user/PacoOtaktay		YouTube Gaming Live: https://gaming.youtube.com/user/PacoOtaktay/live		Websites: http://dwladd.com & http://www.theterrorzone.com		G+: https://plus.google.com/113262444659438038657		G+: https://plus.google.com/+DavidLaddPacoOtaktay
Do you have your CoCo 3 yet?

+-----------------------------------------------------------------------+

​