Originally Posted by TPeterson
OK, here are some other possibilities to look at:
1. MDP firmly seated in PCI slot?
2. Try running with only DRAM stick 1 and, if that fails, with only stick 2.
3. Long shot: Pull the DVB card.
BTW, there is a distinct lack of "me too" chorus here, so I doubt that you have much company on this planet with this problem.
BTW^2, I assume that you have actually confirmed by looking at the desktop display, -tabbing, etc., that the machine really and truly is locked up and not simply stuck with MyHD in an unresponsive state?
I finally had a chance to look into this bug. It really would have been much more customer friendly if MIT support had done the debugging, but apparently that is asking too much. Having said that, here is what I've found...
I first tried to narrow-down the symptom and after many hangs realized that the hang always occurs at the start of the fast forward, rather than after a fast forward has occurred. The other key item is that when using the slider on the screen app (rather than the remote) the system never hangs. Also using the FF button on the screen app never produced a hang (although my sample size is limited for that function).
That that system works properly with the screen app (but hangs when using the remote) seems to indicate that the memory is fine. If there was a memory problem, then whenever that memory location was hit, either by using the remote or by using the slider, the system would hang. This doesn't occur. On top of that the system does not use a swap file (the O/S only uses memory) and the system has been stable since December except for this bug.
I used similar logic for checking the hard drive. I have some progs that write ts files and some that scan ts files and everything works properly. If there was a hard drive problem then the problem should show up more often. If it were a MyHD problem then *likely* the problem would also occur when FF/Rew with the screen app (no remote).
After a while, it occurred to me that the only thing unique in the hang-up was the use of the remote. Since the hang always occurs just as the button is pressed, that provided more evidence that the MyHD card was fine but the remote software or hardware had an issue with my setup. Perhaps the order of USB connections?
I then looked at the registry to find try to find a parameter that would relax the remote timing. The only item that looked promising was, MaximumTransferSize which I doubled to x2000. I also lowered the debug setting to DebugLevel=3 (was 2) just to make sure that some debug was not getting in the way.
Since making those changes (and only those changes) the MyHD card has not hung. I've only made it through three files, so this isn't yet conclusive. However, in the past three files was sufficient for this problem to occur.
The reason I am appending to the forum is in the hopes that other people who have the hang-up issue (there were a few) would try this and see if it fixes their computer's problem as well. It would also be interesting to find out exactly what MaximumTransferSize does. Is it the max transfer size of remote commands?
Let's hope this solves the problem since it was the last (known) bug on my system, for the items I use.