Bilou_Gateux

Ooops! Same answer as Dahi. :: set local install DatabaseUpdateDirectoryHttp variable :: 3 tokens are 'ValueName' 'Type' 'Value under selected Key' :: delims is a tab delimiter for /F "tokens=3 delims= " %%I in ('REG QUERY "HKLM\SOFTWARE\Data Fellows\F-Secure\Anti-Virus" /v "DatabaseUpdateDirectoryHttp" ^| findstr "REG_SZ" ') do set DatabaseUpdateDirectoryHttp="%%I" :: For troubleshooting purposes IF %DEBUG%==TRUE echo. DatabaseUpdateDirectoryHttp = %DatabaseUpdateDirectoryHttp%

MITeC select "System Information Component" download the freeware package: contains RBE ROM BIOS Explorer - tool for BIOS/SMBIOS/DMI browsing and disassembling. Works fine under XP Embedded, haven't yet checked under PE. File > Details <CTRL>+<D> will give you all infos read from SMBIOS.

PXE Network - Linux Based - Boot winpe from the net You can map a network share from WinPE and launch the install WINNT32.EXE from the distribution share. PXES HOWTO: Installing in a Microsoft only environment. PXELINUX and Micro RIS I'm using a mixed method and these links showed me the way. 2K Server with DHCP and TFTPD services. MS network DOS boot disk image stored on the 2K server PXE boot load DOS and MS Network map to network share launch WINNT.EXE (16 bits version)

Thanks RyanVM Something new for Win2K users. This new IE6 update is the first one to use this kind of HF for upgrading OS. Should solve the issues we having with GreenMachine when integrating IE6 HF to W2K RTM + IE6 install from SVCPACK.

Did i forget to use the Search button before asking ? Not the one i was searching for but it answers my question: RyanVM how to SVCPACK update

Doing my updates step by step, i haven't included this HF for recommended updates. Starting to update 2K First, and then recommended WMP, IE6, and if i find some more time, .NET.

@Incroyable HULK I was talking about the two different folders when i have extracted the Hotfix made of 2 subfolders rtmgdr and rtmqfe each containing 9 files after extraction. Comparing update_w2k.inf with update_w2k_RTMQFE.inf shows only differences with shdocvw.dll registry entries. browseui.dll Binary file is identical cdfview.dll Binary file is identical iepeers.dll Binary file is different inseng.dll Binary file is different mshtml.dll Binary file is different shdocvw.dll Binary file is identical shlwapi.dll Binary file is identical urlmon.dll Binary file is different wininet.dll Binary file is different which one should we use to slipstream to i386 source: RTMQFE or RTMGDR content. I'm using XPCREATE by GM to build my UA install. I don't install the HF from RunOnce or a batch file at end of install.

What folder should i keep to integrate to my i386 source.

For More Information Windows Security Updates Summary for February 2005 ADD SVC-HF1\Windows2000-KB<hotfix_nb>-x86-<language>.exe | MD5 Hash Windows2000-KB873333-x86-ENU.EXE 064872A2FD0F89158CF7AEDC1E51C98B Windows2000-KB885250-x86-ENU.EXE 1FB3F1A7D1529F7CF00F8098FBC8AA21 Windows2000-KB885834-x86-ENU.EXE 2038D0C96DDDEBED2FC0EEAAA3B95DCF Windows2000-KB888113-x86-ENU.EXE 7A13E18F5B481368B7803E77EA872149 Windows2000-KB890047-x86-ENU.EXE 9E3369793B562551B5481B6C042DCBA3 Windows2000-KB891781-x86-ENU.EXE EDA02F738DC1BD95BCA3D9099EC7E410 DEL SVC-HF1\WindowsMedia9-KB837272-<language>.exe ADD SVC-HF1\WindowsMedia9-KB885492-<language>.exe | MD5 Hash WindowsMedia9-KB885492-x86-ENU.exe 2375F9A2035D578C1B839F4E57851EA4 DEL SVC-HF1\IE6.0sp1-KB889669-Windows-2000-XP-x86-<language>.exe ADD SVC-???\IE6.0sp1-KB867282-Windows-2000-XP-x86-<language>.exe | MD5 Hash IE6.0sp1-KB867282-Windows-2000-XP-x86-ENU.exe 9A79BA73D97915C550B67E025998B0FF

