1.  In System Performance, any of the devices may be running in MS-DOS Compatibility mode, and/or
2.  The two IDE controllers have conflicts in Device Manager, and
3.  The CD-ROM drive is not listed

In general, DO NOT advise end-users to edit the Registry.  However, at this time the only known method of correcting the issues listed above are to modify the Registry.

After detection of hardware, an invalid entry is made into the system registry.  This causes Windows 95 to see a conflict when the devices are otherwise functioning without conflict.

1.   Make a backup of the registry by copying SYSTEM.DAT and USER.DAT in C:\Windows to SYSTEM.BAK and USER.BAK.  (These files are hidden and will need to be unATTRIBed before copying if it is done from a command prompt.)
2.  Click on Start, then Run
3.  Type REGEDIT and press <ENTER>.
4.  Click on EDIT and select FIND.
5.  Type "NoIDE", (type exactly as shown without the " ") and then select Find Next.
6.  When it has been found:
a.  Highlight the NoIDE and delete it, OR
b.  Right click on NoIDE and select MODIFY.  Change the value to 00.
7.  Close REGEDIT and restart Windows.

Windows 95 reports IDE device resource conflicts.

The cause of this issue is an incorrect registry entry.

1.   Go to the Start button.
2.   Go to Programs.
3.   Go to MSDOS prompt.  (Do not retreat to DOS Mode.  Go to the MSDOS Prompt through Windows.)
4.   From the C:\Windows\Desktop prompt, type EDIT FIXREG.REG
5.   In the blank screen it brings up, type the following: (note, the top and bottom lines are case sensitive, and REGEDIT4 must be the top line.)
 
REGEDIT4
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\IOS]
NoIDE"=hex:00
6.  Save and exit.  This will create a file called FIXREG.REG on the user's desktop.
7.  Exit the DOS prompt
8.  Double click on the new icon on the desktop.
9.  Click OK on the message it brings up, and then reboot the system.

If all seems OK, then delete the file created, or move it to a different location.  A good idea, may be to back up the SYSTEM.DAT file before doing this, just in case.

An end-user may experience their system continuously rebooting. thereby preventing it from entering Windows.

Having NOEMS and i=b000-b7ff on the EMM386.EXE line may cause the system to go into a continuous reboot loop.

Upgrade the BIOS to version 1.18.  A temporary work-around would be to remove the NOEMS and i=b000-b7ff on the EMM386.EXE line.

The Users Guide included with the system has a table that shows 800x600, 16.8 Million color with 2 MB of video RAM.  However, after upgrading to 2 MB of video RAM an end-user might not be able to change the Settings to 800x600 with 16.8M colors.

The cause of this issue is unknown at this time.

According to Cirrus Logic that particular color depth is not obtainable with the GD5430 regardless of any increase in video memory.  A CL-GD5434 chip set will support 800x600xTrue Color (24 Bit) with 2MB of video memory.  Escalate the call for a motherboard exchange.

End-users of PB600 motherboard based systems might experience choppy or distorted sound when trying to play MPEG of AVI files.  One reoccurring symptom is a reverberating distortion of the sound in the Silent Steel MPEG software.

BIOS version 1.07 and 1.11 sometimes cause adverse sound output when running MPEG and AVI files.

Flash the BIOS to version 1.17 or 1.18 to rectify this matter.

The CMOS needs to be cleared on the PB600.

The cause of this issue is unknown at this time.

The CMOS settings on the PB600 motherboard can be cleared using J29, the onboard battery jumper.  Jumper 1-2 on is default.  Jumper off will clear.  Leave the jumper off for 60 seconds to be certain CMOS settings are cleared.

With Windows 95 as the operating system, this motherboard will often enter a state where it gives "INVALID CONFIGURATION ERROR"  message during the POST even though the device settings in CMOS are correct.

The cause of this issue is unknown at this time.

Enable the "reset configuration data" setting and disable the Plug and Play function.   Then the system will consistently boot without generating the error message.  Locking out the PnP functions returns control of more of the system to the user. Go to the CMOS Setup, Advanced menu and select "YES" for the Reset Configuration Data.

There are PB600 Motherboards that do not have on-board cache.
Note:
BPCS 181330 does not have on-board cache.
BPCS 181002 does have on-board cache.

The cause of this issue is unknown at this time.

Match the BPCS number of the manual to the one on the system.  If the system should have cache, use the replacement BPCS 181002.

IRQ conflicts.

The availability of IRQ in Windows depends on the number of devices installed which use up IRQs to address the CPU. All 286 to the present systems are limited to 15 IRQs. Therefore, to avoid IRQ unavailability the end-user must free up at least one IRQ for the PBTV. If all system IRQ resources are used by system devices then installing PBTV will cause an IRQ conflict. (The claim that the Cirrus Logic Video chip set CL-5433 takes two IRQs has not been verified by testing. The Video only takes one IRQ for its operation ).

Make sure two devices are not using the same IRQ.

Some of these components exhibit functional problems when PCI Burst mode is enabled.

Assure the end user that while performance gains can be obtained for graphically intensive applications like CAD packages, Intel continues to recommend a default setting of Disable for PCI Burst mode.

The  Cirrus 5430 and 5434 hold times did not meet PCI Burst pecifications.

Intel recommends the default PCI Burst mode setting  to be "Disabled." In Windows, and with a majority of Windows-based applications, enabling PCI Burst mode achieves very little performance gain (with the exception of the use of graphically intensive applications like CAD packages as mentioned above).

Some PB600 BPCS #842702112 sound card I  28.8 AMSP  #030089 may produce sound distortion playing some WAV files or the Navigator Welcome message.

The cause of this issue is unknown at this time.

The replacement for this sound card is the sound II 28.8 AMSP #030107.

Some systems using the PB600 MB with Windows 95 format 556020 may cause the Power Management setting in CMOS to be set to Customize with an Idle Time Out of 15 seconds.  This will cause the system display to shutdown after no detection of activity on the system within 15 seconds (normal for this setting).  However, this does not affect the functionality of the system.

This issue is caused by the Power Management Mode in the CMOS Setup being set to enabled, as well as Power Management in Windows 95 Control Panel.

From the task bar go to the Start/Settings/Control Panel/Power icon.  Change Power Management to Off.  Shutdown the system and go into CMOS setup.  Select Power from menu bar.  Change Power Management Mode to disabled.

The system produces a CMOS checksum error on bootup.

Some PB600 systems may have been shipped with the Battery Enable jumper in the disabled position causing a CMOS checksum error to occur on system startup. Note that this is but one possible cause for a CMOS checksum error and other known issues may apply to the situation.

Place the battery jumper in the IN position to resolve this issue.

There is a small possibility that some PB600 systems may fail to accept EDO-RAM in Memory Bank 3.

This issue was discovered on a test MBI 609 PB600 MB and may not relate directly to the PB600.

There is currently no known resolution to this issue. (Simply try putting the EDO in Bank 2)

Cirrus Logic is working on the solution.

This issue is fixed with BIOS 1.09.

When the Internal Header is set to "Disabled" in CMOS, Windows 95 will reassign the port to the first available COM address.

The cause of this issue is unknown at this time.

To prevent this, set the internal header to COM 3 or 4.

No current fix.  Hardware modification is under evaluation.

PB600 systems with BIOS versions 1.13 to 1.17, and Windows 95, will go into sleep mode and not wake up.

Update the BIOS with Phoenix BIOS 4.04 rev. 1.18.