|
optical123 wrote: can any body anybody know what is network simulator
http://en.wikipedia.org/wiki/Network_Simulator[^]
optical123 wrote: how it will be use full useful in the network
Imagine that you wanted to test how your network software will perform over satellite but the only problem is that you dont have a satellite. Perhaps you wanted to determine how that same software would perform over a dial-up connection. What if your users are complaining that your software crashes everytime network latency exceeds 300ms.
(Billy Mays[^] voice)
Now you can test all your network software with the super-duper network simulator. And if you call within the next fifteen minutes you will recieve this FREE mouse pad. 
Best Wishes,
-David Delaune
|
|
|
|
|
Randor wrote: (Billy Mays[^] voice)
Now you can test all your network software with the super-duper network simulator. And if you call within the next fifteen minutes you will recieve this FREE mouse pad.
Oh God, I could just smack your toe with a hammer! I can't stand that guy! 
|
|
|
|
|
This is a great windows based NMS tool. Enterprise grade network management software with a very easy to use interface that has tons of features.
Comes with a 30 day trial but you can download it here without registering it ahead of time.
http://www.dopplervue.com/software/setup.exe
Diassemble it for complete code samples of how to do this stuff.
http://www.red-gate.com/products/reflector/
Create plug-ins by adding pollers. One simple entry in a database table and a dll written in .NET.
|
|
|
|
|
No free advertising!
Pay-up like anyone else! Doofus!
Panic, Chaos, Destruction.
My work here is done.
|
|
|
|
|
This twit's suggesting reverse engineering to learn how it works. Somehow that makes me doubt he's commercially involved with the company.
It is a truth universally acknowledged that a zombie in possession of brains must be in want of more brains.
-- Pride and Prejudice and Zombies
|
|
|
|
|
how to send messages to administrator or account holder's mobile through bluetooth or any other means when an unauthorised person tries to access any system login or user account or any sort of login form.
|
|
|
|
|
The first bit's relatively easy, for instance send them an email. But
raviraazk wrote: any system login or user account or any sort of login form
covers so much I afraid can't help you there.
|
|
|
|
|
Unless all of those systems are rewritten to provide that kind of information, you cannot do what you want. There is no way to monitor every type of system and every window for what "looks like" a login form.
|
|
|
|
|
We have a PC/104 (ISA bus) card we designed in 1999 to interface with an internal I2C bus in our line of PROFILE/Plus test equipment for the paper industry. The software was developed under Borland C and runs under DOS. We are porting the design to Windows XPembedded and need a driver for this card. I have studied about 370 pages of "Developing Drivers with the Windows Driver Foundation" by Penny Orwick and Guy Smith, read the article "Bulding and deploying a basic WDF Kernel Mode Driver" by Bruno van Dooren, and several of the Toby Opferman articles on Driver Development.
I still do not know if I am going in the right direction. There is very little mention of the actual interface with the hardware. I recently found some references to "I/O commands" like "READ_PORT_XXX" and "WRITE_PORT_XXX" where XXX can be UCHAR, ULONG, USHORT, ULONG64. However, most references indicate these are to be used in Windows CE. Do I need something to tell WDF that the interface is an ISA bus and the interface is through I/O addresses?
The board in question uses a passive Philips "bridge" part that simply has registers we get to by decoding I/O addresses on the PC/104 I/O bus. Can I get to these directly in response to a IRP initiated by a user request?
My second concern is "adding the device". Does WDF initiate a callback to the "EvtDeviceAdd" immediately after the WdfDriverCreate? van Dooren stated, "The EvtDeviceAdd function will be called each time the system determines that a new device has been connected". If not, how do I "tell" the system that our passive board is present?
|
|
|
|
|
Dear Mr. William R. Price:
I recommend that you post this question onto the following site if you can not get any comments on this site.
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.development.device.drivers&lang=en&cr=US
I hope that you will get good advices and your problem is solved.
Thanks.
Yama Fuji.
|
|
|
|
|
William R. Price wrote: I still do not know if I am going in the right direction. There is very little mention of the actual interface with the hardware. I recently found some references to "I/O commands" like "READ_PORT_XXX" and "WRITE_PORT_XXX" where XXX can be UCHAR, ULONG, USHORT, ULONG64. However, most references indicate these are to be used in Windows CE
No these functions can also be used for your embedded XP project. You can think of these wrappers as the equivilent of the old DOS _outp, _outpw, _outpd[^] functions. You stated your device driver was implemented in Borland-C so your old code would have probably used outport[^] and outportb[^].
William R. Price wrote: Do I need something to tell WDF that the interface is an ISA bus and the interface is through I/O addresses?
If your PC104 card supports PnP ISA then when embedded XP boots the PnP manager will query the card and allocate the appropriate resources then send your driver a IRP_MN_QUERY_RESOURCE_REQUIREMENTS[^] request and ask your driver for its resource requirements which can be described in the IO_RESOURCE_REQUIREMENTS_LIST[^] struct which allows your driver to modify the resource requirements.
You will essentially need to write a PnP ISA device driver using WDF and create am INF file which contains the resource requirements. You could also write a co-installer and install the driver progmatically rather than use the INF file. More information here:
Device Installation FAQ[^]
William R. Price wrote: Does WDF initiate a callback to the "EvtDeviceAdd" immediately after the WdfDriverCreate? van Dooren stated, "The EvtDeviceAdd function will be called each time the system determines that a new device has been connected". If not, how do I "tell" the system that our passive board is present
If the Plug and Play manager has successfully detected your device the EvtDriverDeviceAdd[^] callback is fired. The PnP manager already knows about the existence of your device at this point. The callback is there for you to initialize any additional resources or interfaces.
Best Wishes,
-David Delaune
|
|
|
|
|
Hi Everyone,
I have a windows Application developed with .Net 2005 and C#. It communicates with a device using virtual COM Port. I use Windows XP Home and Prof. It works fine everywhere.
But recently I shipped the software to one of my client. There it creates problem. During its first run the software checks all COM Ports by sending specific command and where it finds proper response it detects that the device is attached to that Port. This is a regular process of the software. But, while checking the COM ports the application gets stuck after sending command to COM Port. And only way to close it is from Task Manager. This happens with 4 to 5 system, the client had tried.
I have also written Log files, there also after sending Command to com port, nothing is logged.
Note : No Anti Virus is installed there; Drivers are installed properly; Device is detected by the system when attached; displayed in device manager
Any suggestion or hint will be greatly appreciated...
Regards,
-SIFAR.
|
|
|
|
|
Sifar - 0 wrote: the software checks all COM Ports by sending ...
That seems to be a bad idea: COM ports can be busy, allocated, non-existing, or connected to special hardware (modem, infra-red, bluetooth,...).
Try the same "sending some command" using HyperTerminal to see it fail.
|
|
|
|
|
Is this a USB device using a virtual COM port? If so, here's what I do to find the COM port it's connected to.
NOTE: I'm not sure what the standard practice is for this, there may be a better way, but this was worked just fine for me so far. If anyone knows of a better, more robust way to do this, I'm open to suggestions.
You can determine which COM port the device is connect to by searching the registry under
HKLM\SYSTEM\CurrentControlSet\Enum\USB\VID_xxxx&PID_xxxx
where xxxx is the hex identifier for the VendorID and ProductID of the device. Inside this key is another subkey for each instance of the device, and then in the Device Parameters key you'll see PortName (I think, can't remember off hand exactly what it is). Anyway, the name of the COM port can be found here. You can iterate through each instance in the registry and attempt to open the .NET SerialPort object. If you successfully open the port, then the device is connected.
So you'll want to look for the key
HKLM\SYSTEM\CurrentControlSet\Enum\USB\VID_xxxx&PID_xxxx\<all subkeys="">\Device Parameters</all>
and read the PortName value from each instance.
foreach(string curPortName in portNames)
{
port.Name = curPortName;
try
{
port.Open();
break;
}
catch(InvalidOperationException ex)
{
}
catch(UnauthorizedAccessException ex){
}
}
You can check the MSDN documentation for how to read info from the Registry in C#.
Dybs
|
|
|
|
|
Thanx Dybs,
I had already tried this approach but it does not work under Windows Vista.
Actually, in Vista when you login as Administrator everything works fine. But with users other than Administrator it does not works. Vista creates different registry entries for othe Users.
I have found below solution :
I have used ManagementObjectCollection and ManagementObjectSearcher.
ManagementObjectCollection ManObjCollection;
ManagementObjectSearcher ManObjSearch;
ManObjSearch = new ManagementObjectSearcher("Select * from Win32_PnPEntity");
ManObjCollection = ManObjSearch.Get();
foreach (ManagementObject ManObj in ManObjCollection)
{
if (ManObj["Name"] == "Name You Are Looking For")
{
}
}
This has worked fine for me with XP and Vista, (Administrator and Non-Administrator) and it is fast also.
Hope this would help you further...
Regards,
-SIFAR.
|
|
|
|
|
Dear All,
How can I show the Windows Mobile circular waiting cursor from my form?
I'm sure it is very easy, but I've been looking for the solution form some time now without aany success.
Thanks in advance,
miguelji
|
|
|
|
|
I would try Cursor=Cursors.WaitCursor;
|
|
|
|
|
Tat was my first try, but in a Windows Mobile 6 device it doesn't work.
I'm probably doing something wrong, but it is so simple that I dont know what can be wrong.
miguelji
|
|
|
|
|
Yes, I think the cursor.waitcursor method may work in your scenario. Windows Mobile by default should display the waiting cursor for you. Is there something specific you are doing inside of your custom app? You didn't leave a lot of details.
|
|
|
|
|
Yes you are right, I was not leaving any detail.
I need to show the waiting cursor while my program performs a series of time consuming tasks. I've isolated the problem and created a WM6 (CF 3.5) application with a single form and a single button in it. Then I write the following code for the click event of the button (I use VB, but this would be the C# equivalent):
----------------------------------------------
Cursor c = default(Cursor);
c = Cursors.WaitCursor;
this.Refresh();
int I = 0;
int J = 0;
for (I = 1; I <= 10000000; I++) {
J = I * 3;
}
c = Cursors.Default;
this.Refresh();
----------------------------------------------
I run the programa, click the button and nothing happens, no cursor is displayed.
What Am I doing wrong here?
Thanks,
miguelji
|
|
|
|
|
Simply try this
Cursor.Current = Cursors.WaitCursor;
Cursor.Show();
and
Cursor.Current = Cursors.Default;
Cursor.Hide();
|
|
|
|
|
Thank you doananhtai!
It works perfect. It was easy, but thank you for being the one to tell how to do it.
Cheers,
miguelji
|
|
|
|
|
Dear All,
I have a critical application for which the performance has to be monitored.
I used the performance monitor in Windows 2003 server to log the data.
I have logged the counters of the Page file bytes and % processor time of the process / the service instance which has to be monitored along with the Processor % Processor time.
When I was analyzing the log I hae found a strange issue, the Processors % Processor time is 88 % but the instances % Processor time is 175 %.
Can any one tell me how this happens and how it is calculated?
Thanks a lot in advance.
Best Regards,
M. J. Jaya Chitra
|
|
|
|
|
Do you have a dual core system? If so the second number appears to be the percentage of time consumed relative to the capacity of a single core.
Today's lesson is brought to you by the word "niggardly". Remember kids, don't attribute to racism what can be explained by Scandinavian language roots.
-- Robert Royall
|
|
|
|
|
M. J. Jaya Chitra wrote: When I was analyzing the log I hae found a strange issue, the Processors % Processor time is 88 % but the instances % Processor time is 175 %
88 percent of 200 == 176
Sounds like you have two processers and the process being performance monitored is multi-threaded.
Best Wishes,
-David Delaune
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
