XP Mode on Windows 10
-
For the simplest current solution, I'd hit eBay and grab XP. I am guessing that XP is getting more expensive these days as people who have a copy know that they control the supply and that no more will ever be available.
-
@scottalanmiller said in XP Mode on Windows 10:
normal software doesn't get locked into an OS version very easily, that normally takes planning or serious incompetence.
I'll take serious incompetence for $2000 Alex.
-
@Dashrender said in XP Mode on Windows 10:
@scottalanmiller said in XP Mode on Windows 10:
normal software doesn't get locked into an OS version very easily, that normally takes planning or serious incompetence.
I'll take serious incompetence for $2000 Alex.
You'd think that, but it is pretty accepted in software circles that you can't reasonably be able to write software and not understand how to avoid this issue. The majority of cases, it is accepted, are that developers see a chance to make something work quickly and easy for minimal effort that then guarantees that the customer will have to keep paying them in the future on a more or less set schedule. Whether most do this or not, lots do. It's a very standard practice and thing to look for where weird, impractical and totally unnecessary "lock in" and "time bomb" features get added to software.
Are there cases where lock in happens for legitimate reasons? Absolutely. Even if you are writing on Python or PHP on CentOS Linux you can run into this, and almost certainly will. But starting from a good place you normally time out with an average lifespan of something like thirty years, not five.
-
When I was programming I assumed that my programs would be upgraded way soon than 20 years. I never once thought "wait a minute, this is 16 bit, what happens when people can only run 64 bit OSes?". And it's not normally a massive job if you keep the source code and the code is well documented. Problems occur when the source code disappears, for whatever reason, and there is no documentation. So you have to re-write the program from scratch.
For all I know, people are going through this exact thing with programs I wrote 20 years ago. I'd like to think that my programs were that awesome that they're still in use, but i doubt it.
-
@scottalanmiller said in XP Mode on Windows 10:
For the simplest current solution, I'd hit eBay and grab XP. I am guessing that XP is getting more expensive these days as people who have a copy know that they control the supply and that no more will ever be available.
Isn't eBay a bit dodgy? What happens when it won't activate and you phone Microsoft and explain that you bought it off eBay? Are they likely to be sympathetic?
-
I understand that companies need to make money, and make it continuously - but to purposefully timebomb with no option other than complete replacement, seems borderline criminal - and frankly, like a lot of credit.
The printer in this case, could have sold an upgrade package for the old printer for a few hundred to a few thousand dollars. the same goes for the CT machine - though granted their hands are a bit more tied by the government.
-
@Carnival-Boy said in XP Mode on Windows 10:
@scottalanmiller said in XP Mode on Windows 10:
For the simplest current solution, I'd hit eBay and grab XP. I am guessing that XP is getting more expensive these days as people who have a copy know that they control the supply and that no more will ever be available.
Isn't eBay a bit dodgy? What happens when it won't activate and you phone Microsoft and explain that you bought it off eBay? Are they likely to be sympathetic?
If you have the certificate of authenticity, then they can't really question you besides to provide proof of purchase (which is the certificate of authenticity).
-
@Carnival-Boy said in XP Mode on Windows 10:
When I was programming I assumed that my programs would be upgraded way soon than 20 years. I never once thought "wait a minute, this is 16 bit, what happens when people can only run 64 bit OSes?". And it's not normally a massive job if you keep the source code and the code is well documented. Problems occur when the source code disappears, for whatever reason, and there is no documentation. So you have to re-write the program from scratch.
For all I know, people are going through this exact thing with programs I wrote 20 years ago. I'd like to think that my programs were that awesome that they're still in use, but i doubt it.
I get it, you write with the assumption that someone is going to be continuously or semi-continuously maintaining it. But building in unnecessary obsolescence is different. That takes work, in most cases. But when writing for the SMB, the assumption basically always has to be that source will be lost and not even understood and that no one will maintain it. Maintaining software is extremely expensive - unless you are the creator of it. Which leads us back to the core problem - that programmers often design software around getting the customer to require them to maintain it.
But.... writing software hasn't required, for business software at least, you to be tied to any bit level going back many decades. And good source is considered to not need documentation, and why would you not have source code unless you were running something compiled and that alone could be (not saying "is") a source of problems. Pretty much any appropriate business language going back a really long time isn't compiled. A few are, but they come with massive caveats that twenty years ago definitely were known and would be included in locking in in most cases. You don't do normal business application programming in things like C, for example, but normally Python or PHP (long ago.) Go back far enough and of course, you did, but that's going really, really far back. Even languages like C# don't get compiled under normal business deployment and that replaces languages that are not compiled. So if you were to be a Microsoft devotee for example and followed the MIcrosoft "way" from the late 1990s or later, you'd be good and not have the issue. So I'm certainly not saying that MS tools or even .NET are a problem, those would work fine if done properly even on the oldest original technology.
-
@Carnival-Boy said in XP Mode on Windows 10:
@scottalanmiller said in XP Mode on Windows 10:
For the simplest current solution, I'd hit eBay and grab XP. I am guessing that XP is getting more expensive these days as people who have a copy know that they control the supply and that no more will ever be available.
Isn't eBay a bit dodgy? What happens when it won't activate and you phone Microsoft and explain that you bought it off eBay? Are they likely to be sympathetic?
XP is a bit dodgy at this point, that's the state of things. Any copy of XP today (that isn't already deployed) is coming from someone selling something used or found in old stock. All current stock sold long ago. eBay is dodgy, but probably the least dodgy option. ANd no, MS is not going to be sympathetic as they provide channels to ensure authenticity of their products and you are now outside of them. If the copy of XP is not genuine, you will be out of luck outside of eBay's fraud controls, but at least eBay has those.
-
@Dashrender said in XP Mode on Windows 10:
I understand that companies need to make money, and make it continuously - but to purposefully timebomb with no option other than complete replacement, seems borderline criminal - and frankly, like a lot of credit.
It should be considered criminal but generally people get it signed off on to protect themselves. And doing it often sounds casual to non-programmers. If you've ever heard someone say something like this "We're going to just use Visual Basic because it is what I know and not going to do some fancy web application but just make a basic desktop application to keep things simple..." you just heard a standard sales pitch for timebombing. They took something enterprise capable (VB) and are using it in a compiled non-enterprise (non-standard enterprise at least) mode and removed the controls that would generally protect the company. Does anything in that statement alone time bomb the code? Nope, but it all sets it up for it. It's using archaic and/or non-standard libraries and such that really does it, but doing legacy apps in a compiled way with less than standard methods or tools makes the development process harder while basically guaranteeing that simple software that could easily last decades will stop being supportable very quickly.
On the other hand, write something in PHP with a web interface and while it might time bomb it is unlikely to do so for an extremely long time, and even if it does the chances are extremely high that fixing it will be quick and easy. It also guarantees that the source code will be available as long as the system is running.
-
@DustinB3403 said in XP Mode on Windows 10:
@Carnival-Boy said in XP Mode on Windows 10:
@scottalanmiller said in XP Mode on Windows 10:
For the simplest current solution, I'd hit eBay and grab XP. I am guessing that XP is getting more expensive these days as people who have a copy know that they control the supply and that no more will ever be available.
Isn't eBay a bit dodgy? What happens when it won't activate and you phone Microsoft and explain that you bought it off eBay? Are they likely to be sympathetic?
If you have the certificate of authenticity, then they can't really question you besides to provide proof of purchase (which is the certificate of authenticity).
That's the part people often refuse to send, though.
-
@scottalanmiller said in XP Mode on Windows 10:
@DustinB3403 said in XP Mode on Windows 10:
@Carnival-Boy said in XP Mode on Windows 10:
@scottalanmiller said in XP Mode on Windows 10:
For the simplest current solution, I'd hit eBay and grab XP. I am guessing that XP is getting more expensive these days as people who have a copy know that they control the supply and that no more will ever be available.
Isn't eBay a bit dodgy? What happens when it won't activate and you phone Microsoft and explain that you bought it off eBay? Are they likely to be sympathetic?
If you have the certificate of authenticity, then they can't really question you besides to provide proof of purchase (which is the certificate of authenticity).
That's the part people often refuse to send, though.
Yeah.... well can't really do anything about that though. It is the proof you own the key. Without it, you're out of compliance with the EULA from microsoft.
-
@DustinB3403 said in XP Mode on Windows 10:
@scottalanmiller said in XP Mode on Windows 10:
@DustinB3403 said in XP Mode on Windows 10:
@Carnival-Boy said in XP Mode on Windows 10:
@scottalanmiller said in XP Mode on Windows 10:
For the simplest current solution, I'd hit eBay and grab XP. I am guessing that XP is getting more expensive these days as people who have a copy know that they control the supply and that no more will ever be available.
Isn't eBay a bit dodgy? What happens when it won't activate and you phone Microsoft and explain that you bought it off eBay? Are they likely to be sympathetic?
If you have the certificate of authenticity, then they can't really question you besides to provide proof of purchase (which is the certificate of authenticity).
That's the part people often refuse to send, though.
Yeah.... well can't really do anything about that though. It is the proof you own the key. Without it, you're out of compliance with the EULA from microsoft.
Yup, understood, but that is the dodgy bit with a lot of resellers. They sell everything but the part that matters.
-
@Carnival-Boy said in XP Mode on Windows 10:
When I was programming I assumed that my programs would be upgraded way soon than 20 years. I never once thought "wait a minute, this is 16 bit, what happens when people can only run 64 bit OSes?". And it's not normally a massive job if you keep the source code and the code is well documented. Problems occur when the source code disappears, for whatever reason, and there is no documentation. So you have to re-write the program from scratch.
For all I know, people are going through this exact thing with programs I wrote 20 years ago. I'd like to think that my programs were that awesome that they're still in use, but i doubt it.
Why do you doubt it? This happens all the time. I've forgotten how many old ass programs I've run into while consulting that had a reliance on DOS, etc. Once a business finds something they can tolerate, they rarely move away from it.
-
@scottalanmiller said in XP Mode on Windows 10:
@Dashrender said in XP Mode on Windows 10:
I understand that companies need to make money, and make it continuously - but to purposefully timebomb with no option other than complete replacement, seems borderline criminal - and frankly, like a lot of credit.
It should be considered criminal but generally people get it signed off on to protect themselves. And doing it often sounds casual to non-programmers. If you've ever heard someone say something like this "We're going to just use Visual Basic because it is what I know and not going to do some fancy web application but just make a basic desktop application to keep things simple..." you just heard a standard sales pitch for timebombing. They took something enterprise capable (VB) and are using it in a compiled non-enterprise (non-standard enterprise at least) mode and removed the controls that would generally protect the company. Does anything in that statement alone time bomb the code? Nope, but it all sets it up for it. It's using archaic and/or non-standard libraries and such that really does it, but doing legacy apps in a compiled way with less than standard methods or tools makes the development process harder while basically guaranteeing that simple software that could easily last decades will stop being supportable very quickly.
On the other hand, write something in PHP with a web interface and while it might time bomb it is unlikely to do so for an extremely long time, and even if it does the chances are extremely high that fixing it will be quick and easy. It also guarantees that the source code will be available as long as the system is running.
I only have one come back to that - often those 'time bombed' desktops apps are easy enough for the non technical, yet dedicated, employee to figure out and get something working.
Not saying this is a good thing, just mentioning that often companies (rightly or wrongly - probably wrongly) look at it and go - heck if Bill can just build that, we don't have to hire NTG to come in and build something for us, something we'd have to pay a lot more than Bill's time for what Bill builds.
Getting over this hump is often difficult if not impossible.
I had this very situation last year. Someone built an Access DB - I was like - WHAT are you doing? you should do that with tools that are more likely forward compatible, etc. Boss didn't care - it works for today and it cost very little versus hiring someone (because they want it NOW, and since I don't know how to build those things now, it would have to be hired out) and paying probably several thousand if not more.
-
@scottalanmiller said in XP Mode on Windows 10:
@DustinB3403 said in XP Mode on Windows 10:
@scottalanmiller said in XP Mode on Windows 10:
@DustinB3403 said in XP Mode on Windows 10:
@Carnival-Boy said in XP Mode on Windows 10:
@scottalanmiller said in XP Mode on Windows 10:
For the simplest current solution, I'd hit eBay and grab XP. I am guessing that XP is getting more expensive these days as people who have a copy know that they control the supply and that no more will ever be available.
Isn't eBay a bit dodgy? What happens when it won't activate and you phone Microsoft and explain that you bought it off eBay? Are they likely to be sympathetic?
If you have the certificate of authenticity, then they can't really question you besides to provide proof of purchase (which is the certificate of authenticity).
That's the part people often refuse to send, though.
Yeah.... well can't really do anything about that though. It is the proof you own the key. Without it, you're out of compliance with the EULA from microsoft.
Yup, understood, but that is the dodgy bit with a lot of resellers. They sell everything but the part that matters.
well if you buy that, that's on you - it's the only part that matters in most cases, I have a dozen XP CDs lying around, the license is another story.
-
@Dashrender said in XP Mode on Windows 10:
@scottalanmiller said in XP Mode on Windows 10:
@Dashrender said in XP Mode on Windows 10:
I understand that companies need to make money, and make it continuously - but to purposefully timebomb with no option other than complete replacement, seems borderline criminal - and frankly, like a lot of credit.
It should be considered criminal but generally people get it signed off on to protect themselves. And doing it often sounds casual to non-programmers. If you've ever heard someone say something like this "We're going to just use Visual Basic because it is what I know and not going to do some fancy web application but just make a basic desktop application to keep things simple..." you just heard a standard sales pitch for timebombing. They took something enterprise capable (VB) and are using it in a compiled non-enterprise (non-standard enterprise at least) mode and removed the controls that would generally protect the company. Does anything in that statement alone time bomb the code? Nope, but it all sets it up for it. It's using archaic and/or non-standard libraries and such that really does it, but doing legacy apps in a compiled way with less than standard methods or tools makes the development process harder while basically guaranteeing that simple software that could easily last decades will stop being supportable very quickly.
On the other hand, write something in PHP with a web interface and while it might time bomb it is unlikely to do so for an extremely long time, and even if it does the chances are extremely high that fixing it will be quick and easy. It also guarantees that the source code will be available as long as the system is running.
I only have one come back to that - often those 'time bombed' desktops apps are easy enough for the non technical, yet dedicated, employee to figure out and get something working.
Not saying this is a good thing, just mentioning that often companies (rightly or wrongly - probably wrongly) look at it and go - heck if Bill can just build that, we don't have to hire NTG to come in and build something for us, something we'd have to pay a lot more than Bill's time for what Bill builds.
Getting over this hump is often difficult if not impossible.
I had this very situation last year. Someone built an Access DB - I was like - WHAT are you doing? you should do that with tools that are more likely forward compatible, etc. Boss didn't care - it works for today and it cost very little versus hiring someone (because they want it NOW, and since I don't know how to build those things now, it would have to be hired out) and paying probably several thousand if not more.
Yes, but YOUR boss specifically doesn't have the business interest of the company in mind, that we know. So that they set the company up for monetary loss isn't surprising. That's not a good indicator. Sure, lots of SMBs act the same, but that doesn't affect what good is.
-
@scottalanmiller said in XP Mode on Windows 10:
Yes, but YOUR boss specifically doesn't have the business interest of the company in mind, that we know. So that they set the company up for monetary loss isn't surprising. That's not a good indicator. Sure, lots of SMBs act the same, but that doesn't affect what good is.
It's still a massive problem to overcome. I'm sure @Jaredbusch's company has come up against this when trying to deploy solutions - I wonder how often he's won/lost?
-
@Dashrender said in XP Mode on Windows 10:
@scottalanmiller said in XP Mode on Windows 10:
Yes, but YOUR boss specifically doesn't have the business interest of the company in mind, that we know. So that they set the company up for monetary loss isn't surprising. That's not a good indicator. Sure, lots of SMBs act the same, but that doesn't affect what good is.
It's still a massive problem to overcome. I'm sure @Jaredbusch's company has come up against this when trying to deploy solutions - I wonder how often he's won/lost?
Jared, like me, tends to talk in money terms. When your boss said she didn't care about doing "The right thing" was she forced to discuss it as a business proposition or just as a technology one? If you present it as "wasting money" and make someone say "I'm authorizing wasting money, just because I want to", things tend to not go the same way. It's not 100% success, but stopping a technology discussion run around and keeping decisions about the business does a LOT to stop people from doing these things.
-
I'm still confused about Microsoft licencing.
Was reading this Spiceworks post by Chris from Microsoft:
https://community.spiceworks.com/how_to/124053-licensing-windows-10-with-virtualization-technologies-how-toand noted this quote:
Q. I need to access Windows XP Pro VMs remotely from my server, how can I license this?
A. Windows SA or Windows VDA would be the license option here from the Windows desktop OS perspective. However, you would already need to have access to the Windows XP Pro OS as the Microsoft Volume License Service Center (VLSC) only provides (n-2) Windows rights to Windows 7. You are licensed to run Windows XP Pro or previous versions, Microsoft just no longer provides the media/keys.Does this mean SA will give me a licence to install an XP VM. People on this ML thread seem to indicate that it is impossible to licence XP now, by any means.
What am I missing here?
