Success!  that's good to hear that it was simple.  It's hard to imagine
the map sensor could cause such an issue, but I suppose it could.  I
would have expected such to throw a code though, as the system usually
has max and min values for sensor inputs and will throw a code if it's
over or below that. The MAP sensor isn't mechanical like some of those
other items you mention, so it almost always will throw a code if it
isn't working right.

Glad to hear it's fixed.