Read Only Bug
I found a weird bug. When you put an SD card into your computer, and it is locked, the slicer will give you a message that you can't save to it. So you close the save dialog box, eject the SD card, unlock it, and insert it back into your computer. Then you try to save to it again, and the slicer still says you can't save to it.
You may ask, why would you put a locked SD card into your computer when you know you're going to save to it? The little slider sometimes gets hooked on the entrance to the SD Card reader and pushed into the locked position as you insert it into your computer.
Steps to reproduce
- Open Prusa Slicer and add an object to slice
- Slice the object
- Insert a locked SD card into your computer
- Export the gcode and try to save it to the locked SD card
- Receive the message saying you can't save it there
- Close the dialog box
- Eject the SD Card
- Unlock the SD card
- Re-insert the SD Card
- Click on the Export gcode button in Prusa Slicer
- Attempt to save the gcode to the SD Card
- Receive the message that you can't save to the SD card
I'm using Prusa Slicer Windows 64 bit version 2.2.0 on Windows 10 Home 64 bit 1903
RE: Read Only Bug
Silly question - when you removed the locked card - did you simply yank it out or did you do the OS "eject"?
Could be the OS is playing games with you.
After reinserting the card, open an OS dialog and refresh the file view. This should clear the write status for P.Slicer.
ps: where did you find a copy of v2.2.0 ?
RE: Read Only Bug
Definitely used the eject method. The first time it happened, I let it go, but then it happened again, and I did some testing. I put the locked card in, had the issue, ejected it, unlocked it, re-inserted it, had the issue, closed the slicer, then went into explorer and opened the root of the card (where I was trying to save the gcode) and created a new text file, no problem. Then I reopened the slicer, exported the gcode, and it worked.
RE: Read Only Bug
I just had the exact same thing happen to me. The 'lock' tab caught on the entry port and ejecting and re-inserting the card did not solve the issue.
Software version is 2.3.0
RE: Read Only Bug
Were you able to set the card back to RW? I have had several SD cards go bad over the years and unexpectedly going RO was somewhat common. I haven't used SD cards much recently, so can't say if they've improved in terms of reliability.
and miscellaneous other tech projects
He is intelligent, but not experienced. His pattern indicates two dimensional thinking. -- Spock in Star Trek: The Wrath of Khan
RE: Read Only Bug
Were you able to set the card back to RW? I have had several SD cards go bad over the years and unexpectedly going RO was somewhat common. I haven't used SD cards much recently, so can't say if they've improved in terms of reliability.
I haven't used an SD card in a while (I set up a web cam on a Pi, then went ahead and setup OctoPi), but when I had this problem, and when I was using an SD card, it was the SD card that came with the printer, and writing to it always worked. If I had the problem, I would do whatever I did to fix it (I don't remember) and then it would work. Also, when PrusaSlicer wouldn't write to it, I could write to it in the OS.
RE: Read Only Bug
Yes, the problem was solved exactly as the original poster, RickSeiden, suggested. Once the slicer program was closed and reopened the issue was fixed.
I have come to the same conclusion RickSeiden did; this is clearly a bug with PrusaSlicer, and is not caused by any issues with the SD card itself.
RE: Read Only Bug
Is this the typical cache issue where if you insert the SD card after you start slicer, slicer doesn't even see the card and you need to refresh the save dialog? This is pretty common with many apps.