I have an XP Virtual Machine running under Windows 7 Professional "Windows Virtual PC" so that I can run some 'legacy' applications which won't work in Win 7. In the virtual machine, Windows Explorer shows a local disk (C and also all the disks on the host machine - and allows me to copy files back and forth. Most of the applications running in the virtual machine are quite happy to read and write data files on the host machine. However Word 2000 (and Excel 2000) are not. If I try to open a file from the host machine in Word, it just hangs - and CPU usage goes to 100% On the other hand, if I copy a file from the host machine to the local disk, it then opens quite happily in Word. It's presumably got something to do with sharing and file privileges etc., but why should Word (and other Office 2000 applications) behave differently from (say) Quicken in this respect? Any ideas?  In case you're wondering why I'm running Word in a virtual machine, I need to use a particular pseudo printer driver (Jaws - for creating PDF files) which won't work in Win7, and I need to open Word files in order to 'print' them. (Yes, there are other PDF converters which *will* run in Win7 - but I haven't yet found one with the same security options as Jaws). -- Cheers, Roger ____________ Please reply to Newsgroup. Whilst email address is valid, it is seldom checked.