Ascii2

I want to set the timeout value that exists in boot.ini of Windows 2000 System Drives to 2. I want to modify the BOOT.INI timeout value without using the Windows Graphical User Interface (GUI) for the purpose (as necessary during an unattended Windows install). I am aware of the existence of the bootcfg.exe utility; however, the bootcfg.exe utility does not work on Windows 2000. Attempting to use bootcfg.exe on a Windows 2000 family operating system yields the following error: If a patched utility with the OS check removed exists, please make it known.How can the BOOT.INI file be modified without using a GUI?

I was wanting to apply updates to system applications and components that require a reboot after the application installations prior to first logon.Normally with attended installations of components or applications of DirectX 9.0c, Internet Explorer 6 SP1, and Microsoft Java Virtual Machine complete, a reboot is required by the setup.

I have noticed that the order listed in svcpack.inf is usually the reverse order in which the updates were integrated. Generally, it does not matter to each update in which order they are installed. Upon inspection of the batch file used to integrate and create the contents of the above posted SVCPACK.INF file, the order did seem to be in reverse order of integration with a single exception: the KB32004 patch ("Windows2000-KB832004-x86-ENU.EXE"). After querying the update patch for its command line parameters, I noticed that the patch does not support the "/integrate" argument (all other usual parameters are supported). Apparently, the KB32004 patch does not integrate. Not at allI have noticed that Microsoft Knowledge Base article that refer to editing manually SVCPACK.INF to use the 8.3 format; however, Microsoft Corporation does not seem to state why should it be done. It is also odd that many newer patches (within the past four years) integrated into an installation source do not adhere to the 8.3 naming format, while most do. The guide provides links to two repackaged, silent, switchless, installers. Someone created those packages.I had downloaded the Windows Media Player 9 setup from the guide page and ran it on my Desktop. The file ran the attended Windows Media Player 9 setup. The file was also invokable using the normal Windows Media Player 9 setup switches. The installer did not appear to be silent nor switchless.

Looping is also what I though would happen. I thought that it may be that an exception for such a thing may have been built-in.

If I include a command to reboot computer during the execution of CMDLINES.TXT, would CMDLINES.TXT run again from its beginning? Should a reboot occur at all? Would setup not function correctly if a reboot is invoked in CMDLINES.TXT?