@Incroyable HULK Adobe Reader download page Adobe Reader 6.02 FRENCH Middle Eastern links: Adobe Reader 6.0.2, basic version (Middle Eastern) for Windows Adobe Reader 6.0.2, full version (Middle Eastern) for Windows Est-ce que le Québec saurait se satisfaire d'une version supportant les langues du Moyen-Orient ? @all I already heard your answer Adobe Reader 7.0 Unattended Mine is "full featured bloatware" don't bother Just posted an answer to pick-up the instructions posted by Alanol about escaping quotes.

Need only a fast command line tool to mount standard ISO images during UA install. I don't want (need) any GUI. End users don't need to have access to this kind of tools on the installed boxes. Installing the ShellExtension DLL is not mandatory. As pointed by Jaclaz, TrueCrypt seems to be a good solution for mounting encrypted containers from the command line. For my own usage, i can use various solutions. @buletov Is your question related to my batch files using filedisk ? IF you can hardcoding the letter of mounted image in !mount.cmd batch file. Just replace %FirstAvailableDriveLetter% with the letter you want to use. I have set the letter through variable to be more versatile.

Personal Use: Pre-configured DVD each new version of software >>> rebuild your UA DVD and reburn. Corporate Use: Network install each new version of software >>> modify your share point and that is.

Yes it's another idea i would like to use. As filedisk can handle IMG files (and not only ISO), we can store some valuable data into an img file and mount it when needed. No left data on the local Hard Drive. I need to have the ability to use command line tool to run it unattended. Reading the features of TrueCrypt, it seems possible to use it with command lines.

Office 2003 Professional Network Install

I'm using an improved solution posted here: filedisk + ISO image stored somewhere on a network share.

infos related to IE6SP1 slipstream into W2K source moved Microsoft Internet Explorer 6 Service Pack 1 (SP1) Version 6.0.2800.1106

The author is idle.newbie Yes, it would be fine to dynamically update the WINNT.SIF at T-39.

OK i have created the same dir tree as you on my D: partition D:\$OEM$\$1\PnPDrvrs contains all drivers subdirs and OEMPnPDriversPath.cmd D:\I386 contains the original WINNT.SIF Open command prompt: cmd /k cd /d D:\$OEM$\$1\PnPDrvrs run: OEMPnPDriversPath D:\$OEM$\$1\PnPDrvrs D:\I386\WINNT.SIF and check the result (new WINNT.SIF) in D:\$OEM$\$1\PnPDrvrs OemPnPDriversPath = "$OEM$\$1\PnPDrvrs\Display\Intel;$OEM$\$1\PnPDrvrs\Display\NVidia;$OEM$\$1\PnPDrvrs\Hdc\Intel;$OEM$\$1\PnPDrvrs\Media\Fujitsu;$OEM$\$1\PnPDrvrs\Net\BRCM;$OEM$\$1\PnPDrvrs\Net\Intel;$OEM$\$1\PnPDrvrs\System\Intel;$OEM$\$1\PnPDrvrs\Usb\Intel" But the solution is not clean as having the PnP Drivers dir on root of harddrive to build the OemPnPDriversPath = Compare the result with my previous post. I suggest to first build the winnt.sif with your DP dir in root of hard drive and then move to the subdir you want ie $OEM$\$1

The batch file doesn't direct edit your source WINNT.SIF but recreate a new one wich is saved to the dir where you have saved the batch file. Try first to move the batch file to your DP dir ie K:\$OEM$\$1\DP and then, the resulting new SIF file should be in K:\$OEM$\$1\DP\WINNT.SIF

My %systemdrive% is as described below: $OEM$ dir PnPDrvrs dir UNATTEND.TXT code Open command prompt in C:\PnPDrvrs: OEMPnPDriversPath C:\PnPDrvrs C:\$OEM$\UNATTEND.TXT C:\PnPDrvrs\WINNT.SIF content: OemPnPDriversPath = "PnPDrvrs\Display\Intel;PnPDrvrs\Display\NVidia;PnPDrvrs\Hdc\Intel;PnPDrvrs\Media\Fujitsu; ***//cut for easy reading//*** PnPDrvrs\Net\BRCM;PnPDrvrs\Net\Intel;PnPDrvrs\System\Intel;PnPDrvrs\Usb\Intel"

Let's MadGutts choose the best solution for him. Although imaging isn't my preferred solution, i would like to help him as i have already encountered some similar problems. @Taggs My own solution is to move my Magnia Z310 with me as it's a small form factor server used only for UA. CD install is too slow for me and i use it only if i have'nt any other solution. Forget to mention my notebook don't have any CD drive. But Wired NIC is PXE compliant. RIS is just the perfect solution to reinstall the OS. I've voted for RIS thread. Hope moderator will find it's a good idea as more and more members post requests about RIS.

