Timeline for Going from Windows XP to WIndows 8
Current License: CC BY-SA 3.0
22 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jul 2, 2013 at 0:06 | comment | added | Christian Chapman | If you need to keep Windows XP alive you might want to unaccept the answer to keep up interest in your question. | |
Jul 1, 2013 at 21:05 | vote | accept | nate | ||
Jul 1, 2013 at 21:00 | comment | added | nate | @Karan This app is 12 years old. Not sure why it was written like it was, but that is not to point. The point is we need to keep using this app on newer systems. | |
Jul 1, 2013 at 20:46 | history | edited | nate | CC BY-SA 3.0 |
added 78 characters in body
|
Jul 1, 2013 at 20:29 | comment | added | Karan | Aren't there API calls to return paths like those? A well-written app wouldn't be using hard coded paths anyway. | |
Jul 1, 2013 at 20:23 | comment | added | Synetech |
filing system changes like c:\douments and settings, is now c:\users Things like that could be handled by “virtualizing” or “portabilizing” the program with programs like Cameyo or Thinstall.
|
|
Jul 1, 2013 at 20:14 | answer | added | Scott Chamberlain | timeline score: 7 | |
Jul 1, 2013 at 20:09 | comment | added | Devid | @nate stupid me, somehow i did not see that you already mentioned XP Mode. Well i can't think of any other method than Virtual Machine which you are already using. | |
Jul 1, 2013 at 20:00 | history | edited | nate | CC BY-SA 3.0 |
added 10 characters in body
|
Jul 1, 2013 at 19:56 | comment | added | nate | @Devid We have tried XP Mode, and we had technical issue out of it in general, as well as with the app | |
Jul 1, 2013 at 19:54 | comment | added | nate | @ScottChamberlain filing system changes like c:\douments and settings, is now c:\users | |
Jul 1, 2013 at 19:40 | history | tweeted | twitter.com/#!/StackSuper_User/status/351787333911195651 | ||
Jul 1, 2013 at 19:38 | comment | added | Devid | Well you mentioned Virtual Machine, Compatibility Mode and Rewriting the App. I can only think of the Windows XP Mode which is actually not officially supported for Windows 8, but you could still run it, check this here: lifehacker.com/5965889/… | |
Jul 1, 2013 at 19:38 | comment | added | Scott Chamberlain | What API calls are not working, What filesystem changes have effected you, why cant you use the old framework? | |
S Jul 1, 2013 at 19:33 | history | edited | oKtosiTe | CC BY-SA 3.0 |
title correction
|
S Jul 1, 2013 at 19:33 | history | suggested | Devid | CC BY-SA 3.0 |
title correction
|
Jul 1, 2013 at 19:30 | review | Suggested edits | |||
Jul 1, 2013 at 19:33 | |||||
Jul 1, 2013 at 19:30 | history | edited | nate | CC BY-SA 3.0 |
question updated
|
Jul 1, 2013 at 19:23 | history | edited | nate | CC BY-SA 3.0 |
updated question
|
Jul 1, 2013 at 19:21 | comment | added | nate | There are many technical reasons. API calls, filing system changed, new frameworks, etc....... | |
Jul 1, 2013 at 19:15 | comment | added | Ramhound | There isn't any technical reason a VB6 application shouldn't work on Windows 8. Have you tried simply to launch it using the Windows XP comapatability? If that doesn't work youre pretty much limited to a Virtual Machine. | |
Jul 1, 2013 at 19:11 | history | asked | nate | CC BY-SA 3.0 |