Kent Hansen
May 19th 04, 02:09 PM
Im making an application that implores multithreading over=20
network, now it works in xp - 2000 but in windows 98, im=20
having the wirdest faults.
1. the windows kernal is unable to close down threads that=20
have been fully executed and are finished with running=20
(not a big problem sins i then just kill the thread my=20
self.)
2. When i try to kill the program it self then it comes=20
and say that it cant kill the program because theres a=20
loos thread hanging now I have verified with the stack=20
pointer and the heap that theres no threads from this=20
program that is left hanging so where this one comes from=20
I have no idear. (Might be from my wifes sewing business.)
Now just incase some one is going to blame the hard ware=20
and say that the fault lies there then hers a littel info=20
on the hardware.
CPU: Athlon XP 2100+
RAM: 256 MB
so this is not the problem i think, and sins the program=20
runs on a Win XP and 2000 on the same machine then I would=20
doud that it=B4s the hardware.
One could then speculate that Win 98 is faulty and not=20
updated i have been there my self and updated the system 2=20
dayes prior to this posting.
Now if some one have an idear please feel free to give a=20
hint im now on the 3 day and my patients is starting to=20
become a very thine thread.=20
mean while Ill pick up my Sir Arthur Connendoyle "If you=20
eliminate all posibilities how ever in propabel what ever=20
is left must be the thing your looking for".
yours Friendly=20
Kent Hansen
AKA Crahsoverride.
network, now it works in xp - 2000 but in windows 98, im=20
having the wirdest faults.
1. the windows kernal is unable to close down threads that=20
have been fully executed and are finished with running=20
(not a big problem sins i then just kill the thread my=20
self.)
2. When i try to kill the program it self then it comes=20
and say that it cant kill the program because theres a=20
loos thread hanging now I have verified with the stack=20
pointer and the heap that theres no threads from this=20
program that is left hanging so where this one comes from=20
I have no idear. (Might be from my wifes sewing business.)
Now just incase some one is going to blame the hard ware=20
and say that the fault lies there then hers a littel info=20
on the hardware.
CPU: Athlon XP 2100+
RAM: 256 MB
so this is not the problem i think, and sins the program=20
runs on a Win XP and 2000 on the same machine then I would=20
doud that it=B4s the hardware.
One could then speculate that Win 98 is faulty and not=20
updated i have been there my self and updated the system 2=20
dayes prior to this posting.
Now if some one have an idear please feel free to give a=20
hint im now on the 3 day and my patients is starting to=20
become a very thine thread.=20
mean while Ill pick up my Sir Arthur Connendoyle "If you=20
eliminate all posibilities how ever in propabel what ever=20
is left must be the thing your looking for".
yours Friendly=20
Kent Hansen
AKA Crahsoverride.