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. 



penpen

Member
  • Content count

    3
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

0 Neutral

About penpen

  1. TEXTMODE MassStorageDrivers Method

    This is mentioned on the driverpacks forums. To quote from that link: This is specific to the AMCC 3ware 7000/8000 series sata controller drivers. Later in that same thread, its stated that these drivers were removed from the driverpacks project (the initial post is in reference to a much older version of DriverPacks). However, for my disk I just ended up using a workaround with a multiboot, with a different winnt.sif for if I am installing on a system using that card, or a different one I can use if I just want to use the native driverpacks drivers (which use method 1 for driver slipstreaming). The guide outlined in the first post of this thread is what i think is known as method2, using $OEM$\TEXTMODE and defining an [OemBootFiles] section in winnt.sif/unattend.txt I also found that with all of the driverpacks mass storage drivers enabled, it takes a long time for the installer to start as it loads every mass storage driver into memory every time you run the installer. For this reason, I may end up making a few other multiboot options to load different sets of drivers to allow the installer to run a little more smoothly at the start. Since method1 drivers add lines for them into txtsetup.sif, you should be able to directly reference them in winnt.sif as such: ;this is example code from txtsetup.sif, of lines which were added by driverpacks [SCSI] aic78xx = "Adaptec AHA-294X/AHA-394X/AIC-78XX SCSI Controller" aic78u2 = "Adaptec AHA-294XU2/AIC-7890 SCSI Controller" arc = "Adaptec RAID Storport Driver" afcnt = "Agilent HHBA-510x PCI Fibre Channel Controller" cpqarray = "Compaq Drive Array" taking these lines, we should be able to create a winnt.sif that only looks for those specific drivers by placing them in [MassStorageDevices] as such: ;this is example code from winnt.sif, referencing the lines above from txtsetup.sif [MassStorageDrivers] "IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL";if you are going to define any set of method1 drivers in winnt.sif, you need at least this one. "Adaptec AHA-294X/AHA-394X/AIC-78XX SCSI Controller" = "RETAIL" "Adaptec AHA-294XU2/AIC-7890 SCSI Controller" = "RETAIL" "Adaptec RAID Storport Driver" = "RETAIL" "Agilent HHBA-510x PCI Fibre Channel Controller" = "RETAIL" "Compaq Drive Array" = "RETAIL" I'll probably test that out later tonight and post my results.
  2. TEXTMODE MassStorageDrivers Method

    EDIT: here is my previous post For reference, this method does override txtsetup.sif, or rather, it overrides where it looks in that file. I placed a different raid controller in my test system which worked before I defined a [MassStorageDrivers] section or [OemBootFiles] section in my winnt.sif and it was unable to find the drive during the installation. Previously, I had added entries to winnt.sif under the IDE cdrom one as such: "Adaptec AHA-294X/AHA-394X/AIC-78XX SCSI Controller" = "RETAIL" "Adaptec AHA-294XU2/AIC-7890 SCSI Controller" = "RETAIL" "Adaptec RAID Storport Driver" = "RETAIL" "Agilent HHBA-510x PCI Fibre Channel Controller" = "RETAIL" "Compaq Drive Array" = "RETAIL" "Compaq Fibre Channel Host Controller" = "RETAIL" "Smart Array 53xx/63xx Controller" = "RETAIL" "Emulex Scsiport Fibre Channel Host Adapters" = "RETAIL" with the same names listed in txtsetup.sif. However, with something like 50 or so drivers to list, or some other factor I may be unaware of, the presence of all of those devices in [massstoragedevices] prevented it from detecting the controller I was trying to add to the install: "AMCC 3ware 7000/8000 Series ATA RAID Controller" = "OEM" As listed previously in this thread, this is the only method that works with this controller. I think it may be possible to get past this by referencing txtsetup.sif in the oembootfiles section, but I'm not sure if that would work.
  3. I'm working on a server 2003 unattended installation in which i want the user to be prompted for the eula/repair in the beginning of text mode, select a partition and leave the rest to the unattended installation. So far, I have something close to that, except during the gui mode installation I am prompted to agree to a license for server 2003 SP2. Is there any way to skip this prompt without disabling the repair/eula agreement during text mode? I started with nlite, but I think I can finish this just by manually ediiting winnt.sif. Here's a copy of my winnt.sif: [Data] Autopartition=0 MsDosInitiated=0 UnattendedInstall="Yes" [GuiUnattended] AdminPassword="password" TimeZone=020 OEMSkipRegional=1 OemSkipWelcome=1 [LicenseFilePrintData] AutoMode=PerSeat [Components] [UserData] ProductKey="xxxx-xxxxx-xxxx-xxxxx-xxxxx" ComputerName=xxxxxx FullName="xxxxxxx" OrgName="xxxxxxxx" [RegionalSettings] Language= "0409" [Networking] InstallDefaultComponents="Yes" [Identification] JoinWorkgroup="WORKGROUP" [GuiRunOnce] "%SystemRoot%\System32\nLite.cmd"
×