TOPIC
DISCUSSION Connecting SCSI devices to the bus and installing their associated drivers and INITs sometimes raise interesting issues. Improper termination is typically the root of hardware conflicts. A less likely reason is forgetting to set the SCSI priority number to a unique number, or using a device that improperly "provides" built-in termination, or improperly powers the terminators. Do not overlook damaged cables, terminators, or the terminator power source. The system could also be running out of memory. Configuring a start-up disk with minimal drivers and INITs or adding more RAM may help test that theory. Software conflicts typically result from INITs clobbering one another at startup, possibly due to poor memory management. Often, you can isolate a troublesome INIT by removing all extraneous INITs, then systematically adding each one back into the System Folder, one at a time, until you can no longer start up or use a device. Also, you can often eliminate the conflict by renaming the INIT (or files that contain INITs in their Resource Fork) so that they install in a different order. (INITs and drivers are installed alphabetically.) For example, you could rename the Apple Scanner INIT to "aScanner" to get it to load sooner. Note that there are some INITs (like Dyna File) that won't work if renamed. If this is the case, and the INIT conflicts with the Apple Scanner, you may have to remove the INIT from the System Folder when you're going to use the Apple Scanner. |
| Document Information | |
| Product Area: | Computers; Peripherals |
| Category: | Cables |
| Sub Category: | SCSI |
Copyright © 2000 Apple Computer, Inc. All rights reserved.