>>>>>I used Amyuni's INSTALL.EXE to install the driver. Are there any extra steps that must be performed on an NT install?
>>>>
>>>>Did you configure a printer in NT? Did you configure the spooling options for the printer? Did you assign rights to the printer to the user? NT, especially an NT server, requires attention to little details like this...
>>>
>>>Amyuni's installation process does all of this automatically. The only thing I'm not sure about is if I've got some kind of rights issue. I've got another NT server box that I have a little more control of. I'll try installing on it and see what happens.
>>>
>>
>>Actually, it doesn't assign rights to IUSR_machinename, or ensure that you have permissions to write in directories, or any of the other things that have to be done in a controlled environment - if you log into a Win9x box, it's open to you, and you can gut it like a fish. NT and 2K don't automatically grant all users access to all rights for all local resources.
>
>Actually, it does.<s> It granted rights to the "Everyone" group. But JIC, I added an entry for the IUSR_ account but it still fails the same. I even tried granting full rights to the temp directory where the PDFs are created but no change.
>

When I did WI's PDF install to Win2K, we had to go back, install under NT4, upgrade to Win2K, and add the user permissions to directories and other resources by hand to AD. It may have been my own relative inexperience with setting up an AD environment (I understand the right way to delegate and add users/machines/scopes into AD much better now) but Amyuni's installer failed to even turn on spooling, which results in VFP choking when the printer is assigned to the device name. Not my idea of fun, but once we realized what caused the errors we saw, the fixes were easy enough. You're pointed to RAW datatype, correct?