I'm going to be stripping another round of machines... probably 10 or so.
All 286, 386, or 486 systems. If anyone wants ANY parts from machines of
that range, let me know and I'll see if I come across them.
This goes for drives, cards, chips, cables, screws, anything. About the
only parts I am currently interested in are standard AT power supplies
(the plain box style that can be used in many different cases... any that
are odd shaped I have no use for). Everything else that I will be finding
will either be of no use to me or redundant enough that I will be happy
to share.
Let me know as this is what I will be doing the rest of today, and part
of next week. The end of next week, the pile of unclaimed scrap goes to
the dumpster.
-chris
<http://www.mythtech.net>
I have bought a Sun DWIS/S card to drop in an old SPARCstation and
hopefully talk to some differential SCSI drives. What I can't
confirm is which kind of differential SCSI the card supports. I'm
guessing that the absense of any information means that it's HVD
(which is not what I need right now).
The SunSolve page on the controller is at:
http://sunsolve.sun.com/handbook_pub/Devices/SCSI/SCSI_DWIS_S.html
...to remove any ambiguity about what card I have coming.
Thanks for any illumination,
-ethan
For those that helped... I found my problem, and solution (sort of).
It seems that the HP JetDirect EX's BootP client doesn't agree with
Sustainable Softwork's DHCP server built into IPNetRouter.
Once I moved my Win2k machine to a private lan, and setup the DHCP server
on it, the JetDirect EX came to life quite nicely. It gets its IP address
and runs very happily doing everything it should do.
I would think that this problem might be fixed in a later firmware
version, but in order to upgrade the firmware, I need a Flash SIMM for
the JDEX. So unless someone on this list has one (or two since I have two
of these things) and wants to give it to me for dirt cheap (free?), then
I can't use these things on my network, and I just killed a day to find
that out.
So thanks for all the help everyone gave me.
-chris
<http://www.mythtech.net>
> You mean you can see it in the Chooser, right? But not in JetAdmin on
>the Mac? If you can see it in JetAdmin you should be able to configure
>it right there.
I can see it in the Chooser, but also, I have an HP LaserJet utility for
the Mac, and it gives you 4 types of printer/devices you can look for.
Postscript printers, JetDirect EX devices, DeskJet printers, and
AppleShare hosted printers.
The printer connected to it shows up when I look for Postscript printers,
and I can configure the printer. But the JDEX doesn't show up when I look
in the JetDirect EX device list, so I can't cofigure it directly.
But since I can send a print job and configure the printer connected TO
it, then it looks like the JDEX is at least doing its job.
All this may wind up being abondonded and I may toss these things... if I
understand the info I just found out, I can't upgrade the firmware on
them anyway because they need a flash simm card to do that, and they
don't have it and HP no longer sells them. If this is a problem with
interaction with my DHCP server (which is what it is looking like) then
if I can't upgrade the firmware and fix the bug, then these become pretty
useless to me.
And when you figure for $60 I can buy a brand new NetGear print server,
it doesn't become worth much more effort (and certainly not worth much
more cost)
-chris
<http://www.mythtech.net>
> IIRC, once you reset one of these to factory settings, there is a
>default IP address you can telnet to to configure it. Don't remember
>what it is, tho...
> BTW, can you see it from the JetDirect software on the Mac? Or is it
>not seen by JetDirect from both the PC and the Mac?
I had thought it should have a default IP as well, but it doesn't seem
to, rather it has a non IP (0.0.0.0) and waits for BootP info. Kind of a
pain.
I can see the printer attached to it from the LaserJet software on the
Mac when looking for Postscript printers, but when I look to see
JetDirect EX devices in that software, it does not show up. I'm not aware
of any other software for the Mac than the app I have (although there may
be a newer version then the one I have).
-chris
<http://www.mythtech.net>
In a message dated 6/13/2003 11:36:01 AM Eastern Daylight Time,
mmonetta(a)dssinc.org writes:
<< Do you need more equipment for the museum?
>>
sure, always looking for more stuff
I was browsing the mailing list archives and noted that the addresses are
not munged or hidden. Was any consensus reached about this?
--
----------------------------- personal page: http://www.armory.com/~spectre/ --
Cameron Kaiser, Floodgap Systems Ltd * So. Calif., USA * ckaiser(a)floodgap.com
-- My Pink Floyd code: v1.2a s BO 1/0/pw tinG 0? 0 Relics 2 8 <6mar98> --------
> Well, can you at least print the test configuration page now?
I could always print a test page as long as I wasn't on the network. Now
I can print a test page while on the private network, but it doesn't have
an IP because there is no BootP server to send data to it.
BUT, I can connect via my Mac on the private network and print a page, so
it looks like the device is physically working just fine, and it just
doesn't like something on my normal network (my guess being the BootP
response from my DHCP server).
-chris
<http://www.mythtech.net>
I have an Intel N80387SX-16 PLCC chip here.
I know some people have been looking for these, so the first person to
send me an address gets it. Totally free, 100%, not even shipping on this
one. :-)
-chris
<http://www.mythtech.net>
>The flashing _Activity_ LED (middle one of the 3), with the Status LED On
>(Left one of 3, also green) should indicate that the unit is receiving
>
>network activity.
>If it is the _Status_ LED that is flashing, then the unit is either not
>configured, not able to reach the network, or running a self-test.
>
>In its ever-helpful way, the manual says that if the yellow Fault light is
>on, disconnect and reconnect the DC power to the unit. If the Fault LED
>again lights, "then replace the unit." :)
In order of what happens.
I connect the printer to the JDEX, connect power. I get Status Light
blinks slowly. I connect network, Status light goes solid, network blinks
a few times, Status light goes out, Fault light blinks, error page prints
on printer. Status light returns to solid, Act light blinks, Status light
goes out, Fault On, error page... repeat until I disconnect from network.
As soon as I disconnect from the network, Status light starts blinking,
error pages stop. If I disconnect the printer but leave connected to
network, Fault light stays on solid all other lights off.
When I run this on a "private" network, everything works just fine. I can
even print to the printer normally from my Mac (haven't tried the PC).
However, the HP firmware downloader still can't locate the JDEX.
So it looks like it is getting an error due to something on my network.
My guess would be it doesn't like the BootP info my DHCP server is
sending. So I am going to try getting a different BootP server for my
Win2k box, one that also handles downloading of config files, and then
run that on a "private" network. I'm hoping once I give it an IP address,
I can get to it via the HP firmware downloader and upgrade the firmware
and the error problem will go away.
-chris
<http://www.mythtech.net>
