Thanks for pointing that out. I didn't realize I had posted it here in the lounge.

I am a lean mean ground beef machine!!!

Pimento PIMit SlimPIM Salsa Jibber Puritan FingerJAM PIMping

I am a lean mean ground beef machine!!!

tuan1111 wrote:

I write boot.asm->compiler->strip header->not copy to floppy,I copy to CD.I do it ?

Why go to all that trouble when you can use virtualization? You can just build your OS and boot directly into it with the VM.

I am a lean mean ground beef machine!!!

General information on programming the VGA: http://www.osdever.net/FreeVGA/vga/vga.htm[^]

I am a lean mean ground beef machine!!!

CaptainSeeSharp wrote:

Its about time you watch it.

Why? I can just spark a bowl and get the same effect.

I am a lean mean ground beef machine!!!

[Message Deleted]

One approach would be to store all message processing objects in a std::map<> container. Although this will only give you a 1 to 1 relationship between the expected window message and the object which handles it you'll have a nice start to begin expanding. When you receive the device notification message you can retrieve the object for that message and then call the appropriate method to handle the operation.

// Call this from your window procedure
void HandleDeviceMessage(UINT msg, WPARAM wParam, LPARAM lParam)
{
ProcObject *obj;
std::map::iterator iter;

iter = m\_DevNotifyMap.find(msg);
if(iter == m\_DevNotifyMap.end()) {
    return; // no object available to handle this notification
}

iter->second->OnNotification(msg, wParam, lParam); 

}

I am a lean mean ground beef machine!!!

kumar sanghvi wrote:

but the increased height of the title bar is not shown properly

This is because you are changing the bounding rectangle of the client area not the caption bar. The default window procedure will adjust this rectangle based on the height of the title bar, the height of the menu (if present) and any other non-client component managed by the window. You have however gotten one step close as you now have extra space reserved at the top of the window for your caption bar. The next step is to handle the WM_NCPAINT message and draw your custom caption bar with the desired height.

I am a lean mean ground beef machine!!!

Sorry I normally don't try to second guess other developers but could you explain why you are trying to do this? The only reason I ask is there may be a different approach than what I am thinking that would better suit your needs.

I am a lean mean ground beef machine!!!

So they finally figure out that if a chick tells a guy she wants to ride his disco stick that she can control his mind. Ppppffft DUH! :)

I am a lean mean ground beef machine!!!

SetFont() will not automatically change the size of the combo box. You can use GetTextMetrics() to obtain size information about about the font, calculate the minimum size necessary to display the font in the control and then manually adjust the size and position of the combobox.

I am a lean mean ground beef machine!!!

Oh snap! Ya'll gotta stop posting this stuff or I'll never get any work done! I'm so cereal guys. STOP! :)

I am a lean mean ground beef machine!!!

It'll definitely help me avoid being chastised by the admins on my cranky days. At the very least it'll keep the vein in my forehead from finally popping :laugh:

I am a lean mean ground beef machine!!!

Bluntman and Chronic!

I am a lean mean ground beef machine!!!

I've never seen that before. COOOOOOOOOL!

I am a lean mean ground beef machine!!!

Disregard my last post about recv()...my meds are making me way too fuzzy :) Ok, I was able to compile and run it and everything worked fine after a couple of changes. The first problem is with the CHECK() macro:

#define CHECK(iStatus) \
if(iStatus==SOCKET_ERROR) return 0;\
if(iStatus==0) return 0

DO NOT DO THIS! When this macro is expanded by the preprocessor the send or recv operation passed as iStatus will be executed twice:

if(::send(hSock,sz,strlen(sz),0)==SOCKET_ERROR) return 0;
if(::send(hSock,sz,strlen(sz),0)==0) return 0

Instead you might try something like this (until you get everything fixed):

#define CHECK(iStatus) \
{ \
int result = iStatus; \
if(result==SOCKET_ERROR) return 0; \
if(result==0) return 0; \
}

Every email client I tried did not like the date format included in the message header. The following change should work:

::GetDateFormat(0x409,0,0,T("dd MMM yyyy"),wa,200);

I am a lean mean ground beef machine!!!

For future reference please wrap your code postings in a <pre></pre> code block so that it's easier to read.

I am a lean mean ground beef machine!!!

If your SMTP client does not handle authentication the first thing I would check is to make sure that the server you are connecting to does not require it. Also make sure that the server allows relaying from the location you are connecting from (it probably does if it's an internal company server but it's always best to make sure). If that doesn't provide any answers I would load up a packet sniffer and monitor the transmissions between your application and the SMTP server. This should give you a better idea of how well the server is responding to your client. It's possible the server is returning an error that your client is not handling (hard to say without seeing the code). If neither of those provide you with any answers you might want to try installing a bare bones SMTP server on a test machine and seeing if your client (and the other examples you have downloaded) works with it.

I am a lean mean ground beef machine!!!

Sounds like you may be installing older versions of a redistributable file that Norton relies on. The first thing I would check is the file versions and then move to make sure that any files you are installing into the System32 folder actually belong there.

I am a lean mean ground beef machine!!!

includeh10 wrote:

anti-virus software blocked mail

Anti-virus and firewall software is one of the most common causes of the problem you are experiencing. It's also possible that your ISP is blocking port 25 (some do, some don't) in an effort to reduce spam on their network. Without more information such as what operation it's failing on (connect, send, etc.) it's hard to tell. Have you tried disabling your anti-virus and/or firewall and then running your app?

I am a lean mean ground beef machine!!!