Ok guys I now need to post posts every 10 hrs but that big problem for me cuz sometimes 10 hrs isn’t enough to make smth actually functional and show someone that doesn’t know assembly what it does unlike the others which you can see on the display. Anyway so what I did now Is bruteforcing bus device and function label strg than naxt thing what happens label ttwo checks every found device if it is ahci device if yes saves it and moves on with the list and now after full port bruteforcing is done label steb stops the device on the found ahci port /bus /smth smth then waits for acknowledgment from device aaah - start of zot zeroes out a block of memory then the other zot sets up some shi forgot the names they are smth like cap hba bar5 and other stupid names they are dozens of these stupid names I didn’t remember which one is which cuz that will be even harder to write that code for me , the way I did it I just looked up what does the device expect and tried to make it until it worked this explanation is fir the c kiddies out there that never in their life touched assembly and say that writing in assembly is ass current mentioning @PavolUlicny my message for you “you are chud and stop writing in c transition to assembly” but you might say why do all this shi , cuz it opens up my ability to read and write to storage