国产91色综合久久免费,久久99中文字幕久久,男女久久久国产一区二区三区

发布一个日语汉字假名�{换��Y件给大家

HuYi — Wed, 30 May 2007 03:03:00 GMT

主要使用了微软的WTL和IME技术，相关链接�Q?br>http://www.shnenglu.com/huyi/archive/2006/03/15/4207.html

下蝲地址�Q?br>http://www.shnenglu.com/Files/huyi/kanji.rar

使用方式�Q?br>选中不知道读音的日文汉字�Q�中国汉字无效）�Q�然后Ctrl+C卛_��。在�pȝ��托盘图标上点��d��键，可以打开关闭监视功能�?br>
软�g截屏:

2007�q?�?1�?br>攑և�1.5版，改动如下�Q?br>1.��化了界面，改进了前一版本中显�C�错位的问题�?br>2.3�U�后查询�H�口自动��时�?br>3.做了部分�q��o�Q�能�q��o掉许多非日文汉字的东�ѝ�?br>4.左键默认立即关闭�H�口�Q�右键定住窗口，使之不会自动消失�?br>新的截图��׃��攑և�了，��M��漂亮了很多，希望大家�l�箋支持�?br>

HuYi 2007-05-30 11:03 发表评论

��成员函��C��为std::for_each的第三个参数

HuYi — Fri, 22 Dec 2006 07:10:00 GMT

vector books;
void CBookEditDlg::ForEachBookFunctor(Book book)
{
    ......
}
for_each(books.begin(), books.end(), std::bind1st(mem_fun(&CBookEditDlg::ForEachBookFunctor), this));

关键点在于mem_fun和bind1st的��用�?br />
for_each的实��C��最核心的一个调用：functor(*iterater);
�׃��c�非静态成员函敎ͼ�必须在实例上调用�Q?instance->*pfn)(params);
所以for_each无法直接使用传过�ȝ��函数地址�Q�函数指针的�W�一个参数是�cȝ��一个实例指针（this指针)�Q�所以必��L��办法把这个指针传�q�去�Q��用std::bind1st�Q?br />
关于mem_fun的一些资料，请参�?br />http://www.stlchina.org/documents/EffectiveSTL/files/item_41.html

对于带两个以上参数的成员函数�Q�用stl是不能达到目的的�Q�因为mem_fun只能生成不带参数�Q�或者是仅带一个参数的函数对象�Q�functor)�Q�bind1st和bind2st也只能对�W�一个或者是�W�二个参数进行绑定�?br />要实现对��L��数量参数的成员函数生成functor�Q�必��d��stl�q�行扩展�Q�所�q�boost已经做到了这点，boost::bind和boost::mem_fn��是更加泛化的std::bind1st和std::mem_func

    void ForEachClassFunctor(Class c, CTreeItem treeItem)
    {
        treeView.InsertItem(c.name.c_str(), treeItem, NULL);
    }

    void ForEachBookFunctor(Book book)
   {
       CTreeItem treeItem = treeView.InsertItem(book.name.c_str(), NULL, NULL);
       vector v;
       v.push_back(Class(0,0,"nameClass1", "titleClass1"));
       for_each(v.begin(), v.end(),
            boost::bind(boost::mem_fn(&CBookEditDlg::ForEachClassFunctor), this, _1, treeItem));
   }

HuYi 2006-12-22 15:10 发表评论

HuYi — Fri, 22 Dec 2006 07:09:00 GMT

今天用到了Sqlite,�׃��它内部是使用UTF-8�~�码�Q�所以在Windows应用中出��C��q��?br />��单的搜烦了一下，�怺�转换的方法很多，我觉得比较好的，�?br />http://www.vckbase.com/document/viewdoc/?id=1444

我稍微改�q�了一�?

    static WCHAR* UTF82Unicode(WCHAR* pBuffer,char *pSource, int buff_size)
    {
        int i, j, max;
        char* uchar = (char *)pBuffer;
        max = buff_size - 2;
        for(i = 0, j = 0; pSource[j] != '\0'; i += 2, j += 3)
        {
            if (i > max) {
                break;
            }
            uchar[i+1] = ((pSource[j] & 0x0F) << 4) + ((pSource[j+1] >> 2) & 0x0F);
            uchar[i] = ((pSource[j+1] & 0x03) << 6) + (pSource[j+2] & 0x3F);
        }
        uchar[i] = '\0';
        uchar[i+1] = '\0';
        return pBuffer;
    }