The MSFN.org guide to use SVCPACK.INF at http://unattended.msfn.org/unattended.xp/view/web/24/ . The method described in the MSFN.org article differs greatly from the result of using "/integrate" parameter with newer update patches and hotfixes. I first will start with an example of SVCPACK.INF that may be created by integrating patches using "/integrate" switch. The following is the contents of a Windows 2000 Professional with Service Pack 4 SVCPACK.INF for which some patches were integrated into an installation source using the "/integrate" switch: [CatalogHeader] [Version] BuildNumber=2195 MinorVersion=0 MajorVersion=5 Signature="$WINDOWS NT$" [SetupData] CatalogSubDir="\I386\svcpack" [SetupHotfixesToRun] KB909520.exe /q /n /z KB893803v2.exe /q /n /z KB908506.exe /q /n /z KB896423.exe /q /n /z KB916281-IE501SP4-20060519.173353.exe /q /n /z KB914389.exe /q /n /z KB918439-IE6SP1-20060530.145346.exe /q /n /z KB914388.exe /q /n /z KB917344.exe /q /n /z KB917953.exe /q /n /z KB913580.exe /q /n /z KB917736.exe /q /n /z KB917537.exe /q /n /z KB911564.exe /q /n /z KB908519.exe /q /n /z KB900725.exe /q /n /z KB905749.exe /q /n /z KB901017.exe /q /n /z KB905414.exe /q /n /z KB905495-IE6SP1-20050805.184113.exe /q /n /z KB893756.exe /q /n /z KB901214.exe /q /n /z KB899587.exe /q /n /z KB890046.exe /q /n /z KB896422.exe /q /n /z Update Rollup 1.exe /q /n /z [ProductCatalogsToInstall] basecsp.cat KB893803v2_w2k.cat KB908506.cat KB896423.cat KB916281-IE501SP4-20060519.173353.cat KB914389.cat KB918439-IE6SP1-20060530.145346.cat KB914388.cat KB917344.cat KB917953.cat KB913580.cat KB917736.cat KB917537.cat KB911564.cat KB908519.cat KB900725.cat KB905749.cat KB901017.cat KB905414.cat KB905495-IE6SP1-20050805.184113.cat KB893756.cat KB901214.cat KB899587.cat KB890046.cat KB896422.cat sp5.cat The order of filenames in SVCPACK.INF when the "/integrate" switch is used does not seem to be sorted alphanumeric or by order patches were integrated into the install. I not that the MSFN.org guide states, "All the hotfixes you have downloaded, renamed and copied to the SVCPACK folder should be added under this section in svcpack.inf in numerical order". Does the order of SVCPACK.INF entries really matter? I noticed that most the integrated patches were renamed to the 8.3 format. However, there seems to be exceptions. Patches beginning "IE5.01sp" were renamed to much longer filenames. Update Rollup 1 of Windows 2000 Service Pack 4 ("Windows2000-KB891861-v2-x86-ENU.EXE") was renamed to "Update Rollup 1.exe" (note the spaces in the name). Should there be a problem with using filenames not adhering to the 8.3 format? The MSFN.org guide conveys that Windows Media Player 9 and Windows Media Player 10 may be installed from SVCPACK.INF by including its filename without any switches. Why can SVCPACK.INF have installed Windows Media Player 9/10 without the use of switches, while other programs like (update patches) require switches? When the "/integrate" switch is used, *.cat files are placed in directory "svcpack" and their filenames are included in heading "[ProductCatalogsToInstall]" in SVCPACK.INF. What is the significance of the *.cat files with respect to SVCPACK.inf?

I thought that the driver defaults would have to be set in the driver INF files or modify the binary driver files themselves (worst case), and that the driver settings would only be written to the Windows Registry when an instance (not all instances) of the driver is installed for use. So, any changes to driver defaults would have to be made by modifying the INF installation files or the driver files themselves. Is this inaccurate? I shall try to examine changes with registry monitoring applications within the next 48 hours (probably within the next 24 hours).

I would have thought renaming files after expanding their compressed form would have been necessary.

How can default settings for drivers for Windows 2000 or Windows XP family operating systems be set? For example, I would like to have the "Primary IDE Channel" and "Secondary IDE Channel" of "IDE ATA/ATAPI controllers" in Device Manager default to a Transfer Mode of "DMA if available" for both devices on a channel. I would like the "ECP Printer Port (LPT1)" driver to default Port settings to "Use any interrupt assigned to this port" and "Enable legacy Plug and Play detection".

Would you please state what it is?

I would think the information I seek should be known. By built-in accounts, I meant accounts like "Administrator" and "Guest". Perhaps a different question: Between "3." and "4." from the timeline above, is the "Default User" and "All Users" information created?

This issue in this thread is resolved. Thanks Flip1001.

Guides for unattended install of Windows state to use "START followed by a title, the /wait switch, then the item to run. The reason given to use START with the /wait argument is to have items run individually (not having multiple things running simultaneously). When applications in a batch file are run without the START command, they seem to run individually and in sequencial order. Is the perception accurate? Is the opting to use START with the /wait switch a preference of multiple ways of doing something?

The distribution folders are copied to the installation location durring text mode of Windows setup; local accounts are created during the GUI part of the setup (which occurs after the text mode part of the setup). Instead, use COPY with the "/B" and "/Y" (binary copy and do not prompt to overwrite) arguments to copy the files to the locations in a batch file luanched from cmdlines.txt or at first logon.

