[Professor Frink]

You know, the one that looks like this:




I'm running my unattended installation on some new computers, and that message pops up after the automatic logon, when my batch file runs, and stays there the whole time until my batch file causes a reboot. I'm not sure what it's referring to exactly (chipset, maybe?), but has that happened to anyone else before?

Should I ignore it? Is there a way to make it go away? Would I be better off doing a reboot right there, and then running my main batch file on a second automatic logon (and if so, what would be the setup for that)?

FYI -- as far as I can tell, if I let it go everything seems to run fine. But it still gives me the creeps.....

[big_gie]

You could launch an AutoIT script at the begining of your batch that will hit "no" on this screen...

I had the same message box yesterday testing in vmware. I never had it before though and its kind of strange I admit...

[Professor Frink]

What would such a script look like?

And is there any way that I could be in trouble by just killing it and not rebooting immediately?

[big_gie]

Example:

WinWaitActive("System Settings Change","")
Send("!n")

thats it

There shouldnt be a problem about not rebooting. I personnelly doesn't like "taskilling" popups... I prefer a workaround like autoit.

You could reboot manually at the end of everything, just to be sure!

[Professor Frink]

I've never used AuotIT before.

I downloaded AutoIt3.exe, but what do I do now? Do I just put that code in a file? And then how do I call it from within my batch file?