Jump to content

Error


Guest jozu

Recommended Posts

Posted

I follow the steps to play mta, but the client SAy "Run-time error 126", plz helpme!!!!! :?:

Posted (edited)

i have the same bloody error

i installed MTA

i configured ASE and choose a not full server

it starts the mta console in the right window it says:

welcome to mta

version 0.3a

connecting to server

waiting for request

and BAM! an error box appears: GTA3MTA: Runtime error '126'

im on win98SE

PS:and yes you can find what correspond to that error if youre a developper. its a microsoft code error so it has some description and meaning. just add error trapping code to your app.

i think (im a developper too) that this error happens when the socket tries to send data for the first time.

Edited by Guest
  • MTA Team
Posted

one the box that says run time error there should be more information. if you can, make a screenshot of the error box or from you entire desktop cause this isn't helping me

Posted

this error box doesnt have a descrpition. it just says run-time error '126'.

see my previous post to see when it happens.

i think this error is related to the winsock control. it occurs when the socket tries to send data for the first time.

Posted

I've got the same error :(

Using win98se too

gta.jpg

Posted

after some research, i found that this bug is related to winsock control and WIN98, which i already was suspecting. it happens when it tries to send data with an UDP connection THE FIRST TIME. the data is actually sent but the ocx somewhat fucks up. after that, the future sends work without error.

to fix this i suggest using a second Winsock control, and set up a dummy TCP connection locally first, then switch to UDP.

Posted (edited)

bloker, installing vb runtimes doesnt fix the pb.

as i mentioned this error is related to winsock control ,udp, and win98.

you have to implement error trapping in the console application so it actually IGNORES that specific error, since data is actually sent.

for example, if youre using vb, do this:

'Ignore error 126 which sometimes occurs

On Error GoTo ErrorHandler

socket1.SendData "blablabla" 'if socket1 is your winsock control name

Exit Sub

ErrorHandler:

'all error except 126 will raise a msg. if its error 126 ignore it.

If Err.Number <> 126 Then

MsgBox Err.Description, vbCritical, Err.Number

End If

Resume Next

Edited by Guest
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...