DMilton

I think, there's no need of using the variable progfiles: SET progfiles=%HOMEDRIVE%\Program Files or SET progfiles=%HOMEDRIVE%\Program Files (x86) Instead of it, if you use the enviroment variable %PROGRAMFILES% in all of the code, it will be not neccesary the progfiles variable. For example, in Spanish version of any Win OS the path must be chaged to: <_< SET progfiles=%HOMEDRIVE%\Archivos de Programa May be it can be changed?

I believe you, then, by the momment, the code do the same as "ver" dos command, isnt it? Im not a C++ programmer, in fact im only a fucking newbie! Feel free to kick my ass in any momment! :( Sorry, if I understand you (my understanding is a bit limmited due im not english speaker but spanish), you ask for the purpose of the needing of this program... As I far I can get, the needing of the program itself will be to do easier and faster the need of testing the OS installed, because it will determine some different behaviours of the payload. The need of the detection of version language installed will be to do more effective the payload against any system, because the paths of certain programs vary depending of it. Have I answered your question? don`t worry... kick it!

1st. I think is a good idea. Probably resolves some problems with the OS detection but... must be compiled or just works as a vb routine? Is your code faster than the piece of the batch that did the same before? Have you verified it? 2nd. Can the code determine when a WinXP32 or WinXP64 (as Vista) is installed? 3rd. May be I must try it before asking nonsenses but can you post the results? 4th. Can you do the same with the language installation? :P

Windows 2000 has a system32 directory then the code must work. You can also try with: ver|%systemroot%\system32\find.exe "[Version 5.00." or ver|%systemroot%\system32\find.exe "5.00." for all os languages... :P

I tried last code in various laptops but in one of them It didnt go as it was expected. It was Windows XP SP3 installed on it but the batch was telling me it was a win2k (1st option of the batch). I tried this code and went perfect in all of the systems. ver|find "5.00." if %errorlevel% EQU 0 goto SetOSwin2k ver|find "5.1." if %errorlevel% EQU 0 goto SetOSXP32 ver|find "5.2." if %errorlevel% EQU 0 goto SetOSXP64 ver|find "6.0." if %errorlevel% EQU 0 goto SetOSVISTA32 ver|find "6.???" if %errorlevel% EQU 0 goto SetOSVISTA64 :SetOSDefault goto SetOSXP32 :SetOSwin2k SET CurrentOS=win2k GOTO EndDetect :SetOSXP32 SET CurrentOS=XP32 GOTO EndDetect :SetOSXP64 SET CurrentOS=XP64 GOTO EndDetect :SetOSVISTA32 SET CurrentOS=VISTA32 GOTO EndDetect :SetOSVISTA64 SET CurrentOS=VISTA64 GOTO EndDetect :EndDetect Someone knows why the batch was jumping the "if errorlevel 1 goto..." instruction? May be this code works better?

For all languages OS detection, If you modify: ver|find "[Version 5.00." if errorlevel 1 goto SetOSwin2k ver|find "[Version 5.1." if errorlevel 1 goto SetOSXP32 ver|find "[Version 5.2." if errorlevel 1 goto SetOSXP64 ver|find "[Version 6.0." if errorlevel 1 goto SetOSVISTA32 ver|find "[Version 6.???" if errorlevel 1 goto SetOSVISTA64 :SetOSDefault goto SetOSXP32 :SetOSwin2k SET CurrentOS=win2k GOTO EndDetect :SetOSXP32 SET CurrentOS=XP32 GOTO EndDetect :SetOSXP64 SET CurrentOS=XP64 GOTO EndDetect :SetOSVISTA32 SET CurrentOS=VISTA32 GOTO EndDetect :SetOSVISTA64 SET CurrentOS=VISTA64 GOTO EndDetect :EndDetect The code will not work for spanish systems (or other I supose), because the ver command shows lines as "Versión 5.00....". You can modify the code with: ver|find "5.00." if errorlevel 1 goto SetOSwin2k ver|find "5.1." if errorlevel 1 goto SetOSXP32 ver|find "5.2." if errorlevel 1 goto SetOSXP64 ver|find "6.0." if errorlevel 1 goto SetOSVISTA32 ver|find "6.???" if errorlevel 1 goto SetOSVISTA64 :SetOSDefault goto SetOSXP32 :SetOSwin2k SET CurrentOS=win2k GOTO EndDetect :SetOSXP32 SET CurrentOS=XP32 GOTO EndDetect :SetOSXP64 SET CurrentOS=XP64 GOTO EndDetect :SetOSVISTA32 SET CurrentOS=VISTA32 GOTO EndDetect :SetOSVISTA64 SET CurrentOS=VISTA64 GOTO EndDetect :EndDetect It will work for all languages OS's. ;)

Hi everybody! I have some questions about your payload. I have been testing for some payloads before, but yours is the best one I've ever found. Have you think about coding your payload in a way it can be useful for everybody in everywhere? I mean, the pocketnife is very useful when it's running in a English Windows machine but... What about other languages as Spanish? :( Im an spanish user (sorry of my english) and I have to modify your code for doing the same in spanish computers. Instead of this I think there is some ways to find the correct paths without the need of "translating" it. Ill be proud to help in developing this beatiful tool If you want. ;)