Also, the weird driver ..\D\L\AM1\amdl7n5.inf has been updated to a proper NT5 driver in the latest LAN [Nightlies].

Am uncertain as of yet of potential impacts to the W2k compatibility of nVidia networking drivers.  <under-study>

So far, the only missing 2k drivers comparing DP_LAN 8053 support to the latest [Nightly] for LAN, is an ASIX AX88772 USB-FastLAN.    Also noting that modern atheros devices not included in either.
Having double checked, yet to triple-check, with fixes impending, i can confidently recommend even the current LAN nightly to supersede DP_LAN_wnt5_x86-32_8053.7z for Win2k.

The latest Win2k/NDIS5.0 drivers should install even with stock certs, except for Broadcom b57, which installs a WHQL'ed 2010 revision, however; some drivers need a newer individual certificate (or rootsupd) to validate as WHQL (after manual update - or otherwise adding b57.cat file to system, if i have that right)  The .Inf files have it all sorted out for the most part, which files to use.

For those devices entirely lacking NDIS5.0 support, either a Win9x driver could be sourced, or a non-WHQL Null-Driver created specifically to block Win2k installation.  This would go a long way to preventing the possibility of bluescreens, which could affect either old or new pack, until corrected.

I'll take this all one pack at a time, if i have to. 

Finally found link to those old packs.  Will work to ensure all drivers still included in nightlies, if not updated or superseded.

Have you considered asking for help on the "Update Pack Discussion" subforum over at RyanVM.net?

For instance, the intel v9.4.1027 chipset drivers.  They include 2000 in the Security Catalog, yet they don't appear to install (manually) without latter certs.
  (win2k usb non-functional due to WHQL-signed editing errors - also take longer to verify than older sigs - i had to go file, by file to check & ... nevermind)

There are also intel "chipset" drivers in the latest nightly for MassStorage, yet have included 2k versions that need not newer certs.

Certificate Issues - XP-SP3 (before any updates):
         - recommend RootsUpd.exe is added to $OEM$\cmdlines.txt
		        or added to winnt.sif @ [GUIRunOnce] section DetatchedProgram="" (include Arguments="")
 - AM\a\1\rccfg.sys & rcraid.sys, AM\a\2\rcraid.sys, As\1\asahci32.sys & asstor32.sys,
   C\HpAHCIsr.sys, I\0\iSSetup.sys, VB\VIOSTOR.SYS
      VerisignClass3PublicPrimaryCertificationAuthority-G5 (issued by Microsoft Code Verification Root)
 - H\r750.*
      SymantecTimeStampingServicesCA-G2 (issued by GeoTrustGlobalCA)
 - I\ drivers from 2013 and newer require "Microsoft Root Certificate Authority" CA (not incl. in W2k)
 - V\VIDEX32.SYS, xfilt.sys
      VIATechnologiesInc. - certificate has expired or is not yet valid
Certificate Issues - XP-SP3 (post-updates):
 - L\msas2k3.* LSI Certificate revoked

Also, many of the latest LAN drivers require a selection of certificates for validation.

That is, if i have that right.

The line about adding rootsupd.exe to one's cmdlines.txt seem incorrect, as that garners errors in setuperr.log, as does expanding rootsupd and manually executing it in a rootsupd.cmd (listed in cmdlines.txt).
Also, i have not yet been able to discern if they install @T33-6 like hoped.  Have kept logs....

Does the driver install even though it's not signed?  To get the XP x64 Radeon X700 driver to install on my laptop I had to remove the existing graphics drivers with nLite, otherwise it installed a generic one even though the specific one was integrated into the source.

Few people appear to have covered 2k updates, like the aforementioned person.
  I previously neglected to mention the few, such as yourself.

Do feel free to link to your work if you like, as i wasn't aware of your efforts.
  Others may find your updates helpful too, whom may also be previously unaware of your work.

Whilst you are here (presumably), am hoping you can help.

Am looking for a way to slipstream or otherwise install a RootCertificates update before Device Driver detection on a Windows 2000 Setup.

Newer valid windows 2000 drivers are either signed with "Microsoft Root Certificate Authority", or "Verisign Class 3 Public Primary Certification Authority - G5" and aren't seen as WHQL until after the update is installed (unconfirmed).  This also affects XP, and probably Win2k3 as well.

Have tried entering it in @T36 via the unattend file & $OEM$ folder, yet an error always results including in setuperr.log.

I hope to include any recommendations within the "Certificate Issues" sections of the DriverPacks changelogs, along with credit for such.  Thank you for your time and consideration.

Important Security Notice: As Windows 2000 has been out of support since July 2010 and no major web browser still supports it, it is not safe to use Windows 2000 on an Internet facing machine.  At this stage Windows 2000 is mainly recommended for use in a virtual machine or on unconnected old hardware to run legacy applications.  If you wish to use old hardware connected to the Internet a Linux Distribution is a much safer choice.

So as I'm targeting OS stability and compatibility with programs that were designed specifically to run on W2K, I don't use a modified kernel.

Using DP Base 8.12.5

However; if you find that it still doesn't fulfil your needs, here are some areas of potential research.

Other than a regulat ATAPI install, DP_MassStorage_wnt5_x86-32_1405176 only supports textmode Intel up to about Intel xESB/ICH7-R(M)DH/EP80579 (Matrix 7.8) & AMD up to about SB6xx (ATAPI, RAID & other controllers too & of course the max amt permitted for UR1 support were included*) 

BlackWingCat covers unofficial drivers and additional 2k Updates like none other i know of.  That includes unofficial support for newer Intel/AMD/nV AHCI/RAID/graphics/processors/(et al).

http://blog.livedoor.jp/blackwingcat/ & also:  http://w2k.flxsrv.org/

* (i had been using a UR1-integrated source for testing, and when i regressed to a virgin SP4 disc for source, ntfs.sys errors were noted.  Did integrating UR1 (or one of other off. KB's) alter textmode memory limit?)

Are you using the latest DPs_BASE version, BTW?

I have bugger-all hardware left for use in testing Windows 2000 (was asked to clean out most of the old junk I had lying around) so I'll stick with the older versions that have had more extensive community testing with the OS and hardware they are likely to be used on.

I've linked to uploaded versions of these for use with my Windows 2000 install media creation guide, but you never know when someone might want access to an older pack (usually to find a regression bug).