test-drb October 2004

test-drb@ccmp.vtda.org

245 participants
540 discussions

South Pole. (was: "System Technology Associates"? SDI-ESDI adapter)

by dwight.elvey＠amd.com

>From: "Ethan Dicks" <dickset(a)amanda.spole.gov> > >On Fri, Oct 22, 2004 at 01:58:22PM -0700, Dwight K. Elvey wrote: >> Hi Ethan >> Wouldn't you do daylights saving in the winter instead >> of the summer? > >Everybody does it in their summer, northern hemisphere and southern >hemisphere... it's summer here *now*. > >-ethan > Hi Ethan Of course, your summer is different than mine. What was I thinking. Dwight

20 years, 2 months

C compilers for RSTS/E?

by aek＠spies.com

What I was getting at is that the RSX native file naming was 9.3, not 6.3. -- It is a DOS-11 (FLX) tape.

20 years, 2 months

C compilers for RSTS/E?

by aek＠spies.com

There was a version from Whitesmiths. I tried to get them to release it, and they were happy to, but the didn't have any copies - the tapes they had got somehow damaged or destroyed. If anyone has a copy, it would be a simple matter to get them to allow it to be distributed -- I've just put a version for RSX up at www.bitsavers.org/bits/dec/pdp11/magtapes/ 1 BLDECH.CMD [ 4, 1] <000> Jan 0, 1970 72 bytes [tape mark] 2 BUILD .CMD [ 4, 1] <000> Jan 0, 1970 1038 bytes [tape mark] 3 BUILDI.CMD [ 4, 1] <000> Jan 0, 1970 1108 bytes [tape mark] 4 BUILDR.CMD [ 4, 1] <000> Jan 0, 1970 904 bytes [tape mark] 5 C .CMD [ 4, 1] <000> Jan 0, 1970 228 bytes [tape mark] 6 CCC .BAS [ 4, 1] <000> Jan 0, 1970 1222 bytes [tape mark] 7 CFPP .CMD [ 4, 1] <000> Jan 0, 1970 232 bytes [tape mark] 8 CHDR .OBJ [ 4, 1] <000> Jan 0, 1970 532 bytes [tape mark] 9 CLIB .OLB [ 4, 1] <000> Jan 0, 1970 77824 bytes [tape mark] 10 CPM .OBJ [ 4, 1] <000> Jan 0, 1970 8642 bytes [tape mark] 11 CRIGHT. [ 4, 1] <000> Jan 0, 1970 1010 bytes [tape mark] 12 CTYPE .H [ 4, 1] <000> Jan 0, 1970 904 bytes [tape mark] 13 ECHO .C [ 4, 1] <000> Jan 0, 1970 824 bytes [tape mark] 14 ECHO .DOC [ 4, 1] <000> Jan 0, 1970 898 bytes [tape mark] 15 END .MAC [ 4, 1] <000> Jan 0, 1970 272 bytes [tape mark] 16 FCC .BAS [ 4, 1] <000> Jan 0, 1970 1226 bytes [tape mark] 17 FHDR .OBJ [ 4, 1] <000> Jan 0, 1970 536 bytes [tape mark] 18 FLIB .OLB [ 4, 1] <000> Jan 0, 1970 65536 bytes [tape mark] 19 HEX .OBJ [ 4, 1] <000> Jan 0, 1970 7312 bytes [tape mark] 20 INSTAL.DOC [ 4, 1] <000> Jan 0, 1970 6606 bytes [tape mark] 21 LBY .OBJ [ 4, 1] <000> Jan 0, 1970 10002 bytes [tape mark] 22 LIMIT . [ 4, 1] <000> Jan 0, 1970 1050 bytes [tape mark] 23 LINK .CMD [ 4, 1] <000> Jan 0, 1970 482 bytes [tape mark] 24 LNK .OBJ [ 4, 1] <000> Jan 0, 1970 19966 bytes [tape mark] 25 LRD .OBJ [ 4, 1] <000> Jan 0, 1970 2832 bytes [tape mark] 26 MATH .H [ 4, 1] <000> Jan 0, 1970 248 bytes [tape mark] 27 MOVEMT.CMD [ 4, 1] <000> Jan 0, 1970 212 bytes [tape mark] 28 P1 .OBJ [ 4, 1] <000> Jan 0, 1970 50160 bytes [tape mark] 29 P2 .OBJ [ 4, 1] <000> Jan 0, 1970 46638 bytes [tape mark] 30 P2CONF.OBJ [ 4, 1] <000> Jan 0, 1970 2714 bytes [tape mark] 31 PP .OBJ [ 4, 1] <000> Jan 0, 1970 21094 bytes [tape mark] 32 REL .OBJ [ 4, 1] <000> Jan 0, 1970 9328 bytes [tape mark] 33 RSX .H [ 4, 1] <000> Jan 0, 1970 2480 bytes [tape mark] 34 SBREAK.MAC [ 4, 1] <000> Jan 0, 1970 454 bytes [tape mark] 35 STD .H [ 4, 1] <000> Jan 0, 1970 1740 bytes [tape mark] 36 STDIO .H [ 4, 1] <000> Jan 0, 1970 1286 bytes [tape mark] 37 STDTYP.H [ 4, 1] <000> Jan 0, 1970 1392 bytes [tape mark] 38 TEST .CMD [ 4, 1] <000> Jan 0, 1970 308 bytes [tape mark] 39 TESTR .CMD [ 4, 1] <000> Jan 0, 1970 228 bytes [tape mark] 40 ULIB .OLB [ 4, 1] <000> Jan 0, 1970 23040 bytes [tape mark]

