Difference between revisions of "Troubleshooting FAQ"

Revision as of 04:15, 29 June 2007

let the copying and pasting... begin!

This FAQ is for technical problems and will only apply to users of the most updated version of Worms Armageddon, or users either trying to update to this version, trying to install WA or trying to access WormNET.

Crashes

I get a black screen when I try to run WA, then it crashes to desktop or I have to restart the computer

Disabling the introduction screens has been known to solve this. To do this, right-click the WA shortcut icon, select properties, and in the "Target" text box, type:

/nointro

This must be outside of the quotation marks for it to work. For example,

"C:\Worms Armageddon\wa.exe" /nointro

If you have the Trymedia version of the game, and the problem persists, one possible cause is "Ultra VNC's video hook" drivers. Open the Device Manager (Right-click My Computer, select Properties, then the Device Manager tab), find the drivers, and disable them. See here for discussion of this.

WA crashes when I try to edit the map

This is caused by having a program with an "Always On Top" feature. MSN Messenger is a common culprit. Try closing other programs, or finding this setting and disabling it.

WA crashes when I try to edit or create a team

This can be caused by having a custom grave or flag with incorrect colours or dimensions, or having a program with an "All On Top" feature. Try removing all custom flags and graves, and closing other programs, or finding this setting on other programs and disabling it.

WA crashes after the title menu

This can be caused by "DirectVobSub" in the Nimo DivX Codec pack. Uninstall the Nimo DivX Codec pack and it should work. You can reinstall it and manually unselect "DirectVobSub" to get WA to work with Nimo installed.

WA crashes when I minimise and then try to maximise

Minimising is not yet stable; WA will always be prone to crashing until this is optimised.

Blue Screen Of Death occurs when I finish single player games, exit WormNET or host an online game

No solution.

My computer crashes to desktop, or restarts, when I finish or exit any game

Making an ISO of the WA CD and using a virtual drive has been known to solve this.

WA crashes when I try to play a game of any sort

Usually caused by improperly updating the game - follow the tutorial carefully. This is also caused by graphics cards that are too new, such as NVIDIA 8800GTS. WA will eventually be able to run on these cards. Until then, either consider downgrading your graphics card or, for NVIDIA 8800GTS, downloading this fix which has been known to work for some people. See this thread on the Team17 forums for details.

Running WA

I can't see the bottom or right side of the screen in the front end

Your font sizes are incorrect. Find your computer's display properties panel and set font sizes to "Normal" (96dpi)

"C:\WINDOWS\SYSTEM32\AUTOEXEC.NT. The system file is not suitable for running MS-DOS and Microsoft Windows applications. Choose "Close" to terminate the application."

In your Start Menu click "Run...", type "cmd" and click OK. In the black prompt box that pops up, type:

copy c:\windows\repair\autoexec.nt c:\windows\system32

If this doesn't work, you can perform the same task manually. Navigate to

c:\windows\repair\

and copy the file "autoexec.nt" to your clipboard. Then navigate to

c:\windows\system32

and paste the file there.

"C:\WINNT\SYSTEM32\AUTOEXEC.NT. The system file is not suitable for running MS-DOS and Microsoft Windows applications. Choose "Close" to terminate the application."

In your Start Menu click "Run...", type "cmd" and click OK. In the black prompt box that pops up, type:

 copy c:\winnt\repair\autoexec.nt c:\winnt\system32

If this doesn't work, you can perform the same task manually. Navigate to

 c:\winnt\repair\

and copy the file "autoexec.nt" to your clipboard. Then navigate to

 c:\winnt\system32

and paste the file there.

I get a "No CD" Error

You probably tried to patch WA when it did not need patching. Uninstall the game and try installing only the update.

"ltkrn10n.dll was not found"

You must install the patch before you install the update. Uninstall the game and install the patch first, then the update.

"The instruction "0x5cb7603a" referenced memory at "0x00483fe2". The memory could not be "read""

You probably forgot to install the update. Try installing the update. You may need to reinstall the game.

When trying to run the game, the Sold Out installation setup sometimes insists that I install the update, even when I have already done so

Ignore the message.

The frontend and menu system suffers flickiness, lacks background sound, messed up animations, or unusually slow/fast animations

Locate your WA directory and doubleclick the file "SlowFrontEndWorkAround_On.reg". If this doesn't solve the problem, do the same with "SlowFrontEndWorkAround_Off.reg". If neither of these work, your videocard is too modern. These problems will be fixed in a future update. See this thread for more details.

Right-clicking in-game fails to open the weapons menu

The program StrokeIt can be responsible for this. Either disable the program when playing, or find the program option that allows you to prevent it from interfering when WA is running.

In-game plays extremely slow on Windows Vista

If you're using a Nvidia graphics card, updating to the latest beta drivers has been known to fix this issue. Currently these are 160.03 32-bit and 160.03 64-bit.

Patching/updating WA

When installing the 3.0 patch, why do I get the error "Failed to find installation path" ?

This is caused by the Registry entries created by the WA installer. This can be solved by reinstalling, or editing the registry entries as follows:

1. Start menu > Run > Regedit
2. Navigate to "HKEY_CURRENT_USER\Software\Team17SoftwareLTD\WormsArmageddon\"
3. Double-click the PATH string and make sure the directory location is correct

Why do I get a "Bad Integrity" error when trying to run the Patch or Update file?

The file is corrupted. Try deleting it and downloading it again.

Installing WA

I can't install Worms Armageddon. The auto-run installation screen disappears, and nothing else will work.

Disabling DMA (Direct Memory Access) has been known to solve this. To disable DMA,

1. Start Menu > Control Panel > System
2. Click the Hardware tab, then click Device Manager
3. Expand the System Devices sublist
4. Double-click "Direct memory access controller"
5. Select "disable" from the Device Usage drop-down list

The installation freezes at 100%, and the game fails to install when I quit it.

Keep waiting, the installation will eventually complete after a few minutes. Cause of this problem is unknown.

WormNET

I get the error "Unable to find IPX protocol"

1. Start Menu > Control Panel > Network Connections
2. Right click your connection and select Properties
3. Select "Internet Protocol" from the list, then click "Install"
4. Select "Protocol" and click "Add..."
5. Select "IPX/SPX/Netbios" and click "Okay"

When I try to connect to WormNET, the game freezes up

ZoneAlarm can cause this by producing a pop-up in the background when it detects your computer trying to connect. Configure ZoneAlarm so that it already allows access to WormNET.

When I try to connect to WormNET, nothing happens

PeerGaurdian can cause this by blocking the WormNET IP address. Consider reconfiguring or disabling PeerGaurdian.

When I join WormNET, the content of the channel list, player list and the message of the day box never loads

In my experience, you'll need to quit and restart the game to solve this. If it still happens, you may need to restart the computer.

When I try to join games, I keep getting a "Checksum 15" error

This occurs when the game has been improperly updated. Follow the installation tutorial carefully.

When I host a color map the other players get an error saying: "PNG error: Invalid distance too far back" and the map doesn't load for them

This is thought to be caused by firewall software that is interfering with outgoing data. Contact your network administrator.

I keep experiencing desynchronisation issues when using the pre-made maps

Cause of this problem is unknown, but reinstallation has been known to solve it.