test-drb

test-drb@ccmp.vtda.org

101090 discussions

by tothwolf＠concentric.net

I just came across a large number of loose 2102 chips in a junkbox, and wondered if anyone has a schematic of a test circuit for these. I'm not sure how many of them there are yet, but they all appear to be from the same batch; AM9102BPC/P2102A-4 7632QD [32nd week, 1976]. An couple interesting facts I dug up on these chips is that the AM9102 was AMD's first RAM product, and it was first produced in quantity in 1975. I'm thinking these chips might be a good source of ram for a 6800 based homebrew system, especially since I already have the chips and lots of wirewrap (and patience)... -Toth

23 years, 11 months

Latest Finds

by dquebbeman＠acm.org

After a trip down to Asian Pearl, Al and I took a trip down to the local recycle place. He spotted an Apple 3.5 inch External drive, the 800k variety we were discussing recently on the list. He wasn't interested, so I snagged it, and it appears to be working fine on the Mac IIci, although I wasn't sure at first, as it took me a while to find any 800k disks. Outside, I found an IBM Type 9331 011 8 inch external floppy drive, a nice black enclosure with the IBM logo in the oval badge set at 45 degrees, like the PS/2 line logos were. The interface connector on the rear has 37 pins and so I'm hoping it's the same as the interface on the old IBM floppy interfaces that had a 37-pin external connector. Anyone know what these drives were used with, and will I luck out on the interface? It needs cleaning... Also, an IDE removable harddrive carry case & two mounting frames, so I can start carrying serious storage two & fro the orifice, er, office. No blinkenlights, although the poprietor indicated he'd dumped a bunch of old stuff six months ago. Oh well, the way he does this is he leaves a pallet out front for people to stack stuff on. I'll start checking more often. Anyway, total damage for the above: eight bucks; five for the Apple drive, two for the IBM floppy, and 1 for the IDE shuttles. -dq

23 years, 11 months

Latest Finds

by dquebbeman＠acm.org

> I got a type 9331 model 011 with an AS/400 system... I > think. When I get home, I'll look at it (and its //manual// :) > again. Excellent, and thanks in advance! -dq

23 years, 11 months

Tape dumping programs for Unix/Linux...

by cdl＠proxima.ucsd.edu

> From: "Stan Sieler" <sieler(a)allegro.com> > To: cdl(a)proxima.ucsd.edu (Carl Lowenstein), classiccmp(a)classiccmp.org, > classiccmp(a)classiccmp.org > Date: Fri, 3 May 2002 12:10:42 -0700 > Subject: Re: Tape dumping programs for Unix/Linux... > Priority: normal > In-Reply-To: <200205030710.AA16219(a)proxima.ucsd.edu.UCSD.EDU> > > Re: > > > Look for a program named "copytape". It copies tapes including the > > block structure, file marks, etc. Unlike dd(1) which only really > > works if all blocks are the same size and there is only one file > > on the tape. It can copy tape-drive to tape-drive or tape-drive to > > disk file, and puts markers in the disk file to indicate the > > structure of the data on the tape. > > > > The versions I found do a fair job of copying a tape...but not > a complete job (particularly for DDS and DLT tapes). > > Why? > > It doesn't know about "setmark". > > On a DDS (DAT) drive, you can have a data record (of variable length, > not just multiples of 128 or 256 bytes, BTW), an EOF (end-of-file mark), > a setmark, or an end-of-tape indicator. OK. It _was_ written long before anything as smart as a DAT drive had been devised. Why do you stress "data record not just multiples of 128 or 256 bytes"? Oh, this is qualified by "on a DDS drive". Certainly 7-track and 9-track 1/2" drives could have fairly arbitrary data records. I have seen tapes with records as short as 14 bytes, and as long as 65535 bytes. Also pre-DLT tapes (DEC TK50) with 1MB records, but only to be read by a MicroVax not a PDP11. > >From "man mt" on HP-UX (since at least 1992, so it fits the 10 year rule, too > :) > DDS format devices also support setmarks which are hierarchically > superior to filemarks. A setmark is used to delineate a group (set) > of files. Reading a setmark is also returned as a zero-length read. > The two can be distinguished by unique bits in the mt_gstat field. > > (In fact, #$%^ HP took out the above text from the 10.20 "man mt" doc, leaving > just a bare reminder that setmarks exist) > > Who uses setmarks? Backup software that wants to be able to locate > files quickly. > > E.g., consider a modified tar/gtar that writes an EOF after every > file, and a setmark after every 1000 files, and also writes s table > of contents (list of files to be backed up) at the start of the tape. > If the user says "restore file FOO", the software can read the table of > contents and determine that FOO is file, say, 2349. It can then issue > two "forward setmark" commands, and then 349 "forward EOF" (or "forward > filemark" or "forward space file") commands to quickly get to the file. > > DDS drives can find a setmark very quickly, faster than they can find > an EOF. > > So....any software trying to *accurately* duplicate a tape should > record the fact a setmark was seen, as well as data record and EOFs > and errors :) As I recall, DDS tapes can also have two partitions, independently writeable. So the tape index can be written onto the first partition _after_ the data is written on the second partition. I don't know any common software that takes advantage of this. carl -- carl lowenstein marine physical lab u.c. san diego clowenstein(a)ucsd.edu

