Valhalla Legends Archive

Programming => Battle.net Bot Development => Topic started by: NetNX on September 18, 2004, 09:02 PM

Title: the memory could not be "read"
Post by: NetNX on September 18, 2004, 09:02 PM
i keep getting crashes when calling NLS.dll that say the memory could not be "read" at specific locations... what does this error message mean?
Title: Re:the memory could not be "read"
Post by: UserLoser. on September 18, 2004, 09:09 PM
It's obvious, isn't it?
Title: Re:the memory could not be "read"
Post by: NetNX on September 18, 2004, 09:51 PM
yes but how would i go about correcting the problem...

ive traced it down to this line...
Call AuthAccountLogonProof(strReturn, strUsername, strPassword, strSalt, strPubKey)
Title: Re:the memory could not be "read"
Post by: Kp on September 18, 2004, 10:06 PM
Quote from: NetNX on September 18, 2004, 09:51 PM
yes but how would i go about correcting the problem...

ive traced it down to this line...
Call AuthAccountLogonProof(strReturn, strUsername, strPassword, strSalt, strPubKey)

Comment out that line.
Title: Re:the memory could not be "read"
Post by: SNiFFeR on September 18, 2004, 10:27 PM
Quote from: Kp on September 18, 2004, 10:06 PM
Quote from: NetNX on September 18, 2004, 09:51 PM
yes but how would i go about correcting the problem...

ive traced it down to this line...
Call AuthAccountLogonProof(strReturn, strUsername, strPassword, strSalt, strPubKey)

Comment out that line.

Dont use the .dll ?
Title: Re:the memory could not be "read"
Post by: NetNX on September 18, 2004, 11:32 PM
I deleted a declares modual and i realized i was using the variable Account instead of Username and it was causing the function to have an overflow error
Title: Re:the memory could not be "read"
Post by: Laff on September 19, 2004, 06:43 PM
that error could be caused by having a pointer pointing to garbage or by jumping the bounds of a variable into something you shouldn't be going into.  but stop asking questions about this junk (dll).
Title: Re:the memory could not be "read"
Post by: MyndFyre on September 20, 2004, 03:09 AM
Quote from: Laff on September 19, 2004, 06:43 PM
but stop asking questions about this junk (dll).

Hey -- mr. 11 posts -- you're not building very good rapport with the more senior members of this community by telling people how they should behave here.
Title: Re:the memory could not be "read"
Post by: Eibro on September 20, 2004, 06:50 AM
Quote from: MyndFyre on September 20, 2004, 03:09 AM
Quote from: Laff on September 19, 2004, 06:43 PM
but stop asking questions about this junk (dll).

Hey -- mr. 11 posts -- you're not building very good rapport with the more senior members of this community by telling people how they should behave here.
Eh? You do it all the time. I've been around here twice as long as you and you don't see me doing it.
Title: Re:the memory could not be "read"
Post by: dxoigmn on September 20, 2004, 06:42 PM
Quote from: Eibro[yL] on September 20, 2004, 06:50 AM
Eh? You do it all the time. I've been around here twice as long as you and you don't see me doing it.

Ditto.  For all we know, that could be some senior bot dev community member in disguise.
Title: Re:the memory could not be "read"
Post by: MyndFyre on September 20, 2004, 09:31 PM
Quote from: dxoigmn on September 20, 2004, 06:42 PM
For all we know, that could be some senior bot dev community member in disguise.

Well then he should be on his senior account if he's going to criticize people.  It'd be completely different if someone, say, $t0rm, criticized someone (in my eyes) than Laff, for two reasons.  1.) I have interacted with $t0rm extensively over IM and on the forums, and his reputation with me is that he generally knows what he's talking about and will actually *work* at a solution.  2.) He hasn't spat in my face when I try to offer helpful advice.

dxo, Eibro, I know the both of you, and while you both have my respect as seasoned vets, I am afraid that I have to disagree with you both on this instance.
Title: Re:the memory could not be "read"
Post by: iago on September 20, 2004, 10:24 PM
Yep, and it's all about what Myndfyre thinks. :)