| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 48089 | 2004-08-13 23:50:00 | Emulate Windows 2000 | M@TT (149) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 261312 | 2004-08-14 06:15:00 | Ok, thought so. We managed to get office in 2002 version (compat with 98se) but Frontpage is 2003 version, maybe its time to start saving :) | M@TT (149) | ||
| 261313 | 2004-08-14 10:14:00 | > running setver to confuse a Microsoft product? I > doubt it :D Setver will not actually confuse a Microsoft product. Setver may confuse an application to run under a different MS O/S for what it was designed for in my opinion. For example an application written for MSDos may be written for MSDos 3.3 and actually checks the version of the operating system before it will install or run. A SETVER command in the autoexec.bat or config.sys file ( not 100% sure which ) will allow the application to run. Last time I had to do this was with Win98 and a MSDOS program for a business. If you want the name of the application I can tell you. Even today with WinXP you can check compatibility for a particular application. You can make a particular application be compatible under WinXP to run as compatible with Win95 and Win98. There are still applications I can't get to run under WinXP but there are others I can. SETVER usually changes the O/S version to ensure the application will do its thing. It reports to the application a different O/S to what you actually run. Just my opinion of course. I don't think that SETVER will get Office 2003 to run on MSDOS 3.3. SETVER was always reporting a backward compatible O/S to the application. Sorry for my inferior help. |
Elephant (599) | ||
| 1 2 | |||||