23 years, 11 months

2102 SRAM test circuit?

by dwightk.elvey＠amd.com

Hi One could throw together a simple socket and connector circuit to put on a parallel printer port. Use a '273 to increase the number of outputs and use one pin as the input. The pins for the 2102 are 1,2,4,5,6,7,13,14,15 and 16 are address lines. 3 is MWR\. 11 is data in and 12 is data out. 10 is +5 and 9 is ground. You do need a bi-directional parallel port. Check out : http://www.lvr.com/jansfaq.htm for ideas on how to control the printer port of a PC ( I would do it with Forth, myself but most others would use C or something ). Write a March "C" and pause between passes for a few seconds to check retention. Dwight >From: Tothwolf <tothwolf(a)concentric.net> > >I just came across a large number of loose 2102 chips in a junkbox, and >wondered if anyone has a schematic of a test circuit for these. I'm not >sure how many of them there are yet, but they all appear to be from the >same batch; AM9102BPC/P2102A-4 7632QD [32nd week, 1976]. An couple >interesting facts I dug up on these chips is that the AM9102 was AMD's >first RAM product, and it was first produced in quantity in 1975. > >I'm thinking these chips might be a good source of ram for a 6800 based >homebrew system, especially since I already have the chips and lots of >wirewrap (and patience)... > >-Toth > >

23 years, 11 months

Looking for...

by vance＠ikickass.org

A power supply for an RS/6000 397. Peace... Sridhar -- "How do you fight such a savage?" "With heart, faith, and steel. There can be only one." -MacLeod and Ramirez, "Highlander"

23 years, 11 months

Available.

by vance＠ikickass.org

Anyone need a power supply for an RS/6000 380/390/390H/3AT/3BT/3CT? Peace... Sridhar -- "How do you fight such a savage?" "With heart, faith, and steel. There can be only one." -MacLeod and Ramirez, "Highlander"

23 years, 11 months

Mac SE PC Drive Card

by univac2＠earthlink.net

I picked up another Mac SE today, and it's got a "Macintosh SE PC Drive Card" installed in it, with a big connector on the back of the SE. What is the card for? -- Owen Robertson

23 years, 11 months

SunOS4 and Sun i386,, ifconfig -a plumb

by fmc＠reanimators.org

JP Hindin <jplist(a)globe.net.nz> wrote: > I see le0 a lot, but I picked up ie0 from my Sun 4/470, which I'm using on > the 386i. Is this an error on my part? Should I try and set up le0 > instead? Maybe. ie is the driver for an Intel Ethernet chip/card (I have vague recollections of the card being a Multibus card in a VME-to- Multibus frame in a Sun 4/370). le is the driver for an AMD LANCE chip. I can't remember what Ethernet hardware is in the 386i, but a LANCE-based design would not be surprising. Does your 386i boot at all? If so I would expect it to tell you at boot time what devices the kernel is finding. If you can log in, the dmesg command should replay those messages for you (if they're still in the kernel's buffer). -Frank McConnell

