//upload features requests and linux improvements

[the-godfather-007]

1. WWIV on linux is unable to //upload any UPPERCASE.ZIP files. If the files are converted to lowercase.zip they can be uploaded using the //upload feature. It would be nice if WWIV would move to a more broad OS friendly environment allowing UpperAndLowerCase.zip and to ignore case and or manage it in a different way.
2. Longer_file_name_support_would_be_great.zip
3. If there is another way, please share. Most of us that use the //upload feature are uploading hundreds if not thousands of files in one shot; therefore if a FILE_ID.DIZ is available, it's inconvenient and time consuming to have WWIV prompt to ask for a file description. Overall the //UPLOAD feature should behave in such a way that it just the sysop can walk away from the process and come back to it completed without having to sit in front of the desk waiting for prompts. This would require:
   a. If file_id exists skip asking for file description.
   b. If no file description exists upload without one
   c. If the file exists in another directory, add to a duplicate file log, but upload anyway.
   d. If file isn't the correct CASE_or_file_length.zip add to ignore list log
   I think these features would be nice additions to the //upload and //uploadall features.

How WWIV handled a large number of files on linux for me were the following:

1. I converted WWIV FTP archive files (all upper case DOS files) to lower case and they all started uploading which was great!!
2. With each file the BBS would read the file_id.diz and add the full description but then prompt me to manually type one. I had to hit the space bar for each file (at least 2,000 (I'm OCD, had to win)). If I just hit "enter" it would abort, if I hit space bar too quickly it would abort.
3. Any file that existed in another directory WWIV would ask me if I wanted to add it to the file listing in the new directory I was uploading to, and if I said "no" it would ask if I wanted to delete it. While this is a great check, maybe this would be better served as a feature to run AFTER a //UPLOAD is performed not stopping the process during.

Any speedy way to improve this or command prompt way to accomplish this would be a nice addition, and if it exists I'll gladly take the embarrassing learning opportunity.