[IsBadWritePtr]

Its not mess and I have never seen someone complain, but by your logic it has to be mess, And how is WIN32 object oriented ? WIN32 was written for C, And why should i aim for backwards compatibility ? This code is for my machine and i guarantee that it should work perfectly on 7 and compatibility for what ? CreateFile, CreateThread, CloseHandle, IOCTL_STORAGE_QUERY_PROPERTY, IOCTL_DISK_GET_DRIVE_GEOMETRY might not get deprecated even after 10 years, but never will be removed, and the DOS paths are fixed, nobody is going to change them, this will be suicidal. I know enough WIN32 to see how they try to make it more easy to use and have removed really important functionality of the Nt family, WIN32 not supported root files is one of the problems. Imagine CreateFile supporting root files, FindFirstFile and FindNextFile can be just on functions and more stuff like this that will speed up WIN32 and make it smaller... I know that Microsoft is so strict of that compatibility but still who cares about WIN16 ? 16 bit is just like that strange kid that you try not to talk but you are in the same class and implements macros that just bloat with __far and __near, Windows headers are such a big mess, from far I know there are different departments that use different types. one will use ULONG while another might use DWORD, One used ULONG64 while another uses ULONGLONG or other stuff like that, And for the compatibility someone told me that Windows has too many old functions and algorithms that slow down the whole system and you can't remove or edit them because some random program used it before 15 years, might get lucky eventually if someone  upper lets you optimize the old stuff. This might sound very arrogant but I don't need to read blogs about WIN32 and C++, I find out only "How arbitrary is the ArbitraryUserPointer in the TEB?" interesting.

Its again early in the morning and you hit me like a coffè, have a good read of my spelling errors lol

E: Next post will use ULONG just for you, I capitulate