Why does Windows 7 x64 have both of these error messages? Some applications show the former error when attempted to run and others showing the latter error when attempted to run. --------------------------- Unsupported 16-Bit Application --------------------------- The program or feature "\??\Q:\SETUP.EXE" cannot start or run due to incompatibity with 64-bit versions of Windows. Please contact the software vendor to ask if a 64-bit Windows compatible version is available. --------------------------- OK --------------------------- [Window Title] Q:\SETUP.EXE [Content] The version of this file is not compatible with the version of Windows you're running. Check your computer's system information to see whether you need an x86 (32-bit) or x64 (64-bit) version of the program, and then contact the software publisher. [OK] Core i7 920 @ 2.66GHZ | ASUS P6T Mother Board | 6 gig DDR3 1600 RAM | 2x 500g SATA2 HDD | Integrated sound | Gainward Geforce GTX 560Ti "Phantom 2" 2048MB PCI-E (latest drivers) | Windows 7 Home Premium x64 | Thermaltake 750watt Toughpower Power Supply | Thermaltake Armor+ MX case.

64-bit Windows does not support 16-bit executable programs and you should do exactly what the computer prompts you to do; "contact the software publisher, or vendor, for a 32-bit or 64-bit version of the program." You are trying to install a relatively old 61-bit program and you cannot do that directly on 64-bit Windows. You can do it in a Virtual Machine (VM) if you install VM software and an earlier version of Windows such as Windows XP.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I understand that, I do, really. I'm just curious why some 16bit programs cause Windows to show the former error message while other 16bit programs cause Windows to show the latter. What is the point in having 2 error messages for the same issue?Core i7 920 @ 2.66GHZ | ASUS P6T Mother Board | 6 gig DDR3 1600 RAM | 2x 500g SATA2 HDD | Integrated sound | Gainward Geforce GTX 560Ti "Phantom 2" 2048MB PCI-E (latest drivers) | Windows 7 Home Premium x64 | Thermaltake 750watt Toughpower Power Supply | Thermaltake Armor+ MX case.

I personally don't know and won't lose any sleep over it. You would have to get an answer from the Windows programmer(s) responsible for that and get an answer from hime/her/them.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I personally don't know and won't lose any sleep over it. You would have to get an answer from the Windows programmer(s) responsible for that and get an answer from hime/her/them.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I understand that, I do, really. I'm just curious why some 16bit programs cause Windows to show the former error message while other 16bit programs cause Windows to show the latter. What is the point in having 2 error messages for the same issue? Core i7 920 @ 2.66GHZ | ASUS P6T Mother Board | 6 gig DDR3 1600 RAM | 2x 500g SATA2 HDD | Integrated sound | Gainward Geforce GTX 560Ti "Phantom 2" 2048MB PCI-E (latest drivers) | Windows 7 Home Premium x64 | Thermaltake 750watt Toughpower Power Supply | Thermaltake Armor+ MX case. These different error messages could be due to the installation program used to perform the application's setup. Only the developer can give you the best answer to this question. Bye. Luigi Bruno