Results 1 to 6 of 6

Thread: Little Cute Blinking Connection Activity LEDs

  1. #1
    Lively Member iataman's Avatar
    Join Date
    Jun 00
    Location
    Turkey
    Posts
    71

    Talking

    Hello World,

    You know, if you are connected to internet via modem, you can see those blinking cute(!) LEDs while sending or recieving data. But I have a static ip and connect to the internet through a server so I can not see what the hell is going on!

    Please help me to make my own code of those blinking LEDs. I can use the Shell_NotifyIcon func. so there is no problem about the interface but i don't know how do wake up an event, when data is sent or recieved.

    Thanks in Advance.
    While YourAge<=40
    Live(YourLife)
    Wend

  2. #2
    Lively Member iataman's Avatar
    Join Date
    Jun 00
    Location
    Turkey
    Posts
    71

    Lightbulb

    I've learned that i can use SetWindowsHookEx function to
    determine the network activity but i have no idea about how to use it. Examples in MSDN does not help so i hope you can.

    Don't care about the interface, i can overcome it myself
    but give me an idea about how to activate a sub when
    network activity occurs or how to 'hook' a dll.

    Thx in advance.

    P.S. If you think I'm not in the right way, please let me
    know.
    While YourAge<=40
    Live(YourLife)
    Wend

  3. #3
    Fanatic Member
    Join Date
    Apr 01
    Posts
    843

    Thumbs up

    I am looking for the same thing. Have you found anything???? Please let me know!!

  4. #4
    Lively Member iataman's Avatar
    Join Date
    Jun 00
    Location
    Turkey
    Posts
    71

    Arrow

    Well, I have news for you..

    Good one : Monitoring network activity is possible!
    Bad one : Not through VB, as I've learned so.

    To monitor netrowk activity, you must 'hook' some of the functions of wsock32.dll; to handle the outgoing data 'send' function and for the incoming data 'recv' function. I don't know how much you now about SetWindowsHookEx, but it requires and outer dll *, a dll which is not a part of current process, to make it systemwide which is out of means of VB. (please refer to MSDN library, SetWindowsHookEx Func.)

    So, these are what I've learned so far. If you get anything else please let me now.



    *
    lpfn
    Pointer to the hook procedure. If the dwThreadId parameter is zero or specifies the identifier of a thread created by a different process, the lpfn parameter must point to a hook procedure in a dynamic-link library (DLL). Otherwise, lpfn can point to a hook procedure in the code associated with the current process.

    iataman@hotmail.com
    While YourAge<=40
    Live(YourLife)
    Wend

  5. #5
    Lively Member iataman's Avatar
    Join Date
    Jun 00
    Location
    Turkey
    Posts
    71

    Post Tnx but..

    Well, to see that someone has made has boosted my motivation!! I'll learn it

    In fact I'm planning to ask it to the designers of the LanLed. Maybe they'll pitty and help

    And as soon as I discover, I'll post it here!

    To whom it may concern
    While YourAge<=40
    Live(YourLife)
    Wend

  6. #6
    Member hgroot's Avatar
    Join Date
    Dec 01
    Location
    Amsterdam
    Posts
    52
    Glad to be of help

    I'd be interested in the code, too, but the tool works fine for me.

    btw, the Windows traybar led has a more extensive properties screen than the tool. It also shows the upstream/downstream compression rate and network protocols.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •