Error lists

voting has never bin easier, just click , and it's done .thanx !

most common pagefaults , taken from The Helpers msg to the Forum :)

I just wanted to share some advice for everyone out there that helps users with page faults. I have noticed that the standard answer to page fault questions have been referred to WARGASM's site. It is true that site has some good information about page faults, but it is not the most common fix for them. You should send them to Wargy's site if they still have problems after they do this.

This procedure usually only works if the page fault error was in Diablo.exe

Restart computer

ctrl+alt+del and end task on all programs except for Explorer and Systray

Uninstall Battle.net from My Computer - Control Panel - Add/Remove programs - Battle.net then remove.

Go to your Diablo folder and make sure the bncache.dat file is gone, if it is not, delete it.

Delete the contents of the Windows\Temp folder

do a scandisk on the hard drive and correct any errors, do a full defragment on your hard drive.

Try again.

If the page fault was in MPREX they need to get the password update from the FAQ at the top of the forum.

If the page fault was in Kernel then they need to download the kernel update from the FAQ at the top of the forum

If the page faults continue after they have done the above advice then its time to send them to Wargy's site.

Hell, just send them to Wargy's site anyway, I like watching his hit counter rise :) The Helper

The above info was added on 082697

If The Helpers suggestions didn't work, it's time for Loralon do help u out !! :)

a few tips!!

and some more info

INVALID PAGE FAULTS (revision 1.0)

This section contains some possible solutions to the dreaded "invalid page fault in module: ...." error that I was also unfortunate enough to experience when I first tried to play Diablo. I hope this helps :)

VIRTUAL MEMORY

First and foremost make sure that you have enough hard disk space set aside for your Windows Virtual memory. To check:

- right-click on "My Computer" Icon on your desktop - click on "Properties" - click on the "Performance" Tab - click on the "Virtual Memory" Button

First and foremost make sure that your virtual memory is NOT disabled. Now verify that you have at least 50 MB free on the drive that contains your swap file (ie virtual memory). If you can spare the room, 100 MB or more would be preferable and a safe number for me to suggest. To do this, you may be forced to either delete existing software on the drive which currently contains the swap file or move the swap file to a drive with more space. Well worth it to play Diablo crash-free if you ask me.

Invalid Page Faults

INVALID PAGE FAULTS (revision 1.1)

This section contains some possible solutions to the dreaded "invalid page fault in module: ...." error that I was also unfortunate enough to experience when I first tried to play Diablo. I hope this helps :) ------------------------------------------------------------------------

First and foremost make sure that you have enough hard disk space set aside for your Windows virtual memory. To check:

- right-click on "My Computer" Icon on your desktop

- click on "Properties"

- click on the "Performance" Tab

- click on the "Virtual Memory" Button

Make sure that your virtual memory is NOT disabled. Now verify that you have at least 50 MB free on the drive that contains your swap file (ie virtual memory). If you can spare the room, 100 MB or more would be preferable and a safe number for me to suggest. To do this, you may be forced to either delete existing software on the drive which currently contains the swap file or move the swap file to a drive with more space. Well worth it to play Diablo crash-free if you ask me.

I would also recommend that you start Diablo after a clean boot (ie don't start any other programs before you start Diablo) and if you're still having trouble make sure that Diablo, systray and explorer are the only active programs. You can find out what programs are active by hitting alt + ctrl + del ONCE. Running any more programs than necessary will take more of your computer's virtual memory away from Diablo. ------------------------------------------------------------------------

Make sure that you have the latest updates to Windows 95. To check:

- right-click on "My Computer" Icon on your desktop

- click on "Properties"

You should see something like 4.00.950, 4.00.950a, or 4.00.950b under "system". If you still only have 4.00.950, then you should go to Microsoft and install Service Pack #1. If you already have 4.00.950a, then there should be an accessable folder called "update information tool" that can be found as follows:

- click on "Start" on the taskbar

- move to "Programs"

- move to "Accessories"

- move to "System Tools"

Check this list against Microsoft's List to see if you are missing any of the updates, particularly the Kernal32 update. If you are missing any of the core updates such as the Win32 Kernal, OLE 32, or DiskTSD virtual device then you should download and install them now.

Also make sure that you have the latest Win 95 drivers for your sound card and graphics card. Contact the particular manufacturer's website for the latest drivers. To double-check I'd also recommend that you reinstall the latest drivers just to make sure that they are properly installed. ------------------------------------------------------------------------

If you already have sufficient space on your hard drive as well as all the updated Win 95 files and drivers and are still experiencing invalid page faults then you should try the following step next:

- goto the "Performance" Tab

- click on the "Graphics" Button

Check the placement of the slider. If the slider is not already at the far left, then move the slider back one step and try to run Diablo afterwards. This process will disable certain functions of your graphics accelerator, functions which may be interferring with the stability of your system. If Diablo continues to be unstable then you should continue as necessary until only the "basic functions" are the only ones available to your graphics card. Hopefully it won't be necessary to disable all but the most basic functions to gain more stability, but it may be necessary on certain systems. ------------------------------------------------------------------------

WARNING: ANY CHANGES OTHER THAN THE ONES I HAVE OUTLINED BELOW ARE DISCOURAGED!!!!!!

If these suggestions haven't worked yet, then you're in for a some more serious tinkering. First try disabling any shadowing and/or caching of your video BIOS. To do this, you will need to gain access to your system BIOS. If you are not sure how to access your BIOS, then edit msdos.sys to include the line logo = 0 in the [options] section. This will remove the windows startup logo and reveal the DOS bootup, including the key necessary to access your BIOS. Note that you may need to cold boot (turn off and then turn back on the computer) or hard boot (hit the "reset" button) to see this key and the entire POST.

If that doesn't do it, then I'd recommend disabling any shadowing and/or caching of your system BIOS in addition to that of the video BIOS as your next step.

If the previous two suggestions have failed to solve your problems, then I'd recommend less aggressive memory timings as a next step. DO NOT make the memory timings MORE aggressive than they already are. Of course this assumes that these can be accessed via the BIOS, which may or may not be the case with your particular system. For more information on memory timing and general BIOS information take a look at Tom's Hardware Site. ------------------------------------------------------------------------

If all this tinkering with the software hasn't done it yet, then it's finally time to open up your computer. Check to see if you are using more than one type of SIMM. Even if the size, speed, and parity are identical on the modules, they may not be entirely compatible if they were produced by two different manufacturers. If you discover that you have modules from more than one source then I'd recommend that you either remove one or the other SIMM and then try running Diablo. Remember that Diablo needs at least 8 MB in single play and 16 MB in multiplay and so this may not be an option for those of you who are a bit short on memory.

If that last suggestion doesn't do it, then I'd recommend that you go back and clean the contacts between the SIMM module and the motherboard. Certainly I'd strongly recommend this if you notice that the contacts on your motherboard and SIMM are of different materials, one gold and the other tin. Over time mixed contacts may produce, through a chemical reaction, a buildup of residue that weakens the electrical signals between the module and the rest of the motherboard.

If all else fails, you really should get your RAM tested to ensure that it is working according to specs, or if you can, borrow RAM from a friend who is not having any problems to test on your own system. Either way, at this point the chances are pretty good that the problem lies with your RAM.

Thank you :)

Loralon - pure lvl 46 sorcerer -

... and I have no imitations, unlike JANNA ... hehe ------------------------------------------------------------------------ Thanx to Loralon for the links and info u may email loralon at jericho@swlink.net

Email: jericho@swlink.net

voting has never bin easier, just click , and it's done .thanx !