I had bought another 'ebay special' for the conducting of further experiments with HD.

I have an IBM Thinkcentre tower, 3.2ghz P4, 500gb drive, two Air2PC 0.2 cards, Streamzap remote & FX5200 vidcard, works quite well, so I use it for production, & don't mess with it much. (Minor gripe about the 'random pause' glitch.)

The new 'ebay special' is a Thinkcenter desktop, also 3.2ghz P4, was new or little used before I got it (No dust bunnies in the fins...) This machine has half height pci slots so I had to put in a Dvico Lite 5 capture card.
It had a standard MX440 (64meg) half height Nvidia card, I left it in.
Streamzap remote.

I started out moving a 250gb Seagate drive from the other machine into it. Had E50 on it... Quick setup ! It developed the common 'stuck in molasses after an overnight at the menu page' problem.
There are three steps to caging this problem in another thread, http://mysettopbox.tv/phpBB2/viewtopic. ... c&start=45
& I went through all of them, without solving the problem.

I have recounted in another thread where I got results using the three steps on other machines- involves the saa7134 module. http://mysettopbox.tv/phpBB2/viewtopic.php?t=15449

So I moved in a new 250gig hard drive, & clean installed F1
& the machine. Went quick as Knopp-Myth installs do these days. Had the same ailment, every time as I moved thru the 3 steps of saa7134 disabling.

Being out of ideas, I put the e50 drive in, wiped it, & went retro- to a D1 distro clean install (one of these provides sunrise reliable service in my satellite dish recorder- albiet not HD) Set up quick & ran good... but STILL had 'molasses in the morning' at responding to commands.

Hardware problem ? I popped in another hard drive with Mepis 6 & let the machine run 24 hours on an open GL screensaver. Not a peep. Ran memtest 6 hours... not a peep.
Popped in a drive with Ubuntu (latest- forgot name) & put on Tvtime & ran that for 24 hours with the Dvico card. Works fine. No heat problems.

So I'm concluding a YMMV hardware issue with the software- perhaps a saa7134 type issue with ANOTHER module ?...

I open the floor for suggestions ??