I've changed a pe exe header, so code section can contain writeable, executable, shareable, uninitialized, initialized data. I've made the same with all sections, except reloc. After that i've placed a code, in which it rewrite for byte in it with otherone (so it place one or more instruction/s here) depending on the state of a register (so it will give the index to the instruction currently need). The instruction which do that, uses ds (default) seg register. cs is "xx1b" and ds is "xx23" (but it may point to the "same" descriptor) in that point of code (actually, it never changes). Everything worked just fine.

However, i've get some info that in pmode (so windows) descriptors with executable bits are only executable, but also, they can't be writeable. So maybe it depends on the used segment register as well, or windows just handle the rising exception (but i guess not).

Don't know much about what you're trying to say, I know some interpreted languages allow modifications of their own code, maybe you should check out MSDN, or even better the most recent PE spec's probably has something in there about weird section things like that.

i think it's not problem of segmentation, it's elsewhere. can you post example code that demonstrates your problem?

A little later, now i don't have the file and i can't remember the exact code.

Protection is done per-page, not through the use of selectors (both code and data are base=0 limit=4g on 32bit windows). So as long as you set the PE section permissions, the windows loader will set the per-page permissions, and you're good to go.

I wouldn't mix "Initialized" and "Uninitialized" though, and why are you adding "Shared"? What you want is Read/Write/Execute/Initialized, nothing more, nothing less.

It pretty much explains, why could i reach the code segment through ds, but what about rewriteable,and executable code? I could rewrite bytes in the code segment. Also i don't know much about pageing. Is there something in pageing which removes write protection?

FLAT address space (is, base=0, limit=4gb for code,data,stack descriptors) is why you can "get to code through DS" (which is the default, by the way). Try adding a CS: segment/selector override, and you'll get a protection violation even though the pages are writable.

Paging offers per-page (duh ) protection, which is much more granular than the segment protection that you get with selectors (well, descriptors). You can set user/supervisor, read-only/read-write, and (on recent processors) eXecute Disable per page. Pages are typically 4kb large, but (depending on CPU and operating system) can be 2meg, 4meg or 1TB as well.

The Windows PE loader sets per-page permissions according to the PE section flags you specify with fasm or link.exe or a hexeditor or whatever you used.

So some TYPE flags in the descriptor depends on the used segment register.

Thank you for the help!

s/segment register/selector.

You can never write to anything with a CS: override, with other selectors it depends on privilige level and paging too, if paging is enabled.

k. Thanks again!