Here are the test account details seanp2500 used: (it's in the video he made so its OK to show it here)
The account id in decimal is: 333758381760163642
This converted to hex is: 4A1BF7AD99FAF3A
The problem with this is it is ony 15 digits not the needed 16.
Adding 0 to the start of the hex works.
the decimal of 4A1BF7AD99FAF3A is 333758381760163642
the decimal of 04A1BF7AD99FAF3A is also 333758381760163642
if you enter 333758381760163642 here https://www.rapidtables.com/convert/number/decimal-to-hex.html
the Hex signed 2's complement: is 16 digits but the normal hex is only 15.
I have no idea what signed 2's complement is, Ive tried to understand it but I cant get my head around it.
When I use my own given decimal account id it converts to a 16 digit hex and the Hex signed 2's complement is also 16 digits.
The big question is, is the Hex signed 2's complement number the correct one to use.
you can get the id from the cma folder alphanumeric, but I discovered it's byte reversed, so 0 would be the last number. that may be why it works there or has to work anyway.
--------------------- MERGED ---------------------------
btw, the aid is in the system.dreg (registry) as well, but it's byte reversed in there as well. modifying it will force a format as I tried it. I was able to make a folder with only 0s.