Gunnar,

I think you should really ask if the all the trouble will add real value to your application. First off there are lots of OS specific issues when installing printers and you need different drivers for different OS's.

I'd also have to question the scale and scope of what you are doing and if the benefits could really pay off in small or large installations.

For example, if you only have a few dozen workstations it would only take a few hours for a tech to go around and install the necessary printers. So it's not worth spending a lot of time trying to automate installing and removing printers from inside your application.

If you have thousands of computers you need to provide this feature for it would be very compelling, but then the variety of printers, OS's, security, and sharing would make the scope of the problem quite large.

I think it's reasonable and most common for a workstation to have the printer driver through traditional means.

Why do you need to remove the driver once it is installed?
Are you working with a fixed number of printers that certainly have drivers that can be installed without UI?
From a business cost-effective standpoint, what is your motivation for providing this functionality?
Can you estimate how much money/time will be saved?

Greg

>>AFAIK
>>
>>You can see the resources available on your network.. But, to go deeper you must have the properly printer driver installed in your machine
>>
>>HTH
>>
>>
>>Claudio
>
>Hello Claudio
>
>Not realy. that is what i am trying to prevent, that the user (or programaticly) has to install the driver on the local machine. I was hoping that there is a way to get the resource from another machine on the net without having to install.
>
>my only thought at this time is to install in the backround (programaticly) get the info, and then remove the driver afterwards. i would have to find an api function which installs and removes drivers without user interface if the printer location is known.
>
>thanks for your help.