Hi all,
got tired of my 2.6CE with Xaptr3 fragging so often when I switched it on that I decided to solder it on instead. Got lad at work to do it as he is handier with the soldering iron than I am.
We don't have a telly at work, but it booted up fine with no FRAG. So I took it home and plugged it all in. Powered it on and up pops the Slayer screen as normal. Happy days. Select XBMC and ... oh oh ... its hung on me (I'm still seeing the slayer screen with "loading"). Ah well, no worries, I'll just reboot.
So reboot again, up loads Slayer, select XBMC and again it hangs at the same point. Try a 3rd, and then a 4th. Still the same.
Try a 5th. Hangs again. I wonder if I have a DVD in there so press eject while its still stuck on the loading screen and the system reboots into the FlashBios screen. The eject button flashes green and orange (I think) when this happens. Strange.
So I power off and back on again. Up comes Slayer. I try a different program (Far Cry). Hangs for the 6th time loading. Try again. This time it works. It takes me into XBMC and everything seems fine there. So I power off and back on again. Hangs in Slayer. sigh
Now the funny thing is it always always always get me to the Slayer dash so the 2.6CE must be working fine, right? I haven't had a FRAG yet, which you would expect if its been soldered. The only thing different from the Xaptr3 install is that I have the LAN/HDD and D0 soldered on the back.
Once in a blue moon, when I was running with the Xaptr3 it would load slayer but hang running XBMC. If I powered off and back on again it would frag so I have always associated this hanging with a loose connection, solved by giving the case a squeeze.
But now the soldering looks fine with no spilled solder anywhere and I always get to Slayer.
Can any of the boffins here give me a diagnosis. Remember, it always boots to Slayer with no Fragging, but frequently fails to launch any further programs. And the eject button takes you the Flashbios, but only if Slayer has hung launching an app. Could it be the BIOS?
Thanks in advance
Mike
got tired of my 2.6CE with Xaptr3 fragging so often when I switched it on that I decided to solder it on instead. Got lad at work to do it as he is handier with the soldering iron than I am.
We don't have a telly at work, but it booted up fine with no FRAG. So I took it home and plugged it all in. Powered it on and up pops the Slayer screen as normal. Happy days. Select XBMC and ... oh oh ... its hung on me (I'm still seeing the slayer screen with "loading"). Ah well, no worries, I'll just reboot.
So reboot again, up loads Slayer, select XBMC and again it hangs at the same point. Try a 3rd, and then a 4th. Still the same.
Try a 5th. Hangs again. I wonder if I have a DVD in there so press eject while its still stuck on the loading screen and the system reboots into the FlashBios screen. The eject button flashes green and orange (I think) when this happens. Strange.
So I power off and back on again. Up comes Slayer. I try a different program (Far Cry). Hangs for the 6th time loading. Try again. This time it works. It takes me into XBMC and everything seems fine there. So I power off and back on again. Hangs in Slayer. sigh
Now the funny thing is it always always always get me to the Slayer dash so the 2.6CE must be working fine, right? I haven't had a FRAG yet, which you would expect if its been soldered. The only thing different from the Xaptr3 install is that I have the LAN/HDD and D0 soldered on the back.
Once in a blue moon, when I was running with the Xaptr3 it would load slayer but hang running XBMC. If I powered off and back on again it would frag so I have always associated this hanging with a loose connection, solved by giving the case a squeeze.
But now the soldering looks fine with no spilled solder anywhere and I always get to Slayer.
Can any of the boffins here give me a diagnosis. Remember, it always boots to Slayer with no Fragging, but frequently fails to launch any further programs. And the eject button takes you the Flashbios, but only if Slayer has hung launching an app. Could it be the BIOS?
Thanks in advance
Mike