test-drb November 2001

test-drb@ccmp.vtda.org

247 participants
886 discussions

by mhstein＠usa.net

Hmmm, that reminds me: I have an EISA Compaq 486sx at a client site from which I had to remove an add-on internal modem; ran the diagnostic/configuration program, it says everything's fine, but when it boots it stops waiting for F1 saying the configuration's incorrect. Press F1 to continue & everything works, just a nuisance 'cause it can't restart after a power failure without someone there to press F1. Any ideas? Can give more details off-list if anyone can help. m ----------Original Message---------- Date: 1 Nov 2001 1:11:30 +0100 From: "Iggy Drougge" <optimus(a)canit.se> Subject: Re: VLB SCSI? ...What I dislike about either system is that it's so awfully software-based. IMO you can't really can't call MCA or EISA plug'n'play...

24 years

Thick Ethernet/Sun networking problems

by pete＠dunnington.u-net.com

On Nov 2, 13:59, Lawrence LeMay wrote: > Well, one way of solving this problem is to reset the M971 card back to > factory defaults, and then setting the IP address. [...] > If the IP is reset back to 0.0.0.0, then the second step is to use the > reverse-ARP procedure to set the IP address. Thanks, Lawrence. I've had a quick look at the URL you posted in your followup, and it seems to me that unless Arno's printer (plotter? I can't remember either) is bust, that procedure is what he needs. I was about to reply to Arno's post, and was thinking about (R)ARP while having my dinner. It's a bit odd the way it says to "make an entry in the ARP table" because that's NOT what you do, exactly. The ARP table on a host has nothing to do with providing responses to other things that need information in order to boot, it's just used to map MAC addresses (Ethernet addresses, typically) to IP addresses when talking to other hosts known by IP address. But I'm sure it's just a case of Calcomp getting the terminolgy slightly wrong. What it obviously (to me!) means is to set up a host on the same subnet (actually in the same collision domain) which will respond to a RARP request. The way you do *that* on a Unix host is to make an entry in /etc/ethers, containing a line with the hostname that matches the MAC address you want to provide the IP address to. Then you also need an entry in the /etc/hosts file, to map the hostname to the IP address. Finally, make sure the rarpd daemon is running. Usually it will be started by a line in one of the startup files in /etc/rc.local, /etc/rc.net, /etc/rc.2 or similar place (it's in the /etc/init.d/network script in SysV UNIX). For Arno, this means: create /etc/ethers if it doesn't exist append a line with printer name and MAC (Ethernet) address /etc/hosts must already exist for the Sun to work, so append a line for the printer start up rarpd if it's not already running (the order in which you do these shouldn't matter) If we call the printer "calcomp", the line in /etc/ethers is: 00:C0:E2:00:0C:8E calcomp and the line in /etc/hosts is 111.1.0.1 calcomp and the command to start rarpd is probably /usr/etc/rarpd or /sbin/rarpd possibly followed by '-l' and the name of a logfile in which to record what it does, and/or the name of the interface on which to listen (le0, for Arno's Sun). -- Pete Peter Turnbull Network Manager University of York

24 years

Thick Ethernet/Sun networking problems

by Arno_1983＠gmx.de

