| T O P I C R E V I E W |
| foxmuldr |
Posted - Aug 05 2014 : 08:35:24 AM
I've had occasion recently to switch to Windows 2000 for a software project and I noticed the latest versions of VAX do not support that older OS. It fails with an inetaddr function not found in ws2_32.dll. I had to revert back to an older VAX version (I just randomly chose one, and 1837 worked).
I was wondering if you could code around that issue to allow the current versions to still work with Windows 2000?
-----
You could write the module that references it as a plugin DLL that, if on Windows 2000, uses the compatible version, but if on a newer OS uses the current version. You can see how to write plugin DLLs here if needed:
The sound plugin itself:
https://github.com/RickCHodgin/libsf/tree/master/vvm/core/plugins/sound
The main code which loads the plugin:
https://github.com/RickCHodgin/libsf/blob/master/vvm/core/oss/oss_plugins.cpp
The structure which holds the interface to the plugin:
https://github.com/RickCHodgin/libsf/blob/master/vvm/core/common/common_oss_plugins.h
Basically you call the structure member after the structure member is populated by the loader. If the plugin wasn't found, you have it go to a placeholder function which simply returns. |
| 7 L A T E S T R E P L I E S (Newest First) |
| feline |
Posted - Aug 12 2014 : 2:22:32 PM
Sadly its not going to be quite that simple, since VA is not a pure C++ product. We made the decision a while ago to stop supporting Windows 2000, and are not going to try and reintroduce support at this stage. We already have enough to do dealing with all of the OS's and IDE's that we support, and the different combinations and quirks this introduces. |
| foxmuldr |
Posted - Aug 12 2014 : 1:57:34 PM
It may be as simple as going in to the solution properties, right-clicking and choosing the C/C++ compiler toolset from a prior generation, rather than the latest. If you'd like to try ... you have my email and I can test it. Or you can create a Win2K VM and test it. :-)
If you do, I'll buy my renewal license before the upcoming October renewal date. :-)
|
| feline |
Posted - Aug 11 2014 : 7:35:02 PM
While this is true, we do try and monitor what most of our users are doing. Sadly, it would be very unwise to connect a Windows 2000 machine to the internet, and its not to wise to connect a Windows XP machine to the internet. Like any organisation with finite resources, we need to choose to focus our resources where they will do the most good for the greatest number of people. |
| foxmuldr |
Posted - Aug 11 2014 : 6:28:20 PM
I'm currently working on developing Visual FreePro, an almost 100% drop-in replacement for Visual FoxPro, because Microsoft decided to terminate support of this truly capable product. There are some times you should do things simply because they're the right things to do, and not because other people are doing them as well.
Best regards,
Rick C. Hodgin
|
| feline |
Posted - Aug 08 2014 : 12:59:55 AM
Unfortunately Windows 2000 is now a very old OS, and I cannot remember the last time we had anyone else report working with this OS. We need to prioritise our resources, and you can still use older versions of VA that still support Windows 2000. |
| foxmuldr |
Posted - Aug 07 2014 : 11:24:53 PM
That's disappointing. You have one dependency preventing it from working.
|
| feline |
Posted - Aug 05 2014 : 10:53:40 PM
Unfortunately no, we don't have any plans to support Windows 2000 for newer versions of VA. Remember that Microsoft has recently ended all support for Windows XP, and that is more recent than Windows 2000.
Like all companies we have finite resources, so we need to focus them where they are going to have the most benefit for the greatest number of people. |
