>When XP was launched a client had a PC which I was able to install my software on as the PC was about to be rebuilt anyway. My software (vfp5) installed and loaded just fine. A friend had the same result. Since then we've both lost access to win xp machines and dont have the funds to purchase a hack machine to test on.
>
XP can be installed in a dual-boot configuration on FAT partitions, or on a Win2K NTFS 5.0 partition, although it is not recommended. If you've got tape backup capable of doing image backups, it's a relatively simple process to blow an image of your current system to tape, install XP for testing (if you're smart, blow an image of the XP install to save the time and headaches in the future) and then blow away XP and reinstall your image backup over the top of XP. I keep about a dozen different configuration images on tape for one machine that I use for testing - it lets me use one box to test a number of different environments (variations in OS, Office versions, etc.) and I don't have to worry about what an install or runaway app might do to the machine - I can always shut down, boot from a floppy and reinstall an image backup to get back where I want to begin.
If you don't already back up before you start testing, you'll eventually wish you had...for me, the cost of a tape is a whole lot less money than the time it might take to reinstall a detailed configuration from the original distribution media, then download patches, etc.
>We've changed our installer from a limited issue installshield (ok it came with delphi) to deploymaster (
www.deploymaster.com) which I like (esp. the price) and that is all.
>
>So has anyone suffered these problems with vfp5 and XP or is it our installer that is the problem?
>
I'd be suspicious of your installer; I've got a number of people running VFP5 applications under XP without any serious problems (I generally take the precaution of reinstalling the runtime engine and ActiveX components on client machines which were upgraded from Win9x to WinXP, already having VFP5 installed on them, since a number of COM components change providers between versions.) If your installer does not use the Windows Installer technology, I'd bet on it being at the root of problems on Win2K and WinXP deploys.
>thanks in advance
>
>Sarah
