T
}T{Reme [Q_G]
c0000005 error
I'm amazed... There's a couple programs I got that simply
stop in the middle of exectution. Found in my logs that it
crashes with c0000005 error. After an hour of searching on
the 'support' site I'm still oblivious as to what this
error means. (I assume illegal memory access, out of
bounds) Funny thing is that it does refer to a
hotfix/service pack for Fox Pro or something... but not to
a hotfix for XP itself. These programs run perfectly fine
on any other windows version (95, 98, 98SE, NT, 2000) yet
fail to run on XP under any so-called compatability
setting. O wait, it ran once after 50 tries, failed to
duplicate the result by running it again 2 seconds later.
You can tell me many lies but this for sure marks it as a
core bug does it not?
Incidentally one of those programs was written by me. So I
modified the code over and over to find the effected error
line. It's a memory allocation bug. I called this
function : malloc(); and it died. I tried replacing it
with calloc(); farcalloc(); farmalloc(); and whatever
other variants I could find to no success. Strangely I got
another program totally filled with malloc() calls and it
runs fine so I'm clueless as to how this can be.
I have 3 computers. 1 has xp, 1 with 2000 and the other
with 98 but recently got changed to xp. I have a bunch of
shares running on the 2000 machine, and also some on the
xp one. Here's the set up with some example shares :
XP : Same user/pass as 2000 machine. Share A opened to
everyone, share B opened to local user only.
2000 : Same user/pass as XP machine. Share A opened to
everyone, share B opened to local user only.
98 (old situation) : Different user/pass. No shares.
When accessing any public share from any computer it works
as expected.
When accessing either XP/B or 2000/B from 98 I get blocked
out as expected.
Here comes the strange part :
When accessing XP/B from 2000 I get a request for
password. No matter how many times I try the correct one
it will not let me enter.
When accessing 2000/B from XP it will ask me for the
password once everytime I acess the share for the first
time (as in every boot).
In the past I had 2 2000 machines and I could move freely
between all shares that were open to only the local user
and the same user/pass was used on both machines. I used
this trick to give myself complete control over my systems
but blocking everyone else.
Right now using this configuration I'm basically forced to
open up my shares to everyone. Something I'll never do as
I got a permanent internet connection and there are plenty
of spammers out there that love to put dialers, messages,
virusses and other junk on my pc. I still gotta test out
if I can access my shares from the recently converted 98
machine that now has xp running on it but I sincerely
doubt it.
Can anyone clarify what difference has been added between
the last (2000) and new (xp) version of windows? How can
it be that it keeps asking for the password if the user
AND password are identical?
Lil side story to amuse the public :
Once I by accident had my F drive shared to the public.
Some moron placed the file explorer.exe (yes, a virus) and
a nice warning in a text file next to it that 'hackers'
could access my comp and download/put files on it. It was
highly amusing to see this attempt to infect my computer
with a virus as any numbskull would've seen the missing
windows/winnt folder on that drive since my OS wasn't
there. Too bad the open shares viewer only shows a
computer name (useless over the internet), not IP number
(thank you Bill Gates) so I wasn't able to return the
favor. I'm not gonna explain how any user with no
knowledge or extra programs whatsoever can reproduce this
ever sad 'hacking attempt'.
Other than this most problems I had so far are solved...
Oh yes, I have one question. When is there finally going
to be an expert release of Windows? I'm sick and tired of
all the 'user friendly' stuff. (Or as I call it 'click and
get a sore wrist') Took me an hour and a half to get rid
of the XP look and save me alot of clicking to access key
system features I user every day. Sure, I like to thank
you for the perfect admin program called mmc
Made my
live alot easier as it even includes remote management in
case I'm lazy to hit my KVM switch. But... there's always
room for improvement. Some examples are : Direct access to
core components settings and to the components themselves
is still blocked. It simply denies me the ability to
repair some problems other than doing a full restore or
reinstall. Second, please get rid of those ridiculous
computer names. I don't know any respectable system admin
that uses these instead of IP numbers and MAC addresses.
These names are utterly useless when trying to track down
a spammer abusing the messenger service (Message from
SPAMMASTER on XXX date : Please buy blabla). Or when
tracking down a newbie hacker trying to probe your shares
in the shares viewer as it yet again just shows the
computer name.
Since it requires me to pay a nice sum of money to pass
this valuable piece of information that could be used to
help improve the software and I refuse to do such a thing
I'm posting it here. Oh, and I wasn't able to find an
email address anywhere as to send this to. But I'm sure
one of the moderators or administrators of this forum will
pass this to other deparements. Still, I'm giving customer
support a big fat zero as it did not help me in any way.
(Knowledge base has nothing, too much referring and
searching etc etc)
Cheers, }T{Reme [Q_G]
I'm amazed... There's a couple programs I got that simply
stop in the middle of exectution. Found in my logs that it
crashes with c0000005 error. After an hour of searching on
the 'support' site I'm still oblivious as to what this
error means. (I assume illegal memory access, out of
bounds) Funny thing is that it does refer to a
hotfix/service pack for Fox Pro or something... but not to
a hotfix for XP itself. These programs run perfectly fine
on any other windows version (95, 98, 98SE, NT, 2000) yet
fail to run on XP under any so-called compatability
setting. O wait, it ran once after 50 tries, failed to
duplicate the result by running it again 2 seconds later.
You can tell me many lies but this for sure marks it as a
core bug does it not?
Incidentally one of those programs was written by me. So I
modified the code over and over to find the effected error
line. It's a memory allocation bug. I called this
function : malloc(); and it died. I tried replacing it
with calloc(); farcalloc(); farmalloc(); and whatever
other variants I could find to no success. Strangely I got
another program totally filled with malloc() calls and it
runs fine so I'm clueless as to how this can be.
I have 3 computers. 1 has xp, 1 with 2000 and the other
with 98 but recently got changed to xp. I have a bunch of
shares running on the 2000 machine, and also some on the
xp one. Here's the set up with some example shares :
XP : Same user/pass as 2000 machine. Share A opened to
everyone, share B opened to local user only.
2000 : Same user/pass as XP machine. Share A opened to
everyone, share B opened to local user only.
98 (old situation) : Different user/pass. No shares.
When accessing any public share from any computer it works
as expected.
When accessing either XP/B or 2000/B from 98 I get blocked
out as expected.
Here comes the strange part :
When accessing XP/B from 2000 I get a request for
password. No matter how many times I try the correct one
it will not let me enter.
When accessing 2000/B from XP it will ask me for the
password once everytime I acess the share for the first
time (as in every boot).
In the past I had 2 2000 machines and I could move freely
between all shares that were open to only the local user
and the same user/pass was used on both machines. I used
this trick to give myself complete control over my systems
but blocking everyone else.
Right now using this configuration I'm basically forced to
open up my shares to everyone. Something I'll never do as
I got a permanent internet connection and there are plenty
of spammers out there that love to put dialers, messages,
virusses and other junk on my pc. I still gotta test out
if I can access my shares from the recently converted 98
machine that now has xp running on it but I sincerely
doubt it.
Can anyone clarify what difference has been added between
the last (2000) and new (xp) version of windows? How can
it be that it keeps asking for the password if the user
AND password are identical?
Lil side story to amuse the public :
Once I by accident had my F drive shared to the public.
Some moron placed the file explorer.exe (yes, a virus) and
a nice warning in a text file next to it that 'hackers'
could access my comp and download/put files on it. It was
highly amusing to see this attempt to infect my computer
with a virus as any numbskull would've seen the missing
windows/winnt folder on that drive since my OS wasn't
there. Too bad the open shares viewer only shows a
computer name (useless over the internet), not IP number
(thank you Bill Gates) so I wasn't able to return the
favor. I'm not gonna explain how any user with no
knowledge or extra programs whatsoever can reproduce this
ever sad 'hacking attempt'.
Other than this most problems I had so far are solved...
Oh yes, I have one question. When is there finally going
to be an expert release of Windows? I'm sick and tired of
all the 'user friendly' stuff. (Or as I call it 'click and
get a sore wrist') Took me an hour and a half to get rid
of the XP look and save me alot of clicking to access key
system features I user every day. Sure, I like to thank
you for the perfect admin program called mmc
Made mylive alot easier as it even includes remote management in
case I'm lazy to hit my KVM switch. But... there's always
room for improvement. Some examples are : Direct access to
core components settings and to the components themselves
is still blocked. It simply denies me the ability to
repair some problems other than doing a full restore or
reinstall. Second, please get rid of those ridiculous
computer names. I don't know any respectable system admin
that uses these instead of IP numbers and MAC addresses.
These names are utterly useless when trying to track down
a spammer abusing the messenger service (Message from
SPAMMASTER on XXX date : Please buy blabla). Or when
tracking down a newbie hacker trying to probe your shares
in the shares viewer as it yet again just shows the
computer name.
Since it requires me to pay a nice sum of money to pass
this valuable piece of information that could be used to
help improve the software and I refuse to do such a thing
I'm posting it here. Oh, and I wasn't able to find an
email address anywhere as to send this to. But I'm sure
one of the moderators or administrators of this forum will
pass this to other deparements. Still, I'm giving customer
support a big fat zero as it did not help me in any way.
(Knowledge base has nothing, too much referring and
searching etc etc)
Cheers, }T{Reme [Q_G]