>>Acually I was using the windows components to install it. I ended up having to use the EXPAND command to create the DLL file and then it worked ok. Weird.
>
>You're lucky, then - if it found everything else and registered whatever it wanted, and just missed that one dll, good. Given the level of intelligence of that old installer (probably aged at windows 3.x or even earlier), good that it didn't screw anything you couldn't fix.
>
>BTW, how do you like the user-friendliness of EXPAND? :)

EXPAND *.dl_ *.dll

ERROR that is can't find the destination directory... Sweet!