Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

11
  • 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.
    – Ramhound
    Commented Jul 1, 2013 at 19:15
  • There are many technical reasons. API calls, filing system changed, new frameworks, etc.......
    – nate
    Commented Jul 1, 2013 at 19:21
  • What API calls are not working, What filesystem changes have effected you, why cant you use the old framework? Commented Jul 1, 2013 at 19:38
  • 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/…
    – Devid
    Commented Jul 1, 2013 at 19:38
  • 3
    Aren't there API calls to return paths like those? A well-written app wouldn't be using hard coded paths anyway.
    – Karan
    Commented Jul 1, 2013 at 20:29