Unrecoverable read error on source.
源盘上不可恢复的读错误。
Read error messages in the XM console carefully
仔细阅读XM控制台中的错误消息
Database read error: The link you specified was unavailable, incomplete or deleted already!
读取数据错误︰您要浏览的连结无效，可能连结不完整或数据已被删除！
I did look at Microsoft KB for This, but, it does not have anything for the registry read error.
我也看了微软KB这，但是，它没有任何的注册表读取错误。
You should take the time to read error messages carefully, but don't assume that everything they say is correct.
所以你得花点时间仔细阅读错误信息，但不要轻易就认为出错信息说的内容都是完全正确可靠的。
Read the error message carefully because it includes a description of the problem.
请仔细阅读错误消息，因为它包含对问题的描述。
He suggests the error happens because when learning to read children first have to unlearn that older survival skill.
他提出这种错误发生是因为当学习阅读的时候孩子们首先需要摒弃旧的技能。
Attempting to read the file directly into an XML parser results in an error.
如果试图将文件直接读入一个xml解析器，就会导致错误。
The code is easier to read, easier to maintain, and (I would say) even encourages you to add error handling, which is always a benefit.
这样的代码更易于阅读、维护，而且我要说，甚至要鼓励您添加错误处理机制，它通常都能带来好处。
Each time a corresponding client socket contains any read, write or error operations, the corresponding callback function is called.
每当对应的客户端套接字包含读、写或错误操作时，调用对应的回调函数。
Read the error message or messages carefully-it might be obvious what has gone wrong.
请仔细阅读错误消息或者相关的消息，可以清楚地看到究竟什么地方出了错。
The last token read (closing parenthesis) is not the cause of the error.
最后一次符号读取(结束括号)并不是这个错误的根源。
Now read that error message again.
现在再次读取错误消息。
V8 will throw an exception if an error occurs - for example, when a script or function attempts to read a property that does not exist, or if a function is called that is not a function.
当错误发生时，v8会抛出一个异常。比如，当一个脚本或者函数试图去访问一个并不存在的属性，或者调用一个并不是函数的函数。
The back-end system should not generate the error message in English if it is expected to be read in Cantonese.
如果期望用粤语读取，后端系统就不应该用英语生成错误消息。
Otherwise, Ekman summed up, users risk what he calls "Othello's error": "Othello read Desdemona's fear accurately.
埃克曼总结说，否则，用户会冒他所谓的“奥赛罗式失误”之风险。 “奥赛罗准确读懂了黛丝狄蒙娜的恐惧。
此时需要仔细阅读错误消息。
Read should return exactly the number of bytes requested, except on EOF or error; otherwise, the rest of the data will be substituted with zeroes.
除非碰到EOF或出现错误，否则read应该返回所请求的字节数的数据；否则，其余数据都会被替换成0。
Without this option, any read or write operation will return an error if the server wants a new handshake, setting the retry flag in the process.
如果没有这个选项，当服务器希望进行一次新的握手时，进行读或写操作都将返回一个错误，同时还会在该过程中设置retry标记。
The read function returns the number of bytes read (up to the maximum that you specify), -1 on error, or zero if the end of the file has been reached.
read函数返回读取的字节数（最高为您指定的最大值）；或者 -1，表示错误；或者0，如果已经到达文件末尾。
Now we can access it (i.e., read it) but we can't update it because the variable is final; another compiler error!
现在run方法可以访问counter变量了(仅仅是读取而已)，但却无法更新该变量，因为它是final的，这又导致了另一个编译错误！
Simulates reading size bytes starting at address addr, generates any purify errors that read would cause, and calls purify_stop_here upon error.
模拟阅读开始于addr的size字节，产生读取将会导致的任何purify错误，根据错误调用purify_stop_here。
However, the CLI does make one thing much, much easier: finding the error messages so you can read them in the first place.
不过，CLI确实使一件事变得更加简单：找到错误消息，以便可以在第一位置读取这些错误消息。
The code would be a lot bigger and therefore harder to read because of all the error-handling code.
由于需要这么多错误处理代码，该代码可能更大，因此更难阅读。
Unable to read file due to Disk or Network error.
由于磁盘或网络错误而无法读取文件。
Utility error processing solution has been added. This enables you to read data within UDMA mode for cases where previous version could read the data only in PIO mode.
实用程序的错误处理解决方案已添加。这使您可以读取数据，在UD MA模式情况下，以前的版本可以读取数据仅在PIO模式，。
You may fail to connect to a site through IPv6 and have an error message sent to the requesting application on your computer (read: web browser).
你有可能在始于IPv6的情况下出现连接失败，并会有一条出错信息发送给你计算机上的请求应用(比如说：web浏览器)。
Reason is usually read or write data error, may be CD quality problems or disk drive read ability not beautiful, or written to the hard disk error.
原因一般是读取或写入数据出错，可能是光盘质量问题或光驱读盘能力不佳，或写入硬盘出现错误。
With Committed read isolation, it will give this error: 244: Could not do a physical-order read to fetch next row.
如果使用Committedread隔离级别，则会发生以下错误：244：couldnotdoaphysical - orderreadto fetch next row。
With Committed read isolation, it will give this error: 244: Could not do a physical-order read to fetch next row.
如果使用Committedread隔离级别，则会发生以下错误：244：couldnotdoaphysical - orderreadto fetch next row。
应用推荐