23 years, 11 months

Tape dumping programs for Unix/Linux...

by cdl＠proxima.ucsd.edu

> From: "Stan Sieler" <sieler(a)allegro.com> > To: "Douglas H. Quebbeman" <dquebbeman(a)acm.org>, > "ClassicCmp List" <classiccmp(a)classiccmp.org> > Date: Thu, 2 May 2002 12:06:37 -0700 > Subject: Re: Tape dumping programs for Unix/Linux... > Cc: fmc(a)reanimators.org > In-Reply-To: <000701c1f1e2$a795cd80$e401a8c0(a)tegjeff.com> > Content-Transfer-Encoding: 7BIT > > Re: > > > The emulator community is vigorously using a tape image container > > format known as TAP for precisely this purpose. > > > > Each record from tape is written to file prefixed *and* suffixed > > by a four-byte record length in little-endian format. A zero- > > length record is represented by a 4-byte value of zero; although > > intuition might call for 8-bytes (a prefix & suffix with nothing > > in between), this is not the case. The convention appears to come > > directly from FORTRAN 77's handling of unformatted sequential files. > > > > And EOF is represented by two consecutive zero-length records. > > Darn...sounds like a subset of what I use. I'd be interested > in knowing more about TAP (with an eye towards adopting use of it), > and would suggest some possibly missing features might be: Is there any more information on "TAP" other than the program that I find with Bob Supnik's simh stuff, namely "mtdump" that produces a "TAP" image given a list of files? It would be nice if someone else had already written the program that reads a real physical magtape and produces a "TAP" image. carl

23 years, 11 months

APPLEVISION Monitor

by mythtech＠mac.com

>The problem is that the popular U.S. vendors expend entirely too much of >their >resources on packaging, thinking, perahaps correctly, that it will help >sales, >but they forget, oir perhaps not, that the individualized packaging will make >their systems difficult to upgrade over time, thereby making the long-term >usefulness of considerably less value. Apple has taken this to the extreme, >as only a vendor knowing he has a market segment to himself could do. Most of the system manufacturers WANT to make it hard to upgrade the system. They don't want you swapping parts to renew the life of your machine... they want you to just buy a whole new machine every few years. These upgrade impared designes are deliberate. -chris <http://www.mythtech.net>

23 years, 11 months

APPLEVISION Monitor

by mythtech＠mac.com

