Torbar
Well-known member
It looks like you'll also need a HD50 to db25 adapter for that, since the 68net uses db25yes, right, the connector exists, I got this https://www.ebay.com/i/273425140933?chn=ps
It looks like you'll also need a HD50 to db25 adapter for that, since the 68net uses db25yes, right, the connector exists, I got this https://www.ebay.com/i/273425140933?chn=ps
It looks like you'll also need a HD50 to db25 adapter for that, since the 68net uses db25
Yeah, would definitely be a nice option.I did not even notice So I guess designing a cheap (< $10) HD30 to DB25 could be a good idea
LOL! Whacky notions from outside the box for solutions to problems were my stock in trade. :blink: Now I play at it for fun.…and I thought my ideas were a little whacky. :-D
Yeah, would definitely be a nice option.
This one appears to be the correct adapter as well
https://www.ebay.com/itm/HDI-30-pin-to-DB25-SCSI-port-adapter-for-legacy-Macintosh-systems-552/253843270894?epid=165012110&hash=item3b1a3cecee:g:xeAAAOxyqUpQ89G4
no problem, I have itIt looks like you'll also need a HD50 to db25 adapter for that, since the 68net uses db25
Short/sweet version: be very careful about using those cheap adapters. I have several from various box lots I've snagged over the years. They're not as robust, but are probably good enough with careful use in a stabilized retro setup. But be careful, the longer the moment arm, the more danger of hot unplugging the SCSI connection a/o breaking something, like the solder connections on the PB logic board's connector.
Someone warned in another thread recently that those types of adapters are to be avoided. Strain relief is provided by Apple's adapter cables. I heartily agree with that. I'll add to that the fact they also lack the slide-lock mechanism of Apple's HD50 connector on the cables. That lock makes a world of difference, I never had great confidence in using my MICRO EN/SC in the field, which uses the same type connector as the inexpensive L-shaped adapters, but in the office or at home I didn't worry too much about it.
edit: I'll take some pictures to show the different connector configurations when I get the chance.
I just wanted to say your project is really awesome and I appreciate it. Thank you for doing what you do, @ronan!
The moderation team has cleaned up some off-topic posts in your thread. We apologize for that, and ask that everyone remember others when posting. Everyone can make a subforum-appropriate topic for projects they need to work on — no need to disrupt another forum-goer's thread!
What do you mean by good enough ? What are the downsides of cheap adapters apart from hot unplugging ?
I think it's mostly the physics of it: the cheaper ones tend to be big rigid things and these will put more strain on the connector on the powerbook, because they'll create a moment around it. The Apple ones tend to be smaller, and the better ones are flexible / cables. So you're much less likely to break something by sheer physics, if that makes sense.
http://www.pacificcable.com/Picture_Page.asp?DataName=SC38Any ideas of what's the name of the HDI-30 connector ? I can't find it on DK. Maybe it has another name ?
yes, right, the connector exists, I got this https://www.ebay.com/i/273425140933?chn=ps
I did not know about that, nice ! I wonder if designing one would be worth it ?
Pros :
- fast to design
- cheaper (especially because the one you suggest does not cheap to EU)
If I can't find one to buy on ebay I'll do this little project I think
Nice! So there is a generic driver in mac OS for SCSCI-Lan adapters?
Nope. Each vendor basically did their own thing. @saybur reverse-engineered the NuovoLink protocol, though, and that work has been what people are building on top of.
Next steps are implement the protocol to communicate with the driver on mac os. I'll keep you updated !
I think that if you review the AppleTalk chapter in Inside Macintosh volume VI you'll find some discussion on the .ENET and .ENET0 drivers which would be applicable.
Do refer to the AppleTalk chapter in Inside Macintosh volume VI for the standard driver interface, if you are not already aware of it.