Forums
New posts
Search forums
What's new
New posts
New media
New media comments
New profile posts
Latest activity
Media
New media
New comments
Search media
Members
Current visitors
New profile posts
Search profile posts
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Forums
Learning
Computers and Software
Unexpected upgrades
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="dslater" data-source="post: 366871" data-attributes="member: 32537"><p>That sounds to me like your legacy is old 16-bit DOS/Windows 3.1 software. If that's the case, then x64 Windows won't run it. Instead, you'll get this error message when you try to run it:</p><p></p><p>[ATTACH]118345[/ATTACH]</p><p></p><p>However, there is still an option for you. x64 Windows 7 includes a feature "XP-Mode". XP-Mode runs a 32-bit version of Windows XP inside a virtual machine. (Note: since Microsoft has now dis-continued support for Windows XP, they may have changed XP-mode to run 32-bit Windows 7 and changed the name too). </p><p></p><p>Even if your old software is 32-bit, you may still run into trouble as early on, there were meny 32-bit programs that still used a 16-bit installer. In that case, even though the software would run, the installer wouldn't, preventing you from installing the software. Again, you can use XP-Mode to work around this. You can also take a look at the installation disk to see if you can manually install the software. Back in the day, many of those old installers did nothing more that copy files from your installation media to the destination directory.</p><p></p><p> XP-mode brings along its own issues. It is a complete XP installation that is installed on a sizable virtual disk, and needs 2G or more of RAM when it's running. So, it's a pretty resource intensive way to run your old software.</p><p></p><p>If your legacy software is indeed DOS based, then there's a chance you can use a free product call <a href="http://www.dosbox.com/" target="_blank">DosBOX</a> to run it. DosBOX is a DOS emulator written to support old DOS games. However, I've found it to be quite good at running most old DOS applications. It is much much less resource intensive than XP-mode.</p><p></p><p>Here's a way to check if your old software is 16-bit on your current 32-bit system. </p><p> </p><p> 1) exit all your legacy applications.</p><p> 2) start the task manager.</p><p> 3) in task manager, go to the Processes tab look and kill for any process named ntvdm.exe</p><p> 4) With Task Manager still up, start your legacy program.</p><p> 5) If your legacy program is a 16-bit application, then a new ntvdm.exe process will start when you start your legacy program. This is because 16-bit applications are run inside of ntvdm.exe when you're on 32-bit windows.</p></blockquote><p></p>
[QUOTE="dslater, post: 366871, member: 32537"] That sounds to me like your legacy is old 16-bit DOS/Windows 3.1 software. If that's the case, then x64 Windows won't run it. Instead, you'll get this error message when you try to run it: [ATTACH=CONFIG]118345._xfImport[/ATTACH] However, there is still an option for you. x64 Windows 7 includes a feature "XP-Mode". XP-Mode runs a 32-bit version of Windows XP inside a virtual machine. (Note: since Microsoft has now dis-continued support for Windows XP, they may have changed XP-mode to run 32-bit Windows 7 and changed the name too). Even if your old software is 32-bit, you may still run into trouble as early on, there were meny 32-bit programs that still used a 16-bit installer. In that case, even though the software would run, the installer wouldn't, preventing you from installing the software. Again, you can use XP-Mode to work around this. You can also take a look at the installation disk to see if you can manually install the software. Back in the day, many of those old installers did nothing more that copy files from your installation media to the destination directory. XP-mode brings along its own issues. It is a complete XP installation that is installed on a sizable virtual disk, and needs 2G or more of RAM when it's running. So, it's a pretty resource intensive way to run your old software. If your legacy software is indeed DOS based, then there's a chance you can use a free product call [URL="http://www.dosbox.com/"]DosBOX[/URL] to run it. DosBOX is a DOS emulator written to support old DOS games. However, I've found it to be quite good at running most old DOS applications. It is much much less resource intensive than XP-mode. Here's a way to check if your old software is 16-bit on your current 32-bit system. 1) exit all your legacy applications. 2) start the task manager. 3) in task manager, go to the Processes tab look and kill for any process named ntvdm.exe 4) With Task Manager still up, start your legacy program. 5) If your legacy program is a 16-bit application, then a new ntvdm.exe process will start when you start your legacy program. This is because 16-bit applications are run inside of ntvdm.exe when you're on 32-bit windows. [/QUOTE]
Verification
Post reply
Forums
Learning
Computers and Software
Unexpected upgrades
Top
