That folder into which converted files are placed in Windows Explorer shell when right mouse click properties is selected (or alt-enter keyboard shortcut) has that the folder's files inherit or will be read-only--The read only check box is characterized as: "Read only (only applies to files in folder)."
Platform is Windows 7 Ultimate x64 running on Intel Core i7 2600 on Asus p8p67 deluxe w/32 Gigabytes of ram. Hauppauge WinTV 7 latest version is running off of two WinTV HVR 2250 MC Kit Dual Tv tuner PCIe 1x cards that creates mpeg-2 .ts files in C:\Users\Public\Videos\.
I developed a C++ command line Unicode program that frees up disk space used by on going PVR recordings on a per-show basis Regex parsed as specified in a config.txt file. When attempting to do a programmatic send to recycle bin for the older files within such folders, the recycle operation fails.
The files themselves within the folder have no read-only attribute on them. Only the folder itself has this property that "seems" to be preventing my software from freeing disk space used by these older files whereas previously the disk space freeing program was able to do its work on the original mpeg-2 .ts files and the MCEBuddy 2.x-produced .mp4 files. I am unsure of what changed--options settings for internet look up of information or newer version of MCEBuddy 2.x?
Could you insure that your application software not mark such folders with this kind of Read-only attribute unless optionally enabled?
I want it so that if the user specifically does not want a show episode repeatedly recycled that they can mark the file or folder themselves as read-only to prevent my disk space freeing software from processing such files, but when your application, by default, marks all such created folders in this way, it halts all of the disk space freeing application's efforts to actually free up disk space.
Is this Read-only attribute done in order to use a .ini file with a corresponding folder icon file for "nice" folder display listings in Explorer when larger folder icon displays are done?
If this is so, please make this an option that is disabled by default so that the user must select that this read-only folder thing happen.
Thanks.
Comments: ** Comment from web user: oldspammer **
Unfortunately, I looked for the "developer readme.txt" file specifically in all of the unzipped file folders of the bundled download source code archive, but no such file exists within the zip file--only text string references to such a file in several other .rtf , text, and other such documents.
In a question or comment that I posted last week, I asked if there were some undocumented developer tool installation steps to permit me to do clean, error-free builds / compiles of the code, but no response back yet--I said that my build attempts resulted in a 799 line output of error diagnostics repeatedly saying various fatal errors having to do with some sorts of small personal encryption key files. I am wondering if I am missing any SDK installations, or other things?
As I mentioned in this initial posting above that for the previous version of the software that I was using or for my current release 13 software's options that I am using now, that my developed disk space recovery program worked since no such folder read-only status had been applied.
I would have to read and understand the MCEBuddy source code to determine what system function calls use what parameters based on what settings to know how this folder read-only status comes about--but it is happening with the current release 13 x64 version software by whatever option mechanisms are in effect.
These folders are freshly created now, and not by software that I was running months ago. I am unsure of how you mean that the software does not have this effect any more and that this mechanism would have been carried over, by default, by the latest software using old options created by prior runs of older versions. I believe that I was only running one prior version before release 13, and it was from Spring time of 2013. I will not download release 14 unless it is specifically available for x64 which I could find no download links on your various download pages--that is why I'm still running the latest x64 release that you have available--release 13 x64.