OK Pete (and everybody else, of course), I admit that was a *long* break since I brought that up last time - but now I think I have collected enough information for a new chapter...So, where did we get stuck? Pete Turnbull wrote: >>>Have you tried pinging the printer by it's IP address instead of >>>it's name? Try a broadcast ping? >> >>As we're not too familiar with the commands, how is a broadcast >>ping done? > >Instead of giving the IP address of a particular machine, give the broadcast address of the local subnet. >The broadcast address is the subnet address but with the host part set to all 1's. For example, for the >class C network 192.168.5.0, the broadcast address is 192.168.5.255. For the class B network >176.18.0.0, the broadcast address is 176.18.255.255, and for the class A network 10.0.0.0, it's >10.255.255.255. >You should get a response from every device on that segment (every device in that broadcast domain, >actually) which has an IP address within the subnet range. OK, as the IP Adress of the SUN 1+ is 111.0.0.14 and the Subnet Mask ff:00:00:00 (says so at boot): ping -s 111.255.255.255 (if everything on the network is powered up and the PC is configured for TCP/IP transfer) gets answers from: hombre (111.0.0.14);the sending machine itself papa (111.0.0.23);the SUN SPARCstation 2 on the next desk ? (111.0.0.83);a PC I've finally set up for sniffing Nothing however from the printer. :-( >>>Have you checked the printer settings to make sure it's using the >>>correct IP address? Is that set from its panel, or by RARP/BOOTP/ >>>DHCP? If the latter, it needs a server to boot. >> >> Tony Duell wrote: >>>That printer isn't attempting to get information (IP address, >>>software, whatever) from a server, is it? No idea whether that helps, but if both the SUN 1+ and the printer are powered up, an arp -a shows: pa3 111.1.0.1 at (incomplete) and out of 25 packets I sniffed (Man, am I high now ;-)), 20 were ETHER type 0806 (ARP), the remaining 5 were type 0800. See also section "Configuring the 971" (Ethernet adapter card of the printer). >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). You need to be logged in as root, and type "snoop -v" or "snoop -V". That >will show you (in some detail; -V gives less detail) all the traffic visisble to the le0 interface. For >example: (...) OK, as I didn't finde snoop on the Suns (and didn't want to fiddle with compiling programs by myself at this stage...), I set up a PC with a network card, packet drivers and EtherLoad 2.00. Connected this to the idle transceiver, started with -r (record traffic), powered up one SUN and recorded the first 10 packets from it, then powered up the printer and recorded until I had 25 (the printer had then finished its warmup cycle and was displaying "READY"). Got only packets sent by the SUN (MAC: 08.00.20.09.BC.D7) destined for FF.FF.FF.FF.FF.FF (everybody?). The sniffer's HEX output file decodes to a lot of unreadable characters if interpreted as ASCII; only in the second packet that appears after switching the SUN on, the host name 'hombre' is readable. Decoding the whole data to decimal numbers show up the SUN's IP adress in all packets, the address the printer should have in the eighth and every following packet. Is there a DOS based sniffer out there which will produce output as understandable as snoop? If not, and if anybody wants a go at making sense out of the output, I'll mail the files private (HEX and decimal 6kB each, data ASCII decoded 2kB)... >On most of the Ethernet-enabled printers I've come across (mostly HPs, Lexmarks, and Xeroxes) you >can do the setup from the front panel -- sometimes tedious, but usually not too hard to understand. No such menu item or anything related to Ethernet. AFAICFO (as far as I could find out, adding to the current acronymania...) on the Internet, this is the procedure for configuring the Ethernet adaptor used in this printer: #Configuring the 971 # #Connect the network cable to the appropriate connector. # #The following tasks are accomplished by the system administrator: #-Make an entry in the ARP table #-Telnet to port 2002 #-Configure the 971 in accordance with your operating system's requirements # #The 971 queue is 'raw'. # #Refer to Model 971 Network Interface User's Guide P/N M0016-490 and CalComp Ethernet Software #Guide P/N M0062-240 for information pertaining to your specific UNIX configuration. # #Refer to CalComp Model 971 Ethernet Hardware Guide P/N 501987 for additional information. However, with us there is no sys admin - so how can we 'accomplish these tasks'? I couldn't find the 'refer to' titles on the web - anybody knowing if/where they're out there, or having them & willing to scan them for me? Any help would be much appreciated. >Have you tried printing out status pages? Sometimes that will show you things like IP address, >protocols enabled, that sort of thing. Usually you can do it by holding down one of the buttons when you >turn the power on. The printer manual tells that test printing is invoked by a long press on the key PRINT FONTS/TEST after switching the printer OFF LINE. Out comes a page which does tell absolutely nothing about network settings. It must however also be possible to print out these settings because in the paperwork, we found a page which reads as follows: CalComp Internal Ethernet Adapter Revision 4.11, Datecode 12/20 1994 10:20 Burnin Value = 0 SRAM = 256K bytes, Novram = 128 bytes Ethernet address 00 C0 E2 00 0C 8E Ethernet options: Ignore Alignment Errors Auxilliary data port = 0 IP address: 111.1.0.1 Telnet password security: OFF Netware options: !!! Netware DISABLED (use 'N' menu to re-enable) !!! Auto sense ethernet type between Ethernet II and 802.3 Apple EtherTalk options: EtherTalk DISABLED !!! (use 'N' menu to re-enable ) Printer name: CalComp CCL600ES Internally stored zone name: * Ethertalk Phase 2 LPD ( remote printer queues ) options: LPD enabled Output Control-D at end of job on Postscript queues Output FF at end of job on ASCII queues Console status monitoring configured as: Telnet port only But no idea on how to get this printed again to verify the settings haven't changed (e.g. due to bitrot in the Novram)... Sorry for the long post Sincerely yours Arno Kletzander Arno_1983(a)gmx.de -- GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net

