I have succesfully set up a dual boot between Windows Vista and XP. Vista = C:\ XP = E:\ Now I have a serious problem. When inside Windows XP, files from the C:\ drive (Vista) are accessible. This means that applications which have installation paths hard-coded into their install scripts rather than using Windows system parameter variables could easily dump files into C: when they should be installing to E:. This isn’t such a great situation. This could even cause damage if files are overwritten in for example the Windows folder of C. Is there any possible way do somehow deny / trick XP to make the C drive invisible from my Windows XP ? Any suggestions would be highly appreciated ! Thanks a lot ! [Smile] - Poul Wittig

Any program that doesn't reference the ProgramFilesDir registry key must be poorly written and should be avoided!

What kinds of files are you talking about? If I understand what you mean this is a normal occurance. Created files are not tied to an OS. If you access any file stored in either OS and make changes you need to save those changes. If you simply use the save command the file remains whare it resided. Problems can only occur when you save to a different folder. That is no different than if you save the same named file to two different foleders in the same OS. Programs are a different story. Very few programs will be usable across OSes. Problems of crosslinked files WILL occur if you install programs from within both programs to the same exact folder.

ignor, post in wrong thread. Something goofy here.

Dunno how you did that. The way vista and xp see the disk is not the same. Vista C: is not XP C: Vista C: is only C: when booted to Vista. and visa versa. I read it wrong and answer it wrong too. So get off my case you peanut.

jefro: Dunno how you did that. The way vista and xp see the disk is not the same. Yes, they do. WinXP and Vista assign C: to the drive with the boot loader, not the drive with the Windows folder. I know, because that's how my system is set up. Deathray: I've been running with this setup since Vista came out, and I have yet to run into issues. If you do, I'd love to hear about it. Then again, I AM running Vista x64, so Vista's 32-bit Program Files folder isn't C:\Program Files. The workarounds are as follows: 1) When in XP, Deny yourself all access to C:\Program Files. That'll keep any program you run from touching C:\Program Files. 2) Set up a custom Program Files for Vista. Say C:\Real Program Files. It's a pain to do, but it should be possible if Vista was just installed. The steps are as follows: - Copy the old Program Files to the new folder - Change the registry keys to the new location. In Win2K, they are: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\ProgramFilesDir HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\CommonFilesDir While you're at it, scan for and change for any other references to the old C:\Program Files in the registry. - Rename the old C:\Program Files, and see what crashes. Something's bound to. Fix it or reinstall the app. If you know how to mount Vista's registry from XP, you might as well do it from there. If not, just make sure you reboot after the registry changes, but before the rename.

" Vista = C:\ XP = E:\ " ??? I read it wrong and answer it wrong too. So get off my case you peanut.