在Windows中的话，�q�有更简单的�Ҏ��完成转换�Q?br />比如从UTF-8到Unicode:
    WCHAR buff[255];
    MultiByteToWideChar(CP_UTF8, 0, argv[i], -1, buff, sizeof(buff));
    item.name = W2A(buff);

argv[i]是要转换的字节数�l?img src ="http://www.shnenglu.com/huyi/aggbug/16734.html" width = "1" height = "1" />

HuYi 2006-12-22 15:09 发表评论

HuYi — Sat, 14 Oct 2006 08:45:00 GMT

File�c�L��w��ƈ不持有文件句柄，它只是集中了一�p�d��Ҏ��件的操作�Ҏ��Q�如Create�Q�Open�{�等。这些方法全部都是静态的�Q�也不进行�Q何的安全��，仅仅是直接调用pspsdk来完成�Q务，如果出现错误�Q�则�q�回负倹{�?
File的Open�{�方法可以创建针�Ҏ��定文件读写的��对象FileStream�Q�句柄由FileStream自己创徏和持有管理，File::Open只是�?wbr>达�\径信息�?
可以把File看作是一个门面，集中了对文�g的所有操作，�q�且不需要创建File对象��可以直接执行这些操作。所以说File为文件的单一操作提供了快��L��便的方式�?
除了几个创徏FileStream��的操作外，其他操作都不会长期占用句柄资源，遵��@"句柄创徏-执行具体操作-释放句柄"的步骤�?

如果需要频�J�的操作文�g�Q�则需要一个类来长期持有句柄，避免�l�常性的打开和关闭文�Ӟ��故此引入FileInfo�c�R��FileInfo执行Append�{�操作时�Q?wbr>都是使用事先打开的文件句柄�?
同时�Q�FileInfo也可以创建FileStream实例�Q�但�q�个时候，文�g的句柄生命周期应该由FileInfo来管理，FileStream可以使用�q�个句柄�Q�但不能�l�束其生命周期，FileStream::Close()�Ҏ��仅仅使这个流处于关闭�Q�不可读写）状态，但�ƈ不实际关闭文件句柄�?
�q�种情况下，FileInfo所创徏的FileStream::Close()的行为和前面File所创徏的FileStream::Close()行�ؓ有差�?wbr>。因为File�q�不持有句柄�Q�所以它创徏了FileStream对象后，句柄应该由FileStream来管理。但FileInfo所创徏的FileStream是��用的FileInfo所创徏好的句柄�Q�所以它�q�不�Ҏ��句柄负责�?

实现�{�略�Q?
1.使用��Z��l�承的多态或��Z��模板的静多态�?
2.使用函数回调。把Close做成调用函数指针�Q�通过不同的FileStream构造函数调用，来设�|�指针指向不同的Close函数实现。（关闭句柄或不关闭句柄�Q?
�q�两�U�做法的优劣性正在考证中，��h��出意见�?

补充�Q�File和FileInfo的关�p�d��dotnet中也有体玎ͼ�不过他们主要是从错误��方面考虑�?br />最�l�的目的是要为客��h��供一个统一的界面，所以不能用太复杂的模板�?br />
�l�过慎重考虑�Q�我�q�是军_��用虚函数�Q�放弃了模板�?br />

HuYi 2006-10-14 16:45 发表评论

��Z��么要用�?(”取代�?�?

HuYi — Fri, 13 Oct 2006 05:50:00 GMT

在做日志接口的时候，真实的接口函数应该是如下样式的：
__static_logger__.log(int level,const char* fmt, ...);
�q�里使用了printf�c�M��的技术：可变参数�?br />�q�个技术可以动态的替换字符串fmt中的内容�?br />同时�Q�这个方法可能会被重载，用于不需要可变参数的情况�Q?br />__static_logger__.log(int level,const char* fmt);

通常�Q�我们还会定义一些辅助用的宏�Q?br />#define KLOG(X) \
    do { \
        KDBG::printf X; \
    } while (0)

使用的时候，必须按照下面的格式：
KLOG((LM_ERROR, "%s\n", strerror(errno)));
注意�Q��用了双层的括号�?(�?br />
��Z��么不把宏�Ҏ��Q?br />#define KLOG(X,Y,...) \
    do { \
        KDBG::log(X,Y,__VA_ARGS__); \
    } while (0)s
从而按如下的“标准�Ş式”来使用LOG呢？
KLOG(LM_ERROR, "%s\n", strerror(errno));

�{�案是宏不能像函数那样重载，KLOG宏只能有一个，��是最后定义的那个�Q�也��是能接受的参数个数是固定的�?br />

HuYi 2006-10-13 13:50 发表评论

HuYi — Mon, 31 Jul 2006 10:26:00 GMT

1.8T发动机��L�� 55000�?br />大众原厂MO250变速箱 20000
1.8T半��u 3000
BMC�q�汽 2500
�q�动�Ƒ֮�来凸轮��u 3000
�q�动�Ƒ֮�来涡轮�?800
SUPERSPRING全段排气 9800
�� 7000
法雷奥离合器 3000
原厂180匹电脑程序�?800
DENSO火花塞�?00
HKS泄气阀 2800
4公斤回��a阀 300

SPAXJ减震器�?000
NEUSPEED前后防倾杆 2000
原厂�?12mm�?56mm刹�R�?000
仿RS418寸轮圈�?200
�c�_��林PS2轮胎 10000

自加工前后包图b?000
自制机头盖�?500
氙气大灯 1800
HKS涡轮压力表�?00
SPARCO方向盘�?800
4MOTION档把 1200

HuYi 2006-07-31 18:26 发表评论

HuYi — Thu, 27 Jul 2006 16:02:00 GMT

�q�个题目大了点，不适合我这�U�刚参加工作不久的�h来回�{��?br />
Blog很久没有更新了，�{�应了朋友写点这斚w��的看法，��在�q�里表达一下自��q��意见�Q�抛砖引玉�?br />
架构师也有不同的�c�d��。我主要惌��Y件方面的架构师�?br />
一是体�pȝ��构��的，要负责��品的部��v�Q�硬�Ӟ��|�络�{�等很多整体上的东西�Q�这一�c�M��仅需要扎实而广泛的基础知识�Q�更需要经验，特别是在大企业工作的�l�验。这一点也是在单位看了一些日本�h的设计，才慢慢体会到�?br />
二是软�g本��n的架构，是我想重点讨论的�?br />软�g应用的领域不同，架构也有很大的差别，嵌入式有嵌入式的做法�Q�电信��Y件有电信软�g的做法，企业应用有企业应用的做法�Q�桌面有桌面的做法。如果要全部讨论�Q�我没有�q�个实力�Q�所以只说最常见的企业应用开发和桌面软�g开发�?br />
最重要的基��Q�我觉得是OO�Q�不��实际编�E�设计是否是OO的，都应该了解，具备OO的思想。强调一下，采用最合适的思想和手�D�|��开发��Y�Ӟ��而不一定非要用OO�Q�或者是非不用OO。我比较坚信的一�Ҏ��Q�当代及未来的程序员�Q�或许在实际工作中不需要用到OO�Q�比如说搞嵌入式开发，或者Linux底层斚w��开发的�Q�事实上�Q�Linux中也用到了OO�Q�比如文件系�l�）�Q�但必须是了解OO的�?br />
一�Q�万丈高��g��地�v�Q�一力承担靠地基

1。敏捯��Y件开�?br />

��Z��么推荐这本呢�Q�其实是推荐�q�本书的前半部分。因为它的前一半一定可以让��目一斎ͼ�让�h知道OO除了��装�Q��承，多态以外，�q�有更多的东西，而且�q�本书十分容易懂�?br />

2。《OOP启思录�?br />

�l�对的经典，不过��比较枯燥了。全部是关于OO的理论及设计准则。所以虽焉��常基��Q�但�q�没有作为第一步推荐的书。看�q�个�Q�需要对OO有了一定的了解�Q�才能坚持下厅R�?br />
二，��摸瓜�Q�寻根究�?br />初学的�h常说�Q�OO��是对象�Q�就是封装��承多态。对�Q�没错，但语�a�是怎么支持�q�些OO�Ҏ��的呢？

1。深度探索C++对象模型

我们CPP�_�丝有福了，本书探烦了C++对OO的支持，底层对象模型实现�{�非常有价值的内容。同��h��相对枯燥的，而且颇具隑ֺ��Q�所以学习之前最好对C++�q�门语言熟悉�Q�而且有兴��去了解它的本质�?br />对于非CPP帮派成员�Q�看�q�个可能比较困难�Q�但我也找不出其他替代的学习书籍了，知道的朋友请补充�?br />
�W�三�Q�练�?/strong>
内功基础有了�Q�就该练习剑招拳�׃��?br />
软�g设计的剑谱，��是设计模式�Q�就是前人�ȝ��出来的套路，当然你也可以自创。但自创之前�Q�一定要多看多想�Q�充分吸取前人的�_�N��?br />
1�Q�Java与模�?br />

国�h写的不得不推荐的一本好书（也有很多��他太啰嗦�Q�。我初学的时候，一上来��是Gof的传世经典，�l�果薄薄的一本册子，�׃��我整整一�q�的旉��Q�还觉得理解不够。当我看了一遍Java与模式，豁然开朗，如果先有了这个，一定不会觉得设计模式那么难�?br />
2。设计模式：可复用面向对象��Y件的基础

前面所提到的“传世之作”，��Z��么那么经典？因�ؓ句句话都是经典，可以说没有一句废话（《java与模式》就被�h说成废话�q�篇�Q��?br />java与模式，我看完后��送女朋友了，而这本书�Q�我却保存了��h��Q�作为手册查�Q�这��是我的用法�?br />

未完待箋。。�?br />

HuYi 2006-07-28 00:02 发表评论

Linux启动协议Ver.2.04

HuYi — Tue, 20 Jun 2006 06:46:00 GMT

       THE LINUX/I386 BOOT PROTOCOL
       ----------------------------

      H. Peter Anvin <hpa@zytor.com>
   Last update 2005-09-02

On the i386 platform, the Linux kernel uses a rather complicated boot
convention. This has evolved partially due to historical aspects, as
well as the desire in the early days to have the kernel itself be a
bootable image, the complicated PC memory model and due to changed
expectations in the PC industry caused by the effective demise of
real-mode DOS as a mainstream operating system.

Currently, four versions of the Linux/i386 boot protocol exist.

Old kernels: zImage/Image support only. Some very early kernels
  may not even support a command line.

Protocol 2.00: (Kernel 1.3.73) Added bzImage and initrd support, as
  well as a formalized way to communicate between the
  boot loader and the kernel. setup.S made relocatable,
  although the traditional setup area still assumed
  writable.

Protocol 2.01: (Kernel 1.3.76) Added a heap overrun warning.

Protocol 2.02: (Kernel 2.4.0-test3-pre3) New command line protocol.
  Lower the conventional memory ceiling. No overwrite
  of the traditional setup area, thus making booting
  safe for systems which use the EBDA from SMM or 32-bit
  BIOS entry points. zImage deprecated but still
  supported.

Protocol 2.03: (Kernel 2.4.18-pre1) Explicitly makes the highest possible
  initrd address available to the bootloader.

Protocol 2.04: (Kernel 2.6.14) Extend the syssize field to four bytes.

**** MEMORY LAYOUT

The traditional memory map for the kernel loader, used for Image or
zImage kernels, typically looks like:

|    |
0A0000 +------------------------+
| Reserved for BIOS | Do not use. Reserved for BIOS EBDA.
09A000 +------------------------+
| Stack/heap/cmdline | For use by the kernel real-mode code.
098000 +------------------------+
| Kernel setup   | The kernel real-mode code.
090200 +------------------------+
| Kernel boot sector | The kernel legacy boot sector.
090000 +------------------------+
| Protected-mode kernel | The bulk of the kernel image.
010000 +------------------------+
| Boot loader   | <- Boot sector entry point 0000:7C00
001000 +------------------------+
| Reserved for MBR/BIOS |
000800 +------------------------+
| Typically used by MBR |
000600 +------------------------+
| BIOS use only |
000000 +------------------------+

When using bzImage, the protected-mode kernel was relocated to
0x100000 ("high memory"), and the kernel real-mode block (boot sector,
setup, and stack/heap) was made relocatable to any address between
0x10000 and end of low memory. Unfortunately, in protocols 2.00 and
2.01 the command line is still required to live in the 0x9XXXX memory
range, and that memory range is still overwritten by the early kernel.
The 2.02 protocol resolves that problem.

It is desirable to keep the "memory ceiling" -- the highest point in
low memory touched by the boot loader -- as low as possible, since
some newer BIOSes have begun to allocate some rather large amounts of
memory, called the Extended BIOS Data Area, near the top of low
memory. The boot loader should use the "INT 12h" BIOS call to verify
how much low memory is available.

Unfortunately, if INT 12h reports that the amount of memory is too
low, there is usually nothing the boot loader can do but to report an
error to the user. The boot loader should therefore be designed to
take up as little space in low memory as it reasonably can. For
zImage or old bzImage kernels, which need data written into the
0x90000 segment, the boot loader should make sure not to use memory
above the 0x9A000 point; too many BIOSes will break above that point.

**** THE REAL-MODE KERNEL HEADER

In the following text, and anywhere in the kernel boot sequence, "a
sector" refers to 512 bytes. It is independent of the actual sector
size of the underlying medium.

The first step in loading a Linux kernel should be to load the
real-mode code (boot sector and setup code) and then examine the
following header at offset 0x01f1. The real-mode code can total up to
32K, although the boot loader may choose to load only the first two
sectors (1K) and then examine the bootup sector size.

The header looks like:

Offset Proto Name  Meaning
/Size

01F1/1 ALL(1 setup_sects The size of the setup in sectors
01F2/2 ALL root_flags If set, the root is mounted readonly
01F4/4 2.04+(2 syssize  The size of the 32-bit code in 16-byte paras
01F8/2 ALL ram_size DO NOT USE - for bootsect.S use only
01FA/2 ALL vid_mode Video mode control
01FC/2 ALL root_dev Default root device number
01FE/2 ALL boot_flag 0xAA55 magic number
0200/2 2.00+ jump  Jump instruction
0202/4 2.00+ header  Magic signature "HdrS"
0206/2 2.00+ version  Boot protocol version supported
0208/4 2.00+ realmode_swtch Boot loader hook (see below)
020C/2 2.00+ start_sys The load-low segment (0x1000) (obsolete)
020E/2 2.00+ kernel_version Pointer to kernel version string
0210/1 2.00+ type_of_loader Boot loader identifier
0211/1 2.00+ loadflags Boot protocol option flags
0212/2 2.00+ setup_move_size Move to high memory size (used with hooks)
0214/4 2.00+ code32_start Boot loader hook (see below)
0218/4 2.00+ ramdisk_image initrd load address (set by boot loader)
021C/4 2.00+ ramdisk_size initrd size (set by boot loader)
0220/4 2.00+ bootsect_kludge DO NOT USE - for bootsect.S use only
0224/2 2.01+ heap_end_ptr Free memory after setup end
0226/2 N/A pad1  Unused
0228/4 2.02+ cmd_line_ptr 32-bit pointer to the kernel command line
022C/4 2.03+ initrd_addr_max Highest legal initrd address

(1) For backwards compatibility, if the setup_sects field contains 0, the
    real value is 4.

(2) For boot protocol prior to 2.04, the upper two bytes of the syssize
    field are unusable, which means the size of a bzImage kernel
    cannot be determined.

If the "HdrS" (0x53726448) magic number is not found at offset 0x202,
the boot protocol version is "old". Loading an old kernel, the
following parameters should be assumed:

Image type = zImage
initrd not supported
Real-mode kernel must be located at 0x90000.

Otherwise, the "version" field contains the protocol version,
e.g. protocol version 2.01 will contain 0x0201 in this field. When
setting fields in the header, you must make sure only to set fields
supported by the protocol version in use.

The "kernel_version" field, if set to a nonzero value, contains a
pointer to a null-terminated human-readable kernel version number
string, less 0x200. This can be used to display the kernel version to
the user. This value should be less than (0x200*setup_sects). For
example, if this value is set to 0x1c00, the kernel version number
string can be found at offset 0x1e00 in the kernel file. This is a
valid value if and only if the "setup_sects" field contains the value
14 or higher.

Most boot loaders will simply load the kernel at its target address
directly. Such boot loaders do not need to worry about filling in
most of the fields in the header. The following fields should be
filled out, however:

vid_mode:
Please see the section on SPECIAL COMMAND LINE OPTIONS.

type_of_loader:
If your boot loader has an assigned id (see table below), enter
0xTV here, where T is an identifier for the boot loader and V is
a version number. Otherwise, enter 0xFF here.

Assigned boot loader ids:
0 LILO
1 Loadlin
2 bootsect-loader
3 SYSLINUX
4 EtherBoot
5 ELILO
7 GRuB
8 U-BOOT

Please contact <hpa@zytor.com> if you need a bootloader ID
value assigned.

loadflags, heap_end_ptr:
If the protocol version is 2.01 or higher, enter the
offset limit of the setup heap into heap_end_ptr and set the
0x80 bit (CAN_USE_HEAP) of loadflags. heap_end_ptr appears to
be relative to the start of setup (offset 0x0200).

setup_move_size:
When using protocol 2.00 or 2.01, if the real mode
kernel is not loaded at 0x90000, it gets moved there later in
the loading sequence. Fill in this field if you want
additional data (such as the kernel command line) moved in
addition to the real-mode kernel itself.

ramdisk_image, ramdisk_size:
If your boot loader has loaded an initial ramdisk (initrd),
set ramdisk_image to the 32-bit pointer to the ramdisk data
and the ramdisk_size to the size of the ramdisk data.

The initrd should typically be located as high in memory as
possible, as it may otherwise get overwritten by the early
kernel initialization sequence. However, it must never be
located above the address specified in the initrd_addr_max
field. The initrd should be at least 4K page aligned.

cmd_line_ptr:
If the protocol version is 2.02 or higher, this is a 32-bit
pointer to the kernel command line. The kernel command line
can be located anywhere between the end of setup and 0xA0000.
Fill in this field even if your boot loader does not support a
command line, in which case you can point this to an empty
string (or better yet, to the string "auto".) If this field
is left at zero, the kernel will assume that your boot loader
does not support the 2.02+ protocol.

ramdisk_max:
The maximum address that may be occupied by the initrd
contents. For boot protocols 2.02 or earlier, this field is
not present, and the maximum address is 0x37FFFFFF. (This
address is defined as the address of the highest safe byte, so
if your ramdisk is exactly 131072 bytes long and this field is
0x37FFFFFF, you can start your ramdisk at 0x37FE0000.)

**** THE KERNEL COMMAND LINE

The kernel command line has become an important way for the boot
loader to communicate with the kernel. Some of its options are also
relevant to the boot loader itself, see "special command line options"
below.

The kernel command line is a null-terminated string currently up to
255 characters long, plus the final null. A string that is too long
will be automatically truncated by the kernel, a boot loader may allow
a longer command line to be passed to permit future kernels to extend
this limit.

If the boot protocol version is 2.02 or later, the address of the
kernel command line is given by the header field cmd_line_ptr (see
above.) This address can be anywhere between the end of the setup
heap and 0xA0000.

If the protocol version is *not* 2.02 or higher, the kernel
command line is entered using the following protocol:

At offset 0x0020 (word), "cmd_line_magic", enter the magic
number 0xA33F.

At offset 0x0022 (word), "cmd_line_offset", enter the offset
of the kernel command line (relative to the start of the
real-mode kernel).

The kernel command line *must* be within the memory region
covered by setup_move_size, so you may need to adjust this
field.

**** SAMPLE BOOT CONFIGURATION

As a sample configuration, assume the following layout of the real
mode segment (this is a typical, and recommended layout):

0x0000-0x7FFF Real mode kernel
0x8000-0x8FFF Stack and heap
0x9000-0x90FF Kernel command line

Such a boot loader should enter the following fields in the header:

unsigned long base_ptr; /* base address for real-mode segment */

if ( setup_sects == 0 ) {
  setup_sects = 4;
}

if ( protocol >= 0x0200 ) {
  type_of_loader = ;
  if ( loading_initrd ) {
   ramdisk_image = ;
   ramdisk_size = ;
  }
  if ( protocol >= 0x0201 ) {
   heap_end_ptr = 0x9000 - 0x200;
   loadflags |= 0x80; /* CAN_USE_HEAP */
  }
  if ( protocol >= 0x0202 ) {
   cmd_line_ptr = base_ptr + 0x9000;
  } else {
   cmd_line_magic = 0xA33F;
   cmd_line_offset = 0x9000;
   setup_move_size = 0x9100;
  }
} else {
  /* Very old kernel */

  cmd_line_magic = 0xA33F;
  cmd_line_offset = 0x9000;

  /* A very old kernel MUST have its real-mode code
     loaded at 0x90000 */

  if ( base_ptr != 0x90000 ) {
   /* Copy the real-mode kernel */
   memcpy(0x90000, base_ptr, (setup_sects+1)*512);
   /* Copy the command line */
   memcpy(0x99000, base_ptr+0x9000, 256);

   base_ptr = 0x90000;   /* Relocated */
  }

  /* It is recommended to clear memory up to the 32K mark */
  memset(0x90000 + (setup_sects+1)*512, 0,
         (64-(setup_sects+1))*512);
}

**** LOADING THE REST OF THE KERNEL

The 32-bit (non-real-mode) kernel starts at offset (setup_sects+1)*512
in the kernel file (again, if setup_sects == 0 the real value is 4.)
It should be loaded at address 0x10000 for Image/zImage kernels and
0x100000 for bzImage kernels.

The kernel is a bzImage kernel if the protocol >= 2.00 and the 0x01
bit (LOAD_HIGH) in the loadflags field is set:

is_bzImage = (protocol >= 0x0200) && (loadflags & 0x01);
load_address = is_bzImage ? 0x100000 : 0x10000;

Note that Image/zImage kernels can be up to 512K in size, and thus use
the entire 0x10000-0x90000 range of memory. This means it is pretty
much a requirement for these kernels to load the real-mode part at
0x90000. bzImage kernels allow much more flexibility.

**** SPECIAL COMMAND LINE OPTIONS

If the command line provided by the boot loader is entered by the
user, the user may expect the following command line options to work.
They should normally not be deleted from the kernel command line even
though not all of them are actually meaningful to the kernel. Boot
loader authors who need additional command line options for the boot
loader itself should get them registered in
Documentation/kernel-parameters.txt to make sure they will not
conflict with actual kernel options now or in the future.

vga=
here is either an integer (in C notation, either
decimal, octal, or hexadecimal) or one of the strings
"normal" (meaning 0xFFFF), "ext" (meaning 0xFFFE) or "ask"
(meaning 0xFFFD). This value should be entered into the
vid_mode field, as it is used by the kernel before the command
line is parsed.

mem=
is an integer in C notation optionally followed by K, M
or G (meaning << 10, << 20 or << 30). This specifies the end
of memory to the kernel. This affects the possible placement
of an initrd, since an initrd should be placed near end of
memory. Note that this is an option to *both* the kernel and
the bootloader!

initrd=
An initrd should be loaded. The meaning of is
obviously bootloader-dependent, and some boot loaders
(e.g. LILO) do not have such a command.

In addition, some boot loaders add the following options to the
user-specified command line:

BOOT_IMAGE=
The boot image which was loaded. Again, the meaning of
is obviously bootloader-dependent.

auto
The kernel was booted without explicit user intervention.

If these options are added by the boot loader, it is highly
recommended that they are located *first*, before the user-specified
or configuration-specified command line. Otherwise, "init=/bin/sh"
gets confused by the "auto" option.

**** RUNNING THE KERNEL

The kernel is started by jumping to the kernel entry point, which is
located at *segment* offset 0x20 from the start of the real mode
kernel. This means that if you loaded your real-mode kernel code at
0x90000, the kernel entry point is 9020:0000.

At entry, ds = es = ss should point to the start of the real-mode
kernel code (0x9000 if the code is loaded at 0x90000), sp should be
set up properly, normally pointing to the top of the heap, and
interrupts should be disabled. Furthermore, to guard against bugs in
the kernel, it is recommended that the boot loader sets fs = gs = ds =
es = ss.

In our example from above, we would do:

/* Note: in the case of the "old" kernel protocol, base_ptr must
    be == 0x90000 at this point; see the previous sample code */

seg = base_ptr >> 4;

cli(); /* Enter with interrupts disabled! */

/* Set up the real-mode kernel stack */
_SS = seg;
_SP = 0x9000; /* Load SP immediately after loading SS! */

_DS = _ES = _FS = _GS = seg;
jmp_far(seg+0x20, 0); /* Run the kernel */

If your boot sector accesses a floppy drive, it is recommended to
switch off the floppy motor before running the kernel, since the
kernel boot leaves interrupts off and thus the motor will not be
switched off, especially if the loaded kernel has the floppy driver as
a demand-loaded module!

**** ADVANCED BOOT TIME HOOKS

If the boot loader runs in a particularly hostile environment (such as
LOADLIN, which runs under DOS) it may be impossible to follow the
standard memory location requirements. Such a boot loader may use the
following hooks that, if set, are invoked by the kernel at the
appropriate time. The use of these hooks should probably be
considered an absolutely last resort!

IMPORTANT: All the hooks are required to preserve %esp, %ebp, %esi and
%edi across invocation.

realmode_swtch:
A 16-bit real mode far subroutine invoked immediately before
entering protected mode. The default routine disables NMI, so
your routine should probably do so, too.

code32_start:
A 32-bit flat-mode routine *jumped* to immediately after the
transition to protected mode, but before the kernel is
uncompressed. No segments, except CS, are set up; you should
set them up to KERNEL_DS (0x18) yourself.

After completing your hook, you should jump to the address
that was in this field before your boot loader overwrote it.

HuYi 2006-06-20 14:46 发表评论

Google��Z��么会被封�?

HuYi — Wed, 31 May 2006 15:28:00 GMT

很早以前��听说过Google被封锁的消息,因�ؓ自己没有遇到�q?也不太相信真会有�q�样的事�?多可�W�呀.

不过自从感受��C��一�ơsourceforge被封,��p��得在中国,或许真会发生�q�样的事�?

今天,google�l�于挂了,gmail也挂�?我也无语�?

打听了一�?全国好多地方的网友都讉K��不了google�?

业内最令�h鄙视的案例莫�q�于微��Y靠捆�l�IE搞跨了网�?微��Y的这个脾气至今还是大安��视它的主�?但是��h��?微��Y�q�没有禁止Windows用户使用�|�景的服�?!!!

希望中国的google事�g不要成�ؓ他国的笑�?

http://post.baidu.com/f?kz=103530334

仅以此脓�U�念Google GMail GTalk

支持Google的朋友请在这里签名吧!

希望zf早点�?font color="#0000ff">GMail�?font color="#0000ff">GTalk�q�给我们!!

HuYi 2006-05-31 23:28 发表评论

�q�回看见好脓子就有话说了^^

HuYi — Fri, 26 May 2006 02:37:00 GMT
     摘要: 看了��g��的帖�? , 不由得精��? �? 之一�? , �? �? �? �l? 八脉 ...  阅读全文

HuYi 2006-05-26 10:37 发表评论

国产91色综合久久免费,久久99中文字幕久久,男女久久久国产一区二区三区

发布一个日语汉字假名�{换��Y件给大家

���成员函��C��为std::for_each的第三个参数

��Z��么要用�?(”取代�?�?

Linux启动协议Ver.2.04

Google��Z��么会被封�?

�q�回看见好脓子就有话说了^^

��成员函��C��为std::for_each的第三个参数