Finally got the firmware installed. I was concerned about the driver / extractable mismatches with my Windows XP x64 edition HTPC, so I tried it via USB from my 32-bit XP laptop. Ended up getting 5 "Device Restart" failures with this setup. I had unplugged the RS-232 cable to be safe here.

Finally, killed the USB connection and tried the upgrade using RS-232 from my x64 machine. Everything worked fine there ... software got upgraded successfully, which was nice.

I still can't switch to VIDEO5 via RS-232 -- is this a known bug, or do I have something wrong on my end? That was my whole reason for performing the upgrade ... every other input switch I've tried via RS-232 works perfectly every time.

I'm following the protocol doc posted in this forum. I posted a thread on this previously.

Thanks in advance for any insight you can provide.

Have you checked with Dean Roddey ? He is involved with Charmed Quark (which was mentioned in the original RS-232 thread ), and has apparently worked a bit with controlling the 990.

To be honest, it seems a bit strange having to contact a 3rd party to answer such a simple question ... I guess I'll go through Outlaw support on this, and report back here with the answer.

Outlaw support would be the best place to start if you haven't gone to them already. I tossed Dean's name out because I remembered him and Prefect working on a third-party interface - and aside from the thread that they both posted in, there's been very little mention of folks using the 990's RS-232 control interface so the only forum members who are likely to have experience relating to the question would be them.

I do not have any trouble switching to Video 05 via RS-232.

Are you sending 83450CD4? I haven't read your other thread.

Regards,
John

Thanks -- just needed to know it was working for someone else so I could motivate myself to dig in.

Ended up being a config issue ... I'm running a different config on my dev machine in the office, and I forgot to update my script to leave the HTPC config in place on new deployments. I'll let you guess the problem:










*blush*

Thanks!

-Derek

Glad to hear you have it working!