CrossOver Support - Community Forums

Steam.exe(main exception): Cannot open blob archive file: 
CMultiFieldBlob(mem-mapped file): Failed to MapViewofFile

This was the error I got when I tried to access Steam through an external hard-drive. I've already tried solutions recommended by the Steam Database(Formatting my Partition), renaming the file, deleting it file, and many solution recommended. But nothing worked out.

History
My hard-drive had gone into a terrible corruption before, I've did many things to recover it, but no use, so I formatted it, and I can access it again. Every-time when I tried to install Steam to it, it just keep getting error. Fine, I copy the files installed on the C: Drive to my hard-drive. It gave the above error. This happened too before I format my external hard-drive which is weird.

Now
I suspect that the PC of mine had been keeping a corruption record, or maybe had a permission that I cannot change that prevent the access of this file. I formatted my external hard-drive, but restored to factory condition before I did that. But both still gives the same error.

Please help me!

I also have this problem on a new install of steam. It was working the day before and I was able to log into Steam and play Day of Defeat for 2 hours. Today, I got this the same error as the user above and reinstalling using the steam bottle does not fix the error.

nakajima wrote:

I also have this problem on a new install of steam. It was working
the day before and I was able to log into Steam and play Day of
Defeat for 2 hours. Today, I got this the same error as the user
above and reinstalling using the steam bottle does not fix the
error.

Yup, sure had, from what I've saw from the latest "Steam On Linux" article, WINE conflicts with NTFS-3G or sort, so you does not have permission to access any files from an NTFS Partition. I'm so sad, first I thought it was error with my hard-drive, like I wrote, it got corrupted before.

I've messed with it, and now, I've formatted both my PC and Hard-Drive just to get a solution for the error. But neither of them helped, then I've came up with that article, seems like they had not updated it for a while, and I notice that only after I've failed.