The interrupt that occurs when software attempts to read from or write to a virtual memory location that is marked "not present." The mapping hardware of a virtual memory system maintains status information about every page in the virtual address space. A page either is mapped onto a physical address or is not present in physical memory. When a read or write to an unmapped virtual address is detected, the memory management hardware generates the page fault interrupt. The operating system must respond to the page fault by swapping in the data for the page and updating the status information in the memory management unit.

Try adjusting the size or location of the swap file (virtual memeory). I have mine manually set at 3 times the size of the physical memory. Also put the swap file on a different drive than Win95. Give it a try anyway. If it doesn't help you can always reset the swap file back to default settings. There are so many causes for invalid page faults that it is nearly impossible to say this or that might be the problem. It could be software or hardware. Try reinstalling the offending program that causes the error if you want to.

Here is a tip that may help you, I don't know your level of computer expertise; I consider this fairly advanced. You can have Better Caching Performance with Win95 by making the following change. Goto Control Panel - System Tab - File system - change the Typical Role of the Machine to Network server, then apply changes. Instead of rebooting your PC, run Regedit and goto to this key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CurrentVersion\FS Templates\Server\. Edit the Namecache and pathcache to these binary values: NameCache - a9 0a 00 00 PathCache - 40 00 00 00. These values are actually reversed before you edit the changes. Exit Regedit and reboot. If you do not understand this post, DO NOT attempt it. FYI

The POST error beeps are not the same for all computers, here are some typical ones:

repeating short or continuous beeps----power supply or system board one long one short----system board, video board or pwr supply one long and two short----system board or pwr supply one short and blank display----system board or pwr supply one short beep and prompt for for system disk----disk drive, disk controller or cables, system board or pwr supply

As you can see most of them point toward the mother board or power supply. A series of three short beeps can be a memory problem, a loose connector ...

Log onto internet then go to a DOS prompt. Type: PING 198.105.232.1 if you get 4 responses your internet connection is working. If you get an error message you need to check your configuration.
Now see if you can access a Domain Name Server (DNS). At the DOS prompt type: TRACERT www.pccomputing.com The results will show all the connections required to hook up to that web site.
If either test fails open the RUN box in WIN95 (START/RUN) type: WINIPCFG then hit enter. Click on more info, get your ISP on the phone and go through the settings with them. Most likely the IP address or DNS settings are incorrect.

USB is a port for connecting to the computer sort of like a serial port or a parallel port. The computer needs to be able to support USB devices.

There are USB cards that you can buy and plug into an open slot inside the computer on the motherboard but I have never used one and am not sure how well they work. I believe the OS also has to support the USB devices. WIN98 does and the last versions of WIN95 does also (I believe you can download a USB patch for WIN95 from Microsofts website if you need it) although I've heard that it does not work well with WIN95.

Plug and Play is great when it works, but Windows 95 doesn't always get the configuration settings correct. And you can go crazy trying to remove all traces of the device and reinstall from scratch. Here are some strategies I recommend:

First, open Device Manager and see if there are any obvious problems. Inspect the properties for the device you've just installed, and pay particular attention to the Resources tab. If that dialog box lists a resource conflict, use the Conflict troubleshooter to find a cure. If you don't see a conflict listed, you may still be able to convince Windows to adjust settings--remove the check mark from the box that says Use Automatic Settings, then restart.

Try removing the device from Device Manager, then turn off the system and physically remove the device as well. Restart the system and repeat the installation. When removing devices, look for related devices that may be confusing the Plug and Play code.

If all else fails and you're considering the drastic step of reinstalling Windows from scratch, there's one final, radical option. You can force Windows to redetect all hardware in your system, and the redetection process could resolve the problem. Open Device Manager, expand the System Devices tree, remove every listed device, then restart. It may take several reboots for Windows to redetect every piece of hardware, but the process sometimes works. Remember, though, this strategy is strictly for situations in which all other efforts have failed!

Here's one of those tips that will help you get out of those jams when something refuses to work. Just go to Start, Settings, Control Panel, Systems, and then remove any of those devices that are not functioning correctly. Now restart your computer. After a few moments, Windows plug and play capabilities will identify your non-functioning device and reactivate it again, making it function again like normal.

It is a good idea to get your system information on paper incase you ever have a computer problem where you need to refer to this. Right click on the My Computer icon and select Properties from the context menu. Click on the Device Manager tab, then the Print button. Select the "All devices and system summary" button, then click on OK. This will give you a print out of information about your hardware, IRQ's, ports, memory usage, devices and drivers.