I recently migrated from Win7 to a Mac Mini and OS-X using the Chrome browser. I believe that when I compile and download, OS-X is automatically renaming my .bin file (adding a sequence number to the name) when it detects an existing .bin file with the project name.
In the download window, I can manually edit the new file name back to the original name and the system will then prompt me to allow me to overwrite the file.
I had been allowing the new file names (with sequence numbers) to be downloaded, and occasionally moving older ones to trash.
I eventually found that even though Finder showed only a few small files, GET INFO showed the flash drive was full, no space remaining. I do not know if moving the files to trash was somehow not freeing the space, but best guess is the drive was "corrupted". I was able to "erase" (reformat) the drive and with a bit more stumbling around got it working again.
Perhaps the corrupted drive was just a coincidence, but I would be interested in hearing from anyone who has had similar problems or anyone who knows how to configure OS-X so the download will not try to add the sequence number to the file name and so the system will prompt me to allow overwriting.
Thanks,
Chuck
I recently migrated from Win7 to a Mac Mini and OS-X using the Chrome browser. I believe that when I compile and download, OS-X is automatically renaming my .bin file (adding a sequence number to the name) when it detects an existing .bin file with the project name.
In the download window, I can manually edit the new file name back to the original name and the system will then prompt me to allow me to overwrite the file.
I had been allowing the new file names (with sequence numbers) to be downloaded, and occasionally moving older ones to trash.
I eventually found that even though Finder showed only a few small files, GET INFO showed the flash drive was full, no space remaining. I do not know if moving the files to trash was somehow not freeing the space, but best guess is the drive was "corrupted". I was able to "erase" (reformat) the drive and with a bit more stumbling around got it working again.
Perhaps the corrupted drive was just a coincidence, but I would be interested in hearing from anyone who has had similar problems or anyone who knows how to configure OS-X so the download will not try to add the sequence number to the file name and so the system will prompt me to allow overwriting.
Thanks,
Chuck