Sysprep modifies timeout in BOOT.INI

  • Thread starter Thread starter Adam Leinss
  • Start date Start date
A

Adam Leinss

We are in the process in making W2K images for our equipment. We have
the Recovery Console installed on these computers. The problem is that
the timeout value gets changed from 3 seconds back to 30 seconds after
you sysprep the machine, then login to the machine and reboot it.
Simple enough, right? I just dropped a batch file (also tried a MSI
file) into C:\INSTALL\TEMP and put this in the [GUIRunOnce] section in
the SYSPREP.INF file. The file runs successfully and pushes out the
correct file, but after you reboot, the timeout value gets changed
back. If I run this batch file a second time, the boot.ini once again
gets pushed and it sticks this time. Is there a way of running
something twice or stop it from modifying the BOOT.INI file?

The next problem is not so serious: we would like to have the "Show
icon in the taskbar when connected" for the network card enabled for
all users. When you sysprep the computer, the ShowIcon option in the
registry gets set from 1 to 0. Simple enough, just change ShowIcon
back from 0 to 1. Unfortunately, it stuffs this option under a unique
GUID of the network card making it impossible to use a generic registry
hack. This guy has a VBS script that is suppose to work, but
it doesn't: http://pages.towson.edu/aczech/win2k/win2k.html.

Adam
 
Adam Leinss said:
We are in the process in making W2K images for our equipment. We have
the Recovery Console installed on these computers. The problem is that
the timeout value gets changed from 3 seconds back to 30 seconds after
you sysprep the machine, then login to the machine and reboot it.
Simple enough, right? I just dropped a batch file (also tried a MSI
file) into C:\INSTALL\TEMP and put this in the [GUIRunOnce] section in
the SYSPREP.INF file. The file runs successfully and pushes out the
correct file, but after you reboot, the timeout value gets changed
back. If I run this batch file a second time, the boot.ini once again
gets pushed and it sticks this time. Is there a way of running
something twice or stop it from modifying the BOOT.INI file?
Click to expand...

I solved this. The MSI file in reality wasn't working. I just used a
CMD file instead of a BAT file and it worked.
 
Back
Top