![]() ![]() Its really easy to build in assumptions about how data that is written arrives at the reader (assuming one blob or various kinds of fragmentation, becoming multiple fragments or different subdivisions of the data). Timing and chunking issues are a particularly awkward area and are very prone to subtle changes over time. This is the problem with old Windows software, or software from any OS. Most of what is in the event log IS gibberish unless you have a passionate interest (wrote the software that produced it) in whatever it is. If its a disk error then you'd see something in the event viewer complaining (with a red icon) about hardware. The reference to read error could be to disk, network or inter-process communication.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |