No one have documentation on this ?
Best Regards,
guga
Search found 8 matches
- Tue Jul 03, 2012 12:38 am
- Forum: General Discussion and Feedback
- Topic: Error in winternl.h ?
- Replies: 4
- Views: 2463
- Wed Jun 27, 2012 9:04 am
- Forum: General Discussion and Feedback
- Topic: Error in winternl.h ?
- Replies: 4
- Views: 2463
Re: Error in winternl.h ?
Analyzing the structure from both sources, i have a question... The one in http://msdn.mirt.net/winxpsp3_x86.html#_TEB seems to be more complete then the one existent in ROS ? It seems to contains different members names of the structure. Ex: What does the ACTIVATION_CONTEXT_STACK do ? Don´t it have...
- Wed Jun 27, 2012 8:20 am
- Forum: General Discussion and Feedback
- Topic: Error in winternl.h ?
- Replies: 4
- Views: 2463
Re: Error in winternl.h ?
here http://www.koders.com/c/fidE07E131D9EA20B1DBAA4207E589C3418F22236A6.aspx ULONG LastStatusValue; /* bf4 */ UNICODE_STRING StaticUnicodeString; /* bf8 used by advapi32 */ WCHAR StaticUnicodeBuffer[261]; /* c00 used by advapi32 */ PVOID DeallocationStack; /* e0c */ <----- It is 0E0A and not 0E0C. ...
- Tue Jun 26, 2012 10:11 am
- Forum: General Discussion and Feedback
- Topic: Error in winternl.h ?
- Replies: 4
- Views: 2463
Error in winternl.h ?
Not sure if the actual version is the same one i have, but...the file winternl.h seems to contains an error on _TEB structure typedef struct _TEB (...) WCHAR StaticUnicodeBuffer[261]; /* c00 used by advapi32 */ (...) here, it is not 261, but it is 262. So, it will result in WCHAR StaticUnicodeBuffer...
- Mon Jun 11, 2007 10:52 pm
- Forum: General Discussion and Feedback
- Topic: To developers mainly-
- Replies: 1
- Views: 1843
To developers mainly-
Concerning the discussion at http://www.reactos.org/forum/viewtopic.php?p=30659 1st, it is important for u guys to know that there is no attacks being taken The problem is that it have, in fact, sources in ReactOS that the developers must be aware of, and must know what happened to they be inadequat...
Hi counting_pine Tks a lot.. You understood perfectly About disclaimer.. we have a overview on the mainpage, expalining what RosAsm was designed to run on. . It might be a good idea for RosAsm to put a disclaimer on their web site, saying that there is actually no official relationship between the t...
The primary target of RosAsm was always ReactOS. A few years ago, it was names SpAsm - The Specific assembler. meaning that it was specifically designed to work with a certain OS, in case, ReactOS, that wass´t even working, btw. For personal reasons, and internal divergences, Spasm was discontinued ...