@Taggs do you always take your server with you when you go to another site not connected to the main site where the server resides ? RIS and Imaging are two differents answers to specific problems. another solution i use is to: install a base PC from my RIS Server with all HF, updates and sofware integrated, add the most used PnP drivers (Display, Media, Net, Chipset) to the %systemdrive%, set the path in registry, sysprep the install and then imaging the Drive. As you mention, then restoring a ghost image is very fast. In a corporate environment, IT Pro uses site licence and most branded computers have standard components (Intel Chipset + Intel Display + SoundMax Media + Intel or Broadcom Net). Easy to create and update a driver package which fits all the HW.

Assuming your destination HDD has already a FAT partition, why don't you first copy your $OEM$ dir to the root of the HDD partition and then launch the install with WINNT.EXE with a batch file. I'm using this method to install W2K from WinPE with a modified batch file and launching WINNT32.EXE Source Code (original from BartPE modified to my needs): u32.cmd Take care this sample code works only from WinPE (using diskpart.exe) The command i use is U32 -f U:\XPCD\I386 C: I only use the second option -f, the code isn't clean as i haven't removed unneeded original lines for installing BartPE as primary OS. I haven't used this method a long time ago, thanks to my RIS Server. it's just a suggestion to help you doing the same from DOS with a batch file. This link can help you to build your tree for UA install from a distribution share (local HDD or network share) Installing Windows XP Professional and Hotfixes in Unattended Mode

@tommyp No, i was refering to "Recommended Updates" to: directX 7.0 MDAC 2.53 WMP 6.4 Most users always want the latest available version, although it's not necessary needed but they want WU claims: "Woooahhh, your PC is Up2Date and you have 0 recommended update to install". Not beeing a hardcore gamer, DirectX 8.1b is just perfect for me, and there is better alternative to WMP but i need to run an updated MDAC >= 2.71 on my computer to use a database application. You're method is nice and i recommend to all 2K users (some of them just discover it after i've posted about it) but in my case, you only apply the HF to MDAC2.53 and i need to upgrade to 2.71 and then apply HF. If i could achieve the same for MDAC as you've made for IE6, it would make my life easier. @Gurgelmeyer Don't see any flag under your avatar. Wärest du ein deutscher Bürger ? Ich habe diesen deutscher Universität Internet-Adresse gefunden here I speak very badly German, please post your messages in English

To making certain your image does not blue screen when deployed to a new PC: ensure all the computers are ACPI compliant machines and use the same Configuration Power Interface-compliant (ACPI-compliant) hardware abstraction layer (HAL). If you are running Windows 2K, the first step is to determine if you have an ACPI compliant system. From the Device Manager, in the hardware list, click on Computer and if "ACPI" is listed then your computer is running in ACPI mode. change the Mass Storage Controller Driver From the Device Manager, open up the "IDE ATA/ATAPI Controllers" section. (On a typical system there will be three entries under this - the controller itself, and then the primary/secondary IDE channels.) Double-click on the entry for the controller, and change the driver to the generic default Microsoft "Standard Dual-Channel PCI IDE Controller". Set DMA to "PIO Only". (Double click on the IDE controller icon in the Device Manager. Click on the "Driver" tab. Click on "Update Driver". Click next. Click "display list of the known drivers for this device so that I choose a specific driver" button. Click next. There it is.) This avoids the INACCESSIBLE_BOOT_DEVICE BSOD. Don't works for the PCs with SATA or SCSI hard disk controllers. Use the SysPrep tool and imaging software (DriveImage or Ghost) to deploy machines with a standard image to move a Windows 2000 installation to new hardware (even to motherboards having a different IDE hard disk controller). Fixing ACPI Problems in Windows 2000 Understanding how Windows 2000 handles power management can boggle the mind. The Advance Configuration Power Interface (ACPI) Hardware Abstraction Layer (HAL) is automatically installed if Windows 2000 detects ACPI features in the BIOS during Setup. Often times, if the PC isn't 100% ACPI compliant, you'll see very odd behavior such as improper shutdowns, DRIVER_POWER_STATE STOP errors, or other odd behavior from the system. If you can flash the BIOS with a compliant version, that should help. The objective is to get a bootable system by installing basic Microsoft default drivers which are compatible with most hardware. After the system is running, new hardware can be detected, and specific optimized drivers can then be loaded Well written tutorial here from: "Bill Geschwind"