>Hi all,
>
>My mom has the following setup:
>
>- Beige G3 minitower
>- Apple LaserWriter Pro 600
>- OS 9.1
>
>The printer and Mac are connected via LocalTalk. (This printer requires
>AppleTalk.)
>
>She is afraid that the next upgrade (OS X) will make the printer unuseable,
>since Apple is phasing out LocalTalk (this Mac is the last model that still
>comes with a damn serial port).
My first suggestion would be that, unless she has a specific reason for
upgrading to OS X, she should stay with 9.1. Like all Version 1.0 items, OS
X is going to need a few things worked out and will likely be adopted
immediately by: a) developers, b) hard core geeks that just have to have the
latest and greatest thing released, c) people that don't know any better and
give in to some form or another of pressure to upgrade. She'd be better off
waiting for it to mature a little bit, especially if she is just a casual
user.
As for the serial ports, since the Beige G3 is a supported machine, I
would thing that it's serial ports would be supported as well. The only G3
or newer system not supported by OS X is the original G3 Powerbook.
Jeff
>That's interesting, there was an Appletalk hardware/software solution for the
>Amiga which was called... Doubletalk. It existed both as an external box for
>A500s and a Zorro card for the big boxes.
There was also the Emplant Deluxe with it's Localtalk ports, which I
used to connect my A4000 up to various Mac's. I never ran it as the Emplant
emulator but as a hardware extension of Shapeshifter's emulation.
Jeff
IBM mainframes, Hitachi mainframes, and Amdahl mainframes.. They sound like
they're 3380-equivalent, at least the Amdahls do. I wish they were closer,
or I'd buy 'em, could use more storage.
Will J
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
On Mar 29, 6:39, Iggy Drougge wrote:
> I see. I really must create a lot of small networks now, so that I may
> saturate all those ports.
Well, they would really all be the same network -- they'd be all one
collision domain (any packet or collision appearing on one port would be
seen on all the others. That's what a repeater does).
> What management would be involved with a repeater? All other hubs and
> repeaters I've used have been entirely automatic.
Partitioning segments deliberately, eg to lock out a faulty host -- maybe
one that's jabbering, or responding to things it shouldn't -- or an
intruder. Monitoring traffic levels (counting packets, octets, collisions,
etc). Monitoring traffic types (unicast packets, multicast packets,
broadcast packets). Keeping a list of MAC addresses seen. Since all this
is usually done by talking to the repeater (or whatever) over the network,
the repeater itself has to have an IP address, and so there are ways to set
that up (setting it by hand, or telling it to use bootp/dhcp) or upgrade
the firmware, or set passwords for read/write operations.
> I'd think so too, but I heard on Usenet that old repeaters (the kind
which
> actually call themselves repeaters =) could slow down modern networks.
Don't
> ask me how, though.
I don't see why, if you're talking about repeaters. Old switches might
well be slow, since they work on a store-and-forward basis. A repeater
("hub") works on the bit level; a switch works at the packet level and
looks at the type and addressing of each packet before passing it on.
Newer switches use ASICs to do this in hardware at wire speed, older ones
use more conventional processing (or a combination).
> >> What does partitioning actually entail?
>
> >See above. Some more modern 3Com hubs also have the capability to split
> >the unit into segments (eg, the SuperStack II PS 40 hubs and others can
> >have 4 segments) but assigning ports to different segments isn't usually
> >called partitioning.
>
> IOW it's just a glorified OFF switch. =)
Partitioning, is, yes. Segmenting isn't, it's just a way of making one
big(ish) hub do the job of a few smaller ones.
--
Pete Peter Turnbull
Network Manager
Dept. of Computer Science
University of York
Yes, you can do that and the perfomance is very good on the
K2-350 box here at work. I use teh 3.5" loaded one to install windows and apps as it's faster than 4x CDrom and since some systems here dont have cdrom at all it really beats floppies
or sucking it down the 10mbs eitherpipe.
I've never tried to boot one directly but I have used one as
C: via floppy boot for W95.
Allison
------Original Message------
From: "Richard Erlacher" <edick(a)idcomm.com>
To: classiccmp(a)classiccmp.org
Sent: March 29, 2001 4:30:02 AM GMT
Subject: Re: ide harddrive
IF you have a DLL to support EPP under W9x, you can certainly do that. I've not
yet found one that comes with enough pre-sale doc to verify that it's up to that
kind of performance. There are a few PCI parallel port boards that claim to
have the speed, however. I tabled my S-100 bus probe a year or more ago for the
simple reason that the ports on the motherboards I was considering were not fast
enough. The PCI ones may breathe new life into the project.
The datasheet for the SMC34C60 turned up immediately on a search via GOOGLE.COM.
There's an IP product that pops up too, perhaps worth a look. Be careful not to
mix up the EPP and ECP functions on the SMC part! The two are TOTALLY
different!
Dick
----- Original Message -----
From: "ajp166" <ajp166(a)bellatlantic.net>
To: <classiccmp(a)classiccmp.org>
Sent: Wednesday, March 28, 2001 7:46 PM
Subject: Re: ide harddrive
> From: Richard Erlacher <edick(a)idcomm.com>
>
> >I'd be VERY interested in seeing that schematic, Tony! I've no doubt
> that it can be done, but I wonder how fast it will be.
>
> The commercial ones are at least several mb/sec using drives designed for
> DMA33. Only took a minute or less to transfer a set of 28 .CAB files
> (w95).
>
> The device driver runs as a SCSI device under W9x or NT4.
>
Undoubtedly that's a driver for the device under Windows, and not a generic port
driver. Too bad ...
>
> Allison
>
> >----- Original Message -----
> >From: "Tony Duell" <ard(a)p850ug1.demon.co.uk>
> >To: <classiccmp(a)classiccmp.org>
> >Sent: Wednesday, March 28, 2001 11:01 AM
> >Subject: Re: ide harddrive
> >
> >
> >> >
> >> > Evening folks, I am looking for a circuit using the parallel port on
> a
> >> > pc to Ide interface, does anyone have a schematic for one?
> >>
> >> Somewhere I have an data sheet for a chip to convert a parallel port
> into
> >> an ISA slot. No, I don't mean a chip for adding a printer port to the
> ISA
> >> bus (like the 82C11 does), I mean a chip that connects to a parallel
> port
> >> (either 'original' or one of the enhanced bidirectional ports), and to
> >> some DRAM, and which allows you to connect anything that you'd
> normally
> >> connect to ISA on the other side of it. It allows you to read/write
> any
> >> port or memory location from the parallel port side, it allows the ISA
> >> device to do DMA into the memory hung off the chip (which can then be
> >> read/written from the parellel port), and so on.
> >>
> >> I think it was made by SMC, but don't quote me on that.
> >>
> >> It looked like a fun device to work with, but I don't know where on
> earth
> >> you'd find one.
> >>
> >> If anyone is interested, I will try and find the data sheet and post
> the
> >> number of the device.
> >>
> >> -tony
> >>
> >>
> >
>
>
> Date: Wed, 28 Mar 2001 19:36:07 +0100 (BST)
> From: ard(a)p850ug1.demon.co.uk (Tony Duell)
> Subject: Re: ZX80/81 expansion
>
> > My ZX80 came with a ZX81 16K RAM pack and it works fine;
> ISTR physical
> > differences aside the only real difference between the 80
> and 81 was the ROM
>
> I thought the ZX81 hardware provided some kind of interrupt
> to the Z80 to
> allow for 'simultaneous' processing and display, and that you
> couldn't
> get this on the ZX80 simply by dropping in the new ROM. There were
> various circuits (a couple of TTL chips IIRC) to add this
> feature to the
> ZX80, though.
Yah, the ZX80 couldn't think and talk at the same time so it blanked the
screen while it was processing! In the ZX81 this was known as FAST mode,
with the slower SLOW mode being able to do both. However, this still meant
that in SLOW mode the machine was 4 times slower than in FAST! Probably
sometime tonight I'll upload the Your Computer reviews of the ZX81, Jupiter
Ace and a couple of others for your reading pleasure, unless you've already
got them round somewhere. Oh, hang on, you're text only aren't you?
> Keyboard overlay I think. The keyboards were somewhat different
> physically, weren't they -- the ZX80 used contacts on the
> main PCB, the
> ZX81 had a separate membrane keyboard linked up with tapewire.
<thinks>. Yep. Looking at the pic on the museum site the keyboard is part of
the main PCB, whereas on the ZX81 it was separate. I still think its funny
to look at the design for the ZX80 and compare it with the heath-robinson
nature of the Issue 1 Spectrum :o)
> I have an Ace, but it's not 'spare' if you see what I mean.
Bugger :)
> ------------------------------
>
> Date: Wed, 28 Mar 2001 22:21:07 +0000
> From: jpero(a)sympatico.ca
> Subject: Re: MacOS on CD-ROM? (was Re: Mac SE/30)
>
> The biggest difference this Basilisk II is freeware where other
> emulators you talked about ( saw them ) are payware.
I think I need to get my paws on that then......
--
Adrian Graham MCSE/ASE/MCP
C CAT Limited
Gubbins: http://www.ccat.co.uk (work)
<http://www.snakebiteandblack.co.uk> (home)
<http://www.binarydinosaurs.co.uk> (The Online Computer Museum)
0/0
On Mar 28, 22:50, Paul Braun wrote:
> But if you REALLY want to do it right, you wind your own coil on a
> shellacked oatmeal box.....or, a shellacked salt box.
>
> All of mine used a germanium diode and a prewound coil, so there.
> I'll shut up now.
:-)
Everyone (at least, everyone in the UK) knows you wind a hundred turns[1]
or so of 24swg DCC (double cotton covered) copper wire (actually, I used
enamelled copper) on a toilet roll centre, to make a coil about 2" long.
I recall one maths teacher using a toilet roll centre for some
demonstration in a maths class (nothing to do with radio or electronics).
In his distinctive accent, which was all the more noticable to Scottish
schoolchildren, he announced that this was a "wiyah fohmah". Despite
heckling, he subsequently refused to acknowledge that it might have had any
connection with more mundane functions.
[1] to be honest, I can't remember the standard number of turns. It might
have been less than a hundred, and I'm too lazy to work it out right now.
And it doesn't have to be 24swg, you just use whatever you can scrounge.
--
Pete Peter Turnbull
Network Manager
Dept. of Computer Science
University of York
OT, sorry - but are there any SCSI fans on the list who know anything about
the SCSI SCA standard? If so can you dro me an email off-list if you know
the answer to the following...
I've got a couple of drives with SCA connectors and adapters plugged into
them to bring them out to the more normal 68-pin connectors. There's a bunch
of inline resistors on each adaptor which I'd like to know whether they are
terminators or just something that's needed when connecting an SCA device to
a normal SCSI bus.
Both drives work together happily despite the resistors (have been doing for
the last 2 years anyway) which surprises me if those are terminators, but
nothing works if I try to chain anything else onto the same bus which makes
me wonder...
ps. one of the drives is 6 years old, but not ten - so take notice of 60% of
this email or something :-)
cheers
Jules
Peter Turnbull wrote:
>Another way to see what's happening, is to use 'snoop' if you have it
>on one of the Suns (tcpdump for Linux/BSD/etc is similar).
Just typing in snoop at the prompt ends up with
snoop: Command not found.
In which subdirectory might this program be (if it's on the system at all),
or how can we search for it? If it isn't, where can one possibly get it?
The printer manual has surfaced, but it only contains the information that
the Ethernet card was an add-on and had its own Installation and Configuration
Guide with it - which must be buried even deeper than the manual itself if
we were given it at all
I guess the remaining problem is really the IP address of the printer, as
the data transfer between the computers and the printer must be all right by
now: Whenever a ping or something else occurs on the network, the orange DATA
LED on the printer's back side blinks a few times (what should indicate it is
receiving the data).
--
GMX - Die Kommunikationsplattform im Internet.
http://www.gmx.net
