>>>Could you be more specific: when you had VFP running successfully, what was the host OS, the VM product/hypervisor, and the >>guest OS under which VFP was running?
>
>You're quite right - when I read back I have given nowhere near enough information!
>
>I originally installed Microsoft VitrualPC on my Windows XP laptop, this worked and I ran a few VFP tests and tested my apps to ensure they are Windows7 Compatible.
>
>I then decided that I would like to work under Windows7 so I reduced the size on my XP partition and created a new partition.
>
>I installed Windows7 onto that new partition and have installed, office etc and have no issues other that the one with VFP.
>
>I installed VFP then upgraded to SP1 and then overwrote the SP2 files into the correct locations. all files were new downloads from MSDN.
>
>
>Have changed DEP setting at Christof's suggestion so it is now "on for all programmes except" and I have VFP in the exception list.
>
>However same issue still occur: VFP starts and immediately windows says "Application has stopped responding", sometimes I also get an update in the vfp error log, but not everytime.
>
>Application log shows:
>

>Faulting application name: vfp9.exe, version: 9.0.0.7423, time stamp: 0x49a31c0c
>Faulting module name: vfp9.exe, version: 9.0.0.7423, time stamp: 0x49a31c0c
>Exception code: 0xc0000005
>Fault offset: 0x0000d630
>Faulting process id: 0x8f4
>Faulting application start time: 0x01c9f8f16287b2e9
>Faulting application path: C:\Program Files\Microsoft Visual FoxPro 9\vfp9.exe
>Faulting module path: C:\Program Files\Microsoft Visual FoxPro 9\vfp9.exe
>Report Id: a06177ee-64e4-11de-8810-001a6b8abf83
>

So, the way I read it:

- your laptop was running XP
- you installed VirtualPC on XP
- you installed Win7 RC on the VirtualPC
- you installed VFP9 on the Win7 RC VM
- everything worked fine

Now, you've created a native Win7 partition, installed VFP9 on that, and VFP doesn't work.

A few things I can think of:

1. My understanding is if you want to arrive at VFP9 SP2, you should not apply SP1 at all, you are supposed to do this:

- install VFP9 RTM (i.e. SP0)
- install SP2
- install the latest hotfix (which apparently fixes the report grouping bug)

I don't know if this has any bearing on your situation.

2. One big difference between the working and non-working environments is the OS device drivers. When running in a VM, Win7 is using virtualized device drivers for display, printing etc. Now that you're running Win7 natively, it's using native drivers.

VFP is notorious for finding problems with device drivers, especially display and printer. Check that the drivers in use are exactly correct for your hardware, also check for updates from the manufacturer/OEM site(s).

If your drivers *appear* to be OK, you could try this test:

- set your display driver to one of the simple MS-supplied VESA drivers such as "SuperVGA 800x600", or maybe even the vanilla 640x480 driver

- set your printer to "Generic/Text Only" or its equivalent in Win7

- there may be other device drivers you could experiment with. The idea is to simplify as much as possible, and not rely on 3rd party or complex device drivers that may not be quite ready yet in an RC

3. Try running VFP as an Administrator (i.e. Run As...). I don't know if there are any other security/privilege things you need to look at

4. Rename or delete the active FoxUser.* files

5. Make sure any temp file folder specified in CONFIG.FPW actually exists, and/or rename CONFIG.FPW for test purposes

6. Test with antivirus real-time scanning disabled