On June 20th I started a thread  here about how I encountered many runways that did not have glideslopes.  After working other forums and many e-mails with Microsoft Tech Support, I finally solved my problem and would like to pass on my odyssey to you.

Bgl files were corrupted either inadvertently by me or during the initial installation of FS2002.

The solution was located in SCENEDB>westhem>(unne, usnw, usse, etc.)>scenery>(usseils.bgl, usneils.bgl, usnw.bgl, etc.)

I went to FS2002 program disk #3 and copied from SCENEDB the contents of folders usne, usnw, usse, etc.  to the corresponding folders in my FS2002. It worked.

I used Easynavs 2000 to open up bgl's usneils, etc. and determined whether or not there were  actually glideslopes programmed. I also went to http://www.airnav.com/airports/ ; to see if the real world runways in question had glideslopes.

I was helped mostly by searching a number of forums, while Microsoft Tech Support kept wanting me to uninstall/reinstall FS2002, which I refused to do.

FYI, there were many people on the forums that  mentioned that runway 28L at Portland(OR) Int'l had the localizer and  glideslope doing crazy things. You can get a fix at AVSIM by searching for John Kramer and file usnwils.zip. It fixed it for me.

It was quite a ride but everything is working now.. Thanks again to all who gave input to my plight.

Regards,

Jeffrey