setup.exe - ntvdm.exe fails preventing Office Install cascade unde b-seven-co 14.08.2006 15:06:02 I have a retail Office 97 office Pro, a retail Win 2K Pro Upgrade and a Retail WinXP Office pro upgrade. I want to install office 97 on my Windows XP pro system, by installing Office 97, and then the Office 2K and Office XP upgrades. Infortunately, double-clicking setup.exe on the Office 97 disk immediately with the message, "the specified path does not exist", and listing the correct path to setup.exe. After that, when I log off, I get the message that ntvdm.exe failed, twice. I see lots of chatter on the web suggesting that the problem is that InstallShield is choking, which makes sense, since the message doesn't pop immediately, but nothing else displays before the error. Any ideas? None of the suggested remedies have helped, so far. (BTW, setup.exe cranks right up under Win 2K pro). All help appreciated.

Re: setup.exe - ntvdm.exe fails preventing Office Install cascade unde "DL" <address[ at ]invalid> 14.08.2006 21:57:52 There is no need to install earlier full retail edition in order to upgrade. You install the latest upgrade edition (OfficeXP), when it complains it cannot find a qualifying app, you pop your earlier full edition in, (Office97), and point to it. PS I'm assuming Office97 is a qualifying app for OfficeXP - I didnt check "b-seven-co" <bsevenco[ at ]discussions.microsoft.com> wrote in message news:E53D0D2D-0445-4417-BE2E-A3866396614B[ at ]microsoft.com... [Quoted Text] > I have a retail Office 97 office Pro, a retail Win 2K Pro Upgrade and a > Retail WinXP Office pro upgrade. I want to install office 97 on my Windows > XP pro system, by installing Office 97, and then the Office 2K and Office XP > upgrades. > > Infortunately, double-clicking setup.exe on the Office 97 disk immediately > with the message, "the specified path does not exist", and listing the > correct path to setup.exe. After that, when I log off, I get the message > that ntvdm.exe failed, twice. > > I see lots of chatter on the web suggesting that the problem is that > InstallShield is choking, which makes sense, since the message doesn't pop > immediately, but nothing else displays before the error. > > Any ideas? None of the suggested remedies have helped, so far. (BTW, > setup.exe cranks right up under Win 2K pro). All help appreciated.