On October 10, Iggy Drougge wrote:
> >How about the original DIX Ethernet? Try a web search for Aloha.
>
> Was DIX really the original Ethernet? Wasn't that 10 Mbps and all?
I believe the original Ethernet was 3Mbps.
-Dave
--
Dave McGuire
Laurel, MD
> Anyway, I've heard that 64Meg RAM was awfully tight to run VMS on an Alpha,
> but is it still faster than Tru64 Unix? (The machine was no screamer, but
> it was still faster than my wife... ;-) Or should I just sell it to someone
> willing to give it a good home? (I have too many computers now - and I'm
> trying to purchase a [smaller] house so may be moving soon... I *need* to
> consolidate my collection & am downsizing machines which I will never have
> time to tinker with...)
If the DEC 3000/300 is anything like a DEC 3000/300LX then you should be
able to get some 72-pin true parity SIMMs and upgrade your RAM. If you can
get it up to a minimum of 112MB it should work great. If you can get it up
to 96MB it will work OK. Less than 96MB, and it will work, but will
probably do a fair amount of swaping. OpenVMS V7.2 won't even load if
you've got less than 64MB RAM.
It's definitly a good VMS box, so I say keep it, get some more RAM for it, and
play with VMS on it. I used my DEC 3000/300LX as my OpenVMS server for a
while with a BA350 chassis attached to it for disks.
Zane
On Oct 9, 17:33, Eric Dittman wrote:
> > > > IP over carrier pigeon!!
> > >
> > > UUCP over floppies ferried by cars! BLEEEAAAAAARGH!!
> > >
> > > Peace... Sridhar
> >
> > Unless I'm mistaken Dave is talking about a transmittion method that's
> > actually been used. There is actually an RFC for it.
>
> Haven't carrier pigeons been extinct long before IP and UUCP were
> developed?
Nope. The RFC exists (RFC 1149) and there has been a practical
implementation. See http://www.blug.linux.no/rfc1149/
vegard@gyversalen:~$ ping -i 900 10.0.3.1
PING 10.0.3.1 (10.0.3.1): 56 data bytes
64 bytes from 10.0.3.1: icmp_seq=0 ttl=255 time=6165731.1 ms
64 bytes from 10.0.3.1: icmp_seq=4 ttl=255 time=3211900.8 ms
64 bytes from 10.0.3.1: icmp_seq=2 ttl=255 time=5124922.8 ms
64 bytes from 10.0.3.1: icmp_seq=1 ttl=255 time=6388671.9 ms
--- 10.0.3.1 ping statistics ---
9 packets transmitted, 4 packets received, 55% packet loss
round-trip min/avg/max = 3211900.8/5222806.6/6388671.9 ms
vegard@gyversalen:~$
--
Pete Peter Turnbull
Network Manager
University of York
I just discovered Window Maker. Installed it on my SGI Indigo2 Maximum
IMPACT. Oh my god. It's like a dream. Running IRIX with the interface
of NeXTstep. I love it. Time to install it on all my headed
workstations.
Peace... Sridhar
On October 9, Pete Turnbull wrote:
> much larger house :-) The same fibre that carries FOIRL can (if it's the
> right size, 50/125) carry 10baseF, 100baseFX, 1000baseSX, ATM, FDDI, ...
FDDI generally uses 62.5/125 fiber.
-Dave
--
Dave McGuire
Laurel, MD
Another good one is Enlightenment.. It has some crazy deps, but it supposedly
compiles
and looks mad snazzy.. I've used it on Sun and Alpha (as well as a myriad of
wintel) but
never on SGI.
Jim
On Wednesday, October 10, 2001 12:27 AM, One Without Reason
[SMTP:vance@ikickass.org] wrote:
>
> I just discovered Window Maker. Installed it on my SGI Indigo2 Maximum
> IMPACT. Oh my god. It's like a dream. Running IRIX with the interface
> of NeXTstep. I love it. Time to install it on all my headed
> workstations.
>
> Peace... Sridhar
Non-IBM, PS/2 floppy drives?? Isn't that an oxymoron?
What about the Mitsubishi drives made for IBM?
Jim
(Isn't misuse of grammar fun?)
On Wednesday, October 10, 2001 4:46 AM, Mike Ford [SMTP:mikeford@socal.rr.com]
wrote:
> I've been looking for some 2.88 non-IBM PS/2 floppy drives, and I found
> some, but the guy says they are SCSI. Is that nuts or what?
>
> TEAC FD-235 J 5670-U W/SCSI Card
> TEAC FD-235 J 5670-U W/SCSI Card
> TEAC FD-235 J 610 W/SCSI Card
>
> Some of the HP/Apollo 725/50 computers I found recently had SCSI floppies,
> but it looked like the SCSI part might be detachable. I wonder if I should
> bother getting the above drives to work in a PC, which I would have to fuss
> around adding SCSI to?
>
> Now for real HV - I was told by an ex-electrical
> engineer - that he watched while someone
> was measuring up for a new HV cabinet with
> a tape measure. The usual metal sort you or I
> might use for DIY. He dropped it and shorted
> out the busbars, instantly melted the tape
> and ended up in hospital with major burns
> across his arms and chest.
At a place I used to work we were setting up a new raised floor.
The (licensed!) electrician that was setting up the new UPS was
leaning with his hand against one end of the bank of batteries.
He leaned down to tighten the nut on the other end of the bank
of batteries with a metal socket wrench. The UPS was about the
size of four large refrigerators side-by-side, 90% of which was
filled with batteries.
He nearly died and spent quite a long time in the hospital. The
investigation kept the area closed for almost a week.
--
Eric Dittman
dittman(a)dittman.net
Check out the DEC Enthusiasts Club at http://www.dittman.net/
On October 9, Iggy Drougge wrote:
> Since I'll be running another headless computer (HP 9000/380), I brought home
> my VT420. Nice terminal, but unfortunately this specimen will only talk, not
> listen.
> At first, I suspected my HP had lost its settings (the stupid boot PROM must
> be set via the keyboard to use a serial console). I proceeded to bring my HIL
> keyboard home and set it (without any screen) to use a "remote" console again,
> and the machine seemed to acknowledge that, beeping happily. But no response
> from the terminal. So I tested it with my DECstation. No response there
> either. So I hooked it up to my Amiga. Typing at the keyboard, there was
> output in NComm, but doing the opposite didn't work at all.
> So we have only one-way communication. What could be the problem?
Is flow control enabled on the terminal? I assume you're using a
DB25 adapter at the other end of an MMJ cable. Try turning off flow
control in the communications setup menu and shorting pins 2-3 on the
connector. At that point the terminal should echo what you type back
to the display. If it doesn't, you might have a toasty RS232 line
receiver in your terminal.
-Dave
--
Dave McGuire
Laurel, MD
