Sign in with
Sign up | Sign in
Your question

Modifying Sysprep

Last response: in Windows 2000/NT
Share
July 29, 2004 6:04:19 PM

Archived from groups: microsoft.public.win2000.setup_deployment (More info?)

I clean a machine and get it all setup. I have modified
my sysprep.inf file to do everything I need it to and make
sure the [SysprepMassStorage] contains the correct IDE
controller. I run sysprep, ghost the image, and all is
well.

Down the road, I decide to use this image for a different
PC with a different IDE controller. So I run PNPIDS and
determine the correct line to add under the
[SysprepMassStorage] section of my sysprep.inf file inside
my image. Problem is that the image is an NTFS image so
you can't edit any of the files in the image with Ghost
Explorer.

I tried Ghosting the image to this other PC and then I
thought I could boot using NTFSDOS and replace the
sysprep.inf file with a modified one but there is no way
that I know of to pass credentials in DOS, so I cannot get
access to overwrite or edit the existing sysprep.inf.

I don't want FAT32 images, so how are you supposed to be
able to keep updating the old sysprep.inf as machines come
out with different IDE controllers?

Thanks,

More about : modifying sysprep

Anonymous
July 30, 2004 9:50:25 PM

Archived from groups: microsoft.public.win2000.setup_deployment (More info?)

Try adding this registry information to your image before you run sysprep, I
had the same type of dilemna, i have about 4 dif models of dells, id take an
image of one model, restore it to another and get a blue screen saying
Inaccessible_boot_device. I got this from this article
http://support.microsoft.com/default.aspx?scid=kb;en-us;822052
FYI, I do not have the MassStorageDrivers section in my sysprep.inf and it
seems to work fine. I do a "sysprep -bmsd" when I sysprep the machine. Hope
this helps

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\
primary_ide_channel]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\
secondary_ide_channel]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\
*pnp0600]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\
*azt0502]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\
gendisk]
"ClassGUID"="{4D36E967-E325-11CE-BFC1-08002BE10318}"
"Service"="disk"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\
pci#cc_0101]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\
pci#ven_0e11&dev_ae33]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\
pci#ven_1039&dev_0601]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase
\pci#ven_1039&dev_5513]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\
pci#ven_1042&dev_1000]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\
pci#ven_105a&dev_4d33]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\
pci#ven_1095&dev_0640]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\
pci#ven_1095&dev_0646]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\
pci#ven_1095&dev_0646&REV_05]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\
pci#ven_1095&dev_0646&REV_07]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\
pci#ven_1095&dev_0648]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\
pci#ven_1095&dev_0649]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\
pci#ven_1097&dev_0038]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\
pci#ven_10ad&dev_0001]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\
pci#ven_10ad&dev_0150]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\
pci#ven_10b9&dev_5215]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\
pci#ven_10b9&dev_5219]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\
pci#ven_10b9&dev_5229]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\
pci#ven_1106&dev_0571]
"Service"="pciide"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\
pci#ven_8086&dev_1222]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\
pci#ven_8086&dev_1230]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\
pci#ven_8086&dev_2411]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\
pci#ven_8086&dev_2421]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\
pci#ven_8086&dev_7010]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\
pci#ven_8086&dev_7111]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\
pci#ven_8086&dev_7199]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

;Add driver for Atapi (requires Atapi.sys in Drivers directory)

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\atapi]
"ErrorControl"=dword:00000001
"Group"="SCSI miniport"
"Start"=dword:00000000
"Tag"=dword:00000019
"Type"=dword:00000001
"DisplayName"="Standard IDE/ESDI Hard Disk Controller"
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,
00,\

52,00,49,00,56,00,45,00,52,00,53,00,5c,00,61,00,74,00,61,00,70,00,69,00,2e,\
00,73,00,79,00,73,00,00,00

;Add driver for intelide (requires intelide.sys in drivers directory)

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IntelIde]
"ErrorControl"=dword:00000001
"Group"="System Bus Extender"
"Start"=dword:00000000
"Tag"=dword:00000004
"Type"=dword:00000001
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,
00,\

52,00,49,00,56,00,45,00,52,00,53,00,5c,00,69,00,6e,00,74,00,65,00,6c,00,69,\
00,64,00,65,00,2e,00,73,00,79,00,73,00,00,00


