As noted on the Western Regionals post. I ran into my very first problem with the "new" SIDS/STARS procedures using the runway transitions on the RLSKs.I can replicate this every time. For the record, I am using the AIRAC-0201 / WP-0201JB and the KLAS_V2.zip package dated 4-17-02 1159PM.Program a flight, say KABQ-(anything)-PGS.LYNSY1-KLAS-all is fineSelect rwy 19R and then using the RLSKs select the runway trans from LYNSY1-again, all is fineNow change the runway to 19L and once again RLSK the trans from LYNSY1-NOW you got a problem, or at least I doAll waypoints have disapeared from the LEGS page and from the EHSI.When I try to reenter PGS on the LEGS page, or anything, to get the arrival back up the FMC locks up completely. My friends all start laughing (LTFAO in fact) and I rip the printed STAR from my binder and start flying headings till approach (after he LHFAO) assigns vectors for the visual. Not really that big a problem unless it's 3AM and you get switched back to 19R with a text controller when on a 3 mile final and then don't get clearance to land. Whew! I trust that someone will sort this out.Thanks guys, I really do appreciate the procedures you have done so much to provide all of us.

I'll try to look into this as I put this package together.Lee Hetherington (KBOS)

Mike, I was able to reproduced. I went to the ARR page for KLAS and had LYNSY1, PGS, 19R, LYNSY1 selected and everything looked fine. Then I went to the ARR page again and selected just 19L and LYNSY1 app transition and LEGS was empty. LYNSY1 and PGS were still shown as (active).Wade, is this a problem with the FMC getting confused in some way?My workaround that I have gotten into the habit of is selecting all four ARR entries any time I change one. In this case, to change 19R to 19L, I select LYNSY1, PGS, 19L, LYNSY1. Probably not optimal, but I do not know what else to do?Lee Hetherington (KBOS)

Bump in hopes that Wade catches your question.