new "Q######" format

[Cary Shultz]

Howdy! Howdy!

Well, I use RIS to install WIN2000 Pro. I slipstream the
SP3 and I use the $OEM$ folder along with Cmdlines.txt and
QChain to install the majority of the Critical and
Recommeneded updates.

All was well in the days when the file format
was "Q######_w2k_sp4_x86_en.exe". However, it seems that
the latest files now have the "WINDOWS2000-KB######-x86-
ENU.exe" format. I am not able to get these to work from
within the $OEM$ folder using qchain. And - I am using
the update qchain file. QFECHECK varifies that the 21
Q###### files are indeed installed. However, the
four "others" are not..

Anyone able to get this to work? I am sure that I can
create a little batch file and run it after the
installation so that these four or five ( as of now )
updates will be installed. I would just prefer to do it
with the CMDLINES.txt...

Thank you all,

Cary

 

[CAry Shultz]

-----Original Message-----
Howdy! Howdy!

Well, I use RIS to install WIN2000 Pro. I slipstream the
SP3 and I use the $OEM$ folder along with Cmdlines.txt and
QChain to install the majority of the Critical and
Recommeneded updates.

All was well in the days when the file format
was "Q######_w2k_sp4_x86_en.exe". However, it seems that
the latest files now have the "WINDOWS2000-KB######-x86-
ENU.exe" format. I am not able to get these to work from
within the $OEM$ folder using qchain. And - I am using
the update qchain file. QFECHECK varifies that the 21
Q###### files are indeed installed. However, the
four "others" are not..

Anyone able to get this to work? I am sure that I can
create a little batch file and run it after the
installation so that these four or five ( as of now )
updates will be installed. I would just prefer to do it
with the CMDLINES.txt...

Thank you all,

Cary
.

No takers....

That's okay. Eventually I will figure it out...Already
figured out how to use the batch file...just much prefer
to use the CMDLINES.TXT file..

Cary