如何阅读bios eprom中的位置 [英] how do I read a location in the bios eprom
问题描述
究竟如何阅读bios eprom中的特定位置。
（例如debug.exe位置ffff：0000）
just4me< ju ***** @ nowhere.com>潦草地写道：我如何读取bios eprom中的特定位置。
（例如debug.exe位置ffff：0000）
你的C问题是什么？
-
/ - Joona Palaste（pa*****@cc.helsinki .fi）-------------芬兰-------- \
\-- http://www.helsinki.fi/~palaste ---------------- -----规则！ -------- /
To doo bee doo bee doo。
- Frank Sinatra
" just4me" <菊***** @ nowhere.com>写道：
究竟如何读取bios eprom中的特定位置。
（例如debug.exe位置ffff：0000）
您的问题超出了comp.lang.c的范围，它只讨论了标准C编程语言
，包括标准C
图书馆。与人们期望的很多
相比，这是一个非常狭窄的话题。
为了您的方便，下面的列表包含的主题不是
on-topic for comp.lang.c，并建议您浏览新闻组
如果您对这些主题有疑问。在发布到任何这些新闻组之前，请务必遵守正确的
网络礼节。特别是，你应该阅读小组的章程和常见问题，如果有的话（常见问题是
来自 www.faqs.org 和其他来源）。如果那些人没有回答你的问题，那么你应该浏览至少两周
的近期文章，以确保你的问题还没有。
已被回答。
*特定于操作系统的问题，例如如何清除屏幕，
访问网络，列出目录中的文件，或者阅读
管道子进程的输出。这些问题应该是针对特定于操作系统的新闻组，例如
comp.os.ms-windows.programmer.misc，comp.unix.programmer或者
comp.os.linux.development.apps。
*编译器特有的问题，例如安装问题和
标题的位置文件。在
编译器特定的新闻组中询问这些，例如gnu.gcc.help或
comp.os.ms-windows.programmer.misc。有关编写
编译器的问题在comp.compilers中是合适的。
*特定于处理器的问题，例如关于
汇编的问题和机器代码。 x86问题适用于
comp.lang.asm.x86，嵌入式系统处理器问题可能适用于comp.arch.embedded中的
。
*特定于ABI的问题，例如如何将汇编
代码连接到C.这些问题都是处理器和
特定于操作系统的问题，通常应该是在特定操作系统中询问
新闻组。
*算法，除了有关
算法的C实现的问题。 如何在C中实现算法X？关于算法的C实现不是一个问题，它是一个
的源代码请求。新闻组comp.programming和
comp.theory可能是合适的。
*使C与其他语言互操作。对于这种互操作，C没有
设施。这些问题应该直接指向系统或编译器特定的新闻组。 C ++
具有与C互操作的功能，因此请考虑
comp.lang.c ++来解决这些问题。
* C标准，而不是标准C.关于
的问题C标准最好在comp.std.c中询问。
* C ++。请不要将有关C ++
的问题发布或交叉发布到comp.lang.c.在C ++新闻组中询问C ++问题，例如comp.lang.c ++或comp.lang.c ++。版本的
。
*测试帖子。请在一个用于测试的新闻组中进行测试，
，例如alt.test。
news.groups.questions是一个讨论适当的好地方
给定主题的新闻组。
-
在我的Egotistical Opinion中，大多数人的C程序应该向下缩进六英尺b $ b英尺向下并覆盖着污垢。 - Blair P. Houghton
" just4me" <菊***** @ nowhere.com>在消息中写道
新闻：cc *********** @ news3.infoave.net ...我怎样才能读取具体位置在bios eprom。
（例如debug.exe位置ffff：0000）
Exactly how do I read a specific location in the bios eprom.
(such as debug.exe location ffff:0000)
just4me <ju*****@nowhere.com> scribbled the following:Exactly how do I read a specific location in the bios eprom.
(such as debug.exe location ffff:0000)
What was your C question?
--
/-- Joona Palaste (pa*****@cc.helsinki.fi) ------------- Finland --------\
\-- http://www.helsinki.fi/~palaste --------------------- rules! --------/
"To doo bee doo bee doo."
- Frank Sinatra
"just4me" <ju*****@nowhere.com> writes:
Exactly how do I read a specific location in the bios eprom.
(such as debug.exe location ffff:0000)
Your question is outside the domain of comp.lang.c, which discusses
only the standard C programming language, including the standard C
library. This is a remarkably narrow topic compared to what many
people expect.
For your convenience, the list below contains topics that are not
on-topic for comp.lang.c, and suggests newsgroups for you to explore
if you have questions about these topics. Please do observe proper
netiquette before posting to any of these newsgroups. In particular,
you should read the group''s charter and FAQ, if any (FAQs are
available from www.faqs.org and other sources). If those fail to
answer your question then you should browse through at least two weeks
of recent articles to make sure that your question has not already
been answered.
* OS-specific questions, such as how to clear the screen,
access the network, list the files in a directory, or read
"piped" output from a subprocess. These questions should be
directed to OS-specific newsgroups, such as
comp.os.ms-windows.programmer.misc, comp.unix.programmer, or
comp.os.linux.development.apps.
* Compiler-specific questions, such as installation issues and
locations of header files. Ask about these in
compiler-specific newsgroups, such as gnu.gcc.help or
comp.os.ms-windows.programmer.misc. Questions about writing
compilers are appropriate in comp.compilers.
* Processor-specific questions, such as questions about
assembly and machine code. x86 questions are appropriate in
comp.lang.asm.x86, embedded system processor questions may
be appropriate in comp.arch.embedded.
* ABI-specific questions, such as how to interface assembly
code to C. These questions are both processor- and
OS-specific and should typically be asked in OS-specific
newsgroups.
* Algorithms, except questions about C implementations of
algorithms. "How do I implement algorithm X in C?" is not a
question about a C implementation of an algorithm, it is a
request for source code. Newsgroups comp.programming and
comp.theory may be appropriate.
* Making C interoperate with other languages. C has no
facilities for such interoperation. These questions should
be directed to system- or compiler-specific newsgroups. C++
has features for interoperating with C, so consider
comp.lang.c++ for such questions.
* The C standard, as opposed to standard C. Questions about
the C standard are best asked in comp.std.c.
* C++. Please do not post or cross-post questions about C++
to comp.lang.c. Ask C++ questions in C++ newsgroups, such
as comp.lang.c++ or comp.lang.c++.moderated.
* Test posts. Please test in a newsgroup meant for testing,
such as alt.test.
news.groups.questions is a good place to ask about the appropriate
newsgroup for a given topic.
--
"In My Egotistical Opinion, most people''s C programs should be indented six
feet downward and covered with dirt." -- Blair P. Houghton
"just4me" <ju*****@nowhere.com> wrote in message
news:cc***********@news3.infoave.net...Exactly how do I read a specific location in the bios eprom.
(such as debug.exe location ffff:0000)
这篇关于如何阅读bios eprom中的位置的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
