![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Okay. Saturday morning, I was getting ready to start work on a project that is overdue. I've planned to spend all of Saturday and all of Sunday working that project.
Saturday morning is interrupted by a phone call reporting a computer failure at work. All of Saturday, all of Sunday and all of Monday morning was spent resolving the problem.
Crashing clipper code, Odd errors from Lantastic network software, unhinged Microsoft networks, and hours of tail chasing.
The original problem, we think, was a corrupted index file on a dBase III dbf. In the midst of working the issue, a second machine running DOS 6 was rebooted. That machine failed to get on the network with an odd Lantastic error.
Many hours later, I discovered a bad port on a Linksys 24-port switch. It was always "on." Replaced the switch and the Lantastic problem was fixed. However the two machines now in the soup were in worse shape than before.
Hair pulling ensued.
Program tracing to figure out how the code was suppose to work finally led back to the corrupted index.
Now it all works.
Now my brain if fried.
This reminds me of my early Navy days in which I would spend many, many hours troubleshooting ship-wide systems with ever changing symptoms. I was always glad to get to the end of it, but if it went on too long, the level of satisfaction was insufficient to make up for the lost sleep. :)
It's been a long time since I spent much time working with compiled code or with Integrated Development Environments. I had forgotten the aspects I used to love. Step-wise debugging, for instance.
Saturday morning is interrupted by a phone call reporting a computer failure at work. All of Saturday, all of Sunday and all of Monday morning was spent resolving the problem.
Crashing clipper code, Odd errors from Lantastic network software, unhinged Microsoft networks, and hours of tail chasing.
The original problem, we think, was a corrupted index file on a dBase III dbf. In the midst of working the issue, a second machine running DOS 6 was rebooted. That machine failed to get on the network with an odd Lantastic error.
Many hours later, I discovered a bad port on a Linksys 24-port switch. It was always "on." Replaced the switch and the Lantastic problem was fixed. However the two machines now in the soup were in worse shape than before.
Hair pulling ensued.
Program tracing to figure out how the code was suppose to work finally led back to the corrupted index.
Now it all works.
Now my brain if fried.
This reminds me of my early Navy days in which I would spend many, many hours troubleshooting ship-wide systems with ever changing symptoms. I was always glad to get to the end of it, but if it went on too long, the level of satisfaction was insufficient to make up for the lost sleep. :)
It's been a long time since I spent much time working with compiled code or with Integrated Development Environments. I had forgotten the aspects I used to love. Step-wise debugging, for instance.