Messages - KodeZwerg [ switch to compact view ]

Pages: prev1 2 [3] 4 5 6 7 8 ... 144next
11
The only thing I do know in that direction is BgInfo from Sysinternals.
Does that satisfy you?

12
I begin to ask in other forums
Well, why not ask in a proper category if someone, maybe I, can program something for you?
https://www.donationcoder.com/forum/index.php?board=71.0

13
I really wonder now why "NICs:" starting with a comma, shouldnt be possible at all.  :'(

It is physical connected to your Pc, no?
FWIW a little bit of PowerShell:
Code: PowerShell [Select]
  1. (Get-NetAdapter -Name * -Physical | % { Get-NetIPAddress -AddressFamily IPv4 -InterfaceAlias $_.Name }) | Format-Table -Property InterfaceAlias, IPAddress
What my app parse for NICs is similar to the PowerShell command you gave me.
So when my app list it, PowerShell would do the same. Please verify again.

14
Sorry for the delay, completely slipped my mind :-[
No worries  :-*

That worked  :Thmbsup:
Amazing to hear  :-*

BTW, would it be a good idea to indicate which interface the local IP is applicable to?
eg.

Local IP: 192.168.0.99 (WiFi)
Everything is possible  :-*

In the case of multiple connected NICs it might help identify which is the one with the highest metric.
This is what "Local IP" shows  :D


Updated my first post
 - added tested features to final version
 - tinkered a little with the text that it display, now more informations for the last things included (ip + name (if it has one))

I hope now everything works everywhere like it should.
Cheers,
Your KodeZwerg!

15
@4wd, I attached another version of my main app, replace the .exe with this new one, the libraries are not included.
App will run its normal job but
 - i fixed the interpretation for "Local IP: "
 - i added a new "PowerShell IPs: "
The app needs now longer to parse and compute the new PowerShell input.

Tell me if this version would be okay so I can update my first post and close this issue.

Pages: prev1 2 [3] 4 5 6 7 8 ... 144next
Go to full version