Additional features to existing project

Existing Deadhead3 software that you wrote needs two new features: 1. Have the app write the processed (changed) file back to *both* the current folder and another folder designated by the file name. That folder's location would be put in an INI or FIG text file. All file names are normally a 6 digit number. The first two digits would be the same as the folder name/number. The INI file would show what drive that folder is located in. 2. Next desired feature is that the app have the ability to skip songs that have already been verified through this app. The way that works is a CSV text file has all the songs that have been previously processed through the app. One of the columns is headed verified. If the song has been verified the old app put a v in that column. The app needs a new button: Skip if already Verified. If that is checked, then the app goes thru the list one at a time and skips any song that has already been verified but processes each it comes to that have not already been verified. The csv file also has a column called ripcut. That is the song's filename, a 6 digit number. If a song is not in the csv file, the title, artist, intro, length and ending get appended to the bottom of the file with the verified = v and file name as the ripcut. The csv file can be either CSV or tab delimited. You pick one. It should probably be able to accept either. The title and artist data from the CSV file is also displayed on the app just below the new title and artist read from the file cart chunk header. See the old version from previous software guy. Also, there is the ability to copy from one similar field to the other thru up or down buttons at the right of each. You should leave nearly all of the fields unchanged. The only possible changes would be title, artist_first, artist_last, intro, length, ending, verify. When adding a new file, append a blank line to the bottom of the file, then populate with the file name's 6 digit number in the ripcut field. When the song is saved with F3 or F5, update the title, artist_first, artist_last, intro, length, ending, verify fields and leave all the other fields blank. There may or may not be a cart chunk header in the wave files. If so, display what you read from the header. If not, start with blanks in all fields. Processing a file that already exists in the csv file would mean that the fields title, artist_first, artist_last, intro, length, end (or is it ending?) and verified would be updated if changed." Most likely the situation would be that the data in the csv file does not include a v = verified, so opening the file and checking the info would be done for the purpose of fixing any file problem and also for updating the csv database. Note that the CSV file will have probably 60,000 lines. If you think that will present memory problems, I would be willing to split the csv files up. Perhaps folders 10-19 in one, 20-29, 30-39, etc. Or, if you wish, 10 in one, 11 in the next, then 12, then 13, up to 99. I want the source code for this (and all projects) as part of the bid.