24 years

EISA - was VLB SCSI?

by mhstein＠usa.net

Thanks for the tip; will give it a try now that you've reassured me. I don't think it's the battery since the config is stable, i.e. the power can be off for a weekend and everything's still fine when it's powered up again, just that annoying F1 request, and the problem started when I removed that modem and had to change IRQ's. I was reluctant to pull the battery & reset the config in case that really messed things up; at least now it's bootable. But sounds like it can't hurt to replace the battery, so might as well while I'm at it. mike -----------Original Message---------- Date: Fri, 02 Nov 2001 02:45:53 -0500 From: Chad Fernandez <fernande(a)internet1.net> Subject: Re: EISA - was VLB SCSI? re-read what he said..... he isn't loosing the configuration, it justs wants attention. I have had this happen before too. I just change things until it stops :-) I think something gets crossed up when changing things around too much, and it asks for F1 to be pressed. You can start over from scratch by pulling the battery..... I have had to do that once or twice when I really screwed things up, to the point that it hung while the bios was loading :-) Chad Fernandez Michigan, USA

24 years

classiccmp-digest V1 #761

by ajp166＠bellatlantic.net

From: Ben Franchuk <bfranchuk(a)jetnet.ab.ca> > >> The 74289 is also the same part/pinout save for instead of open collector >> they are tristate outputs. > >OK I would have used a generic 16x4 non inverting memory. The 74189 is inverting, though adding an external inverting buffer is NBD. If y ou want a part that wasn't inverting then you have to use the 4x4 register file (74170) times for to get nearly the same thing. The 4x4 however allowed was a two port device. >> The 74382 is not an ALU, it's a carry look ahead generator. The 74381 is an >> ALU. > >I have a 74F382 data sheet -- this is a ALU. Really, my TI databooks have it as the lookahead carry generator for the 381 ALU. >> BZZZT!!! By ealy 1980 the 2901 was already passe', as were TTL cpus. >> I presume by that you really meant early (very early) 1970s as the 2901 >> is a 1970s part. > >That is hard to say what era my cpu is from as I have to fake it from >what >I would of built in 1980's. LS TTL was just becoming popular. 8 bit >micros >where the big thing.I used a PDP8/e and a PDP8/S in 1983. Your still off by at least 5 years. 1976 is more the LS ttl era. By early 1980s the designs for CPUs were going to gate arrays. >> Also the 2901 is directly traceable to 74181, 74189 like parts. > >The 2901 is a nice bit slice chip. If I had used it in my alu I would >have >fewer states per instruction, but then I would have needed to go to >micro-code style architecture. This design was random logic where >no PROMS need ever be programed. That was late 60s very early 70s design. By late 70s microcode was common or at least state machines. The availability of bit slices by the early 70s influenced this greatly. >>I already have a real PDP-8. ;) > >I should have known :) ;-) Allison

