Jump to content

><CHAIN><

Members
  • Posts

    115
  • Joined

  • Last visited

Everything posted by ><CHAIN><

  1. lol it was the solution to the problem you posted - so you're very welcome
  2. Sorry for yet another post but.... I have replicated your issue EXACTLY. I did this by telling my software firewall 'Zone Alarm Pro' not to allow GTASA.EXE to accept connections. This is a 'Program Permission' and ZA will typically throw this up when a new program tries to accept connections or if a n existing program's (.exe) checksum has changed. Just thought it was worth mentioning . Oh and the reason I never noticed the ASE ports in the list is becuas of the column width.
  3. If you stick your heatsink sensor right near the core, you dont get true heatsink temp I'm Assuming core temp - Athlons run hotter than Intel - 50c is ok under load... heatsink temps depend on heatsink and sensor location. Overclocked 'slightly' which I took as being the manufacturer default e.g. 203Mhz bus speed is default on most MSI boards that are advertised as 200Mhz (<2%) If it's any more than this then set to advertised speed and see if any difference. And as erorr404 said... Best of luck
  4. I've just experienced something LIKE your issue... When I opened the serverlist in MTA I saw the ports 22126 etc next to the server names whilst the list is still updating. Once it becomes idle, the ports change to the real ports e.g. 22003. And I could see server names also. I cant say that I noticed this before so maybe it's normal, but in your case it's not getting that far - let alone the server names not showing.... So I reckon some sort of connectivity issue is to blame for your symptoms. Using wireless by any chance?
  5. Could well be... but ATI graphics drivers are notorius for causing issues (particularyl if they have been updated (XP file protection can cause issues)). Here's a question then; Does it only crash when you can SEE the explosion? Or just hear it? Assuming we are suspecting the explosions lol (this sounds mad )
  6. I agree. ASE are providing the list to the client PC so it's gotta be something there. Rolling back to pre v1.1.1 should eliminate the issue. Could you try this just to be sure?
  7. Hmmm OK try a few things here. Plucking at straws I know but....: - Run DXDIAG.exe and see if any concerns are highlighted - DirectX up to date i.e. 9.0c? - Are sound card drivers up to date? - Run a disk check on all hard disks select "Automatically fix file system errors" (reboot will be required on C drive) Any better? Can you think of any pattern that links these random crashes?
  8. Sounds like you need to grant FILE permissions for the non-admin users. Do this to the installation folders of both GTASA and MTASA and ensure their respective sub-folders and files inherit these permissions. Please state if this fixes your issue as that runtime error has been experienced by other users and solution may help them also... thanx
  9. Turn off the port forwarding to see if the problem dissappears. Then you know for sure...
  10. Masteralex, close down unnecessary applications/processes to see if that solves your issue. Simple elimination which worked for dawpa2000
  11. You might want to press 'G' before you press ALT+E so you don't close the wrong process. This is assuming, of course, that you cannot see the task manager... and hopefuly you have no other processes with names that start with 'G'
  12. That no longer works for me in v1.1.1 (although I dont need it ) Just thought I'd mention. BTW vilim, your issue is in another post in this forum with a fix. try a search...
  13. Do a COMPLETE install of GTASA to hard disk. Sounds like you are running the radio stations from the DVD yes?
  14. I run D:\games\GTASA and D:\GTA\MTASA and all ok. It's always best to stick with alpha-numeric characters in folder names to avoid issues like yours
  15. also close down any other apps/processes/services. Anything scheduled to run periodically?
  16. You could turn off the option to 'Automatically Restart on 'System failure' to see if it is a BSOD which may show a clue (right-click My Computer>Properties>Advanced then click the 'Advanced' button from 'Startup and Recovery' and remove tick). Is your PC overclocked? Is temperature ok?
  17. Ok, firstly check your event log for any obvious issues: Right-click My Computer>Manage>Expand Event Logs from System Tools and check Application and System logs. Whilst you're there, also check Device Manager to ensure no hardware issues show. Has this always happened or is it a recent thing?
  18. Can you explain this a little more please? Also, try closing some other applications/services (assuming you haven't already) before running MTA, particularly VMware. Any difference?
  19. Wow that's lots of information, thanks! Are the drivers for these up to date? Has it EVER worked?
  20. hi, can you give the specification of your PC? Also, does this happen ONLY when playing MTASA or in other games also?
  21. So does anyone know if MTASA has worked on a laptop with an ATI graphics chipset? Also, I remember in a blog entry that there were some graphics issues with MTASA and ATI cards, although I'm not sure of the details. BTW quickest way to device manager = Right-click My Computer, select Manage and hey presto!
  22. Are you getting exactly the same symptoms as Jakk, LagKing II? Including this....
×
×
  • Create New...