Actisys problems

[Freegoo]

Oh man. My system was working flawlessly so I decided to do some cable cleanup behind the PC. I unhooked most the cords and untangled and ran them around the back. Boot back up and I notice that Sage is no longer changing channels. I check to make sure that the IR is still pointed at the Dish Receiver (it is) and then follow the cord to ensure it's plugged in (it is). I go to setup and remove my source and add a new one, when I get to the IR tuner part it tells me that it cannot find Actisys on com1-4 (should be com1). Could be software so I check to make sure I don't have any new programs running in Windows Task Manager. Seeing nothing I shut down, switch to port 2 and have same problem. Thinking "Oh crap - I must have unplugged the cord while the computer was still on and fried the cord" even though I was pretty sure that I had turned it off. None the less, I ordered a new cord and it came in today.

Bad news, almost same results. I plug it in and Sage finds it. But still doesn't change the channels. Watching the transmitter shows that it isn't lighting up either. I've tried adding it manually, but Sage eventually errors out saying the receiver didn't detect any frequencies. I've tried switching ports again, plugging/unplugging it multiple times (making very sure that the computer is off) and Sage never changes the channel. Though sometimes it can't detect Actisys in the setup area.

Vital stats: amd 2100, hauppage 250, ati 9200, win xp home, 512 mb ram, 125 gb hard drive, firefly remote, sound blaster live sound card. Sage 2.0.20 latest drivers, windows updated.

Any suggestions?
Thanks

[JUC]

I know this is obvious but have you tried reinstalling sage?
JUC

[Freegoo]

Not yet, but this is weird... last night I shut it down and put the extender cable back on. When I booted it back up I zipped through setup and it started working. Not sure how consistant it's going to be with all the trouble it's given me, but I guess for now it's working.

I'm thinking I should have went the USB route. Serial ports are so troublesome.

[Freegoo]

Just a belated update on this problem. This was completly unrelated to Sage TV and involved my Firefly remote. Something about the X10 driver locking up com ports. Not sure why it waited 6 weeks to give me problems, but thats computers I guess.

It is discussed here: Snapstream Firefly Forum Support page

Attached is the fix for the problem, to install make sure you read Brett's stuff:

Please try doing the following...

Please I can not STRESS it enough, please make sure you do these steps EVEN if you are sure of the answer beforehand.

Please reboot your computer
Run BTV for the first time, do the channels change?
Apply the Fix and REBOOT your computer
Run BTV for the second time, do the channels change, does the remote work?

What the attached file will do is disable the serial portion of the driver. Now, we have CONFIRMED already that it should not effect firefly, yet we are not able to reproduce the X10nets.exe error and this is where you guys come in to the solution.

Again, please make sure to do exactly these four steps, even if you are sure of the answers beforehand. Please respond back with your results, this will help us assure it is fixing the issue.

Thanks,

-Brett