Users can't see that theres a 10,000 byte limit on volumes.

[Dunbaratu]

I tried to figure out why on earth I couldn't copy a file to the volume and had to resort to reading the source code here to figure it out.

The fact that there's a 10,000 byte limit for a volume is completely undocumented. No end-user who hasn't read the code would realize it.

And when you try to copy the file into the volume, the error message doesn't tell you that a limited capacity is the reason it failed.

Something definitely needs to be added to make it known to the end user.

One simple thing would be if the "LIST" command showed a line at the bottom of the file list along the lines of:

Volume Capacity Used:   5012 / 10000 bytes.

People would at least then know there was such a thing as a limit.

[Nivekk]

Hmmm... you're right! I thought I was displaying that somewhere...

Do you find that 10,000 is too constricting? I wanted some kind of limit but I figured it would be a while before someone went over the 10k mark, especially since the archive drive is unlimited.

[Dunbaratu]

I think it sort of makes sense to keep it limited to keep the 1960's feel of the game, but 10k is really small to work with, especially when the real space programs were writing in machine language at the time and our 10k limit is measuring source code..I've had to cut down my variable names short to get programs to fit.

[Dunbaratu]

Technically I did just find one place where a user can get a hint that there's a 10,000 byte limit. If you do a "LIST VOLUMES" there's a column for the max capacity of the volumes. But the reason for the failure to copy being no room on the hard drive should also be mentioned in the error message, I would think.