Element Not Found

Hi,

personally I see the built-in read access of the BootCamp 3.0/3.1 drivers as being 'experimental'.
For full and/or better access to your OSX partition from within Windows I would recommend to get MacDrive.

Nonetheless it might also be, that Windows is trying to create some temporary files on your OSX partition, when trying to open an exe or iso file located on that OSX partition.
Since write access is not part of the BootCamp drivers, this attempt fails and maybe creates that error message.

Hope it helps

Stefan

Message was edited by: Fortuny

Hi,

musicwind95 wrote:
That doesn't quite explain why only EXEs and ISOs are affected.

"(it may occur with other file formats, but I haven't tried)" - so you have tried it with other file formats ?

Nonetheless, depending on what other file formats you try or already tried, to me it still comes down to the question, whther these files when you try to open/use them, want to perform any kind of writing to the harddisk/partition from which you use them.
For example, exe files can be self-extracting archives, which, when started, unzip their contents to the same folder the exe file is in.
If you can, tryout a simple txt file or something like it.

Anyway, I want to prevent Windows from writing to OS X...there's viruses and the inability of Windows to handle HFS; a third party program might corrupt the OS X file system...I might be paranoid, but I don't want to lose my work in OS X, even if it means sacrificing some functionality in Windows.

Nothing paranoid about that 😉 I don't want write access as well.

Stefan

Hi,

musicwind95 wrote:
Yes, after the initial posting I've tried with DOCs, DOCXs, PDFs, TXTs, HTMLs, and some application-specific files. No issues.

So that substantiates my initial assumption, that the exe and iso files you try to run/open do want to write into the same folder/harddisk partition they reside in.

If you like to share, what exactly are these exe and/or iso files and what do you want to do with them while in Windows ?

Stefan

Hi,

all the more to make my initial assumption sound correct.

The lack of write access to the OSX partition is the culprit when opening/running these exe andiso files, as they seem to need writing something (at least temporaily) onto the OSX partition where they reside.

Without allowing this I can't think of a solution, other than coyping these files to the Windows partition and running/using the files there.

Regards

Stefan