ًWhy are you saying that?! Because it seems like you are not correctly identifying the issue you may be experiencing. The statement was intended to help you rethink the issue (like identifying the method(s) compatible with your BIOS to make a flash drive bootable).

Indeed. I note that you may not need Ntbootdd.sys on Windows 2000 with your BIOS, but this may not be true with Windows XP or Windows Server 2003 boot files (it is already know that they function differently given that arcldr.exe and arcsetup.exe are not used). It is possible that the Windows XP or Windows Server 2003 boot files handle SCSI devices differently (with respect to Windows 2000), or requires a different configuration in boot.ini for the SCSI devices.So, merely copying the newer operating system files to Windows 2000 may not work for your configuration. To find out what is necessary for your configuration using Windows XP or Windows Server 2003 boot files, you can install a Windows XP or Windows Server 2003 family operating system and examine (and retain a copy of) the files created.

.I don't have the problem with making my USB flash driver a bootable one. The problem is my BIOS don't support boot from USB flash driver so it is not available in the boot order. If you are using a BIOS acquired from your motrherboard manufactured BIOS dowloads, then your BIOS should support booting to USB. If it does not, a defect in the BIOS or motherboard exists.BIOSes are not written consistently to support a method for boot of a USB flash device. Method of setting the drive bootable should be chosen compatible with BIOS (often, it is not obvious which method).

I have examined the timeline at http://unattended.msfn.org/unattended.xp/v...bc7b051b596c95/ and quote the GUI section below: The timeline does not make mention of when Built-in accounts are created. When respective to elements on the timeline are the Windows built-in accounts created?

xtremee, try UltraISO ( http://www.ezbsystems.com/ultraiso/download.htm ); its image write formats seem to be supported by your BIOS (make sure the device is set to boot in Boot Order). The trial mode is limited to 300 MB documents (limitation may only be regarding saving of image files; I am uncertain whether writing image files greater than 300 MB is limited). To write an image to a USB mass storage device with UltraISO, do the following: Open UltraISO. Open the image file to be written. From menus, select "Bootable -> Write Disk Image...". Select Drive to write image and write method if necessary. Select "Write" button.

xtremee's USB controllers should be USB 1.1.

I have tried using "ie6setup.exe /Q:A /R:N", but progress failed to show. I tried using "ie6setup.exe /Q /R:N", and installation seemed to occur as desired. I then tried using "ie6setup.exe /Q:U /R:N", and installation also seemed to occur as desired. What is the difference in function between "ie6setup.exe /Q /R:N" and "ie6setup.exe /Q:U /R:N"?

Wouldn't the "/Q:A" switch not show any dialogues?I want to all a user to see what is being intsalled. Would "/Q:U" do this?

It appears that two powercfg.exe utilities exist for the 32-bit Windows Server 2003 family operating systems: powercfg.exe from Windows Server 2003 (Gold or RTM) and powercfg.exe from Windows Server 2003 with Service Pack 2. Which Windows Server 2003 powercfg.exe should be used with Windows 2000? Also, which powercfg.exe utility is compatible with Windows XP Professional with Service Pack 1 (x86)? EDIT: I would speculate that the powercfg.exe utility included with the Gold Windows Server 2003 can configure power settings for Windows 2000 (except Terminal Services), gold or with any Service Pack, and Windows XP, Gold or with Service Pack 1 (maybe also later versions). It may be that Microsoft Corporation made newer powercfg.exe utilities incompatible with older operating systems. EDIT2: I verified that powercfg.exe for the Gold Windows Server 2003 works on Windows 2000.

I did not know that powercfg.exe existed. It appears that I shall need the powercfg.exe from Windows Server 2003 (not from Windows XP Service Pack 2).

Perhaps what I wanted was not well understood. I want to enable hibernation for Windows 2000 Professional with Service Pack 4 without having to maintaining copies of hiberfil.sys files. It would good if the hiberfil.sys file may be created without having to store a copy on the installation media(s) in its entirety.