>While the logical replacement has never been a problem, the rounded front >that >fits the case is a virtually impossible thing to replace by the time the >drive >needs replacment. They seem to require a rounded drawer front with no bezel >of the drive. Whereas the bezel can be removed easily enough, finding a >drive >with that rounded front that fits, precisely, the slot in the plastic >front-face of the box is a problem. The part number is seemingly never >available more than 90 days after the computer is no longer an off-the-shelf >item. The last HP I had to do a CD swap on, I gave up finding a replacement "HP" drive, and just found the same model Mitsumi drive, then swapped the front bezel off the drawer. Of course, finding an 8x multi-year old Mutsumi CD drive was a challenge in itself (I tried other Mitsumi's, but on newer ones, and on every other CD drive I found, the drawer position and or mounting clips had changed, so there was no way to align it or put the old bezel on it). One more reason I build my own PCs these days. -chris <http://www.mythtech.net>

23 years, 11 months

Tape dumping, bad blocks.

by cdl＠proxima.ucsd.edu

> From: Raymond Moyers <rmoyers(a)nop.org> > To: classiccmp(a)classiccmp.org > Subject: Re: Tape dumping, bad blocks. > Date: Fri, 3 May 2002 01:01:59 -0500 > In-Reply-To: <200205030508.BAA32513(a)conman.org> > > > Funny, on the 9 track tape you dont confront this issue. > 9 track tape is 8 bits + parity right ? so here a bad bit dont > cause you to lose the ability to get the next byte and know > that its a valid byte, a physical superiority it has over the > serial streamers ?. > > Or am i assuming too much again. I think you are assuming that there will never be a dropout over the complete width of the tape. i.e. there will always be at least one "1" bit passing the read head. Data clocking is essentially done on the inclusive OR of all channels, so if they all drop out, you have lost your place. carl -- carl lowenstein marine physical lab u.c. san diego clowenstein(a)ucsd.edu

23 years, 11 months

OT: WTB: Ethernet Hub/Switch

by torquil＠rockbridge.net

Sorry for being a bit off-topic.... I ran out of ports a few weeks ago so i am looking to buy a 4-5 port 10mbit or so ethernet hub or switch. Contact me off-list. Thanks, Torquil MacCorkle III Lexington, Virginia

23 years, 11 months

Tape dumping programs for Unix/Linux...

by erd_6502＠yahoo.com

So I finally got this TSZ07 that I've been wanting for a while so I can archive a mountain of magtape I have (including System III sources for the 11/780, on up to distro tapes of the 1990s). I can use dd to slurp stuff off of tape, but it's tedious. What tools are people using for tape archiving under Linux or Solaris? AIX seems to come with "tcopy" that essentially pulls everything off the tape until logical or physical EOT. I'm looking for something similar - point it at the drive and siphon it on down. At present, because of cable reach, I am talking to the tape drive through an Adaptec AHA1460 PCMCIA SCSI interface on a Dell Latitude LM running RedHat 5.2. I can address the drive fine and dump files with dd and cat. I'm looking for a bulk data slurper, source or RH RPM. I'm willing to throw this beast on the SPARCstation 5, but I'd rather not put it in that corner just yet. At the moment, the drive is several dozen times larger than the computer controlling it. -ethan __________________________________________________ Do You Yahoo!? Yahoo! Health - your guide to health and wellness http://health.yahoo.com

23 years, 11 months

Tape dumping, Rays epiphany

by rmoyers＠nop.org

To Wit (about dd blocking handling) The original need for dd came with the 1/2" tapes used to exchange data with other systems and boot and install Unix on the PDP/11. Those days are gone, but the 9-track format lives. To access the venerable 9-track, 1/2" tape, dd is superior. With modern SCSI tape devices, blocking and unblocking are no longer a necessity, as the hardware reads and writes 512-byte data blocks. ( what i was familiar with ) However, the 9-track 1/2" tape format allows for variable length blocking and can be impossible to read with the cp command. The dd command allows for the exact specification of input and output block sizes, [[and can even read variable length block sizes, by specifying an input buffer size larger than any of the blocks on the tape.]] (Stan was right on target here eh ?) Short blocks are read, and dd happily copies those to the output file without complaint, simply reporting on the number of complete and short blocks encountered. Murphy's Law was postulated long before digital computers, but it seems it was specifically targeted for them. When you need to read a floppy or tape, it is the only copy in the universe and you have a deadline past due, that is when you will have a bad spot on the magnetic media, and your data will be unreadable. To the rescue comes dd, which can read all the good data around the bad spot and continue after the error is encountered. Sometimes this is all that is needed to recover the important data. Example dd bs=265b conv=noerror if=/dev/st0 of=/tmp/bad.tape.image Yup .. using cat to do the same thing, it gets the err signal and drops, but dd can be told to ignore it So in this case its clearly superior, and the *only* tool for 9 track tapes, ( due to the block handling ) So i stand before you better educated. thx to those that filled in the missing bits Raymond

23 years, 11 months

Tape dumping programs for Unix/Linux...

by cdl＠proxima.ucsd.edu

> Date: Thu, 2 May 2002 02:01:33 -0700 (PDT) > From: Ethan Dicks <erd_6502(a)yahoo.com> > Subject: Tape dumping programs for Unix/Linux... > To: classiccmp(a)classiccmp.org > Sender: owner-classiccmp(a)classiccmp.org > Reply-To: classiccmp(a)classiccmp.org > > > So I finally got this TSZ07 that I've been wanting for a while so I can > archive a mountain of magtape I have (including System III sources for > the 11/780, on up to distro tapes of the 1990s). I can use dd to slurp > stuff off of tape, but it's tedious. What tools are people using for > tape archiving under Linux or Solaris? AIX seems to come with "tcopy" > that essentially pulls everything off the tape until logical or physical > EOT. I'm looking for something similar - point it at the drive and > siphon it on down. Look for a program named "copytape". It copies tapes including the block structure, file marks, etc. Unlike dd(1) which only really works if all blocks are the same size and there is only one file on the tape. It can copy tape-drive to tape-drive or tape-drive to disk file, and puts markers in the disk file to indicate the structure of the data on the tape. Copytape is a "classic" piece of software, its source file begins as follows: /* * COPYTAPE.C * * This program duplicates magnetic tapes, preserving the * blocking structure and placement of tape marks. * * This program was updated at * * U.S. Army Artificial Intelligence Center * HQDA (Attn: DACS-DMA) * Pentagon * Washington, DC 20310-0200 * * Phone: (202) 694-6900 * ************************************************** * * THIS PROGRAM IS IN THE PUBLIC DOMAIN * ************************************************** * * July 1986 David S. Hayes * Made data file format human-readable. It should be available at numerous FTP sites. carl -- carl lowenstein marine physical lab u.c. san diego clowenstein(a)ucsd.edu

23 years, 11 months

Tape dumping programs for Unix/Linux..

by cdl＠proxima.ucsd.edu

> From: Raymond Moyers <rmoyers(a)nop.org> > To: classiccmp(a)classiccmp.org > Subject: Re: Tape dumping programs for Unix/Linux.. > Date: Thu, 2 May 2002 20:15:37 -0500 > In-Reply-To: <3CD16EDB.31791.1013160B@localhost> > > On Thursday 02 May 2002 18:52, you wrote: > > > Someone had copied a tape whose records were 16 KB long using software > > that expected the records to be 8192 bytes longs ... and only asked > > for 8192 bytes in each read() request. > > Now i really do find this interesting > > Lets scope out some examples to illustrate my focus. > > On a floppy or a hard disk as examples you have > pad data inbetween its records these are usually > all FF's constant stream on 1's in other words > then an address mark like FE followed by the header data > Head Sector Cylinder ,, then some more FF's then a start > of data mark the block of data then the CRC .. then all > else is ignored ,, be it artifacts from a prev write ( hub speed jitter ) > or whatever .. the controller is looking for its string of a minimum > number of 1's then the FE and so it repeats all round the disk. > > During lowlevel formatting you are basically building an image > of this track .. complete with the between sector filler of FFs > amd dumping a whole track at once with the write track command. > > These devices are random access, but when you pull the image > off the device using it as a streamer, you are not getting > the filler bytes the address marks or the crc's your getting > only the content of the sectors (soft physical records) > back to back a raw spool off a unix device with a typical > device driver gives you the data without the controler > interested bits off the media. > > I would assume that any decent unix driver up to the minimal > expectations of behavior should act the same, including > that for a proper interface to a 9 track tape. > > If the record length is varible, then is not the record length > in the block headder ? and should not the driver read > that from the headder then xxx bits of data ? No. You haven't been around tape drives long enough. The tapes are not preformatted with block headers. They are written sequentially. In general, a tape drive can only record forward and add data beyond whatever has already been written. > it would seem that any tape used as a random access > block device, that ever had a record re written would > have garbage (from a prev update of that record) > in the block, > just like on a floppy where this happens all the time, > (jitter again) and the controller simply ignores looking > for its resetting minimal number of FF's and the next > address mark Only some very special tapes with extra tracks for tape mark information can be reliably used as random-access block devices. The classic example is DECtape, 3/4 inch wide on 3 inch reels. Pre-formatted into blocks of 129 12-bit words or other interesting combinations. > ( im ignoring the hard sector media with a hole for > every sector, but it would still apply in this scope > albeit a bit differently) > > Now .. excuse me, but ive been around this stuff > for a long time, and i think ive got a really firm grasp > of the minimal amount of things needed in place for > any data-to-media, data-from-media scheme to work. > > So, do i have this right ? No. > That if i spooled off a 9 track tape, and assuming no > non-recoverable media errors, that i would *not* > get all of the data from all the records and without > trailing garbage and the controler interested bits left out ? Your tape-reading program might truncate all block lengths to the length that it was "expecting". Or just quit after the first file instead of reading all the files on the tape. > Knowing the proper expected behavior of any unix > driver i could name ... i find this rather .... > well unexpected. Nobody has said that Unix has well-designed tape drivers. carl -- carl lowenstein marine physical lab u.c. san diego clowenstein(a)ucsd.edu

23 years, 11 months

One-upsmanship (was: Secret Mac

by ajp166＠bellatlantic.net

From: Cameron Kaiser <spectre(a)stockholm.ptloma.edu> >> If a formula for determining classic computer cool factor gets finalized, >> I'd like to create a calculator script on the VCF website so that people >> can enter their parameters and have their score automatically computed. >> >> We need a unit or label for this number. > >The neuron. Feh! Too common, everyone has a few many don't use them. First it should be dimensionless, those are weird enough. If not then like DB (DeciBell) which will give it a log or exponential character though I'd be interested in seeing other oddly shaped numbers. A possible name? Calcula with a range of values from microcalcula (watch calc or smaller) to Kilo or maybe megacalcula(Sage! or other beast). Allison

23 years, 11 months

Tape dumping programs for Unix/Linux...

by fmc＠reanimators.org

> Here you are talking about a data tape with fields that make up records > where the records are all the same size and the fields being varaible > length inside the record but repeating in all the other records. No, I am talking about a data tape with a physical structure that can be interpreted as a sequence of physical records (each of which has a length) and end-of-file (EOF) marks. The physical records can be blocks of multiple logical records as well. There are also inter-record gaps that separate the physical records and EOFs from each other, and I suppose the information about how long those are may be of interest to someone too, it just hasn't been of interest to me yet and I certainly don't see an obvious way to get that information using common hardware and software. > But a tape like this, from the days when tapes was used as random > access devices is not the format of a system archive tape is it ? Just because tapes were used as random access devices, that doesn't mean they were always used that way or were particularly good for it. And a system archive tape didn't need to be structured for random access. So, take classic MPE :STORE format. I'm thinking that it defaults to having a maximum on-tape block (physical tape record) length of 8192 bytes, but that's overrideable by the user and variable in any case. A single-volume (single-reel) :STORE set has several parts: (a) two files that could actually contain useful bits if this is really a :SYSDUMP tape (each is followed by its own EOF, even if not present); if this isn't a :SYSDUMP tape then there are two consecutive EOFs at the start (b) a :STORE label, which is a single 80-byte tape block followed by an EOF (c) a :STORE directory, which is written as blocks of up to the maximum block length; each block contains a number of 24-byte logical records which give the names of the files to be stored on this volumeset; again, this is followed by an EOF (Note this presents the order in which the files are stored on the volumeset) (d) user files, each of which is written as one 256-byte block containing a copy of the MPE file label followed by more blocks of actual file data, and finished off with an EOF (Note I may be forgetting some things about how user files are written to the tape; in particular I can't remember how user labels are stored; Stan may know more) (e) a :STORE trailer label, which is another 80-byte tape block followed by three EOFs A multi-volume :STORE set makes for some additional complexity. Volumes after the first don't have the two files and EOFs and just start with the :STORE directory, plus once you get to multi-volume you also need to deal with whether a file was split across volumes. OK, maybe I could kinda sorta do this by cat'ing the tape files to disk files and writing some code to kludge around the lost physical-record boundaries. I'm not sure about the user files but I have some ideas to try. But frankly I'd rather have a container file format and tools to collect and preserve the information. Then I can treat the container file like a tape. If I can write some descriptive text in the container file as well, that would be like sticking a label on the tape to me. > If it was me i would spool the whole raw image to disk, and work > with it there ,, it can certainly be massaged into any format you > like after that ... That is what I want too. The problem is, the "raw image" includes information other than the bytestream. If you use bytestream-oriented tools like cat, you lose that other information. -Frank McConnell

23 years, 11 months

Hauppauge 4860 mboard question

by cpg＠aladdin.de

Hi, don't know whether this is appropriate for this list, but I'll ask anyway (it's over 10 years old). I've got a machine which has a 4860 motherboard, this a combi 80486/80860 with EISA slots. Overall it works fine, but there is a small problem enabling the cache. The battery is broken, so after turning off it loses it's BIOS and EISA configuration. When this happens I can go into the BIOS and setup everything, *enable the cache*, and boot from ide disk. Problem is since the EISA configuration is still invalid, the SCSI controller does not work. After I setup the EISA configuration with the DOS CF.EXE utility, the SCSI controller works, but the cache is disabled, and I cannot re-enable it in the BIOS menu (menu item is disabled). What can the problem be? Anyone experienced s/th similar? regards, chris

23 years, 11 months

Request for Help with the Definicon DSI-32 (NS32032 PC Coprocessor board)

by morgarws＠mh.us.sbphrd.com

I'm looking for any documentation and software for the Definicon DSI-32 (NS32032 PC/XT coprocessor board). ... anything would be useful! Thanks in Advance, Bill Morgart morgarws(a)Molbio.sbphrd.com

23 years, 11 months

Tape dumping programs for Unix/Linux..

by csmith＠amdocs.com

> -----Original Message----- > From: Raymond Moyers [mailto:rmoyers@nop.org] > If i might use the 1991 mips 3k sysVr4 unix thats on my old sony > NeWS again as an example, its tar program cant write > or read from a file. its only provided function is to/from > the tape device to the file system,, how absurd ! Absurd? It is for making "tape archives..." :) On the other hand, I'm sure there must be some way to make it work, though, if you wanted an on-disk archive, I'm sure they would have expected you to use ar. ;) Chris Christopher Smith, Perl Developer Amdocs - Champaign, IL /usr/bin/perl -e ' print((~"\x95\xc4\xe3"^"Just Another Perl Hacker.")."\x08!\n"); '

