|
...and it depends the way the samples have been coded (see the codecs)...
|
|
|
|
|
No, it doesn't. Codec operations are performed on baseband signals, before and after modulation/demodulation.
Some people think of it as a six-pack; I consider it more of a support group.
|
|
|
|
|
Hi,
I got a problem in my programmming project.
I need to develop an agent program that connect between server and client.
The matter is I need to develop it in Win 3.1 and MSVC++ 1.52.
So, I chagned some api functions and I could connect sockets between win 2000 server and win 3.1 client.
However, whenever I try to run some functions after accepting socket and checking the IP, agent program makes "Stack Overflow" error.
But no variable initiation is exeist after that.
So, I wanna use Handle for sockets as I did in Win 2000.
Is this the right way?
If so,
Could you please let me know the api function that close handle like CloseHandle in MSVC++ 6.0?
Thanks in advance.
|
|
|
|
|
Why not try to install platform SDK? Probably it could solve the API not exist problem.
Sonork 100.41263:Anthony_Yio
Life is about experiencing ...
|
|
|
|
|
Life is about reading
This person is trying to use Win3.x, not a Win32 version, so Platform SDK won't help...
Steve S
|
|
|
|
|
When developing socket programs under Win16 the WinSock API (Version 1.1) must be used. (See http://www.sockets.com/winsock.htm[^]).
In short...
You create a socket with the socket() function.
You connect a client socket with the connect(..) function.
You read data from a socket with the recv() function (or if asychron what it a must under Win16 via WSAAsyncSelect and windows messaging on FD_READ)
You close a connected socket with the closesocket() function.
For using this function you must include the winsock.h header. (In the latest MSVC 1.52c version this is included).
A very good book for WinSock Programming under Win16 is named book on the website of the above link: Bob Quinn "Windows Sockets Network Programming"
A pendant for CloseHandle() in Win32 is not known under Win16.
Here you have to handle all socket specific functions with the WinSock API.
|
|
|
|
|
Is it possible for you to post a snippet of code where you get the Stack Overflow?
I don't envy you still developing 16-bit on 1.52. I am glad I no longer need to use this compiler!;)
Ant.
|
|
|
|
|
Please tell me...
How to start another application in my application..
In my application I need to call another application to open. And I am not use the MFC.
Can someone tell me how to open another application.
Thanks..
|
|
|
|
|
ShellExecute would do the trick!
ShellExecute(handle, "open","calc.exe", NULL, NULL,SW_SHOWNORMAL);
/Jarek
As far as the laws of mathematics refer to reality, they are not certain; and as far as they are certain, they do not refer to reality.
Albert Einstein
|
|
|
|
|
Also check out CreateProcess() .
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
|
|
|
|
|
I'm attempting to implement an IP tunneling protocol via TCP/IP on Windows XP platforms. Yeah I know, re-inventing the wheel, but please bear with me. Anyway, the tunneling protocol not only needs to redirect the packets but it needs to modify packet contents and yet be as transparent as possible. The worst part of it all is that I will have to use a pre-compiled DLL to perform certain operations while having no idea how the DLL performs those operations. No, I don't have access to the DLL's code.
I initially thought of implementing it via NDIS drivers, but they run in kernel mode and there isn't any documented way for them to communicate with user-mode processes that I will require to make use of the DLL. There is a way, but it is undocumented which is why I'm shying away from this method.
The other method that I thought of involves creating a tunneling server service coupled with a tunneling client service. The problem here is that I have to intercept IP packets on the client machines and then modify and forward them through the client service. I would also have to add NAT features to the server service. Which I wouldn't have to do using NDIS drivers because they have complete access to the packets before they are sent and I can have Internet Connection Sharing do the NAT work. I was told that it is possible to intercept the IP packets via Windows Sockets but this is unexplored territory for me. I also remember messing with an application running on a Win9x platform which allows the use of a SOCKS proxy for programs which does not include SOCKS support. I suppose the concept is the same, but then again that was Win9x.
I'm more inclined to do the 2nd method since it sounds safer hehe. But I was hoping for a solution that would feel like I'm using the Virtual Private Network implementation built into Windows XP machines. Unfortunately, I simply can't use the MS VPN because of the proprietary design of the protocol I'm supposed to implement.
Right now, I'd be satisfied with information regarding packet interception and modification via Windows Sockets, but I'd be very greatful if someone could come up with a better implementation method.
|
|
|
|
|
How to create dialog to select folder??
|
|
|
|
|
SHBrowseForFolder
modified 12-Sep-18 21:01pm.
|
|
|
|
|
FOr some reason, every time I start my app, the compiler disables my breakpoints, thus I cant debug the way I want.
Any ideas why this is happening?? I'm using VS6.0
-C
|
|
|
|
|
Are you positive that when you built the app you built it in debug mode? I have forgotten that I had built an app in release mode and tried to debug it and received similar results as you have described.
|
|
|
|
|
Yes its in Debug mode, but I know I've debugged in Debug and Release. Just seems odd that I cant set breakpoints now.
-C
|
|
|
|
|
Most likely, you are looking at the wrong code (you might have another copy of your binaries that is being executed).
|
|
|
|
|
Try putting
int asm 3;
in your code
/* Let it ignore that!*/
|
|
|
|
|
Check that in project->settings c/c++ tab debug info is set to 'program database' optimization to 'disable(debug)' and in link tab chaeck 'Generate debug info'
--PM
|
|
|
|
|
Is the code in a DLL that you are trying to debug? If so, build and run the DLL pointing at the appropriate .exe should do the trick.
Ant.
|
|
|
|
|
How about deleting the .pdb file?
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
|
|
|
|
|
I have an application that uses wininet HttpSendRequest and InternetSetOption to send a digital certificate when sending a request to a site for authentication. Everything works great on my development PC, but when we try to run it on a server with Windows Server 2003 HttpSendRequest returns 12157 ERROR_INTERNET_SECURITY_CHANNEL_ERROR.
Both are using the same digital certificate imported using the import wizard in and are located in the same store.
I have searched Microsoft's site for the error, but have not been very successful. I find items for Windows CE, but nothing else.
Does anyone have any insight on this problem?
|
|
|
|
|
I am trying to remove a child window title bar at run time. I have tried it statically using Properties, but it returns, with a title, each time I run the application. How can I remove it?...and I would like to find out how it is being created at run time. Not sure where to look in the code.
Thanks.
Jerry
|
|
|
|
|
have you tried removing the WS_CAPTION style from the window long parameter? That is how the title bar gets added. If you use a style like WS_OVERLAPPED, it is a predefined style that includes the caption as well as others like the border and sysmenu.
Build a man a fire, and he will be warm for a day Light a man on fire, and he will be warm for the rest of his life!
|
|
|
|
|
Actually my project is a SDI with a view and doc. It is the title for the view window which is giving me trouble.
Jerry
|
|
|
|