VC6 in a 64 bit OS
-
XP Mode works fine for me.
Join the cool kids - Come fold with us[^] "Program as if the technical support department is full of serial killers and they know your home address" - Ray Cassick Jr., RIP
-
I apologize, I'm a bit daft. Are you saying that VC6 works without a hitch in Windows 7 64 bit if it is running in XP mode? I thought there were all sorts of limitations and incompatibilities in the WoW64 subsystem.
It creates a virtual 32 bit PC - essentially they have created a virtual PC with XP SP3 on it, you can even assign USB devices to it.
Join the cool kids - Come fold with us[^] "Program as if the technical support department is full of serial killers and they know your home address" - Ray Cassick Jr., RIP
-
It creates a virtual 32 bit PC - essentially they have created a virtual PC with XP SP3 on it, you can even assign USB devices to it.
Join the cool kids - Come fold with us[^] "Program as if the technical support department is full of serial killers and they know your home address" - Ray Cassick Jr., RIP
This is great news. I thought there would be all kinds of problems installing service packs and extensions/add-ins, debugging, etc. Thank you very much for taking the time to help me out.
-
Next week, I will get rid off my last 32 bit system. Windows 7 64 bit from now on. I've got some projects that require the good old VC6. Two questions for those of you in a situation similar to mine: 1. Which virtualization software do you prefer? 2. How do you handle versioning and backup. What I mean is, can you have repositories and backups outside of the virtual machine yet referenced from within? Please forgive my ignorance on the subject. Thank you, good folk.
It's not an officially supported configuration but I've found I can install and compile/edit natively on the Win 7 system without having to run it in XP mode or a VM. You may not need to run it virtualised or in XP mode. I managed to install it on all the Win 7 x64 Ultimate systems I use. During installation it will warn of incompatibilities several times. Elect to ignore these and install - it seems to work fine. I build and code on some legacy VC 6 stuff with no problems on Win 7 this way. Mike
-
It creates a virtual 32 bit PC - essentially they have created a virtual PC with XP SP3 on it, you can even assign USB devices to it.
Join the cool kids - Come fold with us[^] "Program as if the technical support department is full of serial killers and they know your home address" - Ray Cassick Jr., RIP
-
This is great news. I thought there would be all kinds of problems installing service packs and extensions/add-ins, debugging, etc. Thank you very much for taking the time to help me out.
-
It's not an officially supported configuration but I've found I can install and compile/edit natively on the Win 7 system without having to run it in XP mode or a VM. You may not need to run it virtualised or in XP mode. I managed to install it on all the Win 7 x64 Ultimate systems I use. During installation it will warn of incompatibilities several times. Elect to ignore these and install - it seems to work fine. I build and code on some legacy VC 6 stuff with no problems on Win 7 this way. Mike
-
I've installed SP6 for VC 6, but not the 2003 Platform SDK (I already use VS 2003,2008, 2010 as well as 6 for the various projects/products I work on). So I can vouch for VC6SP6 on Win7 x64, but can't comment on 2003 SDK (I imagine that'll work though because VS 2003 is basically the 2003 SDK plus IDE). Mike
-
I've installed SP6 for VC 6, but not the 2003 Platform SDK (I already use VS 2003,2008, 2010 as well as 6 for the various projects/products I work on). So I can vouch for VC6SP6 on Win7 x64, but can't comment on 2003 SDK (I imagine that'll work though because VS 2003 is basically the 2003 SDK plus IDE). Mike
-
Next week, I will get rid off my last 32 bit system. Windows 7 64 bit from now on. I've got some projects that require the good old VC6. Two questions for those of you in a situation similar to mine: 1. Which virtualization software do you prefer? 2. How do you handle versioning and backup. What I mean is, can you have repositories and backups outside of the virtual machine yet referenced from within? Please forgive my ignorance on the subject. Thank you, good folk.
Its just works in Win 7 Professional. Using it for the past 8 months. I had some issues with ActiveX controls. Running VC6 in permanent administrative mode solved the issue.
...selvan
-
Next week, I will get rid off my last 32 bit system. Windows 7 64 bit from now on. I've got some projects that require the good old VC6. Two questions for those of you in a situation similar to mine: 1. Which virtualization software do you prefer? 2. How do you handle versioning and backup. What I mean is, can you have repositories and backups outside of the virtual machine yet referenced from within? Please forgive my ignorance on the subject. Thank you, good folk.
Windows 7-64 bit is famous for it's backward compatibility for most of the 32 bit programs. You can choose the compatibility options under the program properties. In most of the cases, it should work fine. Why don't you consider upgrading to the latest version because the product isn't supported anymore. You're forced for an upgrade by Microsoft. One day or other, you will have to take all the pain to port the code.
-Sarath.
My blog - Reflections of My Thoughts
Rate the answers and close your posts if it's answered
-
Windows 7-64 bit is famous for it's backward compatibility for most of the 32 bit programs. You can choose the compatibility options under the program properties. In most of the cases, it should work fine. Why don't you consider upgrading to the latest version because the product isn't supported anymore. You're forced for an upgrade by Microsoft. One day or other, you will have to take all the pain to port the code.
-Sarath.
My blog - Reflections of My Thoughts
Rate the answers and close your posts if it's answered
A slightly amusing (once you find the workaround) problem with 32-bit on 64-bit is that vbs scripts (which I sometimes use for simple scheduled database imports) don't work in 64-bit Windows if you try to call a 32-bit ActiveX DLL (such as a legacy thing written i VB6), because they are run by a 64-bit scripting engine. But... once you figure it out, you can launch the VBS file through a CMD file that launches the 32-bit version of the script engine (which lives in the 32-bit support folder)... works like a charm.
-
This is great news. I thought there would be all kinds of problems installing service packs and extensions/add-ins, debugging, etc. Thank you very much for taking the time to help me out.
You might run into problems if you have any 16 bit components on your projects. It won't work