;Add driver for Pciide (requires Pciide.sys and Pciidex.sys in Drivers
directory)

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PCIIde]
"ErrorControl"=dword:00000001
"Group"="System Bus Extender"
"Start"=dword:00000000
"Tag"=dword:00000003
"Type"=dword:00000001
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,
00,\

52,00,49,00,56,00,45,00,52,00,53,00,5c,00,70,00,63,00,69,00,69,00,64,00,65,\
00,2e,00,73,00,79,00,73,00,00,00

"Gary" <anonymous@discussions.microsoft.com> wrote in message
news:6c6601c475af$9d4ca8f0$a401280a@phx.gbl...
> I clean a machine and get it all setup. I have modified
> my sysprep.inf file to do everything I need it to and make
> sure the [SysprepMassStorage] contains the correct IDE
> controller. I run sysprep, ghost the image, and all is
> well.
>
> Down the road, I decide to use this image for a different
> PC with a different IDE controller. So I run PNPIDS and
> determine the correct line to add under the
> [SysprepMassStorage] section of my sysprep.inf file inside
> my image. Problem is that the image is an NTFS image so
> you can't edit any of the files in the image with Ghost
> Explorer.
>
> I tried Ghosting the image to this other PC and then I
> thought I could boot using NTFSDOS and replace the
> sysprep.inf file with a modified one but there is no way
> that I know of to pass credentials in DOS, so I cannot get
> access to overwrite or edit the existing sysprep.inf.
>
> I don't want FAT32 images, so how are you supposed to be
> able to keep updating the old sysprep.inf as machines come
> out with different IDE controllers?
>
> Thanks,
Anonymous
July 31, 2004 9:50:02 PM

Archived from groups: microsoft.public.win2000.setup_deployment (More info?)

Dans le message <6c6601c475af$9d4ca8f0$a401280a@phx.gbl>,
Gary [anonymous@discussions.microsoft.com] s'exprima en ces termes :

> I clean a machine and get it all setup. I have modified
> my sysprep.inf file to do everything I need it to and make
> sure the [SysprepMassStorage] contains the correct IDE
> controller. I run sysprep, ghost the image, and all is
> well.
>
> Down the road, I decide to use this image for a different
> PC with a different IDE controller. So I run PNPIDS and
> determine the correct line to add under the
> [SysprepMassStorage] section of my sysprep.inf file inside
> my image. Problem is that the image is an NTFS image so
> you can't edit any of the files in the image with Ghost
> Explorer.
>
> I tried Ghosting the image to this other PC and then I
> thought I could boot using NTFSDOS and replace the
> sysprep.inf file with a modified one but there is no way
> that I know of to pass credentials in DOS, so I cannot get
> access to overwrite or edit the existing sysprep.inf.
>
> I don't want FAT32 images, so how are you supposed to be
> able to keep updating the old sysprep.inf as machines come
> out with different IDE controllers?
>
> Thanks,

Hi

Why don't you update the MassStorage section in your sysprep.inf file and
reimage ?

--
________________________________
Nicolas
enlever (remove) stoplapub

"This behavior is by design" (Microsoft)
________________________________
Related resources
Anonymous
August 9, 2004 5:08:23 PM

Archived from groups: microsoft.public.win2000.setup_deployment (More info?)

Thanks,

I do not have the MassStorageDrivers section in my
sysprep.inf either and I don't beieve you need it unless
you are going to use the image on a machine that has a
special IDE controller.

The bmsd switch is only going to add all of the PNPIDs
that come with Windows to the SysprepMassStorage section
of the sysprep.inf file which can be done manually just as
easy. The problem I have is when you want to use that
same image with a machine that has a PNPID other than what
comes with Windows, you are stuck.

What would be slick is if you could some how edit or
replace the sysprep.inf file inside the image. Ghost
Explorer allows this, but only if the image is from a
partition that was not NTFS. So I can't use NTFS because
I might need the ability to change 1 file in the image
later on. Seems rediculous to me.







