BaseCamp 4.4.2 Backup is invalid or read-only

Is it normal for Backup to fail if Birdseye imagery is present?

I just did a test backup using BC 4.4.2 and it worked fine. I have 2.40GB of Birdseye imagery in my database. I saved the backup to my HD not that it should matter.

PS: Exporting data from BC won't save Birdseye imagery or Geotagged photo's. A backup will. Of course you can manually backup that data (what I do).

StuartMW - thanks for quick test. I wonder if I have a problem caused by my windows 7 pc locking up an hour ago. I had to power down and when I re-powered up Basecamp was still running but had a big red X over the map area. I shutdown BaseCamp and restarted it and it looks OK (no red X) but perhaps something is corrupted. Can I re-install 4.4.2 without losing my data?

I have tried many things with no change - always the ... invalid or read-only. - is there a clue here?
I have already run basecamp as administrator and still get the message.
I have uninstalled and installed 4.4.2
I have run Norton power erase looking for virus and found nothing.
I have tried a new empty database and still the same message.
I imported a .gdb backup into the new empty database - still same error.
I deleted each type of item (track, waypoint etc) and it failed everytime.
I have a copy of Basecamp 4.4.2 on my laptop (W7 Home Premium) - with a different set of data (and no satellite images as it happens). That runs ok and backs up ok!
Any more ideas?
Thanks

You might try

Microsoft .NET Framework Repair Tool

Thanks. Will complete .net repair tomorrow (it is 10pm Uk time) - the net could be related since I have detected that ordinary users have read only access to my 3 Hard drives. 2 of these are shared on my net.
However the good news is that, I have loaded a blank dvd+R and successfully written a back up to that from BaseCamp 4.4.2. Thus the 'read-only' part of the error message seems very relevant to my failures to backup to my internal hard drives.

Stuartmw - thanks for your help. I did not have to repair .NET
I found that I got the error message if I tried to backup up to C: or E: or any other root but the backup was OK into a folder on E:. Thus I think the problem was permissions in Windows 7 Pro and the clue in the error message was 'read-only'.
Peter

For anyone else having this problem, it's a bug in the software.. not a permissions issue. The software cannot handle saving to the root of any drive, at least I tried multiple drives including external and network mapped and none would save to the root even though I have full permissions.

I suspect that the program is parsing drive/directory/filename and then putting them back together incorrectly when there is no path component.

I have the same problem now, but with BaseCamp 4.7.4 on my W10 Pro.

Location of the backup is another disk on my PC.