|
|
Thank you for contributing...  
|
|
|
|
|
|
The CreateFile function creates or opens a file or I/O device.
The following code lists COM Ports in Win32..
#include <iostream>
#include <windows.h>
void main(){
char port_name[16];
for (int port_number = 1; port_number < 256; ++port_number)
{
port_number < 10 ?
sprintf(port_name, "COM%d", port_number) :
sprintf(port_name, "\\\\.\\COM%d", port_number);
HANDLE hFile = ::CreateFile(port_name,
GENERIC_READ | GENERIC_WRITE, 0, NULL,
OPEN_EXISTING, 0, NULL);
if(hFile != INVALID_HANDLE_VALUE)
std::cout << port_name << std::endl;
else
{
DWORD err = GetLastError();
if (err == ERROR_ACCESS_DENIED ||
err == ERROR_SHARING_VIOLATION)
std::cout << port_name << std::endl;
}
CloseHandle(hFile);
}
}
|
|
|
|
|
What if a COM port is in use at the time this code is run? It won't get listed.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Also, under Vista (and probably Weven), you need 'run as admin' to use the "\\\\.\\COM11" form. Stoopid bug I ran into when Vista was first released.
Cheers,
Peter
Software rusts. Simon Stephenson, ca 1994.
|
|
|
|
|
Good info... I hate having to deal with all these "run as admin" issues... 
|
|
|
|
|
This may not be so bad though... in most programs, if a COM port is already in use, then you can't use it for something else... so it shouldn't be listed anyway. Depends on what the OP needs to list the COM ports for.
|
|
|
|
|
umm... yea 
|
|
|
|
|
Hi pandit84,
I highly recommend that you have a look at EnumSerialPorts[^] written by MVP PJ Naughter[^]. Its been in development since around 1998 and supports every enumeration type... WMI, registry, setupapi and QueryDosDevice.
Best Wishes,
-David Delaune
|
|
|
|
|
Thanks a lot to All,
I have successfully enumerated registry and got list of COM ports available . If we have any
virtual port software which can create multiple ports, then also we can enumerate registry and read those port number.
|
|
|
|
|
Hello! I have a function that saves a jpeg file from an IP camera. It works sometimes, but sometimes, it doesnt. When I investigated, i found out that in the instances that it didnt work, the characters of the file when i convert it to a text file looks like this:
ෝ㚆��鍫᱉㓉��⛷통⌫㘿答窂脚麜鋴ᬓ犚厜褝沣놊��ꋂ䴍㢛諱᷐锫잛䕡逺Řޥ舔룣⣅‵쭫帏갪ಱ彗䩂䖒깔숢⢞ᴑ鎵졋쮧呤ᑵ蛝㙕횇涚噈혘㙌සᲷ貚臛诞
Proper jpeg files have characters that look like this:
*456789:CDEFGHIJSTUVWXYZcdefghijstuvwxyzƒ„…†‡ˆ‰Š’“”•–—˜™š¢£¤¥¦§¨©ª²³
I don't know what's wrong. Please help me!!! Here is the function I'm using:
int SendReceiveTest1( Socket^ server )
{
FileStream^ ambot = File::Create("pastilan.jpg");
array<Byte>^ msg = Encoding::UTF8->GetBytes("GET /snapshot.cgi HTTP/1.1\r\n");
array<Byte>^ msg1 = Encoding::UTF8->GetBytes("Authorization: Basic YWRtaW46\r\n\r\n");
array<Byte>^ header = gcnew array<Byte>(224);
array<Byte>^ bytes = gcnew array<Byte>(30000);
try
{
// Blocks until send returns.
Int32 byteCount = server->Send( msg );
Console::WriteLine( "Sent {0} bytes.", byteCount.ToString() );
Int32 byteCount1 = server->Send( msg1 );
Console::WriteLine( "Sent {0} bytes.", byteCount1.ToString() );
byteCount = server->Receive( header, header->Length, SocketFlags::None );
if ( byteCount > 0 )
{
Console::WriteLine( Encoding::UTF8->GetString( header ) );
}
while(byteCount > 0){
byteCount = server->Receive( bytes, server->Available, SocketFlags::None);
}
ambot->Write( bytes, 0, bytes->Length );
if( ambot )
delete (IDisposable^)ambot;
}
catch ( SocketException^ e )
{
Console::WriteLine( "{0} Error code: {1}.", e->Message, e->ErrorCode.ToString() );
return ( e->ErrorCode );
}
return 0;
}
Usually I dont bother asking if it NEVER works. But Im worried about this particular code because most of the time it DOES work. Thanks!!!
|
|
|
|
|
JPEG files contain encoded image data and will make no sense whatsoever if displayed as text. You should investigate what is happening to your data in between receiving it from the camera and passing it to whatever location you do. I am not sure that you should be trying to encode the data as indicated in the code fragment above.
|
|
|
|
|
Im sorry, something went wrong, here's the whole function:
int SendReceiveTest1( Socket^ server )
{
FileStream^ ambot = File::Create("pastilan.jpg");
array<Byte>^ msg = Encoding::UTF8->GetBytes("GET /snapshot.cgi HTTP/1.1\r\n");
array<Byte>^ msg1 = Encoding::UTF8->GetBytes("Authorization: Basic YWRtaW46\r\n\r\n");
array<Byte>^ header = gcnew array<Byte>(224);
array<Byte>^ bytes = gcnew array<Byte>(30000);
try
{
// Blocks until send returns.
Int32 byteCount = server->Send( msg );
Console::WriteLine( "Sent {0} bytes.", byteCount.ToString() );
Int32 byteCount1 = server->Send( msg1 );
Console::WriteLine( "Sent {0} bytes.", byteCount1.ToString() );
byteCount = server->Receive( header, header->Length, SocketFlags::None );
if ( byteCount > 0 )
{
Console::WriteLine( Encoding::UTF8->GetString( header ) );
}
while(byteCount > 0){
byteCount = server->Receive( bytes, bytes->Length, SocketFlags::None);
}
ambot->Write( bytes, 0, bytes->Length );
if( ambot )
delete (IDisposable^)ambot;
}
catch ( SocketException^ e )
{
Console::WriteLine( "{0} Error code: {1}.", e->Message, e->ErrorCode.ToString() );
return ( e->ErrorCode );
}
return 0;
}
The pastilan.jpg file that results is sometimes a proper jpeg file, meaning it's really a snapshot of the ip camera, and sometimes, it's not. It's totally RANDOM. I don't know what's happening...
|
|
|
|
|
while(byteCount > 0){
byteCount = server->Receive( bytes, bytes->Length, SocketFlags::None);
}
ambot->Write( bytes, 0, bytes->Length );
In the above lines you may be overwriting part of your image in the while loop, which means that you only write the last part of the file. You are also using the buffer length rather than the actual bytecount to write to the destination file.
|
|
|
|
|
There are two major flaws AFAICT:
1. you have a receiving loop that overwrites the receiving buffer, whereas your file writing is outside the loop; the correct way would have both receive and write in one loop, there is no need to first hold the entire image in memory.
2. you write a fixed length, independent of what you received. That is so wrong; your write statement needs to be based on the byte count you obtain from the receive statement.
And there is another weakness, if not a bug: you assume the header will hold 224 bytes. What if it doesn't? It is not up to the client to guess how big a header the server will use. Check the standards, or use an official implementation (if this is managed C++, why not use HttpWebRequest/HttpWebResponse classes?).
PS: please learn how to apply proper formatting, using PRE tags[^].
modified 11-Oct-11 12:27pm.
|
|
|
|
|
|
Please edit the above message and use PRE tags, so I can look at it tomorrow.
|
|
|
|
|
int SendReceiveTest2( Socket^ server )
{
FileStream^ ambot = File::Open("pastilan.jpg", FileMode::Create, FileAccess::ReadWrite);
array<Byte>^ msg = Encoding::ASCII->GetBytes("GET /snapshot.cgi HTTP/1.1\r\n");
array<Byte>^ msg1 = Encoding::ASCII->GetBytes("Authorization: Basic YWRtaW46\r\n\r\n");
array<Byte>^ header = gcnew array<Byte>(224);
array<Byte>^ bites = gcnew array<Byte>(1);
try
{
int byteCount = server->Send( msg );
Console::WriteLine( "Sent {0} bytes.", byteCount.ToString() );
int byteCount1 = server->Send( msg1 );
Console::WriteLine( "Sent {0} bytes.", byteCount1.ToString() );
byteCount = server->Receive( header, header->Length, SocketFlags::None );
if ( byteCount > 0 )
{
Console::WriteLine( Encoding::UTF8->GetString( header ) );
}
int count = 0;
while(1){
byteCount = server->Receive( bites );
ambot->Write(bites,0,1);
if (byteCount == 0)
break;
}
if( ambot )
delete (IDisposable^)ambot;
}
catch ( SocketException^ e )
{
Console::WriteLine( "{0} Error code: {1}.", e->Message, e->ErrorCode.ToString() );
return ( e->ErrorCode );
}
return 0;
}
|
|
|
|
|
oh my.
1.
you could have edited the existing message to adapt its formatting, rather than create yet another one, there is an edit widget below each of your posts for you to do so.
2.
when I said you needed to receive and store in a loop, and use the right amount of bytes, I did not imply to deal with one byte at a time; rather something like:
for(;;) {
byteCount = server->Receive( bytes, bytes->Length, SocketFlags::None);
if (byteCount<=0) break;
ambot->Write( bytes, 0, byteCount );
}
The performance difference should be quite noticeable.
3.
I'm still not sure about your header, which you are basically swallowing (i.e. showing as if it were text?????, then forgetting). Is it part of the communication, or is it the header part of the image (which you would need to include in the file)?
And is the camera emitting a JPEG format? Most camera's do, if so the very first bytes are likely to be FF D8 FF (these are three bytes represented in hex, not as text characters!), and most likely the bytes 6 through 9 contain 4A 46 49 46.
So check the incoming data (including your "header") for these values: either use a hex editor to see your resulting JPEG file, or adapt your code so you can see the first 10 bytes (in hex) for both the header and the first (or every) data packet you receive. Alternatively, try your code without the receive-and-show-header statements.
OTOH, if the camera does not generate JPEG, storing some other format into a file and give that a JPEG extension is not the way to convert image formats!
|
|
|
|
|
Oh, by the way, i just displayed the two sets of (jibberish) characters to demonstrate the difference in encoded data that results. The proper set of characters is the second one. I don't know where the first one comes from.
|
|
|
|
|
Member 8250612 wrote: Proper jpeg files have characters that look like this:
*456789:CDEFGHIJSTUVWXYZcdefghijstuvwxyzƒ„…†‡ˆ‰Š’“”•–—˜™š¢£¤¥¦§¨©ª²³
no, they don't.
well, let me rephrase that: nothing in the JPEG spec requires such a sequence of bytes. you might get an image which encodes to that, but that's entirely coincidental.
the most you can say about a JPEG is that it probably starts with these three bytes: FFD8FF. beyond that, the only constant is the structure defined by the file format; and that works with little four-byte headers which precede the various blocks of data and none of those blocks is required to look like that.
modified 11-Oct-11 15:58pm.
|
|
|
|
|
Have you tried asking this question in the Managed C++ forum?
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"Show me a community that obeys the Ten Commandments and I'll show you a less crowded prison system." - Anonymous
|
|
|
|
|
I've been trying to make my Window pretty or appealing, by setting a bitmap in the background of the window. The information I have found is mostly just do this, and it works, I came up with this, and placed it in my WM_PAINT. At first I got a little TT logo at the upper left, then it went away, I thought it was going to work.
I have triple checked my IDB_BG_INSTALL_PANE_BMP, and I know I got that right.
HDC mem_DCInstallation;
HBITMAP bmp_BGInstallation;
hdc = BeginPaint(cWnd, &ps);
bmp_BGInstallation = LoadBitmap(hIIS_Instance, MAKEINTRESOURCE( IDB_BG_INSTALL_PANE_BMP ));
mem_DCInstallation = CreateCompatibleDC(hdc);
SelectObject(mem_DCInstallation, bmp_BGInstallation);
BOOL bbResult;
bbResult = BitBlt(hdc, 0, 0, 500, 311, mem_DCInstallation, 0, 0, SRCCOPY);
DeleteDC(mem_DCInstallation);
DeleteObject(bmp_BGInstallation);
|
|
|
|
|
Do your background bitmap painting by handling the WM_ERASEBACKGROUND[^] message
If your actions inspire others to dream more, learn more, do more and become more, you are a leader." - John Quincy Adams
You must accept one of two basic premises: Either we are alone in the universe, or we are not alone in the universe. And either way, the implications are staggering” - Wernher von Braun
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
