Virtual Machines WINDOWS XP MODE
-
So we have an application that only runs in Windows XP. Now we are using Virtual Machines that runs XP MODE.
I am wondering if what happen to XP Mode in case Microsoft will stop their support in Windows XP? -
same thing that happens to normal XP, no more security updates.
-
If the app does not require any network access, it's safe, but if it does - really need to replace that application.
-
@Dashrender some users need to have network access .
-
Then in some ways you are out of support. But XP Mode will keep working.
-
@scottalanmiller Do you think it is safe?
-
It's not any safer than using normal XP after April 8.
Flat out do I think it's safe - no. Can you mitigate it, yes, assuming you can isolate them from the internet completely.
-
@Dashrender We are planning to do that. But in some application we are required to use Win XP with internet connection. Oh wow I wish our client will upgrade soon.
-
Maybe stop using XPMode let the application adjust for the user. We'll I guess that's my job. What can you say @joyfano? ahaha
-
@pol.darreljade I guess you can. but we still have online application running in XP.
-
@Joyfano said:
@scottalanmiller Do you think it is safe?
Safe-ish. Keep it behind a firewall, don't use it for internet browsing, keep a good AV on it, don't let the users be admins, etc. it is pretty safe. People are still out there running NT4 and 2000 and they have not been supported for a long time.
-
@scottalanmiller Thanks. We been talking about it lately. We don't really give an admin permission to our users. Lucky we all of our computers are Win7.
All of our virtual XP mode installed in windows 7. -
XP Mode was primarily intended to ease the transition period for users stuck with XP legacy apps. I actually had to use it for a specialized database app for a customer while waiting for a new release a couple of years ago after a new computer was purchased with Win 7 Pro. Wasn't downgradeable so we fired up XP mode with the understanding that it was not to be viewed as a long term solution.
-
I'm going to have to use it myself for the next six months to support a 16 bit app. I've been pushing management to transition to something else (there are tons of options) they just can't seem to make it a priority.
I think once they are left to sharing one computer to access this they might finally break and spend the time (more than money) needed to move to a new solution.
-
Sixteen bit apps. Wow. Haven't seen one if those in forever. You could always just run DOS.
-
@scottalanmiller said:
Sixteen bit apps. Wow. Haven't seen one if those in forever. You could always just run DOS.
It's a windows app. At least as far as I can tell it's 16 bit. When I tried to run it on Windows 7 x64 it just said, NO (I haven't tried in years I forget the real error) Trying it right now on my Windows 8 machine gives me the purple bar - This app can't run on your PC, Close.
-
Wow. What Windows was it for originally?
-
We've had it since Windows 95. it will run on anything up to and including Windows 7 x86, but absolutely won't run on x64 anything. I don't have any Windows 8(.1) x86 machines to try it on.
-
@Dashrender said:
it will run on anything up to and including Windows 7 x86, but absolutely won't run on x64 anything.
SysWOW64. Welcome to the jungle baby. No way to run 16-bit because SysWOW64 doesn't have a 16-bit compiler.
Use DOSBOX, XP Mode, hell even Vmware will "support" a DOS install.
http://partnerweb.vmware.com/GOSIG/MSDOS_6_22_and_Windows_3_1x.html
-
I find it so frustrating when an application is "vital" to a company's business, but they don't want to pay to update it so that it works on a current OS. Maybe not the case here, but a pretty common issue, especially in SMB.
