Solving Problems 209Typically, your operating system's start-up files (such as config.sys andautoexec.bat) contain commands to start TSR programs when you bootyour computer. If you suspect that one of these TSR programs is causing amemory conflict, remove the commands that start them from the start-upfiles. If the problem you were experiencing does not recur, one of the TSRprograms probably created the conflict. Add the TSR commands back intothe start-up files one at a time until you identify which TSR program iscreating the conflict.Program ConflictsSome programs may leave portions of their setup information behind, eventhough you have exited from them. As a result, other programs cannot run.Rebooting your computer can confirm whether or not these programs arethe cause of the problem.Memory Address ConflictsMemory address conflicts occur when two or more devices try to access thesame address in the upper memory blocks (UMB). For example, if a networkexpansion card and an expanded-memory page frame are assigned anoverlapping block of addresses, a memory address conflict arises. As a result,when you try to log in to the network, the operation fails.To resolve this type of conflict, you can change the address of one of thedevices. For example, in the case of the network expansion card andexpanded-memory page frame address conflict, you can move the networkcard to an address block in the range of CC000h through D0000h. Toreassign the expansion card's address block, see the documentation for thecard.Interrupt Assignment ConflictsProblems can arise if two devices attempt to use the same interrupt request(IRQ) line. To avoid this type of conflict, check the documentation for thedefault IRQ-line setting for each installed expansion card, then consult thefollowing table to configure the card for one of the available IRQ lines.