If you wrote those DLLs yourself, copy protection is as easy as checking for a key file and comparing it to the existing computer configuration (i.e. ROM BIOS, HD size, Mem size, W9x version, etc. and combining it together to form a key file)...
However, I'm assuming you didn't write those DLLs and EXEs. In that case, here's what I would do...
Rename the main executable program to something other than an EXE file. Write a little Windows EXE program loader to check for a hidden configuration key file specific to that machine (that was created during installation) or key in the Registry. When the program starts, it checks the configuration of the computer and compares it to the hidden key file or the registry. If it differs then don't load the main EXE. If it matches, then load that sucker. This takes some work and Windows programming skills... probably not what you want to do, but it's one way of doing it... It's not bullet proof, however. Anyone with hacking skills can figure this method out easily.