kxylxp / grub4dos-chenall

Automatically exported from code.google.com/p/grub4dos-chenall
0 stars 0 forks source link

rd-base not working??? #138

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?

map --ram-drive=0x9f 
map --rd-base=0x600000 
map --rd-size=0x180000
map --status
map ()/ntldr (rd) 
map --status

What is the expected output? What do you see instead?

second  map --status prints rd_base as near top of memory

Why is it not 0x600000 ???

What version of the product are you using? On what operating system?
0.4.5c may 2013

Please provide any additional information below.

Original issue reported on code.google.com by Steve6375 on 29 May 2013 at 5:15

GoogleCodeExporter commented 8 years ago
map --mem=0x3000 ()/ntldr (rd)
or
map --ram-drive=0x9f 
map --rd-base=0x600000 
map --rd-size=0x180000
map --status
dd if=()/ntldr of=(rd)
map --status

Original comment by chenall.cn on 30 May 2013 at 10:07

GoogleCodeExporter commented 8 years ago
So there is no point in setting rd-base or rd-size if mapping something to (rd)?

Original comment by Steve6375 on 30 May 2013 at 10:42

GoogleCodeExporter commented 8 years ago
I presume rd-base must be 1MB or more?

map --rd-base=0x1000
dd if=()/ntldr of=(rd)

crashes!

but map --rd-base=0x10000   works OK

Original comment by Steve6375 on 30 May 2013 at 12:32

GoogleCodeExporter commented 8 years ago
some low memory ranges are also reserved for grub4dos internal use. you should 
not use those memory ranges. chenall might give you a list of memory ranges 
available for users.

Original comment by tinyb...@gmail.com on 30 May 2013 at 2:43

GoogleCodeExporter commented 8 years ago
rd base can be anywhere, but you should not write to memory ranges that are 
reserved for grub4dos.

Original comment by tinyb...@gmail.com on 30 May 2013 at 2:54