writeos
writeos copied to clipboard
solrex
Automatically exported from code.google.com/p/writeos
``` 用cygwin对boot.s编译出错 chapter2/2 ,boot.S文件在cygwin下 使用make会出现如下错误 bash-3.1$ cd /cygdrive/h/writeos/chapter2/2 bash-3.1$ make gcc -c boot.S boot.S: Assembler messages: boot.S:25: Error: unknown pseudo-op: `.2byte' boot.S:27: Error: unknown pseudo-op: `.2byte' boot.S:29: Error: unknown pseudo-op:...
``` makefile中 应该为boot.elf:boot.o $(LDFILE)，boot.elf应该依赖ld文件 ``` Original issue reported on code.google.com by `[email protected]` on 18 Jul 2011 at 7:46
``` What steps will reproduce the problem? 1. 磁道号 = Q ＞＞ １ 2. 磁头号（柱面号） = Q&1 3. What is the expected output? What do you see instead? 见上 What...
``` What steps will reproduce the problem? 1. DIV BL 2. 根据扇区号获得起始扇区号 DL为18 3. 这个时后AX(DIV BL的默认被除数?)值是多少呢?一直没找到给其赋值的地方 What is the expected output? What do you see instead? What version of the...
``` What is the expected output? What do you see instead? 余数R应该就是起始扇区号，书中写作“起始扇区号=R+1” What version of the product are you using? On what operating system? 书1.0-2版 Please provide any additional information...
``` What version of the product are you using? On what operating system? 1.0-2 Please provide any additional information below. p29 FAT 表项有12 个比特，大约能管理2^12-个文件簇。 2^12-应该是"2^12-1" ``` Original issue reported on...
``` 杨兄： 3.1.4节倒数第二段中有： “GDT（Global Descripter Table,全局段选择子表)是保存着所有段选择子的信息，段选择 子（Segment Selecter）是一个指向某个段选择子的索引” 我认为应该改为如下语句： “GDT（Global Descripter Table,全局段描述符表)是保存着所有段描述符的信息，段选择 子（Segment Selecter）是一个指向某个段描述符的索引” 源语句把“段选择子”和“段描述符”搞混了 ``` Original issue reported on code.google.com by `[email protected]` on 15 Aug 2009 at 11:26
``` “有时候也被成为保护的虚拟地址模式”应为“有时候也被�� �成为保护的虚拟地址模式” ``` Original issue reported on code.google.com by `China.LiuJunFeng` on 3 Jul 2009 at 11:25
``` 博主，您好： 实践本书第3章6节（后面几节都出现这样问题）发现核心堆栈 错误，经过定位发现是 在这个地方出错，比如以7节例子中： LABEL_SEG_CODE32: ... ... push $(ARDSTitle) /* Display addr range descriptor struct title */ call DispStr add $4, %esp call DispAddrMap /* Display system address map...
``` 建议统一使用 7z ``` Original issue reported on code.google.com by `[email protected]` on 27 Feb 2009 at 4:13