23 years, 11 months

Need IDT 7M624 Info

by Innfogra＠aol.com

In a message dated 5/3/02 2:22:42 AM Pacific Daylight Time, tothwolf(a)concentric.net writes: > http://members.aol.com/innfogra/idt624a1.jpg > > Based on looks alone, I'd guess it is some type of RAM. IIRC, IDT did make > some RAM, but also made quite a few other special purpose chips. > > > http://members.aol.com/innfogra/idt624a2.jpg > > This link didn't work btw. > > Fixed the broken link, thanks Toth. The bottom is the same as the top, 8 more small gold caps. I remember something about them being 1 Meg something or other. That something or other is what I am trying to figure out of course. I wonder if they could be an EEPROM like another smaller chip I have. That one is listed on ebay at the moment as a SEEQ EEPROM. It uses a similar but smaller IDT chip like this as a controller. <A HREF="http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=1728103123">eBay item 1728103123 (Ends May-09-02 12:53:43 PDT ) - Unusual Gold SEEQ 1 Meg E</A> Maybe these are a 1 Meg EEPROM based on 64K cores? Anyone got a book out there? Thanks for the help. Paxton Astoria, OR

23 years, 11 months

Mac SE PC Drive Card

by mythtech＠mac.com

>I picked up another Mac SE today, and it's got a "Macintosh SE PC Drive >Card" installed in it, with a big connector on the back of the SE. What is >the card for? Apple made a PC compatible drive that worked with the SE and the Mac II. It needed a special card to connect to the computer (why they couldn't just use the already present Floppy port I have no idea). There was an SE PDS slot card (the one you have), and a NuBus version for the Mac II. They made this for the era before they were shipping the "SuperDrives" that could read/write 1.44 disks, and PC format disks. It ONLY works with the SE or the Mac II. I don't know if it will work with the SE FDHD. If you had the Mac II NuBus card, I would ask you for it, but I already have the SE version. -chris <http://www.mythtech.net>

23 years, 11 months

Jump to page:

2026

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