Jump to content

anthonyy

Member
  • Posts

    2
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

About anthonyy

anthonyy's Achievements

0

Reputation

  1. Dear Pascal, Hello, I spent some time creating an unattended CD for our Dell 2950's At first I had to do the floppy thing, F6 , etc. for the RAID drivers, but I had attempted what you are trying sithout success. I gave it a break for a few months and came back to it the other day and was successful. Here is what I did: Here is my UNATTENDED section in the winnt.sif file: [unattended] UnattendMode=FullUnattended OemSkipEula=Yes OemPreinstall=yes OemPnPDriversPath="drivers\percsas" TargetPath=\WINDOWS I created a $OEM$\$1\drivers\percsas folder right on the CD root and in that folder, I placed all of the Dell PERC driver files. Okay, next I had to add lines to the TXTSETUP.SIF file, with information pulled from the TXTSETUP.OEM file in the PERC drivers folder. Here is what I added to the end of the TXTSETUP.SIF file - note.....you must scroll all the way to the bottom and place your cursor after the last character, hit enter to get to the next empty line and paste this to the end of this file. [sourceDisksFiles] percsas.sys=1,,,,,,3_,4,1 [HardwareIdsDatabase] PCI\VEN_1028&DEV_0015&SUBSYS_1F011028="percsas" PCI\VEN_1028&DEV_0015&SUBSYS_1F021028="percsas" PCI\VEN_1028&DEV_0015&SUBSYS_1F031028="percsas" [sCSI.load] percsas = percsas.sys,4 [sCSI] percsas = "DELL PERC5 RAID Controller Driver (Server 2003 for x64)",percsas Now, these were from the 64bit driver files, but I don't think it's different for the 32 bit files, if that's the Operating System that you are installing. After I did the MAKECAB command line, I made sure that both the PERCSAS.SYS and PERCSAS.SY_ files were in the AMD64 folder, but for you that would be the I386 folder for 32bit O/S I don't recognize the megasas drivers, but this should work for the 2950. Also, I didn't use any of the [MassStorageDrivers] entries in the WINNT.SIF file. I hope this helps. Tony
  2. Hello, I know there have been many questions similiar to mine, but I've yet to find an answer that truly fits my issue. I have built an Unattended install CD that installs a Windows 2003 Standard server with everything we need, all the way up to enabling Remote Desktop. We basically wanted to be able to have a brand new server shipped to a remote office and have a non-technical person use a CD that they basically don't have to worry about inputing specific settings, etc. The answer file I created works great. Then I was asked to take things one step further, since the user still had to create the initial partition manually, then, the unattended install would take over. I did a lot of research and finally figured out that I needed a Windows PE CD. Luckily, the company I work for has an EA agreement and had the CD available. I read some more and figured out how to make the Windows PE ISO, and then use ISOBUSTER to extract certain folders to help create a unique Windows 2003 Server, unattended CD. The problem is I can't seem to get the automatic partition creation part to work. I've seen all the example batch files, scripts, DISKPART command lines and WINBOM.ini files out on the net, but I'm not sure where all of these files and scripts are supposed to go and in which order things happen. I've tried many combinations, but of course it gets tricky erasing and reburning over and over again. Can someone please lay out the procedures for automatically creating one C partition and leaving the balance unallocated, with an unattended Windows 2003 installation. We're trying to get the CD to the point that all one user has to do is place the CD in the CDROM drive, hit a key to boot from CD and then let it go to where my deaprtment can remote desktop in. Thanks in advance, Anthony Yenshaw
×
×
  • Create New...