There's that "Open" again. And again with something to be interoperable
with other systems.
Fortunately, Cisco decided to implement the server side in IOS. Nice!Interesting.
I'll have to check this out.
To get on-topic again: Did you know that IBM once build LocalTalk cardsNo, I did not.
(SPD) for the AS/400?
And at least for V3Rsomething there was a PTF bringing the AppleTalkVery interesting!
network stack to OS/400! Documents I find say that this solution even
provided console capability!
I have herd tell of IBM building a 386 / 486 / Pentium computer that
went into an AS/400 much like an IOA. The idea was to allow a low power
PC to be in the AS/400 foot print for multi-OS compatibility. Somewhat
the same idea of my P/390-E allowing OS/390 to run in a PC chassis.
So the Token Ring, Serial (SDLC), and Coax are all methods to connect to
IBM networking technologies.
I have such a card which additionally has a DB-15 port for Twinax!Are you sure that the DB-15 was for Twinax?
I ask having seen either DB-9 or DB-15, I don't remember which, pigtails
with two twinax connectors.
Or is there a chance that it's an Ethernet AUI port?
I was highly disappointed to learn that SNA.ps doesn't support thatIs there a different file that does?
Twinax-Port.
Or why would a card exist that doesn't have software to support one of its features?
Ya. LocalTalk <-> AppleTalk can be somewhat nebulous. The common
definition that I hear is that LocalTalk os the physical layer(s) and AppleTalk is the protocol(s) that ran on top.
AppleTalk migrated to Ethernet too.
A good friend of mine that does (did) a lot with Apples and Macs states
that the 230 kbps was really the bandwidth between the CPU and the SCC.
Half of it was towards one hardware port and the other half was
towards the other hardware port.
According to my friend, booting over LocalTalk was supported very early on.
Yes. Macs.So it functioned as something like MS-SNA Server and / or Novell's SAA.
I thought that was a 1990's or earlier misconception. Is this stillI think there are still some people that believe it.
true?
Allow me to redirect you to here:
<https://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_72/ifs/rzaaxfsknow.htm>
Thank you for the link.
This really sounds like file system support / drivers in the Linux kernel.
QNTC sounds like SMB / CIFS / SMB2 client.
I think Integrated xSeries Server (IXS) is the PC board that I was talking about.
Question: What is the significance of the "Q" in front of a number of
things? I see it in the file systems and I seem to remember "qsysopr".
Let's call it a simplification for educational purposes.
More and more platforms are gaining better and better support for OSS.
different to IPv4 addresses and netmasks.
Since the Network Number in IPX was already 32 Bit, this solution
*could* have prevented the need for IPv6 in the first place! ;-D
Nope. :-)
MacTCP provided an IP stack and proprietary API to Mac
Applications. Open Transport was a complete rework to integrate
AppleTalk and IP under the STREAMS API, also as PPC native code. AFAIR
the only other company using STREAMS was Novell with their Netware.
On a side note, The Open Transport IP implementation has problems with
Window Scaling. Uploads to current Linux's will be painfully slow, single-digit KBytes/s range, even over 100M Ethernet. If you disable
window scaling in /proc (or /sys?), it's fast again, but everything
else will be slow. Or if you put a Cisco ASA in between to delete
the WScale-Option while the TCP handshake takes place.
I have a Pentium Overdrive Board (2850) with the accompanying board
with S3 graphics chip and other peripheral support. It was hard to
get hand on a breakout cable to actually see what's going on on the
PC side (VGA, PS/2 Keyboard and Mouse, Serial and Parallel Port).
Yes. The Coax/Twinax-Card was special in the way that it couldn't be
used with standard AppleTalk and MacTCP.
The serial card could be used as standard serial ports but also for
X.25 and SDLC. I have Mac X.25 server but I didn't take time to have
a closer look at it. I think, it's also a network central gateway to
provide X.25 services to other Macs via AppleTalk.
The Token Ring Card could be used with AppleTalk and MacTCP but it is painfully slow. I measured about 200 KBytes/s FTP on a reasonably fast
Mac IIfx with not much difference when put into a PowerMac 7100. A
PowerMac 7500 in the same ring with a PCI NIC sucked 1,5 MB/s per
FTP from the same server.
Yes. The card is called "Apple Coax/Twinax Card"
DB-15, M or F depends on what's to be connected on the other side. A distinction I don't understand.
Maybe you confuse DB-9 with Token Ring?
And now I'm again learning that there was even more highly interesting
stuff. CL/1 server vor MVS/TSO! MacAPPC! It seems that the latter
is part of the API stuff for SNA.ps. And MacDFT, which seems to be
the other Application to talk to the Coax/Twinax-Card.
Nope.
I'm not sure.
Because the software support maybe was once planned, but never
released.
A bit similar to the splendid Mac IIfx. The first Mac to incorporate
true DMA for SCSI transfers. Unfortunately, stock MacOS never made
use of that capability. A/UX did, rumor says.
Yap. Early documentation referred to what we now know as LocalTalk as
"Apple Bus". Maybe someone decided it was too technical and renamed
it AppleTalk to sound more friendly.
Not only Ethernet. Afterwards, Apple needed to clarify that Ambiguity
and called AppleTalk different depending on which media: EtherTalk, TokenTalk, FDDITalk. Ah, yes, and LocalTalk.
Did you know that almost every internal HP-Print Server for Ethernet supported AppleTalk, IPX and IP but the Token Ring variants supported
just IPX and IP.
And, in case you ever need to configure the IPX part of those Print
Servers, you really don't need JetAdmin. JetAdmin just configures
SNMP over IPX transport. You can set the same parameters via SNMP
over IP, too. I was very surprised and documented my findings: <https://kb.pocnet.net/wiki/JetDirect_IPX-Konfiguration>
Not true.
First, you can plug a "printer cable" (RS-422 MiniDin 8 with Mac
Pinout) between to Macs and use a terminal program to transfer files
with up to 230.4 kb/s. Given the receiving Mac's CPU is fast enough
to not miss a byte. Buffer? Which buffer?
Second, there was one pin on that connector you could supply an
external clock signal to. No terminal program supported that switchover
but rumor says, there once was an implementation of hardware and
software to supply external clocking with LocalTalk and thus raise throughput. I don't remember the name of that product, though.
Only with Apple II, not with Macs, though.
Unbelievable! Pun intended.
Yes, but very crudely. I never tried hard enough to learn how to
configure a workgroup name, so it might talk to Samba.
This is another mystery to me. I'd really love to ask Frank Soltis
about that before he dies (of age, that is). Meanwhile, I've come to
the conclusion that everything starting with a 'q' is an object which
was supplied by IBM. And 'q' because there are only a few senseful
(english) words starting with 'q', so there'd be no accidental
ambiguity.
Imagine it had been 'F' and there bychance was an object for a User
Class Key...
Granted. Thanks!
Yes but that's not always good in terms of the platforms intrinsic
security.
Because the software support maybe was once planned, but never*facepalm*
released.
A bit similar to the splendid Mac IIfx. The first Mac to incorporateA/UX. That's something I've never messed with.
true DMA for SCSI transfers. Unfortunately, stock MacOS never made
use of that capability. A/UX did, rumor says.
First, you can plug a "printer cable" (RS-422 MiniDin 8 with MacYou said something very key: Mini Din 8 as in the 8 pin cable.
Pinout) between to Macs and use a terminal program to transfer files
with up to 230.4 kb/s. Given the receiving Mac's CPU is fast enough
to not miss a byte. Buffer? Which buffer?
My understanding is that the 8-pin cable was really two 3-pin cables,
plus something, in the same cable. Thus you were using /both/ channels.
Yes, but very crudely. I never tried hard enough to learn how to
configure a workgroup name, so it might talk to Samba.
It's been too long since I've really worked with Samba. I recently had someone tell me that Samba did not support NetBEUI and that it only
supports NetBIOS over TCP/IP (a.k.a. NBT).
I say this because I wouldn't be surprised if the (early) version of
QNTC was NetBEUI only and didn't support NBT, thus might not be able to
talk to Samba.
Yes but that's not always good in terms of the platforms intrinsicI completely agree.
security.
I feel the need to say "73" and "station secure".
over IP, too. I was very surprised and documented my findings:
<https://kb.pocnet.net/wiki/JetDirect_IPX-Konfiguration>
I'm not at all surprised by that.
Not true.
First, you can plug a "printer cable" (RS-422 MiniDin 8 with Mac
Pinout) between to Macs and use a terminal program to transfer files
with up to 230.4 kb/s. Given the receiving Mac's CPU is fast enough
to not miss a byte. Buffer? Which buffer?
You said something very key: Mini Din 8 as in the 8 pin cable.
My understanding is that the 8-pin cable was really two 3-pin cables,
plus something, in the same cable. Thus you were using /both/ channels.
Second, there was one pin on that connector you could supply an
external clock signal to. No terminal program supported that switchover
but rumor says, there once was an implementation of hardware and
software to supply external clocking with LocalTalk and thus raise
throughput. I don't remember the name of that product, though.
Interesting.
Only with Apple II, not with Macs, though.
I thought it was more than just Apple IIs. But there were a number of
Apple II models. I'll give you that Macs didn't have nearly the same functionality.
Unbelievable! Pun intended.
:-P
Yes, but very crudely. I never tried hard enough to learn how to
configure a workgroup name, so it might talk to Samba.
It's been too long since I've really worked with Samba. I recently had someone tell me that Samba did not support NetBEUI and that it only
supports NetBIOS over TCP/IP (a.k.a. NBT).
I say this because I wouldn't be surprised if the (early) version of
QNTC was NetBEUI only and didn't support NBT, thus might not be able to
talk to Samba.
This is another mystery to me. I'd really love to ask Frank Soltis
about that before he dies (of age, that is). Meanwhile, I've come to
the conclusion that everything starting with a 'q' is an object which
was supplied by IBM. And 'q' because there are only a few senseful
(english) words starting with 'q', so there'd be no accidental
ambiguity.
Interesting.
Imagine it had been 'F' and there bychance was an object for a User
Class Key...
:-)
Granted. Thanks!
;-)
Yes but that's not always good in terms of the platforms intrinsic
security.
I completely agree.
I feel the need to say "73" and "station secure".
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 82:45:46 |
Calls: | 6,658 |
Calls today: | 4 |
Files: | 12,203 |
Messages: | 5,333,436 |
Posted today: | 1 |