24. BPAND DOESN'T WORK
  -------------------------------------------------------------------
  The BPAND command does not work for BPX type breakpoints. This
  includes F9 style point-and-shoot breakpoints. You must use a
  hardware type of breakpoint such as BPIO or BPM X.

  Also, the order in which the breakpoints are listed in the
  BPAND command is not significant; they do not have to occur in that
  specific order. The break will occur when all the breakpoints
  listed have occurred at least once.


  -------------------------------------------------------------------
  25. LOAD HI AREA IS NOT CLEARED ON WARM BOOT
  -------------------------------------------------------------------
  Problem: On CTRL-ALT-DEL the programs loaded high remain in place,
  so no space is available to load high.
  Solution: Erase the first 16 bytes of the 1st load high area. The
  program ZERO.SYS should be loaded immediately after Soft-ICE in the
  CONFIG.SYS file to do this automatically upon rebooting.

  -------------------------------------------------------------------
  26. COMPAQ ProSignia 486 WITH EISA SCSI DRIVE (VIRTUAL DMA)
  -------------------------------------------------------------------
  Problem: On bootup, displays a message that the current EMS memory
  manager does not support Virtual DMA.
  Solution: Load the driver SCSIC710.SYS in your CONFIG.SYS file.This
  driver is available on our BBS or from Compaq. The load syntax is
  as follows:

  DEVICE = [drive:][path]SCSIC710.SYS [/N] [/D]

  PARAMETERS:

  /N   This parameter directs SCSIC710 not to display on-screen
	   messages.

  /D   This parameter forces SCSIC710 to always use double
	   buffering.

  NOTE:  When using this driver in conjunction with Compaq's
  EXTDISK.SYS, EXTDISK must be loaded first.

  -------------------------------------------------------------------
  27. USING SOFT-ICE WITH AN ADAPTEK SCSI DRIVE
  -------------------------------------------------------------------
  When using Soft-ICE with an Adaptek SCSI drive, the SCSI driver
  ASPI4DOS.SYS must be loaded before S-ICE.EXE in the CONFIG.SYS.
  The user reporting this also had FUNNEL.SYS and UMB.SYS installed,
  and was able to load all his driver and T&SR's high.

  -------------------------------------------------------------------
  28. MIXED BC/SI SCREEN OR BPM ON STACK DOESN'T WORK
  -------------------------------------------------------------------
  Problem: Mixed BC/SI screen, or BPM that doesn't catch a change
  on the stack.
  Solution: This can occur when a stack is outside the program
  space and Bounds-Checker is being run with Soft-ICE. If a CALL is
  made, a Page Fault occurs when the return address is written to the
  stack, and it overwrites the return address. Also, if there is a
  breakpoint on a PUSH instruction, before the Bounds-Checker screen
  is completely written, it is overwritten by the Soft-ICE screen.
  One way to identify this type of problem is that it won't happen if
  Soft-ICE is single-stepped.
  The only cure is to change to a stack within the program space.

  -------------------------------------------------------------------
  29. USING FOREIGN KEYBOARDS
  -------------------------------------------------------------------
   Soft-ICE supports only the US keyboard: however, in some cases
  it is possible to patch it to allow using foreign keyboards.
  To simplify this process, we have written a program to replace
  the keycode table with a file containing another table, plus a
  document describing how to make such a keycode table file. It is on
  our BBS under the name KEYBOARD.ZIP, and on CompuServe under the 
  name KEYBOA.ZIP. It includes a example for the German keyboard.

  -------------------------------------------------------------------
  30. DEBUGGING DOS-EXTENDED OR PROTECTED MODE PROGRAMS
  -------------------------------------------------------------------
  Problem: Soft-ICE GPFs when trying to debug a DOS-EXTENDED program
  or a protected mode program.
  Solution: There is no workaround for this. Soft-ICE is a protected-
  mode program and cannot be run with other protected-mode programs.

  -------------------------------------------------------------------
  31. SOFT-ICE REBOOTS 
  -------------------------------------------------------------------
  Problem:  System reboots when you install Soft-ICE. 
  Solution: There are several reasons why Soft-ICE may reboot your 
  system. They are:

  1.) Failure to run EMMSETUP on S-ICE.EXE
  2.) Having POWER.EXE in config.sys on low power systems 
  3.) Installing HIGHMEM.SYS before S-ICE.EXE in config.sys
  4.) If reboot is occuring on a BPM (R) with Soft-ICE 2.60-2.62,
  see item #55
  5.) If running on a PENTIUM with Soft-ICE ver 2.61 or less, see
  item #59 in this document.
  6.) If running on a COMPAQ with Soft-ICE ver 2.61 or less, see
  item #60 in this document.
  7.) It has been reported that some systems with CYREX cpu's reboot.
  There is no known fix for this problem.
  8.) Many 486 systems will reboot if you attempt to run S-ICE.EXE
  from the DOS command line. The cause is unknown. There is  
  currently no fix for this problem.
  9.) On certain older COMPAQ models the following patch is needed
  to run with Soft-ICE 2.62 and greater:
 
   Patch Soft-ICE as follows
   ren s-ice.exe s-ice.bin
   debug s-ice.bin
   -s 0 lffff 'XOM'
   (prints out an address in xxxx:yyyy format. Offset should be 17B3)
   -e xxxx:(offset - 2) 30 33 43
   -w
   -q
   ren s-ice.bin s-ice.exe
  
  -------------------------------------------------------------------
  32. INVALID OP-CODE REPORTED BY Soft-ICE
  -------------------------------------------------------------------
  Problem: An INVALID OP-CODE is reported by Soft-ICE.
  Solution: The following things can cause INVALID OP-CODE ERRORS:
   1.) Failure to run EMMSETUP on S-ICE.EXE before installing
   2.) Running with SMARTDRIVE or another DISK CACHING program  
   3.) If Borland compiler, put /EMM 500 in S-ICE.EXE line of 
	  CONFIG.SYS.

  -------------------------------------------------------------------
  33. GP FAULT REPORTED BY Soft-ICE 
  -------------------------------------------------------------------
  Problem: A GP fault is reported by Soft-ICE.
  Solution: The following things can cause G.P. Faults:        
   1.) Failure to run EMMSETUP on S-ICE.EXE before installing
   2.) Running with another Memory Manager (HIGHMEM.SYS is ok)    
   3.) Running with SMARTDRIVE or another DISK CACHING program  
   4.) Running Soft-ICE versions prior to 2.5 under DOS 6.x

  -------------------------------------------------------------------
  34. GP FAULT WHILE LOADING MSC 7/8 PROGRAM
  -------------------------------------------------------------------
  Problem: A GP fault occurs while loading a MSC 7/8 (Visual C)
   program. The DI register is FFFF and the IP register is A99C.
  Solution: This occurs when a module compiled with debug data
   has no line number information. The code which processes line 
   number information does not have a check for a count of zero, so it
   handles it as if the count were 64K. The following patch inserts a 
   check for zero into the code.

  Patch LDR.EXE as follows:

	ren ldr.exe ldr.bin
	debug ldr.bin
	-s 0 lffff 0f 84 11 00 53
	(displays address)
	-e address     74 11 53 26 8b 04 bb 06 00 f7 e3 8b d8 2e 8b 97
	-e address+10  ce 09 5b 83 c6 04 83 c3 04 e3 1a
	-w
	-q
	ren ldr.bin ldr.exe

  -------------------------------------------------------------------
  35. BOUNDS-CHECKER "STACK" GIVES GP FAULT WHEN SOFT-ICE IS LOADED
  -------------------------------------------------------------------
  Problem: A GP fault occurs from doing a STACK command in Bounds-
   Checker while Soft-ICE is loaded. The IP for the code displayed is
   0000, and the ESI register has FFFF in the upper word.
  Solution: When Soft-ICE is loaded, Bounds-Checker minimizes its
   memory requirements by using some of the Soft-ICE routines. Some of
   these routines put an FFFF in the upper word of the EBX register
   when Bounds-Checker expects it to be 0000. EBX is later added to 
   ESI, and when ESI is subsequently used as a pointer, the invalid
   address it contains causes a GP fault. This can be corrected by 
   zeroing the upper word of EBX with a MOVZX EBX,BX instruction.

  Patch S-ICE.EXE as follows:

	ren s-ice.exe s-ice.bin
	debug s-ice.bin
	-s 0 lffff 66 03 f3 26 67 8b 06
	(displays address)
	-e address     66 0f b7 db 66 03 f3 26 67 8b 06 80 f9 01 74 07
	-e address+10  80 f9 02 74 1f
	-w
	-q
	ren s-ice.bin s-ice.exe
  
  -------------------------------------------------------------------
  36. USING WITH CODEVIEW 4.0
  -------------------------------------------------------------------
  CODEVIEW 4.0 that comes with Microsoft C-7 and C-8 is a protected
  mode program and cannot be run with Soft-ICE for DOS.

  -------------------------------------------------------------------
  37. RUNNING IN A DOS BOX
  -------------------------------------------------------------------
  Soft-ICE for DOS cannot be used to debug an application that is    
  running in a Windows DOS box. Use Soft-ICE for windows instead.
  
  -------------------------------------------------------------------
  38. TRYING TO DISPLAY FLOATING POINT NUMBERS
  -------------------------------------------------------------------
  Floating point numbers cannot be displayed by Soft-ICE for DOS.

  -------------------------------------------------------------------
  39. RUNNING OUT OF MEMORY WITH BORLAND 4.0 IDE
  -------------------------------------------------------------------
  If you are out of memory running with the Borland 4.0 IDE try 
  increasing the value of the /EMM switch on the S-ICE.EXE line in 
  CONFIG.SYS.
  
  -------------------------------------------------------------------
  40. HOT KEY FAILS TO POP UP Soft-ICE
  -------------------------------------------------------------------
  Problem: Keying the hot key sequence fails to pop up Soft-ICE 
  screen.
  Solution: Turn on the BREAK option from the Soft-ICE command line.
  This should prevent the keyboard from being disabled and allow you
  to pop up the SI window at any time. This option will make your
  program run somewhat slower.
  
  -------------------------------------------------------------------
  41. USING MEMORY ABOVE 16 MEG
  -------------------------------------------------------------------
  You cannot use Soft-ICE for DOS with memory above 16 meg. Soft-ICE
  loads itself at the top of the first 16 meg and fools DOS into 
  thinking that is all there is.
  
  -------------------------------------------------------------------
  42. "NO HIGH MEMORY AVAILABLE" MESSAGE 
  -------------------------------------------------------------------
  This usually means you have allocated to much memory with the /EMM,
  /EXT or the /SYM switches on the S-ICE.EXE line in CONFIG.SYS.
  
  -------------------------------------------------------------------
  43. "CAN'T FIND S-ICE.EXE" MESSAGE WHEN RUNNING UPDATESI.EXE
  -------------------------------------------------------------------
  This occurs when you are trying to update Soft-ICE to a newer 
  version using updatesi.exe. Check your path to current S-ICE.EXE.
  Make sure it is not on a DOS 6.x compressed volume. If it is the
  update program will not be able to find it.

  -------------------------------------------------------------------
  44. USING WITH OVERLAYED PROGRAMS
  -------------------------------------------------------------------
  Soft-ICE works very well with older Microsoft overlay managers. It 
  does not work with Microsoft MOVE or Borland VROOM. RTLink has 
  caused many problems in the past that will be addressed in the 2.7 
  release of Soft-ICE.
  
  -------------------------------------------------------------------
  45. USING WITH SPAWNED PROGRAMS
  -------------------------------------------------------------------
  Soft-ICE for DOS allows for the loading of two symbol tables.
  See the TABLE command in the Addendum to the manual for details.
  
  -------------------------------------------------------------------
  46. LOADING DOUBLESPACE HIGH
  -------------------------------------------------------------------
  DOUBLESPACE cannot be loaded with with Nu-Mega's LD.SYS. You should
  use UMB.SYS with LOADHIGH commands.
  
  -------------------------------------------------------------------
  47. "Error Loading A Source File"
  -------------------------------------------------------------------
  Problem: This message appears when loading a program with LDR
  Solution: The following are reasons for this message
	* Path to the source files is too long.  Max 40 characters
	* File is somehow protected by DOS
	* File has been packed by something other than CV-PACK
	* File has been written on a UNIX style editor that puts
	  only line feeds at the end of lines instead of
	  carriage return - line feed

  ------------------------------------------------------------------
  48. FAULT WHILE TRYING TO DISPLAY A GLOBAL SYMBOL
  ------------------------------------------------------------------

  Problem : Soft-ICE blows up when trying to display a global symbol
	  Version 2.7 only
  Solution : Patch S-ice.exe as follows:

	ren s-ice.exe s-ice.bin
	debug s-ice.bin
	-r
	-s cs+1000:0 lffff 01 74 28
	 ( prints out an address in xxxx:yyyy format )
	-e xxxx:yyyy 02
	-w
	-q
	ren s-ice.bin s-ice.exe

  -----------------------------------------------------------------
  49. ALTSCR DOES NOT WORK IN VERSION 2.7
  -----------------------------------------------------------------
  Problem: ALTSCR command does not work in version 2.7
  Solution: Patch S-ICE.EXE as follows:
	
	ren s-ice.exe s-ice.bin
	debug s-ice.bin
	-r
	-s cs+1000:0 lffff 80 3E 14 78
	( Prints out two addresses in xxxx:yyyy format )
	-e xxxx:yyyy C7 06 C8 99 28 00 90
	( Use the first address printed )
	-e xxxx:yyyy C7 06 C8 99 30 00 90
	( Use the second address printed )
	-w
	-q
	ren s-ice.bin s-ice.exe

  -----------------------------------------------------------------
  50. GPF ON PUSH FD OR POP FD ( using back door command/BREAK ON )
  _________________________________________________________________

  Problem: A GPF occurs in SI on a PUSH FD or POP FD instruction.
  Solution: Patch S-ICE.EXE as follows

	ren s-ice.exe s-ice.bin
	debug s-ice.bin
	-s 0 lffff 0F 85 EA FA
	  ( prints out an address in xxxx:yyyy fashion )
	-e xxxx:yyyy 0F 85 09 FB
	-w
	-q
	ren s-ice.bin s-ice.exe

  -------------------------------------------------------------------
  51. LDR OF TSR CAUSES A BLOW UP THE NEXT TIME THE TSR IS RUN
  -------------------------------------------------------------------
  Problem: This problem was shown when a guy loaded a TSR into Soft
  ICE, then did an EXIT, then ran the TSR again which caused a fault
  inside of Soft-ICE. It was narrowed down to the fact that Soft-ICE
  was using the ECX register but had never zeroed the high half.
  
  Solution:  Patch S-ICE.EXE as follows:

	ren s-ice.exe s-ice.bin
	debug s-ice.bin
	-s 0 lffff 8A 0E 41 0D FE C1 B5 00 F3
		( prints out address in xxxx:yyyy format )