Share your knowledge on these two classic MPCs
User avatar
By SimonInAustralia Sun Dec 09, 2012 5:42 pm
MPCHunter wrote:SCSI devices do not know if they are internal or external. They only know that they are a SCSI device.

...and they only know how to talk to the SCSI controller over a transmission line that is configured in a particular and exact way.

If you setup that transmission line differently, outside of the specs, there is no way of knowing whether it will work correctly in various situations.

If you change the properties of that transmission line, making a "stub" off of the main SCSI bus that is longer than 10cms as the specs describe, it is possible that it can no longer communicate correctly, and it is unknown how it will react to various different external SCSI cabling configurations that would normally be within the SCSI specs.


MPCHunter wrote:Going back to the original topic of the thread, I think it's been clearly demonstrated here that a clever cabling solution is much more practical than redesigning the SCSI PCB.

If you don't like slop in your cables and having to use lots of adapters, you will have to have a custom cable built. You can certainly go over the maximum length spec if you can find cables that have a better attenuation spec.

Practical doesn't mean much to me, I will do something like this to make what I believe is a better/cleaner end solution, that I am happier with, no matter whether it seems practical to anyone else or not.

Along with much neater internal cabling, you could incorporate the SCSI termination for the external bus onto the new PCB, making it an even cleaner solution.

The cabling solution being used in the photos above is not clever, it is ugly and wrong, lazy and quite the opposite of clever in my opinion.


Back to the original topic of the thread, if I was going to go to the trouble of making a redesigned SCSI Jack PCB, I would do it properly, to give a correctly speced external SCSI chain, so that anyone using it can expect it to behave in a certain way, like an external SCSI chain should.

If you redesign the SCSI Jack PCB, there is no need for any custom cables or excessive use of adapters, you can simply use an off the shelf 50 pin internal SCSI ribbon cable, the way it should be.

Making an external SCSI solution that does not behave the way SCSI is supposed to, that only allows a single and unterminated device to be connected to the external SCSI port, outside the SCSI specs, as you are suggesting, would be a very strange way to do it.

If you provide a solution to be used by others, it needs to meet accepted standard specs, so it behaves as expected in the widest variety of circumstances.

I don't see what the problem is anyway, I have shown above that the same solution and parts can be reconfigured to give a SCSI bus that correctly meets the specified configuration.

I don't understand the insistence to set it up incorrectly, all it requires is an external SCSI terminator plug in addition to the parts above, for when there is no external SCSI device attached.

This thread is about possibly creating a cleaner and more correct solution, as shown above there are plenty of threads showing how to do it with adapters (incorrectly), why do you have a problem with some people wanting to do it in a different way, that they believe is neater/cleaner/better?
User avatar
By SimonInAustralia Sun Dec 09, 2012 5:53 pm
ZWUKOLOW wrote:Simon, what can happen when I will use this type of connection however external device, for example just a single ZIP drive won't be terminated?

...

What can happen to any of the devices in the chain?

No idea how it will behave.

Just set it up correctly, as I have shown above, so that the external SCSI connector is at the end of the internal SCSI ribbon cable, and that it is always terminated, either with your external SCSI Zip connected and termination on the Zip turned on, or with a plug in external DB25 SCSI terminator.

If you insist on setting it up incorrectly, as shown in your photos/links above, it shouldn't damage anything, it is just possible that it will not communicate properly with the device.

I have no idea how this would present itself in symptoms/problems to the user, whether it would corrupt data, trigger error messages, slow down read/write speed, or simply not work at all.

It is also possible that it will work fine, you just have to try it.

I would set it up the correct way, as I described, there is really no reason to set it up incorrectly as shown above and in the various links/photos you provided.
Last edited by SimonInAustralia on Sat Mar 23, 2013 10:11 am, edited 1 time in total.
User avatar
By amenfetamin Sun Dec 09, 2012 6:03 pm
SimonInAustralia wrote:
ZWUKOLOW wrote:Simon, what can happen when I will use this type of connection however external device, for example just a single ZIP drive won't be terminated?

...

What can happen to any of the devices in the chain?

No idea how it will behave.

Just set it up correctly, as I have shown above, so that the external SCSI connector is at the end of the internal SCSI ribbon cable, and that it is always terminated, either with your external SCSI Zip connected and termination on the Zip turned on, or with a plug in external DB25 SCSI terminator.

If you insist on setting it up incorrectly, as shown in your photos/links above, it shouldn't damage anything, it is just possible that it will not communicate properly with the device.

I have no idea how this would present itself in symptoms/problems to the user, whether it would corrupt data, trigger error messages, slow down read/write speed, or simply not work at all.

It is also possible that it will work fine, you just have to try it.

I would set it up the correct way, as I described, there is really no reason to set it up incorrectly as shown above and in the various links/photos you provided.

Understood. No insisting to set it up incorrectly. Rather my curiosity on the subject and different combinations (including wrong ones)..

Well probably I'll go the route only with internal one connected. Only one thing preventing me to do it the correct way you suggested is an ugly SCSI terminator sitting on the back of my MPC everytime no external drive used.

I think the only way to do it nice and clean with both internal and external accessible is the new SCSI PCB you suggested..
Last edited by amenfetamin on Sat Mar 23, 2013 11:06 am, edited 1 time in total.
User avatar
By SimonInAustralia Sun Dec 09, 2012 6:14 pm
ZWUKOLOW wrote:Well probably I'll go the route only with internal one connected. Only one thing preventing me to do it the correct way you suggested is an ugly SCSI terminator sitting on the back of my MPC everytime no external drive used.

I think the only way to do it nice and clean with both internal and external accessible is the new SCSI PCB you suggested..

In your situation, if you don't like the idea of the external SCSI terminator, you should probably try it the incorrect way, with the external connector in the middle of the internal ribbon cable, and see if it works for you.

If it works, then it is all good, for you.

I would not create a solution like that for others to use, which is the point of this thread (I think), but if you know the limitations of the out of spec external SCSI connection you have created, and that it might not keep working if you chain additional external SCSI devices to the Zip, then it really isn't a problem.
Last edited by SimonInAustralia on Sat Mar 23, 2013 10:12 am, edited 1 time in total.
By APH Mon Dec 17, 2012 8:11 am
Image

Not bringing any news here.

I got everything wired up like in the above picture.

I use a microtech cardreader with 2 slots and an external HD (old macintosh) hooked up.

Slot one on my cardreader is scsi id 1 and slot 2 is scsi id 2
The Hd when turned on is scsi id 3

All has worked fine for quite some time now.

-----

I agree, lots of wires. It's not beautiful but it does the trick. I got it all to fit without damaging anything.

I'm looking forward to see what you guys come up with. I'm open to better solutions.