Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 716452" data-attributes="member: 82144">Hi againSo we are guessing that:- the &quot;dropouts&quot; (signal dropping when manually timeshifting) are probably due to HDD issues- the software independent &quot;no signal&quot; problem is due to driver sleep/resume issuesGreat minds think alike! <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" />My comments were based on the assumption that you only had a 1.5TB drive (as listed in your system specs).What drive/s do you use for timeshifting and recording?Is the 300GB drive a 7200rpm drive?A RAM drive really shouldn't be necessary for timeshifting/recording. In my opinion it is only useful when you have a slow HDD, are doing HDD troubleshooting, or you have lots of channels being watched at once (ie. 7200rpm HDD IO requirements exceeded). It would be a useful experiment in this case to determine whether an HDD is the cause of the problem, but I believe you'll have to record to a standard drive so it isn't really a long term solution...I don't use devcon. I stick with XP, or I run 4095MB of RAM (disable the 1 extra MB). When my tuners disappear they can only be brought back by restarting the computer. Attempting to re-detect devices in device manager or with devcon doesn't help. If I were in your position, I would use a scheduled task that uses devcon to restart the tuner driver if necessary, then starts TV Server. In other words, I wouldn't have a delay on the TV Server startup - I would start TV Server manually with the scheduled task which would run on resume from sleep/hibernate...</blockquote>

[QUOTE="mm1352000, post: 716452, member: 82144"] Hi again So we are guessing that: - the "dropouts" (signal dropping when manually timeshifting) are probably due to HDD issues - the software independent "no signal" problem is due to driver sleep/resume issues Great minds think alike! ;) My comments were based on the assumption that you only had a 1.5TB drive (as listed in your system specs). What drive/s do you use for timeshifting and recording? Is the 300GB drive a 7200rpm drive? A RAM drive really shouldn't be necessary for timeshifting/recording. In my opinion it is only useful when you have a slow HDD, are doing HDD troubleshooting, or you have lots of channels being watched at once (ie. 7200rpm HDD IO requirements exceeded). It would be a useful experiment in this case to determine whether an HDD is the cause of the problem, but I believe you'll have to record to a standard drive so it isn't really a long term solution... I don't use devcon. I stick with XP, or I run 4095MB of RAM (disable the 1 extra MB). When my tuners disappear they can only be brought back by restarting the computer. Attempting to re-detect devices in device manager or with devcon doesn't help. If I were in your position, I would use a scheduled task that uses devcon to restart the tuner driver if necessary, then starts TV Server. In other words, I wouldn't have a delay on the TV Server startup - I would start TV Server manually with the scheduled task which would run on resume from sleep/hibernate... [/QUOTE]

Verification