That whole stuff (desktop blackening etc.) is done with a considerable delay, sometimes. Partly because some services are on Delay Start, and the Genuine check tasks may start with some delay, too. This whole situation may lead to a race condition, actually.
Why is there two times a part for writing Check.bat? Also the VB-Script generation part isn´t written to Check.bat so far . It won´t work to use %file% variable for check.bat, as it´s used for writing IR6.bat in VBS section. Problem here, as far as i see, is that part of the code will be writteh 3 times. Kind of an INCEPTION-Scenario in a batch script . Duality writes to Check.bat which writes to IR6.bat which writes to VBS file . Getting dizzy here while reconcidering this .
Unfortunately, you´re wrong here, it should be written once, then is started by the two scheduled tasks. Also it´s not needed to copy Check.bat from inside Check.bat code, as it´s only deleted by IR6Uninstall and will be created by IR6Install every time again. Would also recommend to keep the write part seperately to not mess with Duality as long as it isn´t working as we wish. Problem are still the parts where code is written three times, to get all variables written correctly, when code does it at lest the third time . EDIT:... thread is: Hot Thread on front page .
Yeah...is still my refernce for the reworked version . Would be good to test my Check.bat thoroughly. Will work further then on trying to get it written ... . But tomorrow, will watch some TV, to let my brain idle for now.
Testing myself in Win 7 Pro VMware machine with two snapshots: in initial grace with 5 Rearms to test the backup and via forwarding time the rearm/restore in notification with 0 Rearms to test reinstall of IR6 So in case something gets borked, i can revert to a reference point, to get results without being affected by previous errors. Then simply running Check.bat several times.... EDIT: After forwarding time open system pane and klick on the hyperlink, which is nagging to activate today and the theme will change and you get black background.
Yay...at least solved my challenge on how to escape escape-chars when writing code 3 times in this INCEPTION In case Code: ^>^>%%dl%%\installkey.bat should be written to a file, correct code would be: Code: ^^^>^^^>%%%%dl%%%%\installkey.bat That way code is looking hieroglyphic . Will try now to get the writing part done...hopefully without getting mad .
Nice job s1ave77, I must say Well Done with your continuous persistence with finding solutions to crack this inception, I am sure you will come out as an expert at the end of this development tunnel
Sometimes the timespan between reading and understanding what you read can be annoyingly long . Still trying to shorten it. And yep, i definitly learned a lot new stuff over the last weeks .
We're almost at top of Hot threads section How can I test 0 rearms with days left if I don't wait 30 days? Kinda busy guys, can someone else test? Thanks TS p.s. What's the situation with the restore Can someone reiterate if that is 100% or what bugs are present
Just figured this whole confusion of the 3 checks in D420 I was thinking that we deleted check.bat and IR6 folder (but since IR6 folder and check are static) thus an extra one to place in new IR6 folder was necessary which it would have been if IR6 folder with check inside wasn't left So we're just going to leave IR6 and check within it when installing from check via msg Thanks for tolerating my ideas and way of thinking... I was right but your way is better and simpler again Go ahead and do WMIC IORRT rearm check, instead of doing rearm to get error or not to determine if 1 rearm is present for IORRT install ...lol