hi,
can anyone tell me how the manual cracking of the mBot worked before mBotLoader was explored?
I'm trying to solve the auto-startup of mBot via command line parameters.
The mBot.exe can be executed with command line parameters ID:... PW:... SERVER:.... ,then sro_client.exe should show up automatically and bot starts working.
So i tried to create .bat files that would auto-start all my mBot's and auto start training.
My problem is, the "mBotLoader" executes the "mBot_vSRO110.exe", so you can't start it with command line parameters.
So i renamed "mBot_vSRO110.exe" to "mBot_vSRO110a.exe" and wrote a .bat file that starts this "mBot_vSRO110a.exe" with the command line parameters. Then i converted my .bat to .exe and named it "mBot_vSRO110.exe", so the mBotLoader starts this "bat" and mBot get's started with the right parameters. I can see autologin starting in the logfile but the mBotLoader doesn't "crack" the mBot anymore (i think because the Loader is not directly connected to the mBot anymore?)
Does anyone know a solution?
Maybe it's possible to execute the "mBot_vSRO110.exe" with command line parameters (using a .bat or sth. else) and then manually crack it with the given files? (That's why i was asking about the manual cracking of mBot at the beginng)