test-drb November 2001

test-drb@ccmp.vtda.org

247 participants
886 discussions

by pete＠dunnington.u-net.com

On Nov 2, 15:45, UberTechnoid(a)home.com wrote: > I thought they used a 6507 or 6510 processor... Same family, same instruction set as 6502, just a different bus structure. Some of them have reduced address busses, one or two may lack one or two instructions (? I think), some have different clock requirements, but all are part of the R65xx family. The original R6502 data sheets lists the members and their differences. -- Pete Peter Turnbull Network Manager University of York

22 years, 6 months

An Organization (was: Do we have a VAX organization?)

by vcf＠vintage.org

On Mon, 29 Oct 2001, Jeffrey Sharp wrote: > I think that what is needed most is an international organization that > covers *all* vintage computers, software, and docs. We need something > that's implemented well enough that most of us would be convinced to join. > The best starting point I can think of is Sellam's VCF organization: > > * He already has one of the largest inventories of us all. That's a good > start towards a "Noah's ark" collection, which I think should be one > function of the organization. This is in fact one of my missions. I know I won't be able to get every single model of every single computer, but I can get close. And this has applications of both practicality and posterity. > * He's got www.vintage.org, which would be a primo domain name for the > organization. > > * He's got www.vintagetech.com, which would be the fundraising part of the > organization. Dues could be another. Um, for now, the funds that VintageTech generates are intended for the Sellam Ismail organization of getting by ;) > * He's got experience running VCFs. True dat. > Of course, Sellam would have to be interested in being the organization's > fearless leader! I appreciate being nominated for this lofty organization. In fact, what you've described is what I've been working towards for the past 4-5 years. It's just gone much slower and taken much longer than anticipated due to distractions and detours in my life. And this is hard work, especially for one guy. > Other things the organiztion could do: > > * A central, Yahoo-like web site that would become the world's foremost > resource for vintage computer information. It would try to replicate > all available information for preservation. Individual members would > also be given a mechanism to have their collection hosted on the site > under a uniform interface. Those who resist assimilation could still > have their sites linked to. You could get to info either by > collector name or a category/manufacturer/series/model tree. It would > be wonderful... One day the VCF website will be this portal. > * SIGs would, of course, solidify according to demand. I imagine the VAX > SIG (VSIG?) would be quite well represented. Each SIG could have its > own mailing list. The whole thing would be not unlike the FreeBSD > mailing list system. One of the next things on the agenda (after finishing the VCF Marketplace) is a messaging system. Of course, I don't know how useful this will be in the face of this list and other very active and strong lists. I'll put the tools out there, it'll be up to folks to put them to good use. > * Rename itself from VCF to IVCA. "International Vintage Computing > Association" to outsiders, "International Vintage Computing Asylum" > for insiders. :-) The VCF will eventually become an international "society" dedicated to the preservation of old computers and computer history. The VCF events are to be yearly gatherings that cap off activities that occur throughout the year. My desire for the past couple years has been to sponsor local computer collector clubs throughout the world, to create local interest that then grows into a connected network of clubs. > > * I don't know... other stuff. > > As you can see, I'm all about grandiose ideas. Now won't someone rise up > and implement them? :-) Me too. If I could get organized enough to create an actual organization then things would move faster. Of course it would require the sacrifices of other people interested in seeing this vision implemented. Sellam Ismail Vintage Computer Festival ------------------------------------------------------------------------------ International Man of Intrigue and Danger http://www.vintage.org

22 years, 6 months

VLB SCSI?

by dhquebbeman＠theestopinalgroup.com

> The AHA2842 is a narrow-SCSI card, though it's possibly the best ADAPTEC ever > produced. I've been using them for years without a hitch, while their newer > cards, (2940, 3940, 3985, etc) seem to bring with them both a short life and > lots of compatibility issues. > > Unfortunately, the VLB is alread a "classic" feature, having been "dead" now for > over a decade. While I'm sure they exist (i.e. EISA ones), I don't have any 486 motherboards that aren't VLB boards, the most recent of which was bought new in 1994. Still, while not-quite-classic, VLB sure isn't leading the industry... -dq

22 years, 6 months

Reward for Ethernet Switch

by freds＠monarch-info.com

I am looking for an ethernet switch, circa 1991, that has removable blades with one channel per blade. Not sure if this exists, but if you have one, I can pay $75-100, depending on condition. Fred Scholl

22 years, 6 months

FW: $200 Dollar Reward for TOPS PC to MAC Software

by PHodara＠netwave.com

Skipped content of type multipart/alternative

22 years, 6 months

Thick Ethernet/Sun networking problems

by dhquebbeman＠theestopinalgroup.com

> 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? [..much liberal snippage, no further notices issued..] > 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: > > IP address: 111.1.0.1 > Telnet password security: OFF Ok, likely this won't work for Calcomp, but HP stuff uses a default IP address of 192.0.0.192 for their network interfaces. Try setting up a separate computer and give it an address on the 192.0.0.0 network. Then try pinging it... If that doesn't work, this next idea will take some time and preparation. Get a Windows 2000 or Windows XP machine. They allow you to change the machine's network address on the fly (can Linux do this?) using the NetShell (NETSH.EXE) facility. The syntax is: netsh interface ip set address "Local Area Connection" static <my_ip> <my_mask> <my def_gw> Write a BASIC program that writes out a batch file. Have it iterate through the possible range of network addresses, sending a broadcast ping for each network. Have the output from ping redirected to a file using the append mode ('>>'). Search through the file until you find the network address to which the printer responded. Then make a small change to the BASIC program to iterate through all the node addresses on that network until you find the IP address of the printer. Set up the Windows box to be on that network, TELNET to the printer, change the IP address back to 111.1.0.1 and you should be all set. hth, -doug quebbeman

