Dream Machine ( Build your own PC ) Message Board

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Pastimes : Dream Machine ( Build your own PC )

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next

To: Zeuspaul who wrote (9255)	12/8/1999 9:59:00 PM
From: Clarence Dodge	Read Replies (1) of 14778

You could put the CDROM on the same chain as the harddrive. I recall seeing an adapter in your cable link that addressed termination issues with mixed pin configurations. If you go from 68 to 50 pins the 'missing' 18 pins have to be terminated. I believe the 18 pins (or fraction thereof) are terminated at the adapter and the rest would be terminated (in your case) at the CDROM. In this case you would remove termination from the harddrive and leave termination enabled on the CDROM. Then you could go directly to the in/out connector with a shorter internal ribbon cable. Well I finally got around to collecting the parts to implement the above. I thought it was the neatest alternative that was presented to add an ext Jaz to my scsi chain. And it gave me an opportunity to resolve the termination issue on my 68 pin ribbon by using the actively terminated 68 to 50 pin adapter plus enabling termination on the 50 pin device. This is on the last connector of the ribbon. So, theoretically, at least, the 68 pin ribbon is properly terminated now. All/both devices on the 68 pin ribbon are working ok, strangly enough with the host adapter termination either enabled or disabled. I also found some new documentation on the Aopen site presenting this setup. BUT the simpler run off the 50 pin mobo connection to the int/ext adapter and on to the terminated Jaz is not ok. Both enabled and disabled host adapter termination options end in a BSOD during bootup when the Jaz is connected. Disconnect the Jaz and all is ok. This whole exercise has been worth alot in terms of getting down and dirty with scsi chains. I've learned much. But at this point, I think I'm ready to take Howards original advice and just get an adapter board to service the ext Jaz. I will be defeated for the first time by a hardware issue but the education has made it worth my time and the few bucks extra I spent. BTW Do you or anyone else know of any scsi diagnostic sw which would tell me what is actually going on in terms of termination and whatnot on a scsi chain. I appear to be blindly following the rules of scsi as I learn them, and hoping for success determined merely by whether or not a device works. Sems there should be a way to 'see' what is going on in the chain. Does Adaptec's EZ-SCSI do this? Clarence

Report TOU Violation

Share This Post

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next