VK:
Yes, I think you should implement the suggestion you
made for the network printer.
One quick experiment first, though. Is it possible
to send a signal (any signal) to the printer thru the driver?
If there is, we can use Kaboodle's own sniffer to detect
the response to this signal. So if we send it to "Dad's
LaserJet" and hear a reply from 192.168.1.7, then we know
the right name to assign to the detected network printer.
Just a thought.
-Scott
On Tue, 25 Jun 2002, mailbox wrote:
> Hello Scott,
>
> Should I implement the suggestion I have made for the network printer? I
> could not find any way to get the IP address from the driver data. User will
> see the name of the printer system if the network printer provides the MIB.
> I am getting the sysname at my end by using the SNMP get request for
> system.sysName.0. Can we add any other scheme to get the printer name if the
> SNMP get request fails? Like we can add the web server name that I get from
> the http request. But that is not really the printer name.
>
>
>
> Regards,
>
> Varsha
>
> ----- Original Message -----
> From: "Scott C. Best" <[EMAIL PROTECTED]>
> To: "mailbox" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Monday, June 24, 2002 10:07 PM
> Subject: Re: [Kaboodle-devel] Re: wincvs update
>
>
> > VK:
> >
> > > > 1. The "active list", what gets ping'd every 10 seconds, is
> > > > not the same as what's in the GUI. In the ping list, I
> > > > see 10 device, in my GUI I see only 5.
> > > >
> > > I cannot replicate the above bug. Please give me the more details to
> > > replicate the same.
> >
> > This is just how it acts on my WinNT box. Both Debug
> > and Release builds.
> >
> > > > 2. The PC which is running Kaboodle has a duplicate icon.
> > > > One has the right MAC address, the other has the Kaboodle
> > > > icon and an MAC address of all zeroes.
> > > >
> > > I cannot replicate the above bug with the latest code. Please give me
> > > the steps that need to replicate the bug and the operating system on
> > > which you tested the code
> >
> > Again, this is just WinNT. The duplicate icon comes up
> > after I hit Refresh after it settles out initially.
> >
> > > > 3. My network printer has two icons: one for the driver
> > > > which was detected, and one for the IP address.
> > > >
> > > Here is the suggestion. While enumerating the printer drivers we can
> > > get the attribute and depending on the attribute we can add the printer
> > > drivers. If the attribute is PRINTER_ATTRIBUTE_NETWORK we simply ignore
> > > the driver. The network discovery code will add the network printer
> > > after that.
> > > Can you please suggest the better work around to this problem?
> >
> > That's a good idea. Is it possible from the driver to
> > detect what the printer's IP address is? That might help to
> > associate the two, so we can easily "detect" the Printer's Name
> > for the GUI (right now it comes up as the IP address).
> >
> > -Scott
> >
> >
> >
> >
> > -------------------------------------------------------
> > Sponsored by:
> > ThinkGeek at http://www.ThinkGeek.com/
> > _______________________________________________
> > Kaboodle-devel mailing list
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
> >
>
>
-------------------------------------------------------
This sf.net email is sponsored by: Jabber Inc.
Don't miss the IM event of the season | Special offer for OSDN members!
JabberConf 2002, Aug. 20-22, Keystone, CO http://www.jabberconf.com/osdn
_______________________________________________
Kaboodle-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