22 years, 6 months

classiccmp-digest V1 #761

by ajp166＠bellatlantic.net

From: Ben Franchuk <bfranchuk(a)jetnet.ab.ca> >If the 74289's are the non inverting 16x4 rams I would use them. I plan >to use 74ls382's (the ripple carry alu's). The 74289 is also the same part/pinout save for instead of open collector they are tristate outputs. The 74382 is not an ALU, it's a carry look ahead generator. The 74381 is an ALU. >Can't do that for three reasons >1) I am use a 16 x 12 ram ( 3 chips ) on two boards for a 8 x 24 >register array. Not enough reason there, so you dont use the full byte width. >2) I am using the 486 cache chips as main memory in my FPGA prototype >32k x 12 bits.:) So the cache rams are easy enough to find more. >3) This was a TTL design on paper of what a computer designed in the >early 1980's could have been like. That rules out 2901 bit slices. 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. Also the 2901 is directly traceable to 74181, 74189 like parts. >configuration. Mind you a >larger TTL CPU with lights and switches is more impressive. If you like >lights I already have a real PDP-8. ;) Allison

22 years, 6 months

$200 Dollar Reward for TOPS PC to MAC Software

by dhquebbeman＠theestopinalgroup.com

> $200 Dollar Reward for TOPS PC to MAC Software > > > I am looking for this discontinued piece of software that allows PCs to > connect to MACs via appletalk. I need one copy of the PC software preferably > two (each with unique serial numbers). COPSTalk, which was (I think) the descendent of TOPS, was available for public download from the URL: http://www.downloadsafari.com/Files/utilsnetmisc/C/COPSTalk.html but I didn't have any luck. PC/MacLAN, from Miramar Systems, is still commercially available. I have some licensed copies of an old version (runs on Win95 only) I'd let go for $200. Or, you could buy fully licensed new versions for about $159 each. They're at: http://miramarsys.com I've also got COPSTalk laying around somewhere... Regards, -doug q

22 years, 6 months

$200 Dollar Reward for TOPS PC to MAC Software

by bills＠adrenaline.com

Sorry. Intended that reply to be off-list. Sorry again, Bill

22 years, 6 months

Thick Ethernet/Sun networking problems

by pete＠dunnington.u-net.com

On Nov 2, 8:03, Douglas Quebbeman wrote: > Ok, likely this won't work for Calcomp, but HP stuff uses a default > IP address of 192.0.0.192 for their network interfaces. Try setting > up a separate computer and give it an address on the 192.0.0.0 network. > Then try pinging it... Which is really slightly naughty, as 192.0.0.0/16 is NOT in the private address range (that would be 192.168.0.0/16). But that's not relevant to Arno's problem :-) > If that doesn't work, this next idea will take some time and preparation. > Get a Windows 2000 or Windows XP machine. They allow you to change the > machine's network address on the fly (can Linux do this?) MOST systems other than Windows can do this :-) It's not a good idea if you need to go through all the networks numbers (see end of this post for the reason, if you've not realised yet). If you want to try the Class A addresses, it would be rather easier to do on one of the Suns, just by writing a script that cycles through the network numbers in a loop, issues an ifconfig for each iteration, and a broadcast ping (with the number of packets emitted restricted to a quantity of 1 or 2). Assuming the devices of interest are too old to understand CIDR, there are three ranges of network numbers to consider: class A, class B, and class C; ie those with 8-bit network numbers and 24-bit host parts, 16/16, and 24/8. The quick and dirty way is to run the script once for each class, so that's networks 1..127 with subnet mask 255.0.0.0, networks 128.0 ... 191.255 with netmask 255.255.0.0, and 192.0.0 ... 223.255.255 with 255.255.255.0 (the rest are multicast or reserved addresses). Of course, if the printer's IP address has been really scrambled, it might end up in the reserved range, and I can't think of an easy way to get at that. Unless the Sun has something like the range(1) command, it's probably easiest to make a file containing each list (call the files netsA, netsB, netsC, for example) and then do something like this in the script: #!/bin/sh for i in `cat netsA` do ifconfig le0 down ifconfig le0 ${i}.0.0.2 broadcast ${i}.255.255.255 netmask 255.0.0.0 up ping -c 2 ${i}.255.255.255 2>&1 >/tmp/responses done Check the syntax of ifconfig (and where it is, it might not be in the normal PATH) as I've not used an old Sun for a while. Ditto for ping. It's in /usr/etc/ping on my IRIX boxes, /sbin/ping on recent Solaris, but I can't remember where it is in SunOS. Don't be tempted to simplify the sript by using the "local broadcast" address of 255.255.255.255 every time, as some things deliberately do not respond to that (my HP printers don't, nor do my switches). Don't forget to restore the original address with "ifconfig le0 111.0.0.1 broadcast 111.255.255.255 netmask 255.0.0.0 up" when you've finished :-) It'll take a while to work through the class C range, because ping will take a while to time out on each network number :-) Say two seconds per network, thats (224-192) * 256 * 256 * 2 seconds, about 4 million seconds, or just over 48 days. Oh, and you'll probably want to refine my shell script to eliminate the unneccesary lines generated by ping recording responses from the Sun itself, and the headers. You don't need 12 million extra lines in the output :-) -- Pete Peter Turnbull Network Manager University of York

22 years, 6 months

Jump to page:

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