![](https://static.wixstatic.com/media/0573ed_ab71211235c94ba18e227a3f99221a79~mv2.png/v1/fill/w_709,h_504,al_c,q_85,enc_auto/0573ed_ab71211235c94ba18e227a3f99221a79~mv2.png)
I've had meningitis twice so my memory is not as good as it could have been....
Forgot some other changes that I made in checkfornetwork.vbs.
1.
I try to restore the boot procedure if the script fails. Let's say that the sequence is initiated from software center and checkfornetwork.vbs somehow fails after the client has been rebooted into WinPE. That would cause a boot loop where the computer would load the WinPE-image over and over again even though there's a fully functioning OS installed.
The sub "Reboot" tries to set things straight. Works for both legacy/UEFI.
(Even though checkfornetwork.vbs shouldn't fail since we got conditions that verifies that the computer model is certified before that. Which pretty much translates into "We've tested it and added drivers that should work")
2.
Detecting if "Enable command support" is enabled on the boot image and using it to determine if debug options should be shown in case of failurs.
I'll write another post on this in just some minutes, since I got a powershell equivalent as well.
Comments