Francois PIETTE wrote:
> GDisplayProc is assigned a routine which output the message to the
> console window and to the log file and which is used all over the
> application.
>
> Guess what ? It works !
> This is not satisfying since the log file is full of unwanted
> messages and this probably o
Hi Francois,
> A dual mode service is an application which detect if it run as a
> service
I understeand. I did the same concept years ago
--
mvg, Wilfried
http://www.mestdagh.biz
http://www.comfortsoftware.be
http://www.expertsoftware.be
--
To unsubscribe or change your settings for TWSocket
Actually the service is a dual mode service/app console and it works
perfectly well as a console application (and also as a service when a
debugger is attached).
I do not understand the 'dual mode' but could that be a reason?
A dual mode service is an application which detect if it run as a s
Seriously, what happens if you run the console application as a
service with my NT Wrapper http://www.duodata.de/ntwrapper/?
It will surely not work because my code for dual mode will be fooled,
thinking it is a service application while it is not.
If that works I guess the problem can be fo
Hi. I'm trying to build a first application with ICS (latest version), under
Delphi XE and I'm getting an unexpected behavior. I took WebServer demo as a
tutorial.
The application works well with OnGetDocument events, but when I get a
OnPostDocument event, after I perform the return of the valu
Hi Francois,
> Actually the service is a dual mode service/app console and it works
> perfectly well as a console application (and also as a service when a
> debugger is attached).
I do not understand the 'dual mode' but could that be a reason? What happens
if you put your application into 1 obje
Arno Garrels wrote:
> Francois PIETTE wrote:
>>> Maybe when you use the debugger then the application run
>>> undeer a different user?
>>
>> I start the service which starts sending his UDP datagrams (This is a
>> SNMP client) and waiting for UDP response which never comes. Then I
>> attach the de
Francois PIETTE wrote:
>> Maybe when you use the debugger then the application run
>> undeer a different user?
>
> I start the service which starts sending his UDP datagrams (This is a
> SNMP client) and waiting for UDP response which never comes. Then I
> attach the debugger to the running servic
When the debugger is attached is it exactly the same like when it's not
attached for the program being executed ?
I would say no since my application is working.
But I would say it doesn't change the time required to do domething.
OK then, my idea was that it's different.
Actually I work with
On 18/4/2011 5:35 μμ, Francois PIETTE wrote:
I think that if you consider what I suggested before, might help you...
It maybe has to do with extra process time the debugger gives
Thanks for insisting.
Which extra process time do you mean ? The debugger has just to be
attached. No need to set a
I think that if you consider what I suggested before, might help you...
It maybe has to do with extra process time the debugger gives
Thanks for insisting.
Which extra process time do you mean ? The debugger has just to be attached.
No need to set any breakpoint nor single step. Just attach. I
Maybe when you use the debugger then the application run
undeer a different user?
I start the service which starts sending his UDP datagrams (This is a SNMP
client) and waiting for UDP response which never comes. Then I attach the
debugger to the running service process and suddenly the UDP da
On 18/4/2011 5:12 μμ, Arno Garrels wrote:
Maurizio Lotauro wrote:
Maybe when you use the debugger then the application run undeer a
different user?
Not when the debugger is attached to a running process.
If the debugger spawns the process to be debugged with CreateProcess
then that might happe
Maurizio Lotauro wrote:
> Maybe when you use the debugger then the application run undeer a
> different user?
Not when the debugger is attached to a running process.
If the debugger spawns the process to be debugged with CreateProcess
then that might happen.
--
Arno Garrels
--
To unsubscribe o
Maybe when you use the debugger then the application run undeer a different
user?
Bye, Maurizio.
This mail has been sent using Alpikom webmail system
http://www.alpikom.it
--
To unsubscribe or change your settings for TWSocket mailing list
pl
> *Subject:* Re: [twsocket] UDP receive issue from a Windows service
> The code for the service is the code I already used in other
> application which works fine (using TCP altough).
I have UDP listen sockets in my ComCap application, running as a service,
sucking in syslogs on port 514 24/7 fro
I had a similar experience in the past, not with ICS components but
generally working on a completely different project.
When project was running normally at some point did not work but when
attaching a debugger then it would work.
The problem at that situation was that the program needed some ti
On 18/4/2011 2:34 μμ, Francois PIETTE wrote:
No idea, but that can't be a permission issue IMO. Receiving datagrams
in a service running as system works fine. Also attaching a debugger
doesn't change security context of the debugee.
What happens is that a new thread is created in the process bein
No idea, but that can't be a permission issue IMO. Receiving datagrams
in a service running as system works fine. Also attaching a debugger
doesn't change security context of the debugee.
What happens is that a new thread is created in the process being
debugged, maybe there's some issue with your
Hello Francois,
> Hi !
>
> I have a strange problem: in a windows service and using UDP, the
> service do not receive UDP datagram. Trying to debug this problem, I
> attach Delphi debugger to the running service and suddenly it starts
> receiving the UDP datagrams !
>
> Actually the service is a
Hi !
I have a strange problem: in a windows service and using UDP, the service do
not receive UDP datagram. Trying to debug this problem, I attach Delphi
debugger to the running service and suddenly it starts receiving the UDP
datagrams !
Actually the service is a dual mode service/app conso
Arno Garrels wrote:
> Arno Garrels wrote:
>> Hello Wilfried,
>>
>>> Hi,
>>>
>>> I just discovered that the property editor for LineEnd is broken
>>> using Delphi XE. No big deal for me as I always create TWSocket at
>>> runtime. I don't know how much work it is. If someone can give some
>>> hint
22 matches
Mail list logo
