Reply to thread

Message

<blockquote data-quote="rsbrux" data-source="post: 1113910" data-attributes="member: 49539">[USER=88439]@clarkey2r[/USER] No windows updates, just a Firefox update.[USER=82144]@mm1352000[/USER] Thanks for the tip!&nbsp; MediaPortal.xml was indeed 0 Bytes.&nbsp; I thought that it was only written by MP Config and didn't realize that MP itself&nbsp; was also writing to it during normal operation.&nbsp; After replacing it with a month-old backup version, I can start MP Config again.&nbsp; I am waiting for a backup to finish before I try to restart MP.&nbsp; Meanwhile I have enabled a disk quota for D: so as to avoid this in the future.&nbsp; Of course it would be nice if:<ol>
<li data-xf-list-type="ol">MP would warn when attempting to schedule more recordings than will fit in the space available.&nbsp; Then I could selectively delete the old recordings I least value, instead of letting MP delete them arbitrarily by date.</li>
<li data-xf-list-type="ol">MP (and MP config) would display a useful error message on attempting to start with an invalid MediaPortal.xml.&nbsp; I realize that it might not be possible to catch all types of file corruption, but a zero-length file should be obvious enough.</li>
</ol>Thanks for your help!</blockquote>

[QUOTE="rsbrux, post: 1113910, member: 49539"] [USER=88439]@clarkey2r[/USER] No windows updates, just a Firefox update. [USER=82144]@mm1352000[/USER] Thanks for the tip! MediaPortal.xml was indeed 0 Bytes. I thought that it was only written by MP Config and didn't realize that MP itself was also writing to it during normal operation. After replacing it with a month-old backup version, I can start MP Config again. I am waiting for a backup to finish before I try to restart MP. Meanwhile I have enabled a disk quota for D: so as to avoid this in the future. Of course it would be nice if: [LIST=1] [*]MP would warn when attempting to schedule more recordings than will fit in the space available. Then I could selectively delete the old recordings I least value, instead of letting MP delete them arbitrarily by date. [*]MP (and MP config) would display a useful error message on attempting to start with an invalid MediaPortal.xml. I realize that it might not be possible to catch all types of file corruption, but a zero-length file should be obvious enough. [/LIST] Thanks for your help! [/QUOTE]

Verification