20 years, 2 months

Difference 23512 and 27512 Eprom

by dwight.elvey＠amd.com

Hi I guess the next thing is to find a pinout for the 23512 to see if they have a select that is inverted that might need to be patched around to read on a standard programmer. Dwight >From: birs23(a)zeelandnet.nl > >Dwight, not missing the discussion ;-) > >At 19:15 22-10-2004, you wrote: > >> >From: ard(a)p850ug1.demon.co.uk >> > >> >> >> >> Hi, >> >> >> >> I know very little about electronics and eproms so this question might be >> >> really easy. I would like to know what the difference is between a 23512 >> >> eprom and a 27512 and if there are any differences if its possible to >> make >> > >> >I thought the 23512 was the mask-programmed part (not an EPROM), and is >> >otherwise the same device. You should be able to read it (unless your >> >programmer tries to be clever and read the manufacturer's ID word, etc). >> > >> >-tony >> > >> >>Hi Tony >> I think you are right about the 23xxx being mask versions. >>The problem with the newer EPROM parts is that they do not >>require pulsing of the programming voltage. Many programmers >>simply leave the programming voltage high while reading or >>verifying. This is real bad for mask parts. Also, most mask >>parts use the programming voltage pin as another select. >>This means that it may need to be in the opposite state that, >>even a programmer that allows setting of the program voltage, >>may not be in the right state to read. >> Also, I think this fellow is off the list and doesn't realize >>that he is talking to a list. I suspect he is missing our >>conversations related to his issue. >>Dwight > >

20 years, 2 months

South Pole. (was: "System Technology Associates"? SDI-ESDI adapter)

by dwight.elvey＠amd.com

>From: "Ethan Dicks" <dickset(a)amanda.spole.gov> > >On Thu, Oct 21, 2004 at 10:54:49PM -0400, John Allain wrote: >> Hey, here's a semintelligent, if OT, question. >> What time zone is at the South Pole? > >Well... the easy answer is "whichever one we want". > >In fact, the one we have selected is the one that matches where our flights >come from so it's easy to synchronize operations. That means NZST/NZDT, >since our flights come from McMurdo, and their flights come from Christchurch, >NZ (yes, we are at GMT+13 right now, and we _do_ observe daylight savings >time, even though the sun is up 24/7) > >-ethan > Hi Ethan Wouldn't you do daylights saving in the winter instead of the summer? Dwight

20 years, 2 months

Difference 23512 and 27512 Eprom

by dwight.elvey＠amd.com

>From: ard(a)p850ug1.demon.co.uk > >> >> Hi, >> >> I know very little about electronics and eproms so this question might be >> really easy. I would like to know what the difference is between a 23512 >> eprom and a 27512 and if there are any differences if its possible to make > >I thought the 23512 was the mask-programmed part (not an EPROM), and is >otherwise the same device. You should be able to read it (unless your >programmer tries to be clever and read the manufacturer's ID word, etc). > >-tony > Hi Tony I think you are right about the 23xxx being mask versions. The problem with the newer EPROM parts is that they do not require pulsing of the programming voltage. Many programmers simply leave the programming voltage high while reading or verifying. This is real bad for mask parts. Also, most mask parts use the programming voltage pin as another select. This means that it may need to be in the opposite state that, even a programmer that allows setting of the program voltage, may not be in the right state to read. Also, I think this fellow is off the list and doesn't realize that he is talking to a list. I suspect he is missing our conversations related to his issue. Dwight

20 years, 2 months

Excercising vintage items - was: Commodore 8010 IEEE-488Acoustic Modem ?

by dave04a＠dunfield.com

>> I have to admit - I do not have a burning desire to connect to anything >> at 300 bps --- But I do have a burning desire to see it work. > >Understandable. If you really need a serial port, there are faster items >out there... but AFAIK, at the moment, that's the fastest you have... I don't *need* a serial port (I have a real one on my SuperPET) ... My point is that I don't like to just put stuff on the shelf ... I like to get it working. >> In this case, I think it would be "cool" to be able to demonstrate a PET >> connected through the 8010 IEEE modem to my Hayes S-100 modem (also a 103 type) >> in an Altair running a BBS system - This would show how it really worked! >> - but I don't expect anyone to actually want to use such a setup for any >> other purpose. > >Sure. I even have a couple of devices that are handy for that - Telephone >C.O. simulators... Thats no a problem for me - One of my main lines of "day" work these days is the development of a small office PBX (www.talkswitch.com) which is very small and easily portable (good for demos), and provides full switching etc. I also do dial-up point-of-sale banking terminals, so I have lots of equipment to simulate and monitor various phone line condition - not that it's really needed to "make a call" to a demo BBS. >The other thing I do with vintage equipment is show-and-tell. Mostly at >home with friends, but I have hauled an -8/L, w/rack, w/ASR-33 to a >local convention for a computer exhibit (along with lots of C= equipment) >Unfortunately, some bastard, most likely a hotel employee (or someone >with a lockpick, since it was after hours from a padlocked room) walked off >with my Dell P-133 laptop with about two weeks of recent Open Source >work on it. The show was a success - losing two wireless cards and a >fully tricked out Linux laptop was a real bite. That really bites. Agree completely on "show and tell" - I also find it's a great ice-breaker, I don't know how many people have come to the office for meetings of one sort or another and almost immediately start talking about seeing something on my site which was their first computer. Often said meeting is followed by a trip to the basement to play with the toys. Regards, Dave -- dave04a (at) Dave Dunfield dunfield (dot) Firmware development services & tools: www.dunfield.com com Vintage computing equipment collector. http://www.parse.com/~ddunfield/museum/index.html

20 years, 2 months

Flash ADC selection, or other approach?

by tomj＠wps.com

I'm a fair designer, but could use a hand at parts selection, to build a device to suck data off an old rotating memory. Generally-speaking, I need a little box (black box) that can slurp serial data off five parallel serial streams, synchronously. The native data rate is 80KHz, there are 128 sectors (sector = 32-bit word) per track, 4096 bits/track. Our previous discussion imposing 16X (say) sample rate on 12.5uS/bit is 1.28Msamples/sec, five channels. 4 bits vertically seems adequate. All five tracks must be sampled at the same time; internal machine timing is derived by random logic hung off the timing tracks. Channel-to-channel skew or offset would render the data worthless. Can't read one track, then the next, etc. (That said, it would be possible, if troublesome, to read only two channels at a time, where one channel is always the clock track, but that presupposes the clock track is perfect. I think with all five simultanously sampled I could "fix" a glitch in the clock track and re-write it, but that process will degrade if not simultaneous. I don't think the hardware savings are worth it.) With that assumption, it's 65536 samples/track, five tracks. With a trivial architecture of one 4-bit sample stored per memory byte, it's 320K bytes. Seeing how even little SBCs have a megabyte this will do. As I see it, my two practical (read: lazy) choices are build something around a little SBC, or some kludge around a "PC". The SBC approach: There are many $99 single board computers, many with A/D, but most of them are obsessed with bit depth (10 to 16) and not samples/sec in the lower-cost range. But sticking a five 4-bit ADCs on parallel ports, and every sample-interval, strobing all ADCs and reading 5 nybbles/bytes into local RAM, and a separate command to dump sampled data to a PC via serial port. The PC approach is to somehow wangle the five ADCs into the PC such that it will accept the 65536 5-byte (5-nybble) samples with ZERO LATENCY. There's plenty of memory, but my guess is simply adapting 5 ADCs onto the PC parallel port, or funny hardware to talk USB (and I don't think USB will guarnetee me my latency) is as much work as the SBC solution, which, if coded in assembly, will be plenty fast enough and trivial to build (and easy to test). I favor the SBC approach, as it would make a useful tool for others and it's platform independent. I can't find 4-bit flash ADCs! The smallest ADC on digikey is 8 bits, which is of course fine, but Analog Device's idea of fast is 2.5uS conversion, and they're $15/each. Anyone know of 4-bit ADCs? Or am I barking up the wrong tree here?

20 years, 2 months

arix 800 - last call

by kenziem＠sympatico.ca

I have one sitting in the garage is anyone interested in it? The drives have been pulled already. Also a bunch of communications stuff Cabletrom M8FND with modimm-4, cisco CRM-3E, TPRMIM-36, EMM-E6 Tylink 3250s Westell A90-311073 Noran Tel NT95008-sij Gandalf LDS120 InterLynx 3287-NNP CISCO 1000 lan extender model 1001 -- Collector of vintage computers http://www.ncf.ca/~ba600 Open Source Weekend http://www.osw.ca

20 years, 2 months

DEC stash in VA (gov)

by g-wright＠att.net

Just what you can see looks good ... Sure would like to know whats in the boxes.... Anyone close to this, Looks interesting. Too Bad i'm in Seattle. http://cgi.govliquidation.com/auction/view?id=464866 - Jerry

20 years, 2 months

← Newer
1
...
18
19
20
21
22
23
24
...
54
Older →

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 October 2004