IT & Infrastructure

A lot depends on how your hardware is set-up, is the modem and phone plugged into the same extension? TAPI needs to have opened the device (modem) to be able to see the calls on the line. Your application needs to open the line device using lineOpen and monitor the events and keep a track of the active HCALL handles. You should then be able to do the data transfer using lineGetID to get the COM port. Actually, thinking about it if you have the device opened when the call comes in then you might be able to use lineGetID on the device rather than the call. http:\\www.julmar.com has some TAPI utilities for monitoring lines, you might want to see if these can see the call handle. Also the TAPI Browser on the platform SDK is usefully for seeing what handles are available to you. Michael :-)

I in no way benefit from my constant plugs of the Free Library on InformIT.com, but again, I'd recommend signing up there and taking a boo around the Free Library in the programming sections. There's a lot to be learned from the Visual C++ books. - Jason Do you have a Pulse? SonorkID: 100.611 Jason

How 'bout you show us what you've already done, explain what problems you're having, and then ask specific questions? Sounds like a challenging lab/homework assignment. We did something similar in my mcontrollers class - a digital voltmeter. Oh, and though you might find some HC11 hobbyists and/or experts here, I'm sure there are many other sites that can offer you more directed help. This is a Windows programming site. :) Just Google for 68HC11 and you will be inundated with information. Jon Sagara What about :bob:? Sonork ID: 100.9999 jonsagara

If you are very certain of what you're doing, and very careful doing it, sure! I do all the time, but there are some rules of thumb to follow. Number one is to make sure the power is off on the device you're connecting. Another is to make absolutely sure that you're making an appropriate connection - you'd be amazed at what some people try to do to their PCs. And I'd strongly advise that you resist the urge to add/remove anything inside the case with power applied. The contacts are just too close together to do so safely. On newer systems even shutting off the power isn't completely safe - it's far safer to pull the plug. In many cases, most in fact, the OS will not detect the change until you reboot. Hot-swapping a mouse or a keyboard (the basic kind, not the new fancy ones) will generally do no harm. Adding or removing a modem or router is also harmless, though I wouldn't expect either to work properly without rebooting.

STL was not designed for inheritance. This may have changed, but last I checked destructors weren't virtual, for example, and some key information in some classes, like string, is private, making it difficult to implement certain behaviors in the inherited classes. Also, while generally fast, STL is missing some common place protections, or at least asserts in debug mode. The STL string class is completely lame. The collections classes, however, are generally nice, even if a little obscure. (Having a "common" interface may sound nice in theory but sometimes it's just plain annoying and cumbersome.) Personally, I don't like the STL interface. However I work with a guy who really likes it, so I suppose it's a matter of personal taste. (Even my co-worker has conceded, however, that the documentation of STL leaves much to be desired and many implementations, especially the Dinkumware VC6 version, are very obscure and difficult to debug.)

Yep, here's what we do at the shop to test for 2.2: iErr = WSAStartup(wVersionRequested, &wsaData); if (!iErr) { // Confirm that the WinSock DLL supports 2.2. // Note that if the DLL supports versions greater // than 2.2 in addition to 2.2, it will still return // 2.2 in wVersion since that is the version we // requested. if ( LOBYTE( wsaData.wVersion ) != 2 || HIBYTE( wsaData.wVersion ) != 2 ) { BarkAndWhine(_T("CIdsSocket::WinsockInit() - Could not find a usable WinSock DLL for version %d.%d"), byVersionHigh, byVersionLow); } else { // The WinSock DLL is acceptable. Proceed. } } Chistopher Duncan Author - The Career Programmer: Guerilla Tactics for an Imperfect World (Apress)

This has been mentioned a few times before, but the deal is that it won't integrate with VS6, but you should be able to install it and use it by running the program separately. Jeremy Davis wrote: Is this a Micro$oft marketing ploy Of course it is, they want all developers to use the latest version of visual studio. But can you blame them? If you've released anything commercially how often does your tech support staff say, "If you'll upgrade to the latest version that problem should be taken care of." James Sonork ID: 100.11138 - Hasaki "My words but a whisper -- your deafness a SHOUT. I may make you feel but I can't make you think." - Thick as a Brick, Jethro Tull 1972

A discussion group called "General discussion" is strictly C#? This is new. Topics here are: Icons CGI+Perl problems Directx9 release date Maybe you do not like C, or free compilers, or both. OK. Then do not use it.

After I had sent the last message, that's exactly what I did and it worked. I decided to imitate the program that worked. I should have done that in the first place. :rolleyes: Thanks for your help. Why not throw away a dime? I throw away ten pennies all the time.

I'll try bumping this in case anyone knows *sigh*

http://iconmania.8m.com http://www.iconolog.net

Maybe this article helps? PS. This kind of question would be better in "Visual C++" forum, even if you are using Borland's compiler.

Sorry, I forgot to mention which C++ example was. It is the ShowWindowTree example in this same code project.

I don't know, but I'm waiting for it anxiously too! :jig: James Sonork ID: 100.11138 - Hasaki "Not be to confused with 'The VD Project'. Which would be a very bad pr0n flick. :-D" - Michael P Butler Jan. 18, 2002

With LGPL, you can link dynamically with the code (the LGPL licenced part must be a DLL), and you can use the headers, including deriving classes, from your commercial code without having to release your code under a Free Software licence. GPL code can't be linked with (statically or dynamically) or included to a non-free program. However, you could isolate the GPL part as an independent process, and use its functions from the commercial application through COM or some other communication mechanism.

I may be wrong but I thought you could use Visio.