Can get so far with the installation but it always give me the message go to DOS Use the disks and says it does not recognise Windows NT. I had no idea I had a network card but it should still work. HELP!
Can we clarify this. I've just bought Drive Image but havn't yet installed it. I am running XP Pro. The box has two discs which I have in front of me. They are labelled DI2002 for Win ME, 98, 95 & NT. and DI7 for WinXP and 2000 Pro. So it seems 2002 is the version for NT.
If you are using DI7 you must also download and install .NET Framework.
However I have heard that 2002 is the better version. If it will work OK with XP I would be very grateful for further clarification.
Drive Image 5 - support for XP first appeared but the program still dropped down into dos when performing actions.
Drive Image 6 - Cosmetic overhaul but the program could now remain within Windows while performing except where acting upon the system drive
Drive Image 7 - Cosmetic overhaul and switch to employing .Net Framework.Presumably to convince folk to shell out yet again,Powerquest decide to state that DI7 is for XP,etc.
Frankly, I see DI7 as a cynical marketing exercise to flog the program yet again in new clothes.Might be significant as the last of the line as now that Powerquest have been bought by the boys at Symantec what's the betting aspects of DI & PM will be incorporated into their utilities.
Also have the box set of DI7 with the two discs and as yet still in the sealed box unused. Box wording for use is the same as you have. However, I downloaded the ms update for NET framework but this changed windows startup from single user to having to log on again so I uninstalled NET framework but used the option to keep the files - just in case this is the PC that I actually use DI with and not one of my other PC's. Since I have done this I have lost the automatic update from ms. Whenever I try for an update scan on the ms website I get the error 0 x 800A138F. Have tried ms suggestions to resolve this but it hasn't worked. Pretty sure that it was the installing and uninstalling of NET framework which caused this. Now I have to go on the ms website to check manually for updates.