Ok all, I am dumber than I thought...I ran the codes again and it is P0455 (my orginal post said p0445).

I am guessing this changes things??

(I appreciate all he help)

^That's a large leak in the evap system. Some readers call it a "large" leak, some call it a "gross" leak. That's the code I was having when my evap/charcoal canister and/or evap valve failed.

So, might want to look into the valve Helihover was mentioning.

Will do.

Still seems strange that I can reset the light at all....I realize that means the problem is still there, but if I only have the ignition on you (or me, I guess) would think I could reset it and once I turn the vehicle on, the light would illuminate again....

Update: I dug around more today after installing new gas cap....that's hissing in the YouTube link was a hose to the charcoal canister....I am guessing that was the issue.

The tube to the charcoal canister had to have been disconnected for about 3 weeks...my commute is short, so maybe due to he low miles it took that long to illuminate the light.

Regarding the yellow SES light, I can seem to figure out how to reset the light via the BMW Scanner...?? In fact, I don't even find an "error" when scanning the car. (There are other errors, but nothing for the evap system)

My other code reader is just obdII, I am guessing I need CAN to reset it??

Maybe a trip to Autozone?? I really don't want to wait another 3 weeks to get the light off....

I think trouble codes should be used as indicators of where to look rather than literally interpreted. Even then it is important to bear in mind they can be misleading. As far as the SES light, since the hose has been off for some time the cause of the SES may be another issue. Usually the SES light goes out on its own when the problem has been corrected.

Light reset via Autozone, we will see what happens in the days/weeks that follow.

Thanks everyone for the help.

For the record, your BMW Scanner or yout OBD II Scan Tool should both be able to reset the computer. Scan tools can read any of the protocols that are used. It knows which protocol is used by the wires that the data is presented on. I forget the pin assignments, but there are 16 pins in the OBD II Data Port, but not all of them are used on any given car. They pump data from one protocol down pins 6 & 7, for example, and the other protocol will be on 8 & 9. I probably gave the wrong pins, but the idea is valid -- a set of pins us used for one protocol, and a different set is used for another.

Part of the OBD II specification is that the diagnostic equipment must be commonly available. At least part of the problem with OBD I was that consumers were getting hit with fees for nothing other than to plug the car into a diagnostic reader. The shops justified the fees by saying that each car used a different system and they had to have all kinds of equipment that was costly to do basic service, and consumers that bought a scan tool for an OBD I car had to buy a different tool if they sold the car and bought something else. This was not only true from one automaker to another, but was sometimes true from one model to another from the same automaker. OBD II says that all cars have to be able to be diagnosed using the same scan tool. That is, engine management systems have to all be accessed with the same tool, other systems on the car can use proprietary diagnostics but the engine management has to use common equipment. This means that whether a car uses the CAN protocol or one of the others, the same scan tool can be used. The scan tool determines the protocol by the physical pins that the protocol uses.