24 years

Ecomstation.org (was Re: An Organization (was: Do we have a V AXorganization?))

by technos＠nerdland.org

I Have Been Trolled. See also: YHBT, YHBTHAND, YHBTIHYLIHAND. Jim On Friday, November 02, 2001 4:52 PM, Douglas Quebbeman [SMTP:dhquebbeman@theestopinalgroup.com] wrote: > > >This flame war has been done before. I'm only participating here because > > >I was individually lambasted. Methinks IHBT... > > > > IHBT? > > I Had Better T<something>... > > -dq

24 years

MicronEye

by beesley＠mandrake.demon.co.uk

Please don't tease, Craig. Tell us a bit more about the MicronEye -- Google doesn't throw up much more than "camera from 8 bit era". Phil (Back on the list after a long break and pleased to see the regular posters are still around.) Date: Thu, 01 Nov 2001 19:32:17 -0500 From: Craig Landrum <clandrum(a)monumental.com> FYI, I'm also a Mac junkie. Still have my bootable 128K original with external floppy drive and a rare MicronEye camera that plugged into it. --- http://www.mandrake.demon.co.uk/Apple/

24 years

Disk ID software

by optimus＠canit.se

Haven't you ever ended up with a disk which you don't know what it might contain. For all intents and purposes, it might contain the VAX/MIPS sources. =) So what do you do? Plug it into every computer where it would fit? That could become quite tiresome. So, to get to the point, is there any software out there which might identify what OS or filesystem is on a disk? It really shouldn't be too difficult, just a matter of identifying some hundred partition tables, MBRs, RDBs or boot blocks, right? -- En ligne avec Thor 2.6a. Amiga 4000/040 25MHz/64MB/20GB RetinaBLTZ3/VLab/FastlaneZ3/Ariadne/Toccata

24 years

Thick Ethernet/Sun networking problems

by pete＠dunnington.u-net.com

On Nov 2, 14:40, Ethan Dicks wrote: > > --- Pete Turnbull <pete(a)dunnington.u-net.com> wrote: > > On Nov 2, 16:30, Douglas Quebbeman wrote: > > > What does 'broadcast' do (other than the obvious)? > > > > It's just a way of explicitly stating what the broadcast address for that > > interface is. In every legitimate case I can think of, it should be > > redundant if you provide the netmask (or the netmask is redundant if you > > give the broadcast address). > > I think it's useful when you have an ancient network where the broadcast > address uses 0-bits, rather than 1-bits - i.e., ip 192.168.1.1 with a > netmask of 192.168.1.0 and a broadcast address of 192.168.1.0 *not* > 192.168.1.255. It's archaic, but allowed. So it is -- I forgot about that! The rest of what I wrote may well be drivel :-) -- Pete Peter Turnbull Network Manager University of York

24 years

classiccmp-digest V1 #761

by mhstein＠usa.net

In my TI databook, they're both ALU and/or Function Generators (a rose by any other name :), identical except for the carry/overflow logic. Hope that makes both of you happy. Allison (and sorry for not noticing that you're the exception, gender- wise, Sellam's feminine side notwithstanding), I ran across a thread here last year where you mentioned the Signetics 3000KT8080SK bit-slice board; don't suppose you did ever find any documentation? I've got one here that's pretty useless except as a source of TTL chips, since it's all socketed. m -----------Original Message------------ >> The 74382 is not an ALU, it's a carry look ahead generator. The 74381 is an >> ALU. > >I have a 74F382 data sheet -- this is a ALU. Really, my TI databooks have it as the lookahead carry generator for the 381 ALU.

24 years

← Newer
1
...
81
82
83
84
85
86
87
88
89
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

test-drb November 2001