>-----Original Message-----
>Try adding this registry information to your image before
you run sysprep, I
>had the same type of dilemna, i have about 4 dif models
of dells, id take an
>image of one model, restore it to another and get a blue
screen saying
>Inaccessible_boot_device. I got this from this article
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;822052
>FYI, I do not have the MassStorageDrivers section in my
sysprep.inf and it
>seems to work fine. I do a "sysprep -bmsd" when I sysprep
the machine. Hope
>this helps
>
>Windows Registry Editor Version 5.00
>
>
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Critic
alDeviceDatabase\
>primary_ide_channel]
>"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
>"Service"="atapi"
>
>
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Critic
alDeviceDatabase\
>secondary_ide_channel]
>"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
>"Service"="atapi"
>
>
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Critic
alDeviceDatabase\
>*pnp0600]
>"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
>"Service"="atapi"
>
>
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Critic
alDeviceDatabase\
>*azt0502]
>"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
>"Service"="atapi"
>
>
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Critic
alDeviceDatabase\
>gendisk]
>"ClassGUID"="{4D36E967-E325-11CE-BFC1-08002BE10318}"
>"Service"="disk"
>
>
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Critic
alDeviceDatabase\
>pci#cc_0101]
>"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
>"Service"="pciide"
>
>
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Critic
alDeviceDatabase\
>pci#ven_0e11&dev_ae33]
>"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
>"Service"="pciide"
>
>
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Critic
alDeviceDatabase\
>pci#ven_1039&dev_0601]
>"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
>"Service"="pciide"
>
>
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Critic
alDeviceDatabase
>\pci#ven_1039&dev_5513]
>"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
>"Service"="pciide"
>
>
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Critic
alDeviceDatabase\
>pci#ven_1042&dev_1000]
>"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
>"Service"="pciide"
>
>
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Critic
alDeviceDatabase\
>pci#ven_105a&dev_4d33]
>"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
>"Service"="pciide"
>
>
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Critic
alDeviceDatabase\
>pci#ven_1095&dev_0640]
>"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
>"Service"="pciide"
>
>
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Critic
alDeviceDatabase\
>pci#ven_1095&dev_0646]
>"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
>"Service"="pciide"
>
>
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Critic
alDeviceDatabase\
>pci#ven_1095&dev_0646&REV_05]
>"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
>"Service"="pciide"
>
>
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Critic
alDeviceDatabase\
>pci#ven_1095&dev_0646&REV_07]
>"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
>"Service"="pciide"
>
>
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Critic
alDeviceDatabase\
>pci#ven_1095&dev_0648]
>"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
>"Service"="pciide"
>
>
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Critic
alDeviceDatabase\
>pci#ven_1095&dev_0649]
>"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
>"Service"="pciide"
>
>
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Critic
alDeviceDatabase\
>pci#ven_1097&dev_0038]
>"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
>"Service"="pciide"
>
>
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Critic
alDeviceDatabase\
>pci#ven_10ad&dev_0001]
>"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
>"Service"="pciide"
>
>
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Critic
alDeviceDatabase\
>pci#ven_10ad&dev_0150]
>"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
>"Service"="pciide"
>
>
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Critic
alDeviceDatabase\
>pci#ven_10b9&dev_5215]
>"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
>"Service"="pciide"
>
>
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Critic
alDeviceDatabase\
>pci#ven_10b9&dev_5219]
>"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
>"Service"="pciide"
>
>
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Critic
alDeviceDatabase\
>pci#ven_10b9&dev_5229]
>"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
>"Service"="pciide"
>
>
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Critic
alDeviceDatabase\
>pci#ven_1106&dev_0571]
>"Service"="pciide"
>"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
>
>
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Critic
alDeviceDatabase\
>pci#ven_8086&dev_1222]
>"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
>"Service"="intelide"
>
>
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Critic
alDeviceDatabase\
>pci#ven_8086&dev_1230]
>"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
>"Service"="intelide"
>
>
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Critic
alDeviceDatabase\
>pci#ven_8086&dev_2411]
>"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
>"Service"="intelide"
>
>
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Critic
alDeviceDatabase\
>pci#ven_8086&dev_2421]
>"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
>"Service"="intelide"
>
>
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Critic
alDeviceDatabase\
>pci#ven_8086&dev_7010]
>"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
>"Service"="intelide"
>
>
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Critic
alDeviceDatabase\
>pci#ven_8086&dev_7111]
>"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
>"Service"="intelide"
>
>
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Critic
alDeviceDatabase\
>pci#ven_8086&dev_7199]
>"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
>"Service"="intelide"
>
>;Add driver for Atapi (requires Atapi.sys in Drivers
directory)
>
>
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\atapi
]
>"ErrorControl"=dword:00000001
>"Group"="SCSI miniport"
>"Start"=dword:00000000
>"Tag"=dword:00000019
>"Type"=dword:00000001
>"DisplayName"="Standard IDE/ESDI Hard Disk Controller"
>"ImagePath"=hex
(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,4
4,
>00,\
>
>52,00,49,00,56,00,45,00,52,00,53,00,5c,00,61,00,74,00,61,0
0,70,00,69,00,2e,\
> 00,73,00,79,00,73,00,00,00
>
>;Add driver for intelide (requires intelide.sys in
drivers directory)
>
>
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Intel
Ide]
>"ErrorControl"=dword:00000001
>"Group"="System Bus Extender"
>"Start"=dword:00000000
>"Tag"=dword:00000004
>"Type"=dword:00000001
>"ImagePath"=hex
(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,4
4,
>00,\
>
>52,00,49,00,56,00,45,00,52,00,53,00,5c,00,69,00,6e,00,74,0
0,65,00,6c,00,69,\
> 00,64,00,65,00,2e,00,73,00,79,00,73,00,00,00
>
>
>;Add driver for Pciide (requires Pciide.sys and
Pciidex.sys in Drivers
>directory)
>
>
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PCIId
e]
>"ErrorControl"=dword:00000001
>"Group"="System Bus Extender"
>"Start"=dword:00000000
>"Tag"=dword:00000003
>"Type"=dword:00000001
>"ImagePath"=hex
(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,4
4,
>00,\
>
>52,00,49,00,56,00,45,00,52,00,53,00,5c,00,70,00,63,00,69,0
0,69,00,64,00,65,\
> 00,2e,00,73,00,79,00,73,00,00,00
>
>"Gary" <anonymous@discussions.microsoft.com> wrote in
message
>news:6c6601c475af$9d4ca8f0$a401280a@phx.gbl...
>> I clean a machine and get it all setup. I have modified
>> my sysprep.inf file to do everything I need it to and
make
>> sure the [SysprepMassStorage] contains the correct IDE
>> controller. I run sysprep, ghost the image, and all is
>> well.
>>
>> Down the road, I decide to use this image for a
different
>> PC with a different IDE controller. So I run PNPIDS and
>> determine the correct line to add under the
>> [SysprepMassStorage] section of my sysprep.inf file
inside
>> my image. Problem is that the image is an NTFS image so
>> you can't edit any of the files in the image with Ghost
>> Explorer.
>>
>> I tried Ghosting the image to this other PC and then I
>> thought I could boot using NTFSDOS and replace the
>> sysprep.inf file with a modified one but there is no way
>> that I know of to pass credentials in DOS, so I cannot
get
>> access to overwrite or edit the existing sysprep.inf.
>>
>> I don't want FAT32 images, so how are you supposed to be
>> able to keep updating the old sysprep.inf as machines
come
>> out with different IDE controllers?
>>
>> Thanks,
>
>
>.
>
Anonymous
August 9, 2004 7:47:59 PM

Archived from groups: microsoft.public.win2000.setup_deployment (More info?)

Why do people reply and then not write anything?
>-----Original Message-----
>Dans le message <6c6601c475af$9d4ca8f0$a401280a@phx.gbl>,
>Gary [anonymous@discussions.microsoft.com] s'exprima en
ces termes :
>
>> I clean a machine and get it all setup. I have modified
>> my sysprep.inf file to do everything I need it to and
make
>> sure the [SysprepMassStorage] contains the correct IDE
>> controller. I run sysprep, ghost the image, and all is
>> well.
>>
>> Down the road, I decide to use this image for a
different
>> PC with a different IDE controller. So I run PNPIDS and
>> determine the correct line to add under the
>> [SysprepMassStorage] section of my sysprep.inf file
inside
>> my image. Problem is that the image is an NTFS image so
>> you can't edit any of the files in the image with Ghost
>> Explorer.
>>
>> I tried Ghosting the image to this other PC and then I
>> thought I could boot using NTFSDOS and replace the
>> sysprep.inf file with a modified one but there is no way
>> that I know of to pass credentials in DOS, so I cannot
get
>> access to overwrite or edit the existing sysprep.inf.
>>
>> I don't want FAT32 images, so how are you supposed to be
>> able to keep updating the old sysprep.inf as machines
come
>> out with different IDE controllers?
>>
>> Thanks,
>
>Hi
>
>Why don't you update the MassStorage section in your
sysprep.inf file and
>reimage ?
>
>--
>________________________________
>Nicolas
>enlever (remove) stoplapub
>
>"This behavior is by design" (Microsoft)
>________________________________
>
>
>.
>
!