Leaderboard

BeepSongEditor v1.0.2.4 Create easily Beep Songs and Mp3 Ringtones After >Beep Song Creator by Paulie, mine is more intended to hobbyists musicians ( based on a TT22 idea ) Now you can easily create Beep Songs and Mp3 Ringtones without being musician ! Source and Executable are available in the Download Section See Tray menu for options and help. If somes includes are missing : Bass Includes.rar Somes examples of ini files : Ini files.rar Thanks to Brett Francis, Prog@ndy and Eukalyptus for Bass Udf and trancexx for >DSBeep.au3 As usual several files are downloaded at first execution. Beep Party is back !!! Hope you like it !

No problem with a Braille terminal attached to your keyboard.

Thanks guys for inputs but I'm not interesed especially to get this specific information as much to know how to get all data from this registers in a single call. If I would need just to get VendorID your code would be nice. EDIT: I'm such an idiot, I could pass a string and add the content of registers to it. #AutoIt3Wrapper_UseX64=n #include <Memory.au3> MsgBox(0,"",GetVendorID()) Func GetVendorID() $Code = "0x" & _ ; use32 "55" & _ ; push ebp "89E5" & _ ; mov ebp, esp "60" & _ ; pushad "B800000000" & _ ; mov eax,0 "0FA2" & _ ; cpuid "8B7D08" & _ ; mov edi, [ebp + 08] "891F" & _ ; mov [edi], ebx "895704" & _ ; mov [edi + 4], edx "894F08" & _ ; mov [edi + 8], ecx "B000" & _ ; mov al, 0 "88470C" & _ ; mov [edi + 12], al "61" & _ ; popad "5D" & _ ; pop ebp "C20400" ; ret 4 $iSize = BinaryLen($Code) $pBuffer = _MemVirtualAlloc(0,$iSize,$MEM_COMMIT,$PAGE_EXECUTE_READWRITE) $tBuffer = DllStructCreate("byte Code[" & $iSize & "]",$pBuffer) DllStructSetData($tBuffer,"Code",$Code) $aRet = DllCallAddress("int",$pBuffer,"str","") _MemVirtualFree($pBuffer,$iSize,$MEM_DECOMMIT) Return $aRet[1] EndFunc

The code would need modifying accordingly but you could generate a 4 group of 4 characters, sure. That goes for any product. The reason hackers are able to make a key generator for someones's product is because they do exactly that I would assume. They find the parts which are being checked and make valid keys for that version of the product. Then the company realises there are keygens out there and alter which parts of the key sections are checked and now everyones old illegal codes stop working, same with the old key generator. That means the hacker group has to be aware of the new version and find the time to make a whole new keygen from scratch, which benefits companies because I am sure that if someone is desperate enough for the software that they will feel obligated to buy it if they cannot find working key generators anywhere. Either way it is a good thing to be doing partial key checks. As for the hash, as you can see in the source code I am using SHA1 because thats currently the best autoit has to offer

Macro Reference look for it in help file your probably gona need @ScriptDir and look for FileExists in help file

Hi! I'm guessing you've never used a memory stick, then!!! <g>. The problem with absolute paths lies in the Windows weakness that makes it dependent on drive letters. Unfortunately, USB flash drives get assigned a different letter from computer to computer. Of the 3 ports available on my home computer, the one I plug my USB stick into gets assigned the P drive. At work, it's the E drive. ALL the scripts that work at home stopped working once I got the office the first time I used the new stick because of this. Yet mimicking my USB stick's launcher way of referencing paths, which is truly portable (vs. just being a standalone), that way doesn't always work since it can change depending on the means to launch the file. So using something like SoundPlay ("..\Scripts\WAVs\Bladerunner.wav") can fail in certain cases. But using this syntax instead, SoundPlay(@ScriptDir & "\WAVs\Bladerunner.wav") works every time! So in conclusion, @ScriptDir can be vital in making things work extremely reliably when using AI off of removable items such as a memory stick. Hope that helps! (oh, p.s., I gave the full path to the XLS file initially just to show its location. I always had intention of eventually making it a relative path. But in this particular case, @ScriptDir wouldn't work due to the location of the file itself. Moving it from the Excel folder into the script folder fixed this problem as so because of @ScriptDir this will work reliably no matter which computer I use. Very important. [The final script now has a relative path rather than an absolute one as shown here.] Thanks!! <g>)