Cannot save file in Maya 2022

[Anonymous]

I have a question about a certain error that I keep getting when I attempt to save my work from Maya 2022: "cannot save changes to read only file". This is regardless if I am saving progress ("Save") or making a new file ("Save as"). When I actually make a new file, it says it has no bytes. I have one file that I was able to save days ago, but now I have this error. Could someone help me with this? Thank you very much

[BenBisares]

Seems like some kind of Windows permission issue. What if you save to the Desktop and then in the Windows Explorer, drag&drop to the place you actually want to save to?

[Anonymous]

Can you please explain how to do that? I never had this issue before, and I have never done this either. 

[hamsterHamster]

Also,

Check the free space on your C:\ and H:\ drive, you need at least some hundred megabytes to operate.

Check if the parent directories don't have this Readonly flag enabled.

The file properties you are showing is for whatever, but not for the file named <Part 2 new extra copy.mb> - it has no extension (mb or ma) and since you are on Windows, you have to use those. Check the properties for the file in question, not some extensionless blackhole.

Make a habit naming your files without using spaces, use the underscore _ instead, otherwise it is hard to tell apart the messages from the actual file. And the name of the file in question is already memetic:

Use the increments at least, e. g. Part2_New02.mb, Part2_New03.mb.. and so on - it is both easier to read and sort by name chronologically.

[Anonymous]

How can I free up space on my C and H drive ? When I go to my drives, it doesn't give me the amount of space I have left. I couldn't find the parent directories either for the files. 

For the files in question,  the file is an mb file specifically. I can't find where I can check the properties. The file is saved in Maya, but I can't find it on my my computer. 

I will save the files as you instructed as well. 

[hamsterHamster]

Ok, let's step back a little.

1) When you started working, did you set up your project at all?  File>SetProject.. or File>ProjectWindow - it either sets the current project, or creates new one, with dedicated folder structure, where /scenes are place where you could find your scene. If you are oblivious of this, then at least do file search on, I guess, F: drive to find scene and set it's location as the project (which is a bad practice, yet better than nothing).

2) Do you know how to browse to the MyComputer and check the Properties for C: and F: drive? There will be a dialog like you have posted above, just with piechart that will show free/occupied space. There are many places in the C: where temp files are held, also the contents of Recycle Bin might occupy many gigs of space. If you can't find yourself, then install some uttilities, like CCCleaner.

[Anonymous]

"When you started working, did you set up your project at all?  File>SetProject.. or File>ProjectWindow - it either sets the current project, or creates new one, with dedicated folder structure, where /scenes are place where you could find your scene."

Yes I did all of this in the beginning, the file is saved in a Toshiba H Drive. My project is called Assignment 5.mb,  now for some reason files are saving to my computer. I have no idea what the problem was specifically. I did this by making a file called "Test". But the file that wouldn't save before (the one I mentioned in the beginning of the thread). I don't know if it had something to do with the fact that it was an Animation. 

"If you are oblivious of this, then at least do file search on, I guess, F: drive to find scene and set it's location as the project (which is a bad practice, yet better than nothing)."

No I don't think I am oblivious of how the Drives work. but thank you for mentioning this. 

[937303742]

You could click file and right mouse button File- Properties-Attributes-Uncheckmark "Read-only"

[paulmfogarty]

I just solved this issue for one of my students and I can see you have possibly the same. It is because of the ":" in your file name. I told him to maybe get ride of it, he did, and problem was solved.