1/5/2055: We win our first 4 Big 10 games, all of them easily.
Rutgers was here for the first and we embarrassed them 84-34. We held them to 14 first half points. 15, 6 for Mal Niro, 14, 4, 5 for Buck, who played 32 minutes. Dub Wite turned an ankle early and we kept him out. It's nothing serious and he was back for our next.
A big computer issue in the engine room. I don't really know what it's about but the Chief Engineer told the Captain that it would be best if we stopped the ship until it gets fixed. We're stationary in space. This is not a problem. We can stay this way for as long as necessary.
This is, of course, a concern, but the Chief Engineer has his people and the geek squad working on it. Life support is not affected.
78-66 at Ohio State in the closest of the four games. We led by only 1 at the half but we took control early in the 2nd. Dub Wite had 21, 4, 5. 20, 4 for Vic Coop, 13, 7, 6 for Wolf. +34 in the paint.
77-51 at Indiana. We were never challenged in this game. 22, 9 for Abe Wolf, 16, 5, 7, 3 for Wite. 11 TOs.
At this point we were still at a standstill with the engine room computers still down. We don't seem to be anywhere near a solution.
“It's the main engine. We could run on the auxiliary in an emergency, but the computer people feel that there's a strong possibility that if we do that the problem may spread to the auxiliary engines. So unless there's big trouble we're better off just waiting it out until we figure out what's going on.”
Back home for a very easy 81-56 win over Minnesota. 18, 17, 3, with 5 blocks for Miro, 13, 13 for Coop, 15, 3, 3 for Stou. +19 RBs.
Great start to Big 10 play!
Still no idea what's going on with the engine room computers.
“It gets complicated trying to figure these things out. You dig deeply into the programs, and then more deeply and more deeply. One tiny little mistake in the code is often the culprit, and that can be miserably difficult to find. Other times, as a program is operating, it will somehow get corrupted, and it's a matter of figuring out when that happened. The program can run for a long time before the corruption affects it. So we work backwards and hope to catch the problem. No luck so far.”
“Can we just start over again? Print a new 3D engine and a new computer to run it?”
“The error would almost certainly exist in the new computer since the operating systems and programs would come from files in the corrupted computers. We just need to wait it out. We'll find it.”