Eagle, EBFD should run on your system without a doubt !
About the error messages (I assume it only happens while playing EBFD ?)..
1) Check your BIOS settings for anything incorrect (your RAM speed for example). Check the manual for your motherboard for detailed explanation on the settings.
2) Update your BIOS.
3) Try to run the game with the option -s behind the games shortcut.
4) If you have any Norton programs installed, please uninstall and try to run the game again.
More explanation on the error message and how to retrieve more information:
The description and format of the event log differs from the format that is displayed when the computer is writing the Memory.dmp file, but the majority of the information is the same. Below is an example of the event log:
Event ID: 1001
Source: Save Dump
Description:
The computer has rebooted from a bugcheck. The bugcheck was : 0xc000021a (0xe1270188, 0x00000001, 0x00000000, 0x00000000).
Microsoft Windows NT (v15.1381). A dump was saved in: C:WINNTMEMORY.DMP.
This information contains the stop code 0xc000021a and the four parameters. These can be very useful when troubleshooting certain types of stop codes. The parameters will mean different things depending on what type of stop code it is.
If you use Dumpchk.exe from the Service Pack 3 CD, you can determine all of the above information as well as the address of the driver that generated the stop message. This information can often give you a direction to begin troubleshooting. Before you run Dumpchk.exe, be sure to adjust the properties of the command prompt so that the screen buffer size height is set to 999.
This height will allow you to scroll back to see the output. Run Dumpchk.exe from the command prompt with the following syntax:
dumpchk.exe Memory.dmp
This is an example of the portions of the output that are most useful:
MachineImageType i386
NumberProcessors 1
BugCheckCode 0xc000021a
BugCheckParameter1 0xe1270188
BugCheckParameter2 0x00000001
BugCheckParameter3 0x00000000
BugCheckParameter4 0x00000000
ExceptionCode 0x80000003
ExceptionFlags 0x00000001
ExceptionAddress 0x8014fb84
Note that not all sections will give the same information. This will depend on the type of stop code. The information above tells you the stop code (0xc000021a) and the parameters (0xe1270188, 0x00000001, 0x00000000, 0x00000000), as well as the address of the driver that called the exception (0x8014fb84). This address can be used to identify the driver name by using the output from running Pstat.exe, which can be found in the Resource Kit. Dumpchk.exe will also verify that the dump is valid.
Pstat.exe, a Resource Kit utility, will give you a picture of the processes and drivers currently running on your system. For these purposes, the most useful information will be the list of loaded drivers that appears at the end of the output. All you need to do is run Pstat.exe from the command line. The information given by Pstat.exe can be piped to a file by using the following syntax:
pstat.exe > filename
This is an example of the driver list at the end of the output (hope it comes out right):
ModuleName Load Addr Code Data Paged LinkDate
----------------------------------------------------------------------
ntoskrnl.exe 80100000 270272 40064 434816 Sun May 11 00:10:39 1997
hal.dll 80010000 20384 2720 9344 Mon Mar 10 16:39:20 1997
aic78xx.sys 80001000 20512 2272 0 Sat Apr 05 21:16:21 1997
SCSIPORT.SYS 801d7000 9824 32 15552 Mon Mar 10 16:42:27 1997
Disk.sys 80008000 3328 0 7072 Thu Apr24 22:27:46 1997
CLASS2.SYS 8000c000 7040 0 1632 Thu Apr 24 22:23:43 1997
INO_FLPY.SYS 801df000 9152 1472 2080 Tue May 26 18:21:40 1998
Ntfs.sys 801e3000 68160 5408 269632 Thu Apr 17 22:02:31 1997
Floppy.SYS f7290000 1088 672 7968 Wed Jul 17 00:31:09 1996
Cdrom.SYS f72a0000 12608 32 3072 Wed Jul 17 00:31:29 1996
Cdaudio.SYS f72b8000 960 0 14912 Mon Mar 17 18:21:15 1997
Null.SYS f75c9000 0 0 288 Wed Jul 17 00:31:21 1996
KSecDD.SYS f7464000 1280 224 3456 Wed Jul 17 20:34:19 1996
By using the starting address shown above under the "load addr" column, you can match the exception address to the driver name. Using 8014fb84 as an example, you can determine that Ntoskrnl.exe has the nearest load address below the exception address and is most likely the driver that called the exception.
"Doc" Nyar...
