If you're running windows, why is there a real-mode CD-ROM driver in your config.sys? The SDVXD message is related to that in that the OAKCDROM.SYS driver is not one that Windows recognizes. The ndis2sup.vxd failure is normal and should not cause a problem.
Have you tried booting into Safe Mode?
Booting in Safe Mode I believe is the same thing (freezes 40-60% of the time, but I'm not certain; I'll try tonight when I get back).
Not sure why I did that when I wrote the config.sys, I thought it was needed I guess. So just delete the oakcdrom.sys line? Replace it with nothing?
Anyway, I ran
Bootlog Analyzer. It's good, it lists the fails and the delays. Here they are:
3:41:19 0.44 Loading Device = C:\WINDOWS\EMM386.EXE
3:41:20 0.56 LoadSuccess = C:\WINDOWS\EMM386.EXE
3:41:20 2.44 Loading Device = C:\DOS\OAKCDROM.SYS
3:41:23 0.39 LoadFailed = C:\DOS\OAKCDROM.SYS
3:41:22 1.06 LoadSuccess = C:\WINDOWS\IFSHLP.SYS
3:41:23 5.06 C:\DOS\MOUSE.COM[0003A5EF] starting
3:41:28 0.89 Loading Vxd = vnetsup.vxd
3:41:29 0.00 LoadFailed = ndis2sup.vxd
3:41:31 0.00 DEVICEINITFAILED = MTRR
3:41:33 0.33 Enumerating ATI 3D Rage Pro (atir3) (PCI\VEN_1002&DEV_4744&SUBSYS_00801002&REV_5C\0008 00)
3:41:34 0.33 Loading PNP drivers of Intel PC Camera Pro (USB\VID_0733&PID_0430\INST_0)
3:41:34 0.39 Starting Intel PC Camera Pro (USB\VID_0733&PID_0430\INST_0)
3:41:37 0.83 Starting PS/2 Compatible Mouse Port (BIOS\*PNP0F13\0A)
3:41:38 7.56 Started Intel(R) PRO/100B PCI Adapter (TX) (PCI\VEN_8086&DEV_1229&SUBSYS_00018086&REV_02\BUS_ 00&DEV_09&FUNC_00)
3:41:46 27.28 Starting TCP/IP (NETWORK\MSTCP\0002)
3:42:14 0.39 Initing esdi_506.pdr
3:42:15 1.44 Initing drvwq117.vxd
3:42:16 0.28 Init Success drvwq117.vxd
3:42:17 0.00 INITCOMPLETEFAILED = SDVXD
3:42:17 0.28 Dynamic load success C:\WINDOWS\system\serial.vxd
3:42:18 0.28 Initing drvwppqt.vxd
3:42:19 0.28 Dynamic load success dsound.vxd
3:42:19 6.17 InitDone = TSRQuery (time estimated)
3:42:25 4.44 Enumerating TapeDetection (TAPECONTROLLER\TAPEDETECTION\0000)