Jump to content

freeze

Members
  • Content Count

    15
  • Joined

  • Last visited

Community Reputation

0 Neutral

About freeze

  • Rank
    Square

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. whats the point of this poll? its meaningless. the true question has to be asked to developpers: are they going to debug their mod on win98 as ppl has been waiting for, yes or no?
  2. to developpers: maybe you'll find the solutions if you would take the time to DEBUG on a win 98 box! i remind you most of gta players use win98 and still you release stuff that only a minority can run..its totally non-sense. see what happens when its not open source...at least give the code to somebody of your team that have win98 so he can debug it on that platform..............we are really fed up waiting for *one* of your mods to work
  3. again they did it... I thought with the MANY complains concerning mta 0.3b and the fact that ppl cant play on win98, they were going to be serious and solve the pb with mta vc. no. again, a majority of gta gamers use win98 and again they are denied to run this mod. do the creators really care about the gta communauty? i start wondering...
  4. thanx for adressing my concerns..we'll judge with time. I only hope that now you have a plethora of team members, you'll release betas more often and more importantly test b4 your mod on all platforms (win9x,2k,xp) so that we all can "try" to play some mta. good luck
  5. i understand the benefits for te mta team of merging. mta 0.3b is slow as hell, full of bugs, bandwith hog, progged in vb, and even doesnt work on win9x/Me. so merging can only be profitable for them, especially since Yamm team seems to be capable C++ developpers and advanced very quickly in their development. so i wonder why yamm decided to join mta. whats their benefit, apart sponsoring, a forum and some publicity that mta name has? whats the point of porting mta stuff to C++ since it doesnt even work and when it does its lags like hell? why not letting the yamm team follow their design
  6. this is not a "glitch". this is a play stopping bug in the sense that the connexion to the server is cut when you try to play , as i already explained long ago. basically, owners of win98, win98se, and prolly winME, are enjoying SingleTheftAuto, not MULTI theft auto. time to debug the app on those operating system guyz. i already gave a diagnosis of what the pb is. hope its being worked out, as for now we're getting..hmm..BORED.
  7. seems all ppl who have win98/winme share the same pb as i described. please fix this as we cant play any mta for now.
  8. ppl who have win98 experience a disconnection pb when playing: 1) once the game joined and the team chosen, we see strange stuff for 1 second (car flying in the air etc) then everything goes dead and you play like if you're alone. 2) alt-tabbing to the console we notice that the line "D/L rate:xx" is stuck. that means the exchange of data is cut. 3) disconnecting and connecting again doesnt solve the problem. it goes back to situation described in 1) we notice that outgame chat is possible if we havnt switched back to the game yet. once we alt tab to the game to play, and alt tab back agai
  9. bloker you obviously chose to ignore my numerous contributions concerning the error 126. i explained what is the cause of that error clearly and i even gave a very simple solution. but again that means adding few lines of code in the console and maybe building up the setup again. if that bothers you and prefer to leave win98 ppl to their fate till mta 0.4, then say it, but dont lie by saying "for the moment we have no idea what causes these 2 problems, therefore, whe have no solution".
  10. 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.Descr
  11. 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.Descr
  12. freeze

    Error

    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
  13. freeze

    Error

    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.
  14. freeze

    Error

    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.
  15. freeze

    Error

    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.
×
×
  • Create New...