>The problem is that, besides the error, the application was developed not by myself but a childrens educational software manufacturer. I don't know what it is written in. So I was looking for a work around for this installation.
>
> I do appreciate and want to thank you for your response!
>
> I will probably have to build a Win 95 box or send the software back!

I haven't tried this, so be prepared for cosmos-shattering meltdowns to occur (or at least, the need to shut down and fix what I'm breaking for you).

Try copying SPOOLSS.DLL in NT's system directory into the directory that the application starts in as WINSPOOL.DLL; if they haven't hard-coded the path for the .DLL, WIndows will search the startup directory before searching the default NT path, and it -might- be able to load up the renamed copy and use the DLL entrypoints in there.

DO NOT RENAME OR DELETE THE SPOOLSS.DLL IN NT's System32 directory