How to explain this, GetTickCount64 is not some exclusive 64bit only function. It returns a 64bit value, which 32bit code is perfectly capable of storing and using.
Z98 wrote:How to explain this, GetTickCount64 is not some exclusive 64bit only function. It returns a 64bit value, which 32bit code is perfectly capable of storing and using.
That's what I meant I tested it today and realized, that Microsoft did this "to identify bugs that might not occur until the system has been running for a long time" <-- MSDN. So in laymans Terms: "we make a 64bit return value to prevent (arithmetic)overflows".
Thomas Faber wrote:[NTOSKRNL] - Return process pool quota on free - Do not use POOL_QUOTA_FAIL_INSTEAD_OF_RAISE on non-quota allocations - Welcome back, device installation wizard CORE-7459 #resolve
EmuandCo wrote:Well... regression^^
Lets call it revealed hidden bug.
A function that worked before a change, but doesn't after the change is a regression imo.
The revealed hidden bug is the cause of the regression Ätschibätsch
but this doesn't matter, devwiz is back and everything is fine
So I was wondering about the DLLs that are swappable. I have been experimenting with them and mixing/matching different ones. Can anybody give me a rundown of what DLLs do what and what they need from each other. And also how they relate to things like winlogon.exe, crss.exe, smss.exe, etc?
Okay. That will work. Just wanted to let everyone know that I was able to get some Windows 7 DLLs to work with ReactOS as well. I don't know if that means much though. Also the Windows 7 userinit.exe works well too.
Pierre Schweitzer wrote:[NTOSKRNL] - Finally fully implement FstubVerifyPartitionTableEFI(). It is capable of fixing a GPT disk. - Fix implementation of FstubReadHeaderEFI() (which returns a pointer to the header). Fixed all the other functions accordingly. Note that you have to be careful when using Disk->Buffer. You can easily read a buffer that doesn't contain your data anylonger. - Fix implementation of FstubReadPartitionTableEFI(). It was improperly dealing with the backup table. Now, it will look for it and replace/recreate it if not found where expected. - Fix implementation of FstubWriteEntryEFI(). The computation of memory placement was wrong, and thus it was missing partitions and causing corruption. Thank you checksums! In case you format a disk with GPT using Linux (with GParted, for instance), don't be surprised if once started with ReactOS your GPT is modified, and especially its backup table moved. They don't have the same sector counts. It was a nice way to tests whether ReactOS properly write GPT. Which it does now .
I think after many weeks w/o FOTW this is a good candidate. (I thought to take the psapi one at first but then I read Partition and I knew that this is the chosen one :p)
I think next week's will be fixing the Explorer shell copy bugs. Those have been around for years and result in data loss, so that will be a big improvement.