>But the real question is.... where the heck is the eater eggs? I know there is at least one but can't ever get anyone to come off it...

An easter egg is a hidden feature usually to give credit to some or all of the people who worked on the product. One of the early versions of Excel for Windows had an easter egg in the About dialog, where you hit certain keys in order, then a visual part of the game DOOM by ID was shown, with credits to the entire team (all names) to the Excel team, like credits scrolling up at the end of a movie.

Easter eggs in products are no longer allowed. The government and other customers starting questioning that if a company like Microsoft didn't know or have control of what some developer team members included in a shipping product, it's lack of quality control and possible security risk. So in the late 90s, word came down from Bill Gates that if anyone added an easter egg to a product, they would be fired immediately. An easter egg is not the same as an undocumented feature. Microsoft losing the DOJ case in the last 90s required Microsoft to document all Windows features, to be fair to competitors. But there are often undocumented features in products, usually not intentional.

BTW, when I worked at JPL, Bill Anderson who sat next to me use to get new versions of FoxPro 2.x and VFP 3.0 betas, when there was only about 25 people on the early beta cycle including a few of us at JPL, and he'd run MODIFY FILE vfp.exe, then use the FoxPro text editor to scan the FoxPro and VFP binary file EXE looking for strings. An early build of VFP 3.0 had a string "Object Basic". I once brought it up to the Fox team, and for a while they thought they had a major leak within the team at Microsoft when they were experimenting with some Visual Basic code embedded within Visual FoxPro. :)