Intel had webcams earlier than Logitech, just tried out the Intel PC Pro Camera and the Logitech Quickcam Pro 3000, one of the better orbs from around the turn of the century.

Quickcam now fails to provide a hardware ID but the Intel works.

No Intel drivers this old built into Windows 10 any more or from Windows Update, but there was no need for Windows 9x or the matching VfW or WDM drivers on the original CD.

By the time Windows XP came out there were built-in NT WDM drivers for Intel cams right there in the INF & SYSTEM32 folders.

In Windows 10, pointing Device Manager manually to those XP folders gets the cam working without any need for compatibility mode or anything.

Then the Windows 10 Camera App can not detect the installed WDM cam, but Expression Encoder or VLC have no problem at all.

Incidentally if you are using Windows 10 on a primary partition of a system booting in BIOS (not UEFI) mode, that means you traditionally have a WINDOWS folder on your NTFS _C:_ volume, not much differently than in previous decades. Ideally your NT6 BOOT folder would be on your C: volume too, and that partiton would be Actively bootable instead of some separate hidden boot partition. The NT6 BOOT folder migrated toward hidden during Windows 7 support period. Both NT5 & NT6 work with either combined or separate Boot & System partitions.

So you're basically ready to install XP alongside W10 (without reformatting of course) into its own dedicated folder other than WINDOWS. I suggest the folder WINXP instead of the WINNT name that was also shared by W2K and earlier NT. The XP setup routine will prompt you to create a different folder on your target volume if there is already a WINDOWS folder there. You will have already needed to rename the W10 Program Files folder to something like Program10Files so it will not be replaced by the XP install. The only other folder written by XP setup is Documents And Settings, so there will be a real folder there when finished and W10 can handle it no differently than the default symlink it carries for backward compatibility.

Simply XP setup will overwrite the bootsector of your Active volume with an NT5 NTLDR-seeking version, put NTDETECT.COM, BOOT.INI, and NTLDR on the root of your Active boot volume next to the NT6 BOOTMGR and BOOT folder already there, and write the three WINXP, Program Files, & Documents and Settings folders to C:.

And act like you no longer have Windows 10 unless you know better.

Windows 10 is of course still properly installed too, but it will need a BOOTMGR-seeking bootsector again which can be easily replaced from the command prompt of W10 install media using the BOOTSECT.EXE command. Before you boot back to Windows 10, you need to also rename the new Program Files folder to something like ProgramXPFiles, and rename Program10Files back to plain Program Files.

Then it will act like you don't have XP any more

So then you add an NTLDR entry to the W10 boot menu using BCDEDIT.EXE, not a difficult exercise, and you get freedom of choice.

When XP boots it doesn't use the Program Files folder anyway until you actually try to run a program residing there.

So you can do file management, and lots of other things when booted to XP whenever you want with fewer headaches many times than NT6.

Even without drivers for all your devices, none of them current either, and default low-resolution graphics.

Too bad going forward Intel is discontinuing BIOS support leaving only UEFI on its branded mainboards.