Santino_k
asked on
Can a WDM Video capture driver be installed on network?
Hi,
Can a WDM Video capture driver be installed on network?
I mean like printers can we install a Video capture device over network?
just wondering abt its feasibility and also why/how is printer device installed over network as a "network printer"
have a nice day
Can a WDM Video capture driver be installed on network?
I mean like printers can we install a Video capture device over network?
just wondering abt its feasibility and also why/how is printer device installed over network as a "network printer"
have a nice day
Eagle6990
You can't directly access a WDM device over a network but you can setup the capture device to stream the video over a network so you can view the output over the network. You'll need a proram to do this with such at ATI's Multimedia Center or others. Do a search on google for Network video streaming.
ASKER
Can you tell me how Printers can be installed over network?
Install a printer on Computer A. Right click on the printer and share it. Go to Computer B and go to add a printer. Select network printer and then select \\ComptuerA\Printername
Now Computer B can print to the printer without it being directly attached.
Now Computer B can print to the printer without it being directly attached.
ASKER
ya thats what I want to know.. how is it possible.. is there some protocol for it?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
take a look at the hidden shares on the machine sharing the printers (the ones ending in $)... there's a bunch of files that the connecting client looks for to find the printer drivers in the share called print$
for example, if I explore my local print server's print$ directory I see a subdir called w32x86 in which I see these files:
4 . 109 HPBF2111.DLL 63 HPBF4124.PMD 202 hpfntum0.dll
4 .. 1293 HPBF2112.DLL 150 HPBF4125.DLL 196 hpfpcle0.dll
4 2 1074 HPBF2113.DLL 449 HPBF4126.DLL 446 hpfpegn0.exe
44 HPBAFD32.DLL 350 HPBF2114.DLL 98 HPBFTM32.DLL 138 hpfprvw0.exe
12 HPBF0410.DLL 48 HPBF2114.HLP 58 HPDCMON.DLL 25 hpfrelb0.hlp
99 HPBF0411.DLL 63 HPBF2114.PMD 59 hpf970a0.dat 1556 hpftbox0.exe
1260 HPBF0412.DLL 176 HPBF2115.DLL 138 hpfbxtr0.dll 405 hpfuint0.dll
1042 HPBF0413.DLL 450 HPBF2116.DLL 251 hpfcfig0.exe 356 PCL5EMS.DLL
345 HPBF0414.DLL 12 HPBF4120.DLL 179 hpfeime0.dll 17 PJLMON.DLL
55 HPBF0414.HLP 99 HPBF4121.DLL 783 hpfeimg0.dll 72 RASDD.DLL
77 HPBF0414.PMD 1260 HPBF4122.DLL 128 hpfftrc0.dll 69 RASDDUI.DLL
504 HPBF0415.DLL 1043 HPBF4123.DLL 164 hpfhlpb0.hlp 15 RASDDUI.HLP
449 HPBF0416.DLL 351 HPBF4124.DLL 285 hpfjbui0.dll
12 HPBF2110.DLL 57 HPBF4124.HLP 21 hpfntkm0.dll
I suppose you could create a share called "drivers" and set the machines up to search that share automatically when installing new hardware, but it'd still be a somewhat manual process
hope this helps
Paul
for example, if I explore my local print server's print$ directory I see a subdir called w32x86 in which I see these files:
4 . 109 HPBF2111.DLL 63 HPBF4124.PMD 202 hpfntum0.dll
4 .. 1293 HPBF2112.DLL 150 HPBF4125.DLL 196 hpfpcle0.dll
4 2 1074 HPBF2113.DLL 449 HPBF4126.DLL 446 hpfpegn0.exe
44 HPBAFD32.DLL 350 HPBF2114.DLL 98 HPBFTM32.DLL 138 hpfprvw0.exe
12 HPBF0410.DLL 48 HPBF2114.HLP 58 HPDCMON.DLL 25 hpfrelb0.hlp
99 HPBF0411.DLL 63 HPBF2114.PMD 59 hpf970a0.dat 1556 hpftbox0.exe
1260 HPBF0412.DLL 176 HPBF2115.DLL 138 hpfbxtr0.dll 405 hpfuint0.dll
1042 HPBF0413.DLL 450 HPBF2116.DLL 251 hpfcfig0.exe 356 PCL5EMS.DLL
345 HPBF0414.DLL 12 HPBF4120.DLL 179 hpfeime0.dll 17 PJLMON.DLL
55 HPBF0414.HLP 99 HPBF4121.DLL 783 hpfeimg0.dll 72 RASDD.DLL
77 HPBF0414.PMD 1260 HPBF4122.DLL 128 hpfftrc0.dll 69 RASDDUI.DLL
504 HPBF0415.DLL 1043 HPBF4123.DLL 164 hpfhlpb0.hlp 15 RASDDUI.HLP
449 HPBF0416.DLL 351 HPBF4124.DLL 285 hpfjbui0.dll
12 HPBF2110.DLL 57 HPBF4124.HLP 21 hpfntkm0.dll
I suppose you could create a share called "drivers" and set the machines up to search that share automatically when installing new hardware, but it'd still be a somewhat manual process
hope this helps
Paul