Good, this is a fresh activation request - the RSA key and timestamps are different from your previous uploads, so the app generated a new one. The file structure is correct: valid header, product tag HPTEDITORNEW-3.0.3, protection SOL-HARDENED-2.0.0, and your HWID 89F3-4DF9-3E9A-C4FA-348F-249F is visible at the expected offset.
If you're still getting "Name Mismatch" with this newly generated file, I need to know exactly what you typed in the license name field when the app created it. The name must match your forum username character-for-character.
What string did you enter as the license name when generating this activation3.req file?
If you entered maalmull exactly (lowercase, no spaces), and it still rejects with "Name Mismatch," that's an account-side registration issue that Bin will need to resolve - it would mean the server isn't recognizing your account for product activations, which I can't fix from here.
I can't issue the license file myself, and I don't want to leave you waiting on something that won't come from my side. License responses are generated by the product author, so this one has to go through Bin / the resource support workflow.
The good news is your request is already complete in this thread: activation3.req (903 B, header the forum-ACT-V2, product tag HPTEDITORNEW-3.0.3, protection SOL-HARDENED-2.0.0), with the HWID bytes at offset 0x38 matching 89F3-4DF9-3E9A-C4FA-348F-249F. Nothing more needs to be uploaded.
What to do now
Tag Bin in this thread so the request gets picked up, that's the normal route when a license is pending.
Don't regenerate another activation.req while you wait. A new one may not pair with the license that gets issued.
When the .lic arrives, import it through the same prompt the app is showing, on the same PC that produced this request.
One thing still worth answering before the license is cut: what exact string did you type into the license name field when the app built this file? If that name doesn't match your forum account, the same "Name Mismatch" will come back even after a valid .lic is issued, so it's better sorted out now than after.
Good, maalmull lowercase is correct, so the name side should be clean once the license is issued.
On delivery: license files come back the same way the request went out. Bin will either attach the .lic to a post in this thread or send it to you by conversation (DM), depending on how he handles it. There's no automated email or in-app download for this, so watch your forum alerts and your inbox here. I can't give you a timeframe, that's on Bin's side.
When it arrives
Save the .lic file locally, don't rename it.
Import it on the same PC that generated activation3.req, HWID 89F3-4DF9-3E9A-C4FA-348F-249F. A different machine or a hardware change will invalidate the pairing.
Use the same import prompt the app is already showing you.
Keep a backup copy of the .lic somewhere off the machine in case of a reinstall.
Until then, leave the app as it is and don't generate another request. If you tag Bin in this thread he'll see the pending one.
That won't alert him, plain text doesn't trigger a notification. Type @ then start typing Bin and pick him from the dropdown that appears, so the mention becomes a proper tag.
Everything else is already in place: activation3.req is posted, HWID 89F3-4DF9-3E9A-C4FA-348F-249F, name maalmull confirmed. Once the tag goes through, just sit tight and wait for the .lic.
An hour is normal here, Bin isn't on call around the clock and licences get cut when he's at the machine. Nothing is stuck on your side.
One thing to check though: your last two posts show "Bin" as plain text again, not a linked mention. If it isn't blue/clickable in the posted message, no alert was ever sent. Type @ first, then start typing Bin and select him from the dropdown before posting.
Everything else is complete and doesn't need touching: activation3.req is attached in the thread, HWID 89F3-4DF9-3E9A-C4FA-348F-249F, name maalmull confirmed. Don't generate another request while you wait, it would only complicate the pairing.
If there's still nothing by tomorrow, a conversation (DM) to Bin with a link to post #17714 is the next step.
