System hangs or panics when non-memory PC cards are inserted. 

Non-memory PC cards cannot use the same memory resources used by other devices. To correct this, use a DOS debugger to identify device memory usage, then manually reserve memory resources for the PC card device using the following instructions. 

1. Boot the system using the Solaris 8 Device Configuration Assistant.

2. When the Solaris Device Configuration Assistant screen is displayed, select F2_Continue.

   The Bus Enumeration screen is displayed, followed by the Scanning Devices screen. The system is scanned to identify system hardware. When scanning is finished, the Identified Devices screen is displayed.

3. Select F4_Device Tasks.

   The Device Tasks screen is displayed.

4. Select View/Edit Devices and then press F2_Continue.

   The View/Edit Devices screen is displayed.

5. Press F3_Add Device.

   The Add ISA Device screen is displayed.

6. Select Unsupported ISA device and then press F2_Continue.

   The Select Resource Types screen is displayed.

7. Select Memory and then press F2_Continue.

   The Specify Memory Resource screen is displayed.

8. Enter the address range to reserve (for example, CA800-CFFFF), and then press F2_Continue.

   The Select Resource Types screen is displayed.

9. Press F4_Add.

   The View/Edit Devices screen is displayed.

10. Press F2_Continue.

    The Device Tasks screen is displayed.

11. Select Save Configuration and then press F2_Continue.

    The Save Configuration screen is displayed.

12. Type the name you want to assign to the configuration and then press F2_Continue.

    The Device Tasks screen is displayed.

13. Press F3_Back.

    The Identified Devices screen is displayed.

14. Press F3_Back.

    The Solaris Device Configuration Assistant screen is displayed.

15. Press F2_Continue to continue booting your system.

The BIOS primary IDE drive on your system was not detected by the Solaris Device Configuration Assistant during the pre-booting phase. 

• The drive might be unsupported. Check the Solaris 8 (Intel Platform Edition) Hardware Compatibility List.

• Make sure the ribbon and power cables are plugged in correctly. Check the manufacturer's documentation.

• If only one drive is attached to the controller, designate the drive as the master drive by setting jumpers. Some drives have different jumper settings for a single master, as opposed to a master operating with a slave. Connect the drive to the connector at the end of the cable to reduce signal ringing that occurs when an unused connector is dangling at the end of the cable.

• If two drives are attached to the controller, jumper one as master (or as master operating with a slave), and the second as slave.

• If one drive is a hard disk and the second a CD-ROM drive, designate the drive as the slave by setting jumpers. Any drive can be plugged into any connection on the cable.

• If there are persistent problems with two drives on a single controller, attach one drive at a time to verify that each works. Jumper the drive as master or single master and use the drive connector at the end of the IDE ribbon cable to attach the drive. Verify that each drive works, then jumper the drives back into a master and slave configuration.

• If the drive is a disk drive, use the BIOS setup utility to ensure that the drive type (which indicates the number of cylinders, heads, and sectors) is correctly configured. Some BIOS software automatically detects a drive type.

• If the drive is a CD-ROM drive, use the BIOS setup utility to configure the drive type as CD-ROM, if possible.

• If MS-DOS does not recognize the drive, there is probably a hardware or BIOS configuration problem. For many systems, IDE CD-ROM drives are only recognized by MS-DOS if an MS-DOS CD-ROM driver has been installed.

The IDE disk or CD-ROM drive on your system was not found by the Solaris Device Configuration Assistant in the pre-booting phase. 

• If IDE disks are disabled in the BIOS, use the Solaris Device Configuration Assistant to boot from the hard disk.

• If the system has no IDE disks, it might be a diskless client.

System hangs before displaying the prompt. 

See the Solaris 8 (Intel Platform Edition) Hardware Compatibility List.