Just gor test reasons if your SDD has gone wild:
Close Lazarus. Open Gimp/Photoshop/whatever. Open a big image. Save it with a new name. And now: Any problems?
Otherwise you might have a problem in your code.
Winni
maybe you wrote to a write protected drive?
Also if memory serves at one time there are some folders on the user system in windows that has a limited size set to them, it's possible you hit the limit but I am guessing this isn't the case.
The message you are getting sounds very suspicious, please show us minimum code where you are doing the file open and writing attempts.
Can you verify that Filename is what you expect it to be?Exactly my thoughts.
Put a ShowMessage('Filename="'+Filename+'"') in your code, just before the call to AssignFile.
IIRC DiskFull errors sometimes get raised on filenames windows cannot digest.
Bart
What's the Value of "FileName" in your Line 14?
Because right now i can't make heads or tails from your code in Line 12 and Line 13
In Line 12, you construct your local var "FileName" from something called "C-BasePath" and "Bit2" (which you seem to use as a constant).
What's C_BasePath (Yes, i can guess what it is!)?
In the next Line you check a (boolean)-Variable from somewhere, and if True, you overwrite the Value in "FileName" with something called "LOC" and Bit2 again.
Can you verify that Filename is what you expect it to be?
Put a ShowMessage('Filename="'+Filename+'"') in your code, just before the call to AssignFile.
IIRC DiskFull errors sometimes get raised on filenames windows cannot digest.
Bart
Back in older times, drive "X" was an invalid drive.Since at least Windows NT that isn't the case anymore.
Your drive 'X', is that an external Drive?Can you verify that Filename is what you expect it to be?
Put a ShowMessage('Filename="'+Filename+'"') in your code, just before the call to AssignFile.
IIRC DiskFull errors sometimes get raised on filenames windows cannot digest.
Bart
I think so Bart. I ran it under the Debugger and it was correctly set.
When I got the disk full message I was running the program in normal mode. I then ran it under the debugger and got the same message.
Filename was correctly set.
So I set the ONEDIRECTORY switch to true and wrote to another drive just fine. Turned off the ONEDIRECTORY switch, Disk Full.
Rebooted the computer and everything seems to work, can't reproduce the problem now. So I don't know if it's Windows 10 Pro, my Intel SSD Drive or Free Pascal problem.