1. RE: TCP (Mirawald) in XP
The Windows NT Kernel(wich XP uses) handles things differently than
previous ones, I don't know why.
I use Hawk NL, never had a problem on XP, or 98:
http://www.rapideuphoria.com/cgi-bin/asearch.exu?win=on&keywords=hawknl
Julio C. Galaret Viera wrote:
>
>
> I am working on a program on Windows XP and using TCP.ew from Jason
> Mirawald.
>
> Server and clients connect fine, detect host and IP fine too.
>
> But they can't interchange messages. According to my tests they aren't
> recognizing WM_SOCKET messages.
>
> Server and client work nicely on both Windows 95 and 98, including
> sending and receiving messages.
>
> Anybody knows why?
>
> Thank you,
>
> Julio C. Galaret Viera
>
2. RE: TCP (Mirawald) in XP
Jason ...
Not sure exactly what your using sockets for, but I do extensive network
management tools using sockets.
I have 95,98,NT,2000 and XP machines. I use TCP4U.ew and its always solid as a
rock ...
Just a thought ....
mike
-----Original Message-----
From: Julio C. Galaret Viera [mailto:euphoria at ured.net]
Sent: Saturday, March 06, 2004 12:19 PM
To: EUforum at topica.com
Subject: TCP (Mirawald) in XP
I am working on a program on Windows XP and using TCP.ew from Jason
Mirawald.
Server and clients connect fine, detect host and IP fine too.
But they can't interchange messages. According to my tests they aren't
recognizing WM_SOCKET messages.
Server and client work nicely on both Windows 95 and 98, including
sending and receiving messages.
Anybody knows why?
Thank you,
Julio C. Galaret Viera
TOPICA - Start your own email discussion group. FREE!
3. RE: TCP (Mirawald) in XP
Thank you everybody for the replies.
Code seems to be fine since it works on Win9x, though not fully tested
on these platforms.
But I think I've discovered why it's not working on XP. The window
handling TCP was not the main window but a child one. Once code was
changed to the main window, it began to work!
In relation with EuLibnet, yes, it crashes after about thirty minutes.
But it stop working not only on XP but also on Win 95 and '98.
Cojabo/Elliot, I'm missing something in your messages. It's not clear to
me if crashes you refer in Win98 are said about Hawk NL or TCP.ew.
Many thanks,
Julio C. Galaret Viera
Mario Steele wrote:
>
>
> Leave it to the Expert of TCP.ew to figure it out. ^.^
> If you can show me some code that your using in your server, and what
> WinAPI Library you are using, I'm sure I can help ya out.
>
> EuMario
>
> Hance, Michael wrote:
>
> >
> >Jason ...
> >
> >Not sure exactly what your using sockets for, but I do extensive network
> >management tools using sockets.
> >
> >I have 95,98,NT,2000 and XP machines. I use TCP4U.ew and its always
> >solid as a
> >rock ...
> >
> >Just a thought ....
> >
> >mike
> >
> >-----Original Message-----
> >From: Julio C. Galaret Viera [mailto:euphoria at ured.net]
> >Sent: Saturday, March 06, 2004 12:19 PM
> >To: EUforum at topica.com
> >Subject: TCP (Mirawald) in XP
> >
> >
> >I am working on a program on Windows XP and using TCP.ew from Jason
> >Mirawald.
> >
> >Server and clients connect fine, detect host and IP fine too.
> >
> >But they can't interchange messages. According to my tests they aren't
> >recognizing WM_SOCKET messages.
> >
> >Server and client work nicely on both Windows 95 and 98, including
> >sending and receiving messages.
> >
> >Anybody knows why?
> >
> >Thank you,
> >
> >Julio C. Galaret Viera
> >
> >
> >TOPICA - Start your own email discussion group. FREE!
> >
> >
> >TOPICA - Start your own email discussion group. FREE!
> >
> >
