Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content count

  • Donations

  • Joined

  • Last visited

Community Reputation

0 Neutral

About goldfinger

  1. Native x64 sleep.exe

    Maybe someone will need a native 64-Bit sleep.exe for unattend installation with winpe 2005 x64, too. sleep.exe
  2. MD5 hash of MSDN Windows Vista english

    Thanks for the information. Unfortunately I have the same md5 hash. Next I will try to install another machine. Source: en_longhorn_beta1_dvd.iso Sectors: 1268876 MD5 Signature: 8e7dd8f00de969ba362293a8192ef177 goldfinger
  3. Please can someone send the MD5 checksum of a working MSDN Windows Vista Beta 1 ISO file (en_longhorn_beta1_dvd.iso). I think my image is corrupt but I'm not sure. goldfinger
  4. Integration of Mui languages

    I think the right way is to add the mui package to the x64 image and install it automatically. Since the language pack is big you have to use a dvd instead of a cd. http://www.msfn.org/board/index.php?showtopic=45790 goldfinger
  5. BootCD not working w/ Adaptec Hostraid

    The problem is solved. First you can't use $OEM$\TEXTMODE [massstoragedrivers]/[oembootfiles] for a CD-boot style installation. What will work is to slipstream the drivers and to modify some registry hives. But this method is an unsupported hack. It will be better to use WINPE. Here are a short description: txtsetup.sif: [SourceDisksFiles] a320raid.sys = 1,,,,,,5_,4,1,,,1,4 a320raid.inf = 1,,,,,,,20,0,0 a320mgt.inf = 1,,,,,,,20,0,0 a320raid.cat = 1,,,,,,,,3,3 a320mgt.cat = 1,,,,,,,,3,3 [HardwareIdsDatabase] PCI\VEN_9005&DEV_809F = "a320raid" PCI\VEN_9005&DEV_8090 = "a320raid" PCI\VEN_9005&DEV_8091 = "a320raid" PCI\VEN_9005&DEV_8092 = "a320raid" PCI\VEN_9005&DEV_8093 = "a320raid" PCI\VEN_9005&DEV_8094 = "a320raid" PCI\VEN_9005&DEV_809E = "a320raid" PCI\VEN_9005&DEV_808F = "a320raid" PCI\VEN_9005&DEV_8080 = "a320raid" PCI\VEN_9005&DEV_8097 = "a320raid" PCI\VEN_9005&DEV_809D = "a320raid" PCI\VEN_9005&DEV_809C = "a320raid" PCI\VEN_9005&DEV_8095 = "a320raid" PCI\VEN_9005&DEV_8096 = "a320raid" [SCSI.Load] a320raid = a320raid.sys,4 [SCSI] a320raid = "Adaptec HOSTRAID driver for Windows XP/2003 x64 Edition" copy scsi-driver files to: CDROOT\$OEM$\TEXTMODE and CDROOT\$OEM$\drivers\09_Storage\A320RAID I also compressed the driver files with makecab and added it to CDROOT\AMD64 Modify <amd64>\setupreg.hiv using regedit (load hive unload hive) If you don't enter this entries the driver will be loaded during textmode setup but won't find any disks. [HKEY_LOCAL_MACHINE\ControlSet001\Services\a320raid] [HKEY_LOCAL_MACHINE\ControlSet001\Services\a320raid\Parameters] [HKEY_LOCAL_MACHINE\ControlSet001\Services\a320raid\Parameters\PnPInterface] "5"=dword:00000001 Add entries for the mini-port driver to <amd64>\HIVESYS.INF. If not you will get a BSOD STOP 0x/B after textmode setup has completed and when attempting to boot into GUI mode setup for the first time. add the two entries *above* the line: HKLM,"SYSTEM\CurrentControlSet\Services\adpu160m","ErrorControl",0x00010003,1 ... HKLM,"SYSTEM\CurrentControlSet\Services\ACPIEC","Type",0x00010001,1 HKLM,"SYSTEM\CurrentControlSet\Services\a320raid\Parameters",,0x00000012 HKLM,"SYSTEM\CurrentControlSet\Services\a320raid\Parameters\PnpInterface","5",0x00010003,1 HKLM,"SYSTEM\CurrentControlSet\Services\adpu160m","ErrorControl",0x00010003,1 HKLM,"SYSTEM\CurrentControlSet\Services\adpu160m","Group",0x00000002,"SCSI miniport" don't forget to add the path to winnt.sif OemPnPDriversPath="drivers\09_Storage\A320RAID" Burn new CD/DVD.
  6. BootCD not working w/ Adaptec Hostraid

    Yes, manufacture and modell section seems to be correct. Stripped version of a320raid.inf [Version] signature="$Windows NT$" Class=SCSIAdapter ClassGUID={4D36E97B-E325-11CE-BFC1-08002BE10318} Provider=%INF_PROVIDER% CatalogFile="a320raid.cat" DriverVer=03/25/2005, [SourceDisksNames] 1 = %FLOPPY_DESCRIPTION%,,,\ [SourceDisksFiles] a320raid.sys= 1,, [AdptMgtFiles] ; ; Dummy section to satisfy ChkInf tool ; [ControlFlags] ;ExcludeFromSelect= [Manufacturer] %ADP%= ADAPTEC, NTamd64 [ADAPTEC.NTamd64] ; ; All U320 HostRAID device IDs (AIC-7902s and ASC-39320Ds) ; %PCI\VEN_9005&DEV_809F.DeviceDesc% = HostRAID_Inst,PCI\VEN_9005&DEV_809F %PCI\VEN_9005&DEV_8090.DeviceDesc% = HostRAID_Inst,PCI\VEN_9005&DEV_8090 %PCI\VEN_9005&DEV_8091.DeviceDesc% = HostRAID_Inst,PCI\VEN_9005&DEV_8091 %PCI\VEN_9005&DEV_8092.DeviceDesc% = HostRAID_Inst,PCI\VEN_9005&DEV_8092 %PCI\VEN_9005&DEV_8093.DeviceDesc% = HostRAID_Inst,PCI\VEN_9005&DEV_8093 %PCI\VEN_9005&DEV_8094.DeviceDesc% = HostRAID_Inst,PCI\VEN_9005&DEV_8094 %PCI\VEN_9005&DEV_809E.DeviceDesc% = HostRAID_Inst,PCI\VEN_9005&DEV_809E %PCI\VEN_9005&DEV_808F.DeviceDesc% = HostRAID_Inst,PCI\VEN_9005&DEV_808F %PCI\VEN_9005&DEV_8080.DeviceDesc% = HostRAID_Inst,PCI\VEN_9005&DEV_8080 %PCI\VEN_9005&DEV_8097.DeviceDesc% = HostRAID_Inst,PCI\VEN_9005&DEV_8097 ; Rev B IDs %PCI\VEN_9005&DEV_809D.DeviceDesc% = HostRAID_Inst,PCI\VEN_9005&DEV_809D %PCI\VEN_9005&DEV_809C.DeviceDesc% = HostRAID_Inst,PCI\VEN_9005&DEV_809C %PCI\VEN_9005&DEV_8095.DeviceDesc% = HostRAID_Inst,PCI\VEN_9005&DEV_8095 %PCI\VEN_9005&DEV_8096.DeviceDesc% = HostRAID_Inst,PCI\VEN_9005&DEV_8096 ; Management Device %ADPTManagement.DeviceDesc% = NODRV, SCSI\ProcessorADAPTEC_HostRAID________1.0_ [NODRV] ; ; Dummy directive to satisfy ChkInf tool ; CopyFiles = AdptMgtFiles [NODRV.Services] ; ; this is blank to just allow the install to succeed ; AddService = ,%SPSVCINST_ASSOCSERVICE%; null service install [HostRAID_Inst.nt] CopyFiles=@a320raid.sys [HostRAID_Inst.nt.HW] DelReg = LegacyScsiportValues [HostRAID_Inst.nt.Services] AddService = a320raid, 0x00000002, HostRAID_Service_Inst, Miniport_EventLog_Inst [HostRAID_Service_Inst] ServiceType = 1 ; SERVICE_KERNEL_DRIVER StartType = 0 ; SERVICE_BOOT_START ErrorControl = 1 ; SERVICE_ERROR_NORMAL ServiceBinary = %12%\a320raid.sys LoadOrderGroup = SCSI Miniport AddReg = pnpsafe_pci_addreg AddReg = TimeOutValue_addreg AddReg = MaxLunsToScan_addreg ;AddReg = QueueDepth_addreg [pnpsafe_pci_addreg] HKR,"Parameters\PnpInterface","5",0x00010001,0x00000001 [TimeOutValue_addreg] HKLM,SYSTEM\CurrentControlSet\Services\Disk,TimeOutValue,0x00010001,0x0000003C [MaxLunsToScan_addreg] HKLM,System\CurrentControlSet\Services\a320raid\Parameters\Device,"DriverParameter",0x00000000,"MAXLUNS=8" [LegacyScsiportValues] HKR,Scsiport,BusNumber HKR,Scsiport,LegacyInterfaceType HKR,Scsiport,SlotNumber [Miniport_EventLog_Inst] AddReg = Miniport_EventLog_AddReg [Miniport_EventLog_AddReg] HKR,,EventMessageFile,0x00020000,"%%SystemRoot%%\System32\IoLogMsg.dll" HKR,,TypesSupported,0x00010001,7 [DestinationDirs] DefaultDestDir = 12 [Strings] INF_PROVIDER="Adaptec" ADP="Adaptec" FLOPPY_DESCRIPTION="Adaptec HostRAID U320 Driver For Windows 2000/XP/2003" #FLOPPY_DESCRIPTION="Adaptec Windows SCSI Driver" #ADPTManagement.DeviceDesc = "Adaptec Processor Device (Pseudo)" ADPTManagement.DeviceDesc = "Adaptec HostRAID Management Processor Device for U320" ; Adaptec SCSI Controllers supported by this driver. ; ; All U320 HostRAID device IDs (AIC-7902s and ASC-39320Ds) ; PCI\VEN_9005&DEV_809F.DeviceDesc = "Adaptec Embedded SCSI HostRAID Controller" PCI\VEN_9005&DEV_8090.DeviceDesc = "Adaptec Embedded SCSI HostRAID Controller" PCI\VEN_9005&DEV_8091.DeviceDesc = "Adaptec Embedded SCSI HostRAID Controller" PCI\VEN_9005&DEV_8092.DeviceDesc = "Adaptec Embedded SCSI HostRAID Controller" PCI\VEN_9005&DEV_8093.DeviceDesc = "Adaptec Embedded SCSI HostRAID Controller" PCI\VEN_9005&DEV_8094.DeviceDesc = "Adaptec Embedded SCSI HostRAID Controller" PCI\VEN_9005&DEV_809E.DeviceDesc = "Adaptec Embedded SCSI HostRAID Controller" PCI\VEN_9005&DEV_808F.DeviceDesc = "Adaptec Embedded SCSI HostRAID Controller" PCI\VEN_9005&DEV_8080.DeviceDesc = "Adaptec Embedded SCSI HostRAID Controller" PCI\VEN_9005&DEV_8097.DeviceDesc = "Adaptec Embedded SCSI HostRAID Controller" PCI\VEN_9005&DEV_809D.DeviceDesc = "Adaptec Embedded SCSI HostRAID Controller" PCI\VEN_9005&DEV_809C.DeviceDesc = "Adaptec Embedded SCSI HostRAID Controller" PCI\VEN_9005&DEV_8095.DeviceDesc = "Adaptec Embedded SCSI HostRAID Controller" PCI\VEN_9005&DEV_8096.DeviceDesc = "Adaptec Embedded SCSI HostRAID Controller" ;******************************************* ;Handy macro substitutions (non-localizable) SPSVCINST_ASSOCSERVICE = 0x00000002 a320mgt.inf [Version] Signature = "$WINDOWS NT$" Class = System ClassGuid = {4D36E97D-E325-11CE-BFC1-08002BE10318} Provider = %ADPT% CatalogFile.ntamd64 = a320mgt.cat DriverVer=09/18/2004,3.00.045 [ControlFlags] ExcludeFromSelect = * [SourceDisksNames] 1 = %FLOPPY1_DESCRIPTION%,hraidsk1,, [SourceDisksFiles] [AdptMgtFiles] ; ; Dummy section to satisfy ChkInf tool ; [DestinationDirs] DefaultDestDir = 12 [Manufacturer] %ADPT% = ADPT,NTamd64 [ADPT] ; On the right hand side, what you insert is exactly what's sent in the inquiry. Each byte and its case should be identical. An underscore "_" character means dont care. The following line is for the inquiry string with ; 8 byte Vendor = "ADAPTEC" ; 16 byte Product = "HostRAID " ; 4 byte Revision = "1.0 " ; %ADPTManagement.DeviceDesc% = NODRV, SCSI\ProcessorADAPTEC_HostRAID________1.0_ [NODRV] ; ; Dummy directive to satisfy ChkInf tool ; CopyFiles = AdptMgtFiles [NODRV.Services] ; ; this is blank to just allow the install to succeed ; AddService = , %SPSVCINST_ASSOCSERVICE% ; null service install [strings] ADPT = "Adaptec" ADPTManagement.DeviceDesc = "Adaptec HostRAID Management Processor Device" FLOPPY1_DESCRIPTION = "Adaptec HostRAID U320 Driver Ver 3.00" ;******************************************* ;Handy macro substitutions (non-localizable) SPSVCINST_ASSOCSERVICE = 0x00000002 Yes, this will work. I tried to slipstream the driver, too. The driver will be load but it will see no drives.
  7. By loading the a320raid driver from a customized x64 CD I get the message: File TXTSETUP.OEM caused an unexpected error (18) at line 1896 in d:\srvrtm\base\boot\setup\oemdisk.c Here you can see the complete configuration Does anyone know if there is a difference of textmode installation (txtsetup.oem between XP x64 and XP 32 Bit? Did someone successfully add SCSI Raid Adapter (not SATA) to a unattended CD of Windows x64 edition? BTW: Sorry for cross posting but it's not clear to me which will be the right forum for x64 unattended questions: Windows XP 64 Bit Edition or Unattended Windows?
  8. I tried to make a CD based installation for Dell Precision 670 with Adaptec U320 hostraid controller 7901. I know that the drivers are correct because I can install windows x64 manually with help of the F6 key (Filename R98304 from Dell FTP Server) When try to boot from the CD, I get the message: "File TXTSETUP.OEM caused an unexpected error (18) at line 1896 in d:\srvrtm\base\boot\setup\oemdisk.c." press any key to continue" In the next step the CDROM driver will be load and further the message will appear that no disks are found. Ok it's clear that the a320raid Driver won't be load correctly. The driver are digitally signed and decorated. Here are my configurations: I copied the adaptec driver files under <CDROOT>\$OEM$ and <CDROOT>\$OEM$\TEXTMODE a320mgt.cat a320mgt.inf a320raid.cat a320raid.inf a320raid.sys DriverLanguageMap.xml hraidsk1 txtsetup.oem Version.txt txtsetup.oem [Disks] d2 = "Adaptec U320RAID Driver v1.00 (Windows EM64T/AMD64 for 2003 )", \hraidsk1, \ [Defaults] scsi = ADAPTEC_64BIT_U320HOSTRAID [scsi] ADAPTEC_64BIT_U320HOSTRAID = "Adaptec HOSTRAID driver for Windows XP/2003 x64 Edition" [Files.scsi.ADAPTEC_64BIT_U320HOSTRAID] driver = d2,a320raid.sys, a320raid inf = d2,a320raid.inf inf = d2,a320mgt.inf catalog = d2,a320raid.cat catalog = d2,a320mgt.cat [Config.a320raid] value = "", Group, REG_SZ, "SCSI Miniport" value = "", Start, REG_DWORD, 0 value = "", Tag, REG_DWORD, 1 value = "", Type, REG_DWORD, 1 value = Parameters\PnpInterface,5,REG_DWORD,1 [HardwareIds.scsi.ADAPTEC_64BIT_U320HOSTRAID] id = "PCI\VEN_9005&DEV_809F","a320raid" id = "PCI\VEN_9005&DEV_8090","a320raid" id = "PCI\VEN_9005&DEV_8091","a320raid" id = "PCI\VEN_9005&DEV_8092","a320raid" id = "PCI\VEN_9005&DEV_8093","a320raid" id = "PCI\VEN_9005&DEV_8094","a320raid" id = "PCI\VEN_9005&DEV_809E","a320raid" id = "PCI\VEN_9005&DEV_808F","a320raid" id = "PCI\VEN_9005&DEV_8080","a320raid" id = "PCI\VEN_9005&DEV_8097","a320raid" # Rev B IDs id = "PCI\VEN_9005&DEV_809D","a320raid" id = "PCI\VEN_9005&DEV_809C","a320raid" id = "PCI\VEN_9005&DEV_8095","a320raid" id = "PCI\VEN_9005&DEV_8096","a320raid" winnt.sif [Data] AutomaticUpdates = 1 AutoPartition=0 MsDosInitiated=0 UnattendedInstall=Yes [Unattended] AutoActivate=No UnattendMode=DefaultHide OemPreinstall=Yes OemSkipEula=Yes ExtendOEMPartition=1 FileSystem=ConvertNTFS DriverSigningPolicy=Ignore OemFilesPath = ".\$OEM$" OemPnPDriversPath="drivers\00_Chipset\IntelINF;drivers\02_Video\nVidia71.84" UnattendSwitch=Yes Hibernation=1 WaitForReboot=No DisableDynamicUpdates=Yes [GuiUnattended] AdminPassword=* OEMSkipRegional=1 TimeZone=110 OemSkipWelcome=1 [UserData] ComputerName=dell FullName="xxx" OrgName="xxx" ProductID= "xxxxx-xxxxx-xxxxx-xxxxx-xxxxx" [GUIRunOnce] [Display] BitsPerPel=32 Xresolution=1600 YResolution=1200 Vrefresh=75 [MassStorageDrivers] "Adaptec HOSTRAID driver for Windows XP/2003 x64 Edition"="OEM" "IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller"="RETAIL" [OEMBootFiles] txtsetup.oem a320raid.sys a320raid.inf a320mgt.inf a320raid.cat a320mgt.cat [RegionalSettings] LanguageGroup=1 Language=0407 InputLocale_DefaultUser=0407:00000407 UserLocale_DefaultUser=0407 [Components] Dialer="off" [Identification] JoinWorkgroup = XXX [Networking] InstallDefaultComponents=Yes [NetAdapters] Adapter1=params.Adapter1 [params.Adapter1] INFID=* [NetClients] MS_MSClient=params.MS_MSClient [NetServices] MS_SERVER=params.MS_SERVER [NetProtocols] MS_TCPIP=params.MS_TCPIP [params.MS_TCPIP] EnableLMHosts=No DisableDynamicUpdate=Yes SyncDomainWithMembership=0 DNS=Yes UseDomainNameDevolution=No AdapterSections=params.MS_TCPIP.Adapter1 [params.MS_TCPIP.Adapter1] SpecificTo=Adapter1 DHCP=Yes WINS=No NetBIOSOptions=0
  9. x64 MUI Installation

    For networkbased installation see readme.txt file of the MUI CD I used the following steps to make a customize CD installation to add the german interface to Windows x64 Prof. Edition. 1.) Copy all files from the MUI CD to the Root $OEM$\MUIINST of the x64 iso image 2.) Create a CMDLINES.TXT file in \$OEM$ cmdlines.txt: [CD-Path: \$OEM$, Network: AMD64\$OEM$, ] [Commands] ;Installing German Multi Language Pack ".\muiinst\muisetup.exe /i 0407 /d 0409 /r /s" 3.) Create an answer file named MUI.TXT in \$OEM$\MUIINST MUI.TXT: [CD-Path: \$OEM$\MUIINST, Network: AMD64\$OEM$\MUIINST] [unattended] OemPreinstall=Yes OemFilesPath=".\$OEM$" OemSkipEula=YES [RegionalSettings] LanguageGroup="1" Language="0407"
  10. Unattended Installation of x64 Edition

    What nonsense.If you made unattended installs of WinXP 32-bit, then its all still the same. This thread is a lot of hot-air on an irrelevant subject. From basic unattending to extreme advanced uA: http://unattended.msfn.org/ And the exact same thing can be extrapolated for RIS installs over the network - needs only Win2k or WS2k3. The bottom-line: If what you have been doing all along has never required WinPE, nor are you going to need it now with x64 either. <{POST_SNAPBACK}> **** straight, I practised with the XP64 beta and it was fine. Just had to put your stuff in the AMD64 folder rather than i386. <{POST_SNAPBACK}> I agree unattended CD based installation using winnt.sif is no problem. But network based installation via winnt32 is a problem without winpe. RIS or PXE installation will work but it's an overkill for my environment. Sorry that I don't pointed out enough that I want to make a network based installation with the x64 clients.
  11. Unattended Installation of x64 Edition

    RIS, ADS and SMS OSD will use WINPE. If I remember right you need the OPK (winpe) for RIS installation of x64, too. Windows PE is not included with RIS. The new version of the deployment tools above use the new winpe/w2k3sp1 feature to load winpe via ramdisk and PXE. I know that OSD will include WINPE 2005. Unfortunally there is no tool to extract WINPE 2005 from the WIM File. goldfinger
  12. Unattended Installation of x64 Edition

    I think WinPE 2005 is needed for a network based unattended installation. The winnt.sif methode will work only on a CD/DVD. Maybe this winnt.sif method will work with a local harddisk, too. I don't know. The main problem is that you can't run winnt32 of x64 edition under xp (32 Bit) or winpe 2004 (32 Bit) or BartPE. And there is no support of any DOS based installation (winnt). goldfinger
  13. How to make a unattended installation of windows x64 edition? -> Buy winpe 2005 (hope you will get it) What cheek! For a basic installation task you have to buy an additional software. Really I don't understand why winpe 2005 is not included with the x64 final edition. Ok M$ must make money ... I don't think that this is a sagacious policy. Setup and installation considerations for Windows x64 Edition-based computers http://support.microsoft.com/kb/896334/ goldfinger
  14. Hello, I tried today to use RunOnceEx to install hotfixes and applications but in the most cases I got a "file open - securiy warning" popup and the user could cancel the installation. Since I download some applications with a XP SP2 client I had to unblock the exe-files. Now I didn't get the warnung and all will work as expected. Is there a command line utility available to unblock the files? goldfinger