Re: Using sysprep on Win2K to unplanned different hardware
From: Michael Leone (mleone_at_contributionship.com)
Date: 08/27/04
- Next message: NIC Student: "Re: RIS cannot generate a unique conputer name"
- Previous message: ekim: "RIS cannot generate a unique conputer name"
- In reply to: Dennis Calhoun: "Re: Using sysprep on Win2K to unplanned different hardware"
- Next in thread: Dennis Calhoun: "Re: Using sysprep on Win2K to unplanned different hardware"
- Reply: Dennis Calhoun: "Re: Using sysprep on Win2K to unplanned different hardware"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 27 Aug 2004 14:22:52 -0400
"Dennis Calhoun" <dcalhoun@blomand.net> wrote in message
news:bdmti014rg82360evle6odapedv48kd0pg@4ax.com...
>
> If you can be assured that all involved systems with have the same
> HAL, such as they will all be ACPI uniprocessor PC type systems, get
> sysprep 1.1 from the MS website and extract it. In the cab you will
> find a DOCS folder and in it are two files that contain ALL of the IDE
> and SCSI entries that Win 2000 includes. The files are idepnpids.txt
> and scsipnpids.txt.
>
> You can add the entire list of IDE and SCSI mass storage device
> entries to the [SysprepMassStorage] section of your Sysprep.inf file.
> When you boot up a machine that has all of these, so long as the
> machine contains a device that is in the list, it *will* be properly
> assigned the necessary driver and will boot up ok.
The hard disks in the replacement machines will be connected to RAID
controllers that are (almost certainly) not in that list. That list includes
no Dell PERC RAID controllers, that I saw, and these machines will
(probably, altho not defintely) be Dell machines, using Dell RAID
controllers (altho I can not guarantee ahead of time with model RAID
controller). So adding those drivers entries you speak of to the sysprep.inf
wouldn't help me, in that sitution, would it?
> Also, in your distro you need to add the cmdlines.txt file to your
> $OEM$ folder and in that file have the *first* command be
> C:\Sysprep\Sysprep -clean
> assuming you have Sysprep located in C:\Sysprep [adjust to fit your
> location]
My sysprep.inf file has all the IDE drivers listed (altho I also had to add
a registry file with those same drivers, according to an MS KB article I
found). This works for all machines I've tried, that are on machines with no
SCSI controllers. Everytime I add the SCSI list to the sysprep.inf file
(making no other changes), and re-do sysprep, it blue screens with "07B". If
I remove the SCSI entries from the list, and leave just the IDE, it boots
fine. Every time, on multiple models of hardware.
Never boots with both IDE and SCSI controllers listed. I even downloaded a
sysprep.inf from the Net, from the author of the Windows 2000 Deployment
Guide book ... still blue-screens. Every time, and on multiple models (IDE
only, IDE and SCSI drives attached).
- Next message: NIC Student: "Re: RIS cannot generate a unique conputer name"
- Previous message: ekim: "RIS cannot generate a unique conputer name"
- In reply to: Dennis Calhoun: "Re: Using sysprep on Win2K to unplanned different hardware"
- Next in thread: Dennis Calhoun: "Re: Using sysprep on Win2K to unplanned different hardware"
- Reply: Dennis Calhoun: "Re: Using sysprep on Win2K to unplanned different hardware"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
