[cctalk] Re: Z80 vs other microprocessors of the time.
On Mon, Apr 22, 2024 at 9:18 AM Chuck Guzis via cctalk wrote: > > On 4/22/24 08:36, Lamar Owen via cctalk wrote: > > > Die real estate forced the design to do without a full 8-bit ALU. When > > you have a 4-bit ALU, and you are doing 16-bit math, you will need 4 > > cycles through the ALU. > > I don't know if this applies to the Z80, but on the 8080, 16-bit > increment/decrement is handled by a separate increment block (also used > to advance the P-counter and stack operations). Probably one of the > reasons that INX/DCX doesn't set any flags. All sorts of interesting details are covered in several of Ken Shirriff's blog posts. Here are a few: The Z-80 has a 4-bit ALU. Here's how it works. https://www.righto.com/2013/09/the-z-80-has-4-bit-alu-heres-how-it.html Reverse-engineering the Z-80: the silicon for two interesting gates explained https://www.righto.com/2013/09/understanding-z-80-processor-one-gate.html The Z-80's 16-bit increment/decrement circuit reverse engineered https://www.righto.com/2013/11/the-z-80s-16-bit-incrementdecrement.html Why the Z-80's data pins are scrambled https://www.righto.com/2014/09/why-z-80s-data-pins-are-scrambled.html
[cctalk] Re: PDP-11 thingy. What is it?
On Wed, Apr 10, 2024, 7:22 PM Carlos E Murillo-Sanchez via cctalk < cctalk@classiccmp.org> wrote: > Jonathan Chapman via cctalk wrote: > >> 1. I have read that the card and the drives were compatible with the > dec rx02 drives. Why would the CRDS even bother to redesign a card where > DEC had perfectly good working ones? Anyone know if there is any value in > keeping the FC-202 or just keep with the DEC cards? > > A lot of the third-party controllers could talk to Shugart-style 8" > floppy drives. They can also usually *format* the diskettes, which the > RX01/RX02 systems from DEC can't do -- you have to use preformatted media. > This isn't a *huge* deal since RX01 is just IBM 3740 and you can format it > on CP/M boxes, with ImageDisk, etc. There's an XXDP utility to upconvert > RX01 media to RX02, which is M2FM and very few things can work with it. > > > > Apparently a lot of small shops kept a CP/M box just for the task, the > Alspa ACI-2 I had was supposedly used like that. > > > >> 2. Any idea on that other card? > https://w2hx.com/?prefix=x/What-Is-It/PDP-11-Thing/Board1/ > > Looks like a non-DEC Qniverter -- QBus to Unibus converter. If that's > what it is, you'd plug your Unibus cable into that pair of connectors on > top and run it to whatever Unibus device you were wanting to talk to, > potentially another backplane full of Unibus stuff. Commonish upgrade on > e.g. CNC machines that were originally controlled by a PDP-11/05 or > something in one Unibus chassis, with another Unibus chassis full of > machine-specific cards. > > > > Thanks, > > Jonathan > > . > > > I spy two AM2901 4-bit slice ALUs, two N82S181 1024x8 PROMs, three > AM2911 microprogram sequencers, and an SN74150 3-to-8 line decoder. This > thing is doing arithmetic. > > Carlos. That is not an unusual bit slice architecture for a drive controller. This Dilog DQ419 also has two AM2901 ALUs and three AM2911 sequencers, and what appears to be six microcode PROMs. https://avitech.com.au/?page_id=847
[cctalk] Re: PDP-11 thingy. What is it?
On Wed, Apr 10, 2024, 4:14 PM W2HX via cctalk wrote: > Hi all, I picked up this PDP-11 thing. Can anyone help me understand what > it is? > Pictures are here: > https://w2hx.com/?prefix=x/What-Is-It/PDP-11-Thing/ > > I could not find any designation on the backplane. It is a wire-wrappable > backplane. I don't know if it is Qbus, unibus or whether it is 18 or 22 bit > addressing (this is because I am a newbie in this area). > H9270 Backplane, Page 366 (page 376 of the pdf) http://www.bitsavers.org/pdf/dec/qbus/EB-23144-18_QbusIntrfs_1983.pdf
[cctalk] Re: DEC VT340/330 ROM Cartridge
On Sat, Apr 6, 2024 at 8:26 AM Douglas Taylor via cctalk wrote: > > On 4/6/2024 11:14 AM, Tony Duell via cctalk wrote: > > On Sat, Apr 6, 2024 at 3:54 PM Douglas Taylor via cctalk > > wrote: > >> The DEC VT340 has a slot in the back of the terminal to insert a ROM > >> cartridge. I can't find any description of what this DEC labeled ROM > >> cartridge would do for you. I've seen them with V1.1 and V2.1 markings, > >> does anyone remember what additional capabilities these ROM cartridge > >> provide? > > Will the terminal work at all without that cartridge fitted?. I've had > > a quick look at the VT330 and VT340 printsets and I can't obviously > > spot any firmware ROMs on the main board schematics. So my first guess > > is that said cartridge is the terminal firmware. > > > > -tony > > Hmm, I have a VT340 that seems to pass POST but no video. It does have > a cartridge inserted into the slot, you may be exactly correct. > > Doug The VT340 I have does not have an opening on the back where the ROM slot would be. Maybe the ROM card is still there in that location, but the back cover molding was changed to remove the user accessible slot. I'd have to pull the cover off to see if the ROM board is still in that location. The VT330 I have does have a removable ROM card. That one might be a pre-production unit. Instead of mask ROMs it has EPROMs, and the manuals it came with are not production level manuals.
[cctalk] Re: typical IC kits on Amazon and elsewhere
On Sun, Mar 31, 2024 at 8:15 AM John Robertson via cctalk wrote: > > On 2024/03/30 7:53 p.m., Glen Slick via cctalk wrote: > > On Sat, Mar 30, 2024 at 5:11 PM Jonathan Chapman via cctalk > > wrote: > >>> Standard TTL 74XXX is drying up rather quickly. Futurlec still has some > >>> TTL but 7404s are all gone. Even LS is hard to find. > >> Ours comes from Mouser, between two part #s they have over 7,000 74LS04s > >> in DIP packaging in stock. Didn't check ACT, HCT, or ALS. I don't think > >> we've had a 7400 series part that we couldn't just order off Mouser in > >> recent history, and we're usually buying QTY 100. > >> > > You can also buy parts direct from TI, for example they currently show > > around around 3000 SN74LS04N parts in stock. > > > > https://www.ti.com/product/SN74LS04/part-details/SN74LS04N > > > > The prices for that part match the current Mouser prices of $0.674 > > each, or $0.519 each if you buy at least 4 tubes of 25 parts. > > > > I've bought some tubes of 74LS parts direct from TI in the last year. > > Interesting, but does TI offer free international shipping with import > duties & taxes covered if you order over $100US? > > John :-#)# My last order directly from TI was 2.5 years ago, longer than I remembered. Back in November 2021, in addition to the line item cost for each quantity of parts that I ordered, there was a total shipping charge, plus the total local WA state sales tax charge. There was no separate import charge. The shipping charge at the time seemed very reasonable. For one order of 4 tubes of DIP parts it was $7 total, with that shipping charge then split between FedEx shipping from TX for some parts, and DHL shipping from ASIA for other parts. I forget why I ordered directly from TI at the time. Maybe they had some of the parts in stock that were not currently in stock at Mouser or Digi-Key, or maybe the total with shipping was lower than at either Mouser or Digi-Key.
[cctalk] Re: typical IC kits on Amazon and elsewhere
On Sat, Mar 30, 2024 at 5:11 PM Jonathan Chapman via cctalk wrote: > > > Standard TTL 74XXX is drying up rather quickly. Futurlec still has some > > TTL but 7404s are all gone. Even LS is hard to find. > > Ours comes from Mouser, between two part #s they have over 7,000 74LS04s in > DIP packaging in stock. Didn't check ACT, HCT, or ALS. I don't think we've > had a 7400 series part that we couldn't just order off Mouser in recent > history, and we're usually buying QTY 100. > You can also buy parts direct from TI, for example they currently show around around 3000 SN74LS04N parts in stock. https://www.ti.com/product/SN74LS04/part-details/SN74LS04N The prices for that part match the current Mouser prices of $0.674 each, or $0.519 each if you buy at least 4 tubes of 25 parts. I've bought some tubes of 74LS parts direct from TI in the last year.
[cctalk] Re: Looking for an HP 9000/778 workstation B160/180
On Sun, Mar 24, 2024, 10:05 AM Keith M via cctalk wrote: > I'm looking for an HP 9000 Visualize workstation, like a B160L or B180L+. > > I'll be attending VCF East in a few weeks so might find one there. > > Has anyone used Cypress technology out of Clearwater, FL? It seems they > provide a nice, fully configured to spec turnkey solution, but there's no > doubt they charge for it. > http://www.cypress-tech.com/ > > Any better HP-specific forums or references would be appreciated! > > Thanks > Jesse of Cypress is on this list, and the vinthp...@groups.io list. I've bought an HP A990 system from Cypress direct, and other HP parts from them through eBay. You get what you pay for.
[cctalk] Re: Vmebus
On Tue, Jan 30, 2024 at 4:34 PM Paul Koning via cctalk wrote: > > There's also VXIbus, which is VMEbus with some extensions and packaging > standards for instrumentation modules. It seems to be still alive and well > today. I have a couple of PA-RISC based HP/Agilent V743/64 (E1497A) and V743/100 (E1498A) single-slot, C-size VXI embedded computers. You can run standard HP-UX on them and control VXI instrument modules installed in the same VXI mainframe. I also have a couple of 68000 based HP/Agilent E1406A VXI GPIB Command Modules, which provide a GPIB controller interface to VXI instrument modules installed in the same VXI mainframe. The versions I have can also run Instrument Basic on the E1406A as a standalone controller with a terminal interface attached to the E1406A serial port. Plus also a couple of X86 based Radisys EPC-5 or EPC-7 VXI CPU modules. I forget what versions those are. I haven't touched those in around 20 years, and forget why I have those.
[cctalk] Re: Vmebus
Oh yeah, that reminds me, I have a Sun 4/110. Never really thought much about it being a VME system, such as a Motorola MVME system. I can't say I use the Sun 4/110 at least occasionally. I don't remember the last time I powered it on. I suppose I should see if it still boots up sometime. On Tue, Jan 30, 2024 at 2:30 PM Alan Perry via cctalk wrote: > > I was given a Sun 3/260 that had been sitting in an open barn for a decade. > It is a 12-slot, 9U VME system. I got it running with its CPU board (25Mhz > 68020) and a Sun 32M memory board (the 8M board it came with has a h/w issue). > > After that people started giving me Sun VME stuff. That includes a > Computervision Sun3-based (so VME) CADDS Station that I need to get working > at some point. > > alan > > > On Jan 29, 2024, at 20:07, Bill Degnan via cctalk > > wrote: > > > > Anyone have a VMEbus system they use at least occasionally? If so, what > > make/model/config? > > Bill
[cctalk] Re: VAX 4000-200 in BA215 chassis. Can I install a KFQSA card and connect the cabinet disks to it?
On Tue, Jan 2, 2024 at 11:51 AM Jonathan Stone via cctalk wrote: > > On Tuesday, January 2, 2024 at 11:29:36 AM PST, thomasdzubin--- via cctalk > wrote: > > > Can I install the KFQSA card in my 4000-200, disconnect the internal disks > > from the SHAC and connect the disks to the KFQSA thereby allowing NetBSD > > >to run? > > Oh wait, your "Vax 4000-200" is a KA660 in a BA215? Then the internal DSSI is > connected via the 50-pin connector piggybacked on the KA660. > Not via the BA430 backplane. Connecting the KFQSA's external DSSI connector > to the other end of the DSSI bus, via an external DSSI cable, should still > work. > > The possible problem with just disconnecting the DSSi internal cable from the > CPU and leaving it hanging, is no longer terminating that end of the DSSI bus. > The BA215 internal DSSI cable wouldn't be left hanging when it is disconnected from the KA660 DSSI connector, it would be connected to the KFQSA instead. So there would be no DSSI bus termination issues. I have a BA215 that I sometimes alternate between a KA660, and an M7554 KDJ11-D/S PDP-11/53 (which was originally a DECserver 550 CPU board). When the M7554 KDJ11-D/S is installed I either use a QBus SCSI controller, or a KFQSA attached to the internal DSSI bus.
[cctalk] Re: programming the IBM PC synchronous serial boards (Northstar Advantage project)
On Fri, Dec 22, 2023 at 2:13 PM r.stricklin via cctalk wrote: > > Did IBM ever publish programming information for their PC SDLC or BiSync > communications boards? I’m wondering about the possibility of programming one > to drive the synchronous protocol needed for “booting” a Northstar Advantage > over its serial port. > Are you looking for something beyond the low level information in the IBM Options and Adapters reference manuals? https://minuszerodegrees.net/oa/oa.htm IBM Synchronous Data Link Control (SDLC) Adapter https://minuszerodegrees.net/oa/OA%20-%20IBM%20SDLC%20Adapter.pdf IBM Binary Synchronous Communications (BSC) Adapter https://minuszerodegrees.net/oa/OA%20-%20IBM%20Binary%20Synchronous%20Communications%20Adapter.pdf
[cctalk] Re: PDP11 and Ultrix 11
On Wed, Oct 18, 2023 at 7:32 AM Paul Koning via cctalk wrote: > > If you have an MSCP translator type controller, but the translation is poorly > done, you might end up with it failing for some operating systems. That's > not too unlikely given that the MSCP spec was for a long time a DEC > confidential document, so third parties had to reverse engineer things (and > dodge DEC lawyers). > > paul I have at least one third-party vendor QBUS MSCP SCSI controller which has a sticker on the PCB which says "Licensed under U.S. Letters Patent 4,449,182" Which is of course the DEC MSCP patent: http://www.bitsavers.org/pdf/dec/dsa/mscp/MSCP_Patent_4449182.pdf So I guess at least in that case the vendor did play along with DEC lawyers.
[cctalk] Re: Logic Analyzers - HP/Agilent 16700B or 1670G?
On Sun, Aug 20, 2023 at 1:39 PM Tony Jones via cctalk wrote: > > I'm in Portland OR I have one 16702B and one 16700B for sale.As Glen > says, an external monitor is really nice. There are a few modern LCDs that > can make use of opt B if your unit has it. The built-in LCD on the 16702A / 16702B is 800x600. Without the extra memory of Opt 003 installed, the maximum supported resolution on an external monitor is 1280x1024. With Opt 003 installed, the maximum supported resolution on an external monitor is 1600x1200, but at 75Hz, which isn't supported by all monitors. With a 1600x1200 or 1920x1200 monitor which supports 60Hz but not 75Hz, it is possible to use a video scaler to convert between the 16700-series 1600x1200 at 75Hz output to 1600x1200 or 1920x1200 at 60Hz. I tried this today with an Extron DVS 304 DVI video scaler and got decent results with 16700-series 1600x1200 output on a 1920x1200 at 60Hz monitor. I've had mixed results between different Extron video scalers. I couldn't figure out how to configure an Extron DVS 510 to give the same results in this scenario as the DVS 304 DVI.
[cctalk] Re: Logic Analyzers - HP/Agilent 16700B or 1670G?
On Sun, Aug 20, 2023, 12:05 PM John H. Reinhardt via cctalk < cctalk@classiccmp.org> wrote: > Hello all. I looking around for a Logic Analyzer for doing (mostly) DEC > QBus/UniBus stuff. Being the way I am I want something with enough lines > to handle the most of the signals so I'm guessing something with roughly > 80-ish channels. I think that lets out all/most of the USB based LA. I've > looked around and it seems the the HP/Agilent 16700 series (16700B/16702B) > are probably what I want. I've also seen the 1670G which also seems quite > doable. I've seen a lot of posts at the EEVblog and it seems I missed > possibly the golden age of 16700 LA by a few years price-wise. > > What I'm wondering is if there is something specific I should be looking > for, or opinions on which LA is more suitable. Or even if there is a > different make of LA to look for. > > Thanks in advance for your help > > John H. Reinhardt > Where are you located? That can have a large impact on the cost of acquiring a large 16700-series logic analyzer. For example, I have more of those than I need in the Seattle area. A local deal might work out well, but if shipping is involved that can quickly get too expensive. If bench space is limited, a 1670G takes up a lot less, and is completely self contained and easier to move around and set up. On the other hand, a 16700-series is more flexible, and if you have space to set up an external monitor you can see a lot more data on the screen at the same time without scrolling around.
[cctalk] Re: Little Databases
On Sat, Aug 19, 2023, 7:33 PM Sellam Abraham via cctalk < cctalk@classiccmp.org> wrote: > On Fri, Aug 18, 2023, 8:31 PM Gavin Scott via cctalk < > cctalk@classiccmp.org> > wrote: > > > It [SQLite] has billions of installations and on the order of a trillion > > databases in use. > > > > Surely you hyperbole. > > Sellam > They are serious, and don't call them Shirley. >
[cctalk] Re: BEWARE: Phishing
On Fri, Jul 7, 2023 at 12:24 PM Sellam Abraham via cctalk wrote: > > How else are we to know that the capacitor is charged, or that the link is > dangerous? I clicked on the link. Now all of my apes are gone.
[cctalk] Re: IMSAI BASIC PROM set?
On Thu, Jun 29, 2023 at 7:39 PM Bill Degnan via cctalk wrote: > > So I was able to get the listing for the PROMs by using the HEX file of > IMSAI BASIC 1.4 from.Rich Cini's website. I was able to then pull the > Intel papertape file image using Teraterm to capture the log of the session > while using to load BASIC into the IMSAI. I can use the log to make an > ePROM-friendly file. Sounds like a convoluted way to convert a HEX file into a binary file, or whatever you mean by an EPROM friendly file. I imagine most EPROM programmers can directly take an Intel HEX file as an input file. If you needed a binary file, you could also use SRecord 1.65 srec_cat to convert the Intel HEX file to a binary file, and split it up into smaller chunks if you need to split the 8KB binary into smaller EPROMs. https://srecord.sourceforge.net/
[cctalk] Re: IMSAI BASIC PROM set?
On Wed, Jun 28, 2023 at 7:43 PM Bill Degnan via cctalk wrote: > > Anyone have the 2716 ePROM listing for IMSAI Basic. Version 1.4 or > whatever. I once had it, can't find my copy. If not 2716, I'll take any > listing that I can convert somehow. > Thanks > Bill Here's a machine readable version of the 8KB Version 1.4 source code, and a hex file of an assembled version of that code: http://cini.classiccmp.org/zips/IMSAI%20BASICs.zip
[cctalk] Re: IMSAI BASIC PROM set?
On Wed, Jun 28, 2023 at 8:01 PM Bill Degnan via cctalk wrote: > > Steve > I was looking for the original prom listing format files. Not sure if > theyre 1702 2708 2716 or ?? This IMSAI 8K BASIC Version 1.4 manual says 32 chips in two IMSAI PROM 4 boards. That would be 32 256-byte 1702 EPROMs. One board starting at address 0, the second board starting at address 4KB, and RAM starting at address 8KB. https://www.autometer.de/unix4fun/z80pack/ftp/imsai/imsai_8k_basic.pdf
[cctalk] Re: IBM RT Graphics
On Wed, Jun 7, 2023 at 11:54 AM r.stricklin via cctalk wrote: > > > On Jun 7, 2023, at 11:26 AM, Jonathan Katz via cctalk > > wrote: > > > > Hello! > > > > I have an IBM 6152 aka IBM RT system I rescued. (It may be a 6151?) > > You have a 6151, the 6152 has VGA graphics (is built inside a PS/2 Model 60) > > > I'm 90% sure it has colour graphics. The system does seem to POST > > correctly (according to the LED on the front) but the CRT is dead. I'm > > wondering if anyone has built an adapter to hook this to a VGA > > monitor. > > You’re going to run into trouble, then, as the video signal is completely > incompatible with a normal VGA multisync monitor. It’s TTL color, interlaced, > with a horizontal scan frequency less than 31kHz. 720x512 interlaced. > > The RT knows how to use a “standard” IBM PC MDA or EGA adapter. Might be > better off using one of those instead, at least for now. > > ok > bear. All of the IBM RT 6151 systems I saw years ago (ugh, 36 years ago now...) must have all had Megapel display adapters attached to monochrome or grayscale monitors. That was the early days of Project Athena and X11. At the time they seemed like reasonably nice systems, comparable to the more common VAXstation 2000 systems. I imagine if you have an IBM RT 6151 system now without a Megapel display adapter, it would probably be difficult to find one.
[cctalk] Re: Getting floppy images to/from real floppy disks.
On Fri, May 19, 2023, 7:12 AM Liam Proven via cctalk wrote: > > I I think that Windows ME had USB 2 at launch. > That would have been impossible. Windows 2000 RTM date was December 15, 1999. Windows Me RTM date was June 19, 2000. Windows XP RTM date was August 24, 2001. The Intel Enhanced Host Controller Interface (EHCI) specification revision 1.0 is dated March 12, 2002, almost 2 years after Windows Me RTM. Windows XP SP1 was released on September 9, 2002, which was the first time Microsoft released any USB 2.0 support. Windows 2000 SP4 was released on June 26, 2003, which is when Microsoft released USB 2.0 support ported back to Windows 2000. At that point in time Windows Me was essentially dead and had been for a while. No one at Microsoft was interested in the effort required to port USB 2.0 support back to Windows Me. >
[cctalk] Re: Getting floppy images to/from real floppy disks.
On Fri, May 19, 2023, 4:36 AM Liam Proven via cctalk wrote: > > [3] Win98SE was, I _think_, maybe the first version to support USB _2_ > and maybe the first version with USB key support as standard. This > needed a driver on original 98. [4] Microsoft didn't add USB 2.0 support until Windows XP SP1. That USB 2.0 support was also back ported to Windows 2000 SP 4. Microsoft never added USB 2.0 support to Windows 98SE or Windows Me. [5] Microsoft first added USB mass storage support to Windows 2000. That was back ported to the original Windows Me release, but never to Windows 98SE. [6] Any USB 2.0 support on Windows 98SE or Me would have been provided by third-parties, same with any USB mass storage support on Windows 98SE. >
[cctalk] Re: Schematics for Lear Siegler ADM31?
On Sun, Apr 23, 2023 at 3:10 PM John Robertson via cctalk wrote: > > Oh, I am missing two key caps for the ADM31, anyone have spares? Not > sure what is printed on them at this point, but any caps would be better > than missing ones to start! Keyboard photo to see what key caps are missing: https://terminals-wiki.org/wiki/index.php/Lear_Siegler_ADM-31 https://terminals-wiki.org/wiki/images/2/29/Lear_Siegler_ADM-31_321477505131-3.jpg
[cctalk] Re: VMS V4.2 MUP (Mandatory Update) wanted!
On Fri, Mar 17, 2023, 6:11 AM Hans-Ulrich Hölscher via cctalk < cctalk@classiccmp.org> wrote: > The mandatory update for VMS V4.2 is still missing in my collection. > > Because of that, VMS V4.2 is not fully usable, > neither can layered software be installed nor can > it be upgraded to VMS V4.3. > > Who can help??? http://www.bitsavers.org/bits/DEC/vax/vms/VMS_4.x/BB-BT05B-BE_VMS_4.2_85.tap.gz http://www.bitsavers.org/bits/DEC/vax/vms/VMS_4.x/BB-FY83A-BE_VMS_4.2_mand_Ud_85.tap.gz
[cctalk] Re: Power supply for DEC VK100 GIGI?
On Wed, Mar 15, 2023 at 7:25 PM bob--- via cctalk wrote: > > P.S. Oh, and no - I don't have the subchassis for the supply, nor the fan, > switch, IEC inlet or any of that fancy stuff. Maybe something like a MEAN WELL RPT-60B open frame power supply would be easier to fit into the enclosure than an ATX power supply. Around $23 new at Mouser.
[cctalk] KDJ11-E M8981 11/93 EPROM firmware dump?
Anyone have a dump of the KDJ11-E M8981 11/93 EPROM firmware? That would be U106 377E7 V2.01 (I assume the full part number would have been 23-377E7) Don't see a copy at the obvious places to check: http://www.bitsavers.org/bits/DEC/pdp11/firmware/ http://www.dunnington.info/public/DECROMs/
[cctalk] Re: Store with "vintage" computers and parts
On Wed, Feb 8, 2023 at 7:17 PM Will Cooke via cctalk wrote: > > This place may be of interest. Most of the stuff they have for sale probably > isn't of much interest here, but there are a few gems. The link takes you to > one, which is how I found it. > https://www.bryanipad.shop/product/microlog-corporation-atr-6800-vintage-rare-738148146177114113.html > Very skeptical that this site is legitimate. "Free Shipping & Returns: Free Shipping for all orders. Free Return" Uh, no way, no how. Reviews are just some Lorem Ipsum text. 1 Review For Chaz Kangeroo Hoodies Admin - 30 Nov, 2018 Aliquam fringilla euismod risus ac bibendum. Sed sit amet sem varius ante feugiat lacinia. Nunc ipsum nulla, vulputate ut venenatis vitae, malesuada ut mi. Quisque iaculis, dui congue placerat pretium, augue erat accumsan lacus
[cctalk] Re: Q-BUS Boards available
Are you referring to this board listed below? M7165 Qbus SDI disk adapter That's not SCSI. That's one board of a two board set, the other being the M7164, that are an SDI controller for RA6x, RA7x, RA8x, RA9x drives. On Sat, Feb 4, 2023, 1:22 PM John Maxwell via cctalk wrote: > Hi David, > If still available, I'd like the uVII RAM and CPU and SCSI adapter. Any > interest in shipping to the USA? I'd pay for freight. I have been looking > for a Qbus SCSI adapter for a while now. Even if that's the only item that > you are sending. > >Thanks, > -John > > -Original Message- > From: David Coolbear via cctalk > Sent: Friday, 3 February, 2023 16:48 > To: cctalk@classiccmp.org > Cc: David Coolbear > Subject: [cctalk] Q-BUS Boards available > > I have the following Q-BUS boards available. > M7168 VCB02, QDSS Q 4-plane colour bitmap module > M7169 VCB02, QDSS Q 4-plane video controller module > M7608 MS630 RAM for KA630 > M7608 MS630 RAM for KA630 > M7606 KA630 Microvax II CPU > M7620 KA650 Q MicroVAX III CPU > M7165 Qbus SDI disk adapter >
[cctalk] Re: RQDX3's: Lessons learned.
Some other good sources of information: PDP-11 Diagnostic Database - module "ZRQC" http://www.retrocmp.com/tools/pdp-11-diagnostic-database/202-pdp-11-diagnostics-database RQDX3 firmware source code. Not sure what version this is. http://www.bitsavers.org/pdf/dec/qbus/rqdxx/rqdx3_src.zip
[cctalk] Re: RQDX3's: Lessons learned.
On Sat, Feb 4, 2023, 4:44 AM emanuel stiebler via cctalk < cctalk@classiccmp.org> wrote: > On 2023-02-03 22:48, Chris Zach via cctalk wrote: > > > 2) There are at least two RQDX3 ROM sets. The earlier one does not > > support the RX33 floppy and doesn't give any info during formatting. The > > later version (Version 4) does support the RX33 and is a lot nicer. > > Is it just the ROMs, or also some HW changes? > Do we have backup of the newer versions? > http://www.dunnington.info/public/DECROMs/ http://www.dunnington.info/public/DECROMs/ROMlist > 23-216E523-217E5M755516KRQDX3 T-11 code issue 1 0 23-217E523-216E5M755516KRQDX3 T-11 code issue 1 1 23-243E523-244E5M755516KRQDX3 T-11 code issue 2 0 23-244E523-243E5M755516KRQDX3 T-11 code issue 2 1 23-285E523-286E5M755516KRQDX3 T-11 code issue 3 0 up to RD53 only(?) 23-286E523-285E5M755516KRQDX3 T-11 code issue 3 1 up to RD53 only(?) 23-339E523-340E5M755516KRQDX3 T-11 code issue 4 0 Handles RD54 23-340E523-339E5M755516KRQDX3 T-11 code issue 4 1 Handles RD54 Some good 30+ year old information here: http://www.ibiblio.org/pub/academic/computer-science/history/pdp-11/hardware/third-party-disks.txt >
[cctalk] Re: Reading Old Floppies
On Mon, Jan 9, 2023, 10:23 AM Warner Losh via cctalk wrote: > On Sun, Jan 8, 2023, 6:29 PM Zane Healy via cctalk > wrote: > > Also, a normal USB Floppy drive can only handle 1.44MB formatted floppies. > 720k might work (but there is nothing in the standards to describe this) > and oddball formats are right out. > > Warner > https://www.usb.org/sites/default/files/usbmass-ufi10.pdf USB Mass Storage Class – UFI Command Specification Revision 1.0 4.10.2 Formattable Capacity Descriptors The UFI device supports the following capacity descriptors. Table 35 - Capacity Descriptors Supported by USB-FDU DD 720 KB HD 1.25 MB (1024-byte sectors) HD 1.44 MB
[cctalk] Re: Downsizing "feeler"
On Sat, Jan 7, 2023, 11:12 AM George Currie via cctalk < cctalk@classiccmp.org> wrote: I need to go through and hit some highlights, but there are things from rack mount PDP-10's -- Did you really mean PDP-10 instead of PDP-11?
[cctalk] Re: [SPAM] Re: what is on topic?
On Thu, Dec 22, 2022, 6:16 PM Fred Cisin via cctalk wrote: > >> Win95/Win98 would be happy with a PC/AT 286, with appropriate RAM > > On Thu, 22 Dec 2022, Grant Taylor via cctalk wrote: > > I don't think "happy" is how I would describe that. > > Would it run? Maybe. > > Would I want to run it like that? Nope. Not at all. > > I stand corrected. > "Run", no. > "limp along", yes > It could do a few useful things; but was far from suitable for general > purpose. > Shirley none of you are serious about a 32-bit (at least partially) operating system being able to execute on a 286 processor. You couldn't even run Windows 3.1 in Enhanced mode on a 286 processor. >
[cctalk] Re: what is on topic?
100's of replies later... The first rule of Off-Topic Club is that you do not talk about Off-Topic Club.
[cctalk] Re: Inline Serial Device?
On Sat, Nov 12, 2022 at 12:36 PM Chuck Guzis via cctalk wrote: > > On 11/12/22 11:56, ben via cctalk wrote: > > On 2022-11-12 12:33 p.m., Chuck Guzis via cctalk wrote: > > > Watch out for Indians. :) > > Ben. > > Nonsense--they have some very fine restaurants here. > > --Chuck I went to an Endian restaurant once. I was disappointed. I wanted something little, but everything on the menu was big.
[cctalk] Re: Disk imaging n00b
On Thu, Nov 3, 2022 at 2:08 PM Grant Taylor via cctalk wrote: > > Hi, > > n00b alert > > Does anyone have a 101 level boot strap guide for someone wanting to get > into creating better-than-dd disk images? > > I'm finding myself back in a position where I want to image / preserve > multiple 5¼ & 3½ inch disks. I think all of them are PC compatible > disks. Probably standard FAT-12 and a handful of super capacity disk > formats from the likes of IBM / Microsoft where they tried to squeeze > 1.6 (?) MB on a 3½ inch disk. If they are 5¼ & 3½ inch disks which are not copy protected and are readable with standard PC compatible floppy controllers, but not necessarily limited to standard DOS formats, and you had a older PC with a floppy controller which you could set up to boot into real mode DOS, I would start with Dave Dunfield's ImageDisk program. See a link for ImageDisk 1.19 here: http://dunfield.classiccmp.org/img/ Even if a disk is in a standard DOS format, it can be helpful to have an image of the disk rather than just a ZIP of all of the files copied off of the disk. In one example I was trying to run a setup program from a set of files extracted from a ZIP and copied back to disks and the setup program blocked when it was necessary to change installation disks because the next disk didn't have the expected disk label. Of course the disk labels weren't saved in the ZIP, while they would have been saved in images of the disks.
[cctalk] Re: looking for DQ696 and RQDX3
On Mon, Oct 10, 2022 at 3:06 PM Nigel Johnson Ham via cctalk wrote: > > Hi folk, > > I am still looking for a DQ696 to allow me to get ESDI drives going on > both my microVAX and 11/73 since the Webster RQD11 controller failed I > only have the one. I'd also like to get old of an RQDX3 since I built a > Gesswein emulator and have nothing to test it with :-) Do you have ESDI drives that have been formatted with a Dilog DQ696, and you need a DQ696 to use the drives with their existing format, or would it be OK to low level format the drives and any QBus ESDI controller would work, such as an Emulex QD21, or a RQD11 from various vendors? Where are you located, and what is a QBus ESDI controller worth to you? Here's an Emulex QD21 for around $100 in the US: https://www.ebay.com/itm/372959317948 Does that exceed your budget, or wrong location, or not compatible with your needs? I probably have more Dilog DQ696, Emulex QD21, and SDC-RQD11-EC controllers than I do working ESDI drives. At one point I had several working ESDI drives that have now gone bad over time while not being used. It's been a while since I tried spinning up any of them to see if any still work.
[cctalk] Re: 11/45 and 11/34 Taken!
On Thu, Sep 22, 2022 at 8:32 AM Kevin McQuiggin via cctalk wrote: > > Hi All: > > I’m pleased to report that my 11/45 and 11/34 which were in need of a new > home have been taken by another collector here in BC. They will be off to a > very good home! > Good news. I really didn't need to spend a day driving up to Vancouver from Seattle to collect these, and then try to make room to get them set up. A few years ago when I still had some room I would have been all over trying to collect these.
[cctalk] Re: VAXstation 100 ROM image
On Tue, Sep 21, 2021 at 10:18 AM Al Kossow via cctalk wrote: > > On 9/21/21 9:58 AM, Chris Zach via cctalk wrote: > > How the hell did I miss *that*? Cool beans device, I've never heard of a > > VS100. Was it in a Rainbow sized box or a Pro/350 box? > > Smaller. I have access to one to take pictures and dump the firmware Reviving a year old thread, did anyone get around to dumping the VAXstation 100 firmware? I don't see it where I looked here: http://www.bitsavers.org/pdf/dec/vax/vaxstation100/ http://www.bitsavers.org/bits/DEC/
[cctalk] Re: Connecting a physical terminal via LAN to Serial Port
On Sat, Jul 30, 2022 at 10:23 PM Ali via cctalk wrote: > > So I am wondering if there is a box that provides a telnet CLIENT to a > serial port device? I.E. a box smart enough that handles the telnet client, > LAN functions, and terminal emulations internally and then provides a text > based interface through a serial port that is compatible with my physical > terminal? That way my physical terminal would be connected to the RS232/LAN > bridge all the time and I could connected to not only the serial ports > connected to the console server but other telnet accessible services as all > the heavy lifting would be done on the bridge. I am ideally looking for a > ready to go, low power device, I can hide away as opposed to setting up a PC > of my own running some *nix flavor that I know can do this but is way over > kill. Oh yeah and if it is super cheap even better. Thanks! > You can do what I believe it is that you want with any Digi PortServer. I just verified this with one of the original Digi PortServer 16, 5260 models. With that model you can configure a port device type as a "term", and when a terminal is attached to such a port it will connect to a command prompt. You can also configure a port device type as a "prn", which can be a general purpose outgoing port connection, not just a printer. >From a "term" port command line, you can open an outgoing telnet connection to other hosts on the network, or to any other "prn" port on the local PortServer. Other hosts on the network can open telnet connections to the "prn" ports. Newer PortServer models may have different names for port device types, and different commands for connecting to ports on the local PortServer, but should still have those capabilities. If you look at an original PortServer, or PortServer II model on eBay, make sure the power adapter is included. They use a triple voltage 5-pin DIN connector power supply, which you wouldn't want to have to find separately. Newer PortServer models use single voltage power adapters, which would be easier to replace. Some PortServer models have built-in power supplies. How many ports total would you like to have? A 4-port or 8-port Digi terminal server can be found on eBay at reasonable prices in the US ($20 - $35 today for some models). You will almost always have to supply your own RJ45 - DB9/DB25 cables at additional cost.
Re: Memory Card Explorer for the Elan P423
On Wed, Jul 6, 2022 at 7:51 PM Glen Slick wrote:
>
> I'll have to boot up again the Linux system I had set up for this and
> refresh my memory on some of the details. If I remember correctly, one
> of the things I had to do was to rebuild the pcmcia driver with the
> CONFIG_MTD_PCMCIA_ANONYMOUS option enabled. Some of the linear flash
> cards I have might not have a separate attribute memory plane and no
> valid CIS, so the card wouldn't get recognized without that option
> enabled. Pretty sure there was something else I had to change to get
> things to work with some of the cards I have. Just don't remember now.
>
Maybe no one else is interested in this detail, but just for future
reference reference, it looks like one of the changes I had to make to
get the MTD driver to work with some of my linear flash cards was to
this read_pri_intelext() routine in this source file:
drivers / mtd / chips / cfi_cmdset_0001.c
from:
if (extp->MinorVersion >= '0') {
extra_size = 0;
/* Protection Register info */
extra_size += (extp->NumProtectionFields - 1) *
sizeof(struct cfi_intelext_otpinfo);
}
if (extp->MinorVersion >= '1') {
/* Burst Read info */
extra_size += 2;
if (extp_size < sizeof(*extp) + extra_size)
goto need_more;
extra_size += extp->extra[extra_size - 1];
}
to:
extra_size = 0;
if ((extp->MinorVersion >= '0') && (extp->FeatureSupport & 64)) {
/* Protection Register info */
extra_size += (extp->NumProtectionFields - 1) *
sizeof(struct cfi_intelext_otpinfo);
}
if ((extp->MinorVersion >= '1') && (extp->FeatureSupport & 128)) {
/* Burst Read info */
extra_size += 2;
if (extp_size < sizeof(*extp) + extra_size)
goto need_more;
extra_size += extp->extra[extra_size - 1];
}
The problem with the original code is that without checking the
Optional Feature and Command Support bits, it assumes that if the
Intel CFI Primary Vendor-Specific Extended Query Table exists then the
flash device has OTP support, and if the Minor Version is >=1 then the
flash device has Page Mode Read support. According to the 290606-015
datasheet for Intel 28F320J5 and 28F640J5 StrataFlash devices the
Minor Version number in the Intel CFI Primary Vendor-Specific Extended
Query Table is 1, but those device do not have OTP support nor do they
have Page Mode Read support, which causes the read_pri_intelext() fail
or hang while trying to parse the Intel CFI Primary Vendor-Specific
Extended Query Table.
I must have some linear flash cards that are based on Intel 28F320J5
or 28F640J5 StrataFlash devices that encountered this issue. Without
going through my stack of cards I don't remember which cards those
might be.
Re: Memory Card Explorer for the Elan P423
On Wed, Jul 6, 2022 at 4:58 PM Jonathan Chapman wrote: > > > I ended up getting a PCI bus PC Card adapter based on the TI PCI1131 > > PCI-TO-CARDBUS CONTROLLER UNIT chip. I set that up in a Linux system > > and eventually managed to get some MTD (Memory Technology Devices) > > software installed so that I could read and write to a variety of > > linear flash cards. > > Careful doing this, always flip the write protect switch! Default behavior, > when the kernel/pcmcia-utils is trying to figure out what's in the slot is to > run down a list of identification steps. The final one is to scribble on the > card's memory space to see if it's writable SRAM! Blasted a card just by > inserting it a few years ago, fortunately one I already had backups of. > > If you don't wish to futz with expensive commercial software or rolling your > own, you can almost certainly use the Data I/O card utils with a generic ISA > to PCMCIA adapter. I have their actual branded hardware, and it's a Vadem > PCMCIA chip that follows whatever the early Intel standard was. Software is > available on the Data I/O groups.io file archive. The Data I/O software > includes basically "dd for Flash cards." > > Thanks, > Jonathan Not all of the linear flash cards I have on hand have write-protect switches. I would be somewhat surprised if a card identification probe could unintentionally write to a linear flash card. All of the linear flash cards that I have looked at require specific command sequences to be sent to the flash to enter programming mode, or to erase blocks. Writing random data to the flash address space wouldn't do anything, unless the random data just happened to match the programming command sequence. I'll have to boot up again the Linux system I had set up for this and refresh my memory on some of the details. If I remember correctly, one of the things I had to do was to rebuild the pcmcia driver with the CONFIG_MTD_PCMCIA_ANONYMOUS option enabled. Some of the linear flash cards I have might not have a separate attribute memory plane and no valid CIS, so the card wouldn't get recognized without that option enabled. Pretty sure there was something else I had to change to get things to work with some of the cards I have. Just don't remember now. I'll have to take a look at the Data I/O card utils sometime. Didn't know that was a thing. I also have a PC Card adapter for my BP Microsystems device programmers. Unfortunately the supported device list is rather limited.
Re: Memory Card Explorer for the Elan P423
On Wed, Jul 6, 2022 at 5:48 PM D. Resor wrote: > > Memory Card Explorer can Exclude/Include up to 1 through 8 PCI card slots. > This is to prevent the software from "killing" the operation of other plugged > in cards such as modem, network card, etc. > That doesn't make much sense that it would care about PCI slot numbers. I found a Memory Card Explorer for RICOH XP DEMO screenshot online which shows a dialog box for including or excluding PC Card Slot 1 through Slot 8. I assume that is referring to the physical PC Card slots into which you insert PC Cards, which is a completely separate numbering space than the PCI slot into which the adapter card is installed. Most likely you would only ever have one or two PC Card slots, controlled by a single adapter card. I suppose you could get as many as 8 PC Card slots if you had multiple adapters installed. > The mother board I tried it on and was able to actually get the program to > start under Windows XP with no memory hurdles is a Gigabyte GA-Z77-DS3H. > Unfortunately for some reason the PCI slot closest to the CPU socket is > marked PCI Slot #12. There weren't no way I could configure MCE to find the > Elan P423 Card Reader/Writer. Again, that doesn't make much sense to me that the adapter driver or the software would care about which PCI slot that the adapter is installed in. > I don't have to buy the Ricoh Memory Card Explorer software as there is a > full working 30 day trial version (which I have). Not a problem. Is the Demo version of Ricoh Memory Card Explorer software available to download somewhere on the net? I might be curious to try installing it some time to take a look, instead of just making guesses about how some of it works.
Re: Memory Card Explorer for the Elan P423
On Tue, Jul 5, 2022 at 6:31 PM D. Resor via cctalk wrote: > > Does anyone have past experience with Memory Card Explorer and the Elan P423 > BUS to PC Car Reader-Writer 2 Slot Internal unit? > > https://www.synchrotech.com/products/card-rw_33_p423_elan_pcmcia_pc-card_rea > der_slot.html > > Memory Card Explorer has certain compatibility rules for the Motherboard it > is installed in. The software seems to be a bit picky. > > Which mainboard/motherboard is best suited for the task and using Windows XP > x32 SP3? If you are trying to use a PCI bus PC Card adapter on Windows XP, my guess is that most of those system restrictions don't really apply, as long as the system has a PCI slot. I have never used Memory Card Explorer, nor do I have a copy of it to try. Seems too expensive to justify buying a copy (if it is still available for purchase) for anything I would do with it. What do you actually need to accomplish with the PC Card adapter and software? In the last year or so I wanted to read and write to some linear flash cards, which were used to store firmware for some older devices (e.g. DECserver 900TM, NCD Explora X-Terminal). I ended up getting a PCI bus PC Card adapter based on the TI PCI1131 PCI-TO-CARDBUS CONTROLLER UNIT chip. I set that up in a Linux system and eventually managed to get some MTD (Memory Technology Devices) software installed so that I could read and write to a variety of linear flash cards. It was not trivial to do so. I think I had to rebuild the kernel at some point to get some of the drivers to work. I'd have to dig up notes I might have about it to remember the details.
Re: Viking SCSI controller RS232 adapter
On Thu, Jun 30, 2022, 12:34 PM Douglas Taylor via cctalk < cctalk@classiccmp.org> wrote: > Update - I have 3 of these Viking controllers, 2 are rebadged to > Alphatronix. > > 1. I was able to 'kludge' together jumpers to connect a laptop serial > port to the controller. Pin 20 IDC -> pin 2 DB-9, pin 22 IDC -> pin 3 > DB-9 and pin 24 or 25 IDC -> pin 5 DB-9. It didn't seem to matter if > you used 24 or 25 for the ground. > Did you split off the connections to Pin 20 and Pin 22 of the controller so that they only connected to the serial port, and not to the SCSI bus, or were they wired in parallel to both the serial port and the SCSI bus?
Re: IBM PC Connecting to DECNET
On Fri, Jun 3, 2022 at 5:41 AM Bill Gunshannon via cctalk wrote: > > Is there a schematic anywhere for the hockey puck mice? Don't know if there is a VSXXX-AA mouse schematic anywhere. There is a DEPCA print set: http://www.bitsavers.org/pdf/dec/ethernet/depca/MP02421_DEPCA_sch_May87.pdf Page 33 of the PDF has the DEPCA side of the mouse interface. 7-pin connector: (1) Ground (2) RX Data to DEPCA (goes to 9639 Dual Line Receiver) (3) TX Data from DEPCA (comes from 9636 Dual Line Driver) (4) -12V (5) +5V (6) +12V (7) N/C http://www.bitsavers.org/pdf/dec/ethernet/depca/EK-DEPCA-PR-001_Apr89.pdf DEPCA Hardware Reference Manual, EK-DEPCA-PR-001 Chapter 3, Mouse Information details the mouse communication protocol
Re: IBM PC Connecting to DECNET
On Thu, Jun 2, 2022, 9:36 PM Warner Losh via cctalk wrote: > Speaking of DEPCA, does anybody (a) know what kind of mouse connects (the > docs just say DIGITAL MOUSE) and (b) know where to get one? > > Warner > The usual VSXXX round mouse that is also used with VAXstations, either the ball version or the Hawley wheel version. >
Re: IBM PC Connecting to DECNET
On Wed, Jun 1, 2022, 6:52 AM Paul Koning via cctalk wrote: > > > > On Jun 1, 2022, at 5:53 AM, Warner Losh via cctech < > cct...@classiccmp.org> wrote: > > > > ... > > I believe the DEPCA was based on the venerable > > SONIC chipset, but it may have been the LANCE. It wasn't NE-2000 > compatible > > (that came later) :). > > LANCE seems plausible, or perhaps one of the later chips designed by DEC > Jerusalem (SGEC etc.). What's a SONIC? > > The non-LANCE non-DEC Ethernets I remember are in the DEUNA (no idea > what), QNA (Fujitsu???) and CNA (Intel 82586, *groan*). The LANCE was > designed well, with a fair amount of DEC input, and the subsequent > internally produced chips were constructed along similar lines. Once DEC > learned how to make them at not quite insane cost, they became a very good > choice and were generally used in DEC products. > > paul > The DEPCA did use the AMD Lance Am7990. >
Re: IBM PC Connecting to DECNET
On Tue, May 31, 2022 at 8:56 PM Bill Degnan via cctalk wrote: > > Specific to IBMPC to DECNET networking...anyone worked in this > environment? Not me. I don't have the D drive that fails or the > network, but I am curious what I would need to make this work. Maybe > I can put something together. Anyone using a Digital Ethernet > Personal Computer Bus Adapter today? > No one ever called it a "Digital Ethernet Personal Computer Bus Adapter", just a DEPCA. I never previously knew that there was any meaning behind the DEPCA name. I have a DEPCA in a 486 box that I got set up a while ago with some version of DECnet DOS, or Pathworks, from here, I forget which version without setting it up to take a look: http://www.bitsavers.org/bits/DEC/decnet/ Over 30 years ago I worked on PC DECwindows for DOS for a couple of years. There were Rational 286 and PharLap 386 DOS Extender versions. The DECnet DOS development was in a different group in a different building. The PC DECwindows for DOS server used DECnet DOS as a network transport.
Re: Alphastation 200 login (Wayne S)
On Wed, May 18, 2022 at 11:25 AM Wayne S via cctech wrote: > > I should have specifically said it’s Windows Nt. Issue is that it’s an > Alpha so can’t use the usual software to change or remove the password > unless there’s an Alpha version. Best suggestion so far is to use a version > of Unix that runs on Alpha and rename the SAM file. Or maybe try attaching the boot drive to an x86 system and try using the usual Windows NT password reset tools? (e.g. chntpw Live CD) I have no idea if all of the file systems and data file formats are identical enough between x86 and Alpha versions of Windows NT. Would probably be a good idea to make a backup image of the boot drive before using any tools to modify its contents.
Re: Alphastation 200 login (Wayne S)
On Wed, May 18, 2022 at 10:45 AM Craig Ruff via cctech wrote: > > > On May 18, 2022, at 11:00, cctech-requ...@classiccmp.org wrote: > > > > Got my Alphastation to boot but i can?t logon because i don?t the > > administrator password? Any ideas on how to get past that? > > For VMS, if I recall correctly, you set the boot R5 register to 1. Then > obviously the reset of the administrator user password is also OS dependent. Here's one example description of how to do that with OpenVMS. https://web.archive.org/web/20151122033453/http://labs.hoffmanlabs.com/node/204
Dumping an Intel P8742AH
Anyone here have experience dumping the contents of an Intel P8742AH OTP EPROM device? I have one that I haven't been able to dump with either a BP Microsystems BP-1610, or a Data-I/O UniSite device programmer. Both have device entries for that specific device. Both report device connection errors when attempting to read the device. The device pins all look clean. I tried putting a machine pin socket between the device and the programmer ZIF socket in case there was a flakey connection, but that didn't make any difference. I was told the device was working properly in the target system before it was removed to dump its contents. Looking at the UPI-41AH/42AH datasheet 210393-007 the P8742AH does have a security bit which can be programmed. As far as I can tell though, if the security bit is set the device should still respond to the standard device verification algorithm, but just return the wrong data, and the device manufacturer signature should still be able to be read. Or does an Intel P8742AH not respond at all to the standard device verification algorithm if the security bit is set? I don't have the target system myself to reinstall the device and verify that it actually works.
Re: HP 54200D oscope practically worthless?
On Thu, May 12, 2022 at 5:55 PM Eric Smith via cctalk wrote: > > These appear to be derived from the 1630/1631 logic analyzers, some models > of which have 'scope capability, which works as you've described. They must > have decided to offer models with only the scope and without the logic > analzyer (except for a digital triggering option), which seems like a bad > idea. Probably why I'd never heard of these before. > Without taking a close look at the specifications for any differences, the scope capability of the 54200 might be basically the same as the 1631. The 54201 scope adds a repetitive sampling capability that doesn't appear to be present on the 54200 and 1631, which increases the bandwidth up to 300MHz instead of 50MHz in the real-time sampling mode.
Re: PCI floppy controller
On Fri, Apr 22, 2022 at 11:25 AM Grant Taylor via cctalk wrote: > > I'd swear that I've used a PCI Adaptec card with a floppy controller. > 2942 comes to mind. Swearing about it doesn't make it so. Are there any Adaptec SCSI controllers other than the various flavors of these models which have floppy controllers? AHA-1522 (ISA) AHA-1542 (ISA) AHA-1742 (EISA) AHA-2742 (EISA) AHA-2842 (VLB)
Re: idea for a universal disk interface
I also have multiple ESDI controllers, more than one these flavors: Dilog DQ686 http://www.bitsavers.org/pdf/dilog/2120-0137-1_DQ686_Nov89.pdf Emulex QD21 http://www.bitsavers.org/pdf/emulex/QD2151002-J_QD21_Jun90.pdf Sigma SCD-RQD11-EC (There seems to be multiple versions from different vendors of this same basic board). http://www.bitsavers.org/pdf/sigmaInformationSystems/400740-B_SDC-RQD11-EC_Disk_Ctrl_Man_Jul88.pdf They all support block mode DMA transfers, and command queuing with seek optimization. The Dilog DQ686 and Emulex QD21 are dual wide boards. The Sigma SCD-RQD11-EC is a quad wide board and has 1MB of cache memory (which takes up about a quarter of the board area). The examples I have might only be populated with 512KB of cache memory. I might have had close to a dozen working full height 5.25-inch ESDI drives at one point. Unfortunately most of them have failed while sitting idle over the last few years. Without checking now I don't know if any of them still work. So the dozen or so Q-Bus ESDI controllers don't have any use for me now. (Fortunately I also have more Q-Bus SCSI controllers than backplanes to put them in). I also have a single Andromeda ESDC ESDI controller. Never found a manual for that one. Did eventually figure out how to get into the on-board configuration utility. On Tue, Apr 19, 2022 at 8:56 AM Douglas Taylor via cctech wrote: > > Once upon a time I used an Emulex QD21, but I sold it because the actual > ESDI disks I had were a pain in the butt. Always crashing. > I still have a Webster (quad board) SRQD something. > I think I had a Dilog board also. It's been a while, probably 20 years. > Doug > > On 4/18/2022 9:12 PM, Chris Zach via cctech wrote: > > Interesting, what kind of ESDI controllers do you have? They got > > advanced features like cache, ordered seeks, and burst mode/block mode > > DMA?
Re: ID UV erasable PROMS used on an IBM PC board?
On Wed, Mar 23, 2022 at 10:38 AM Chris Elmquist via cctalk wrote: > > On Wednesday (03/23/2022 at 04:18PM +0100), Christian Corti via cctalk wrote: > > > > I didn't even know that primitive EPROMs have device IDs... > > Without looking for a data book, how is the ID mechanism implemented? > > Intel called it "Intelligent Identifier(tm) Mode". > > From page 5-43 of my 1991 Intel Memory Products book, for the 27256, > > You put Vh (+12V) on address A9 and then, > > with A0=0, you will read out the manufacturer ID > with A0=1, you will read out the device ID > > Chris It is interesting that the Table 1 Operating Modes referenced above on page 5-43 says that the Manufacturer ID is 89H for UV erasable Cerdip parts, and 88H for OTP Plastic parts. The interesting thing is that previously Intel data books (e.g. 1983_Memory_Component_Handbook.pdf, page 4-28) said "All identifiers for manufacturer and device codes will possess odd parity, with the MSB (D7) defined as the parity bit". The Manufacturer ID of 88H does not have odd parity. I don't know if the odd parity requirement was removed, or if this is an exception.
Re: ID UV erasable PROMS used on an IBM PC board?
On Tue, Mar 22, 2022 at 12:25 PM Chris Elmquist wrote: > > On Tuesday (03/22/2022 at 12:20PM -0700), Glen Slick wrote: > > On Tue, Mar 22, 2022 at 11:56 AM Chris Elmquist wrote: > > > > > > Trying not to hijack the thread too much but I have an Intel D27C256-200 > > > here in my TL866II+ programmer and it returns ID 89h / 8Dh. > > > > > > > http://www.bitsavers.org/components/intel/_dataBooks/1993_Intel_Memory_Products.pdf > > Page 5-78 (Page 1201 of the PDF) > > Table 1. Mode Selection > > Intelligent Identifier - Manufacturer 89H > > Intelligent Identifier - Device 8DH > > That is for the A27C256 "Automotive" rated version. > > > > My BP Microsystems BP-1610 device programmer software doesn't have an > > entry for that one either. > > Interesting. Thanks Glen. The part is clearly labeled as > "D27C256-200V10" so they must not have gotten around to changing the D > to an A :-) (Flogging a dead horse here slightly) Just took a look at a previous version of that Intel databook: http://www.bitsavers.org/components/intel/_dataBooks/1991_Intel_Memory_Products.pdf Page 5-56 (Page 325 of the PDF) 27C256 Table 1. Mode Selection Intelligent Identifier - Manufacturer 89H Intelligent Identifier - Device 8DH NOTES: 4. Programming equipment may also refer to this device as the 27C256A. Older devices may have device ID = 8CH So apparently the Device ID change is not specific to the A27C256 "Automotive" rated version, just that in the 1993 version of the databook where I first looked the only EPROMs listed are the "Automotive" ones.
Re: ID UV erasable PROMS used on an IBM PC board?
On Tue, Mar 22, 2022 at 11:56 AM Chris Elmquist wrote: > > Trying not to hijack the thread too much but I have an Intel D27C256-200 > here in my TL866II+ programmer and it returns ID 89h / 8Dh. > http://www.bitsavers.org/components/intel/_dataBooks/1993_Intel_Memory_Products.pdf Page 5-78 (Page 1201 of the PDF) Table 1. Mode Selection Intelligent Identifier - Manufacturer 89H Intelligent Identifier - Device 8DH That is for the A27C256 "Automotive" rated version. My BP Microsystems BP-1610 device programmer software doesn't have an entry for that one either.
Re: ID UV erasable PROMS used on an IBM PC board?
On Mon, Mar 21, 2022 at 8:25 PM Chuck Guzis via cctalk wrote: > > The PROMs are most likely house-labeled Intel commodity parts with > JEDEC-standard pinouts, so it should be fairly easy, using an EPROM > reader, to figure out if these are 8KB, 16KB, 32KB or 64KB devices. Some device programmers can read the manufacturer and device ID codes from a device, if they are implemented. That would be another way to check for a Intel standard part. Intel 2764 - 89h / 02h Intel 2764A - 89h / 08h Intel 27C64 - 89h / 07h Intel 27128 - 89h / 83h Intel 27128A - 89h / 89h Intel 27C128 - 89h / FCh Intel 27256 - 89h / 04h Intel 27C256 - 89h / 8Ch Intel 27512 - 89h / 0Dh Intel 27C512 - 89h / FDh
Re: cctalk Digest, Vol 89, Issue 21
On Tue, Feb 22, 2022 at 2:20 PM Rod Smallwood via cctalk wrote: > > I'm sure that will work. Unfortunatly dd is a linux command. > > I only have windows PC's. > You never answered if you have a SCSI controller in your PC, or have the ability to add a SCSI controller to your PC. If you don't, the whole discussion of using 'dd' or equivalent is moo. > simH is highly complex and needs a lot of setup. ( I know - I tried - > total nightmare) > If you think setting up and using SIMH is highly complex, wait until you find out how complex setting up and using real PDP-11 hardware is. > It does not have support for the CMD CDD 220 SCSI controller and a RH-18A > Huh? SIMH emulates MSCP controllers and attached disks of arbitrary size just fine.
Re: Installing an operating system on an 11/83
On Mon, Feb 21, 2022, 4:32 PM Rod Smallwood via cctalk < cctalk@classiccmp.org> wrote: > Hi > >I have built an 11/83 in a BA23 box. > >It has a KDJ-11B, 2mB PMI memory, an RQDX3 with an RX50 attached, > > Plus a CMD CQD 220A Disk controller with a digital RH18A 2Gig SCSI drive > attached. > > Diag sees drive as RA82. > > It boots and runs the diag disk and XXDP+ just fine. > > I do not have install distributions for any of the 11/83 operating systems. > > Daily driver system is a Windows 10 PC. > > So how do I install an operating system? > > Suggestions please. > > Thanks > > Rod > Is the PC old enough to still have PCI slots? If it is, one option would be to pick up a cheap PCI SCSI controller, e.g. an AHA-2940, that you can use to write disk images to a SCSI hard drive. Then use SIMH to create disk images of an OS of interest that can then be dumped to the SCSI hard drive. Or pick up a SCSI2SD device to use with the CMD CQD-220A instead of a SCSI disk drive. Then copy disk images created using SIMH on the PC to an SD card. Is the CQD-220A a /TM version, or an /E version? If it's a /TM version you could also pick up a cheap SCSI tape drive, and create installation tapes for RSTS/E or 2.11BSD and boot from those to install on a SCSI hard drive. I've done that a few times just for the heck of installing from tape. If you have the /E version (or /T/M version) instead of the /TM version you can do either MSCP or TMSCP, but not both at the same time. For RT-11, that is small enough it wouldn't be difficult to install from RX-50 disks, if you had a means to create disks from images. >
Re: ID these DEC floppy disks
On Thu, Feb 17, 2022 at 4:28 PM Chris Zach via cctalk wrote: > > Hey all! > > While going through floppies I found these and was wondering what they > were. Only clue in Google was someone asking in 1997 same thing. > > BL-T540B-M1 CZUFDB1 USER TESTS > BL-T541B-M1 CZXD1B1 FIELD SERVICE TESTS 1 > BL-T542B-MC CZXD2B0 FIELD SERVICE TESTS 2 > BL-T565B-MC CZXD3B0 FIELD SERVICE TESTS 3 > BL-T583B-MC CZXD4B0 FIELD SERVICE TESTS 4 > > Any ideas? The first one does not have a write protect tab, the others > do. There is also one other disk I found > > CZMX4E0 Micro 11 Maint RX50 4 > > On this one the write protect flag was torn off (was on from factory and > removed) My guess is that these are Micro-11 diagnostic test disks, as mentioned in Section 5.7 USER TEST DISKETTES, on Page 5-12, of this manual: MicroPDP-11 Systems Technical Manual, EK-MIC11-TM-002 http://www.bitsavers.org/pdf/dec/pdp11/microPDP11/EK-MIC11-TM-002_MicroPDP11_Systems_Technical_Manual_Sep85.pdf These possibly related tests are listed as being included as part of the XXDP distribution on page A-22 of the PDP-11 Diagnostic Handbook, 1988 http://www.bitsavers.org/pdf/dec/pdp11/xxdp/PDP11_DiagnosticHandbook_1988.pdf ZUFlEO.BINMICRO-11 USER TEST #1 ZUF2EO.BINMICRO-11 USER TEST #2 ZUF3AO.BINMICRO-11 USER TEST #3 ZUF4AO.BINMICRO-11 USER TEST #4 If you have the ability to create ImageDsk images of these disks it might be interesting to take a look at them.
Re: Wanted: Pinout IDT 49C402 PGA84
On Thu, Feb 10, 2022 at 3:21 PM Maciej W. Rozycki via cctalk
wrote:
>
> On Thu, 10 Feb 2022, Holm Tiffe via cctalk wrote:
>
> > Has anyone a databook newer than 1989 where the PGA84 Pinout is listed?
>
> It seems like datasheetarchive.com has a copy of a 1995 datasheet listing
> what you need ("IDT49C402/A/B 16-BIT CMOS Microprocessor Slice", IDT doc
> #9011; original, not a scan). I have just downloaded it.
See also:
http://www.bitsavers.org/components/idt/_dataBooks/1995_IDT_High-Performance_Logic_Data_Book.pdf
Chapter 11, 16-BIT CMOS MICROPROCESSOR SLICE
IDT49C402, IDT49C402A, IDT49C402B
Page 4 of Chapter 11, PGA TOP VIEW
Re: DEC AXV11-C analog board
On Sun, Feb 6, 2022 at 9:20 AM Douglas Taylor via cctalk wrote: > > Does anyone have any info on the A/D module? Who made it? Can you open > it up? Does XXDP have a test for this? http://www.bitsavers.org/pdf/dec/pdp11/xxdp/PDP11_DiagnosticHandbook_1988.pdf PDP11 DIAGNOSTIC HANDBOOK 1988, Page A-7: VAXAB0.BIC ADV11-C/AXV11-C A/D CONVERTER TEST
Re: Origin of "partition" in storage devices
On Tue, Feb 1, 2022 at 10:04 AM Paul Koning via cctalk wrote: > > > Slower on the outer tracks, I believe. CDs work this way. > > I suspect CLV was invented for CDs, in fact. Which came first CLV CDs, or CLV LaserDiscs?
Re: What was a Terminal Concentration Device in DEC's products?
On Sun, Jan 30, 2022 at 11:43 AM Chris Zach via cctalk wrote: > > From the books, the kmc11 had an "lsi11 on board", 1k of 16 bit ram, 1k > of 8 bit data memory a 300ns cycle time, 16 bit microprossor with a 16 > bit micro-instruction bus and 8 bit data path. This is according to the > 1980 Terminal and Communications handbook, so it's a few years after the > 1976 timeframe of Sha Tin. > > Now the original LSI11 processor was 4 main chips, an EIS/FIS chip (or > the CIS lite chip or the weird 1k*20 bit micro-ram board which I have > somewhere). The DCT11 was a single chip lsi11 that had an 8 or 16 bit > outside bus and a 16 bit internal structure and ran pdp11 instructions. > So the KMC11 probably had the DCT11 chip. > > The LSI11 chipset was around in 1975, so it makes sense that DEC could > use it. The SBC11/21 came out in 1981 but the chip was probably avail > internally by 1980 so I'm guessing that the KMC11 and the COMM-IO-DP was > using the DCT11. > http://www.bitsavers.org/pdf/dec/unibus/MP01118_KMC11B_EngrDrws.pdf KMC11-B Field Maintenance Print Set The KMC11-B used a custom bit-slice processor implementation. (3x) 93S16 4-bit counters for a 12-bit program counter (2x) 74S181 4-bit ALUs for an 8-bit ALU (2x) 74S189 16x4 RAM for 16 8-bit working registers
Re: ISO: Canon Scanner Driver
On Sun, Jan 30, 2022 at 12:52 PM Jim Carpenter via cctalk
wrote:
>
> On Sun, Jan 30, 2022 at 3:36 PM Jim Carpenter wrote:
> >
> > On Sun, Jan 30, 2022 at 3:02 PM Jason T via cctalk
> > wrote:
> > > By any chance, does someone out there have this driver? The filename
> > > in question is "300350DRIT_V11.exe". You can google that name and end
> > > up either back at Canon's site or in Malware Hell ("just download this
> > > Chrome plugin to get your driver!").
> >
> > How about http://downloads.canon.com/cpr/software/scanners/300350INF.exe
> > ?
>
> Nevermind. Too small. Just the INF files. Sorry. :(
Just manually edit that URL with the desired filename:
https://downloads.canon.com/cpr/software/scanners/300350DRIT_V11.exe
Directory of C:\tmp
11/21/2005 03:20 AM 7,200,768 300350DRIT_V11.exe
That's a self-extracting ZIP file. You can rename it to
300350DRIT_V11.zip and extract the files that way,
Re: What was a Terminal Concentration Device in DEC's products?
http://www.bitsavers.org/pdf/dec/qbus/EK-DHQ11-UG-002.pdf DHQ11 User Guide, EK-DHQ11-UG.002 The main application of the M3107 DHQ11 is for interactive terminal handling; it can also be used for data concentration and real-time processing. It has two programming modes, DHV11 and DHU11. The register sets in these modes are compatible with those of the DHV11 and DHU11 respectively. The preferred mode of operation is DHU11 mode. The main features of the DHQ11 are: • For transmission: DMA transfers; or for each line, program transfers to a 1 character transmit buffer in DHV11 mode, or to a 64-character transmit FIFO in DHU11 mode • For receive: a 256-entry FIFO buffer for received characters, dataset status changes, and diagnostic information The M3118 CXA16 and the M3119 CXA08 have the same programming interface as the M3107 DHQ11 The M3108 DSV11 can do DMA transfers in both directions, although it is a synchronous interface, not asynchronous. http://www.bitsavers.org/pdf/dec/qbus/EK-DSV11-TM-001_Jan87.pdf DSV11 Technical Manual, EK-DSV11-TM-001 Functional Description (Section 1.5). The DSV11 supports a range of synchronous protocols on the serial interface, and transfers data to and from the host by DMA transfer. This section describes the way in which the DSV11 handles data. On Sat, Jan 29, 2022 at 3:49 PM Chris Zach via cctalk wrote: > > Maybe that is the dhv11. Or the dv11 I'll look it up tomorrow > > On January 29, 2022 5:12:41 PM EST, Paul Koning via cctalk > wrote: > > > > > >> On Jan 29, 2022, at 3:58 PM, Noel Chiappa via cctalk > >> wrote: > >> > >>> From: Paul Koning > >> > >>> DH-11 is unusual in that it has DMA in both directions > >> > >> McNamara's DH11? (I don't know of another DECdevice of that name.) Per: > >> > >> > >> http://www.bitsavers.org/pdf/dec/unibus/EK-ODH11-OP-002_DH11_Asynchronous_16-line_Multiplexer_Users_Manual_Sep76.pdf > >> > >> it's DMA on output only; the input side has a FIFO that has to be emptied > >> by the CPU. > > > >Oh. That's amazing, all these years I thought it had DMA both ways. > >Clearly not. I wonder how I got that misunderstanding. > > > > paul
Re: VAX 780 on eBay
On Tue, Jan 11, 2022, 4:52 PM Glen Slick wrote: > On Sun, Jan 9, 2022 at 10:05 AM Josh Dersch via cctalk > wrote: > > > > No blinkenlights. It's not exciting looking. This tracks for PDP-11s > (and > > 8's!) as well. No one pays big money for 11/04, 11/34, 11/44 or LSI-11 > > systems (though prices are creeping up like everything else) but 11/05, > > 11/40, 11/70, etc. sell for huge amounts every time. There's an 11/70 > > front panel at over $500 on eBay right now with two days left, it'll > > probably sell for $2500. > > > > Not even close. Only sold for $1800 :) > > https://www.ebay.com/itm/185225084454 Another DECDataSystem 570 version front panel just sold for $1850 https://www.ebay.com/itm/265512455331 Blinkenlights always makes a huge difference.
Re: VAX 780 on eBay
On Sun, Jan 9, 2022 at 10:05 AM Josh Dersch via cctalk wrote: > > No blinkenlights. It's not exciting looking. This tracks for PDP-11s (and > 8's!) as well. No one pays big money for 11/04, 11/34, 11/44 or LSI-11 > systems (though prices are creeping up like everything else) but 11/05, > 11/40, 11/70, etc. sell for huge amounts every time. There's an 11/70 > front panel at over $500 on eBay right now with two days left, it'll > probably sell for $2500. > Not even close. Only sold for $1800 :) https://www.ebay.com/itm/185225084454
Re: DEC RF30 Integrated Storage Element Service Guide
On Sun, Jan 2, 2022 at 9:22 AM Rob Jarratt via cctalk wrote: > > Hmm... There was already a terminator installed. I tried to remove it in > case there was some kind of double termination, but that didn't seem to > resolve it. The terminator is good because the machine works with other > disks. If other disks work when they are swapped in without making any other changes, it is probably not a termination issue. However, you still might want to double check that the DSSI bus is properly terminated at both ends. If the M7769 KFQSA is attached to a bulkhead connector panel, there are two versions, one with a single DSSI connector, and one with two DSSI connectors. If the bulkhead connector panel has a single DSSI connector, there should be SIP terminators installed on the M7769 KFQSA next to the DSSI connector on the M7769 KFQSA as one end of the DSSI bus. If the bulkhead connector panel has two DSSI connectors, the SIP terminators should be removed on the M7769 KFQSA next to the DSSI connector on the M7769 KFQSA, and there should be an external terminator on one of the two DSSI connectors on the bulkhead connector panel. If there is no bulkhead connector panel connected directly to the M7769 KFQSA, and instead it is connected to an internal DSSI bus cable inside the chassis, and the M7769 KFQSA is at the end of the internal DSSI bus cable, there should be SIP terminators installed on the M7769 KFQSA next to the DSSI connector on the M7769 KFQSA as one end of the DSSI bus. I would expect the other end of the internal DSSI bus cable to connect to a bulkhead connector panel, which should have an external terminator attached as the other end of the DSSI bus.
Re: HP 1000 A900 ("Magic") Questions
On Sat, Dec 18, 2021 at 11:46 PM Joseph Dziedzic via cctalk wrote: > > Are you still in need of any HP1000 RTE equipment? I have a lot of boards, > chassis’, tape drives, etc. If not and if you know of someone who would be > interested in this equipment please let me know…Kind Regards…Joe > Where are you located? While shipping boards might not be expensive, shipping chassis and tape drives could be expensive depending on location. Do you have a list of what equipment you have?
Re: NI PCI-GPIB+ Analyzer boards on ebay
On Thu, Dec 9, 2021 at 2:26 PM Guy Dunphy via cctalk wrote: > > About the software: > I bought a couple of that seller's cards; one each of 284088568161 & > 284088570014. > Asked him about the software. Here's his reply. > > Regarding your question about the Analyzer software, if I recall correctly it > comes bundled in the "NI-488.2" software package. I believe the version in my > screenshot in the eBay listing was v17.6 for Win7 SP1 x86, but it should > still be fully supported in the newest v21.0 package for x86 or x64 systems. > I was curious enough that I also picked up a PCI-GPIB+, one of the newer versions and apparently the current version, same version as item 284088570014 instead of the earlier version as item 284088568161. The two versions might be functionally equivalent, maybe it was just a redesign for cost reduction and/or some components of the design reaching end of production status. When I receive the PCI-GPIB+ I'll have to see if I can get it up and running with the analyzer software.
Re: NI PCI-GPIB+ Analyzer boards on ebay
On Wed, Dec 8, 2021 at 10:50 PM Rodney Brown via cctalk wrote: > > NI National Instruments PCI-GPIB+ Analyzer PCI IEEE488.2 Interface Card > > While a photo shows the Windows NI Analyzer software in use, the item > doesn't mention it. > > If NI will provide the analyzer software, these could be used to capture > HP-IB traffic to characterize the attached devices, timings etc. > Has anyone recently installed and used the NI GPIB Analyzer software? Is that something that must be obtained and installed separately, or is it included as an optional component of the standard NI-488.2 download and installation? I suppose I could try downloading and installing the 1.19 GB current 21.0.0 version of the NI-488.2 software to take a look. The current 21.0.0 version of NI-VISA is another 1.11 GB download.
Re: IEEE-488 on the PDP-11
On Tue, Nov 16, 2021 at 2:58 PM Toby Thain via cctalk wrote: > > On 2021-11-16 1:25 p.m., Glen Slick via cctalk wrote: > > On Tue, Nov 16, 2021 at 9:23 AM Douglas Taylor via cctalk > > wrote: > >> > >> I'm going by the 'Instrument Bus Subroutines Programmer's Reference > >> Manual' that is on bitsavers. [/pdf/dec/pdp11/minc] In section 4, page > >> 4-1 it seems to imply that there are 6 files: > >> > >> IBLIB.OBJ > >> IBSVER.FOR > >> IBMNC.SYS > >> IBNMNC.SYS > >> IBXMNC.SYS > >> IBXNMC.SYS > >> > >> I think that's it. *.OBJ is a library to link to, *.FOR is a test > >> program, *.SYS are device drivers for MINC and ordinary PDP-11 SJ, FB > >> and XM monitors. It probably is on it's own disk (RX01 RX02?) > >> > >> Doug > > > > I have an original DEC RX01 floppy labeled: > > > > AS-H300E-BC > > INSTMT BUS SUB V2.1 BIN RX1 > > (c) 1983 Digital Equipment Corporation > > > > I have an image I created from that floppy which I can mount using > > PUTR, and then access the files on the floppy image: > > > > > Hi Glen, > > Can you make the image available? > > Thanks > --Toby Disk images have been sent to Al. I assume he will eventually upload them to Bitsavers when he has time to do so...
Re: IEEE-488 on the PDP-11
On Tue, Nov 16, 2021 at 9:23 AM Douglas Taylor via cctalk
wrote:
>
> I'm going by the 'Instrument Bus Subroutines Programmer's Reference
> Manual' that is on bitsavers. [/pdf/dec/pdp11/minc] In section 4, page
> 4-1 it seems to imply that there are 6 files:
>
> IBLIB.OBJ
> IBSVER.FOR
> IBMNC.SYS
> IBNMNC.SYS
> IBXMNC.SYS
> IBXNMC.SYS
>
> I think that's it. *.OBJ is a library to link to, *.FOR is a test
> program, *.SYS are device drivers for MINC and ordinary PDP-11 SJ, FB
> and XM monitors. It probably is on it's own disk (RX01 RX02?)
>
> Doug
I have an original DEC RX01 floppy labeled:
AS-H300E-BC
INSTMT BUS SUB V2.1 BIN RX1
(c) 1983 Digital Equipment Corporation
I have an image I created from that floppy which I can mount using
PUTR, and then access the files on the floppy image:
C:\PUTR>PUTR
PUTR V2.01 Copyright (C) 1995-2001 by John Wilson .
All rights reserved. See www.dbit.com for other DEC-related software.
COPY mode is ASCII, SET COPY BINARY to change
(C:\PUTR)>MOUNT RX0: AS-H300E.IMG /RONLY /RX01
(C:\PUTR)>DIR RX0:
Volume in drive RX0 is RT11A
Directory of RX0:\*.*
16-Nov-2021
IB.MAC76 27-Mar-1982
IBBASE.MAC 8 27-Mar-1982
IBCBLK.MAC 3 27-Mar-1982
IBCMD .MAC 2 27-Mar-1982
IBDCL .MAC 1 27-Mar-1982
IBDEV .MAC 2 27-Mar-1982
IBERMF.MAC 5 27-Mar-1982
IBERR .MAC 4 27-Mar-1982
IBERRF.MAC 2 27-Mar-1982
IBERSH.MAC 3 27-Mar-1982
IBGET .MAC 1 27-Mar-1982
IBGTL .MAC 1 27-Mar-1982
IBIFC .MAC 1 27-Mar-1982
IBINIT.MAC 6 27-Mar-1982
IBLEGL.MAC 2 27-Mar-1982
IBLLO .MAC 1 27-Mar-1982
IBLNR .MAC 2 27-Mar-1982
IBLSN .MAC 5 27-Mar-1982
IBPPD .MAC 2 27-Mar-1982
IBPPE .MAC 2 27-Mar-1982
IBPPL .MAC 2 27-Mar-1982
IBPPU .MAC 1 27-Mar-1982
IBRCVS.MAC 1 27-Mar-1982
IBRDA .MAC 1 27-Mar-1982
IBRECV.MAC 3 27-Mar-1982
IBREMO.MAC 2 27-Mar-1982
IBREN .MAC 1 27-Mar-1982
IBSDC .MAC 1 27-Mar-1982
IBSEND.MAC 3 27-Mar-1982
IBSPL .MAC 3 27-Mar-1982
IBSRQ .MAC 5 27-Mar-1982
IBSRQF.MAC 1 27-Mar-1982
IBSTER.MAC 2 27-Mar-1982
IBSTS .MAC 2 27-Mar-1982
IBTERM.MAC 2 27-Mar-1982
IBTIMO.MAC 2 27-Mar-1982
IBTLK .MAC 4 27-Mar-1982
IBUNIT.MAC 2 27-Mar-1982
IBUNL .MAC 2 27-Mar-1982
IBUNT .MAC 2 27-Mar-1982
IBWAIT.MAC 1 27-Mar-1982
IBXFER.MAC 3 27-Mar-1982
IB.ASM 9 27-Mar-1982
IBLOC .ASM 1 27-Mar-1982
IBMNC .SYS10 27-Mar-1982
IBXMNC.SYS11 27-Mar-1982
IBNMNC.SYS10 27-Mar-1982
IBXNMC.SYS11 27-Mar-1982
IBDBLD.COM 1 27-Mar-1982
IBLIB .OBJ45 27-May-1982
IBSVER.FOR 7 27-Mar-1982
IBXBLD.COM 1 08-Mar-1983
IBSBLD.COM 2 08-Mar-1983
IBLBLD.COM10 27-Mar-1982
< UNUSED > 193
54 Files, 293 Blocks
193 Free blocks
(C:\PUTR)>COPY RX0:IBSVER.FOR C:
IBSVER.FOR
C
C
C THIS PROGRAM IS THE INSTALLATION/VERIFICATION PROGRAM FOR THE IBS IEEE BUS
C INTERFACE ROUTINES.
C
C*
C
EXTERNAL SERVE !ADDRESS OF USER'S SRQ HANDLING ROUTINE.
BYTE ASCII(26) !ASCII ARRAY CONTAINING THE ALPHABET.
INTEGER TALK,STAT
IBZERO=' ' !ASCII CODE FOR ZERO INSTRUMENT ADDRESS
LISTEN=5 !OUR LISTENER'S PRIMARY IEEE BUS ADDRESS.
TALK=6 !OUR TALKER'S PRIMARY IEEE BUS ADDRESS.
MAXL=15 !OUR MAXIMUM TRANSMIT/RECEIVE LENGTH.
LINE=6
C
TYPE 1000
1000 FORMAT('1 IBS-11 V2.1 Verification Program'///
1' This procedure assumes that IB.SYS (or IBX.SYS) has been INSTALLED
2 and LOADED'/' in this system. Also, this procedure assumes
3 that no devices'/' are connected to your IBV11-A/IB11
4 instrument bus.')
TYPE 1001
1001 FORMAT(//' The first part of this test calls routines that do
1 not depend'/' on any device and thus should produce no
2 error messages.'//)
C
CALL IBSTER(16,20) !ALLOW ERROR NUMBER 16 (TIME-OUT) TO OCCUR 20 X
CALL IBSTER(5,5) !ALLOW THE NO DEFAULT LISTENER ERROR 5 TIMES
CALL IBSTER(7,2) !ALLOW THE BAD UNIT ERROR TO OCCUR TWICE
CALL IBSTER(15,25) !ALLOW THE NO VALID LISTENER ERROR TO OCCUR 25 X
CALL IBSRQ(SERVE,,,STAT) !SET-UP TO HANDLE SRQ'S
CALL IBSRQF(IFLG) !GET STATUS OF SRQ IEEE INTERFACE CONTROL LINE
CALL IBTERM() !CLEARS INTERNAL TERMINATOR'S LIST
CALL IBPPL !CONDUCT A PARALLEL POLL
CALL IBIFC !ISSUE THE IEEE INTERFACE-CLEAR
STAT=IBERRF() !GET ERROR INFORMATION
CALL IBRDA !DISABLE (TURN-OFF) THE IEEE REMOTE LINE
CALL IBREN !ENABLE (TURN-ON) THE IEEE REMOTE LINE
TYPE 1002,IBREMO() !READ AND TYPE THE REMOTE LINE STATUS
1002 FORMAT(' IBREMO should return minus one at this point. IBREMO ='
1I6)
C
TYPE 1003
1003 FORMAT(//' At this point non-fatal error messages should begin to
1 appear.'//' EXPECTED ERROR MESSAGES'
2/' ---')
CALL IBTIMO(120) !SET TIME-OUT VALUE TO 2 SECONDS
CALL IBDEV(TALK,IBZERO) !SET-UP SRQ-CAPABLE DEVICE ADDRESS LIST
CALL IBLNR() !CHECK FOR VALID LISTENERS
CALL IBSEND(ASCII,MAXL,LISTEN)
CALL
Re: SQ703/6 conversion and a little fun
On Mon, Nov 1, 2021 at 4:23 AM Nigel Johnson Ham via cctalk wrote: > > A few months ago, thanks to help from several people here, I converted > an SQ703 TMSCP controller to SQ706 MSCP. > > .. > > It seems that one of the PALs is maybe setting up the address! > > Anybody else tried this? I never tried it with a Dilog SQ703 and SQ706. The two that I have have numerous differences between the boards, which made me skeptical that just a simple EPROM swap would be the only change necessary. However with the newer S-handle versions of the Dilog TMSCP SQ3703A and MSCP SQ3706A boards that I have, they appear identical except for the EPROMs. On those I did try swapping the EPROMs between the two boards and that did appear to completely swap them between TMSCP and MSCP functionality.
Re: Programming Bipolar PROMs
On Mon, Sep 27, 2021 at 11:20 AM Brent Hilpert via cctalk wrote: > > The 82S23 programming algorithm is in the 1975 Signetics Bipolar Memories > databook (also on bitsavers). > Looks like it may be a little more complex than that for the 188. http://www.bitsavers.org/components/signetics/_dataBooks/1977_Signetics_Bipolar_and_MOS_Memory.pdf Page 91, timing diagram on Page 92 82S23 PROGRAMMING PROCEDURE 1. Terminate all device outputs with a 10K Ohm resistor to Vcc. 2. Select the address to be programmed, and raise Vcc to Vccp = +10 ± 0.5V. 3. After 10us delay, apply Iout = 65 ± 3mA to the output to be programmed. Program one output at a time. 4. After 10us delay, pulse the /CE input to logic low for 0.3 to 0.5us. 5. After 10us delay, remove Iout from the programmed output. 6. After 10us delay, return Vcc to 0V. 7. To verify programming, after 50us delay, raise Vcc to Vcch = +5.5 ± 0.2V, and apply a logic low level to the /CE input. The programmed output should remain in the high state. Again, lower Vcc to Vccl = +4.5 ± 0.2V, and verify that the programmed output remains in the high state. 8. Raise Vcc to Vccp = +10 ± 0.5V and repeat steps 3 through 7 to program other bits at the same address. 9. After 10us delay, repeat steps 2 through 8 to program all other address locations. http://www.bitsavers.org/components/signetics/_dataBooks/1975_Signetics_Bipolar_Memories.pdf Page 24, timing diagram on Page 25 Same as above, except different timing in step 4. 4. After 10us delay, pulse the /CE input to logic "0" for 1 to 2 ms. (of course in case of typos above, refer to the manuals)
Re: Programming Bipolar PROMs
On Mon, Sep 27, 2021 at 8:23 AM Tom Hunter via cctalk wrote: > > The part is an Intersil IM5600CP, but these were also made by others, for > example Signetics and Philips made the 82S23 and TI and NTE made the faster > SN74S188N. Some vendors still sell these parts and there are even a few on > Ebay. > > How do I program these PROMs? I found one somewhat obscure description of > the algorithm in the NTE datasheet, but I suspect that each manufacturer > had (somewhat) different algorithms. > > Is there an affordable commercial programmer out there which can program > these PROMs? > How do you program a single bipolar PROM as a one time occurance? Find someone willing to do it for you for the cost of the postage :) Are there affordable commercial programmers which can reliably program bipolar PROMs with device vendor approved programming algorithms? I have an older Data I/O UniSite and a newer BP Microsystems BP-1610 which between the two of them can cover the majority of those older devices, and the BP-1610 is currently supported with regular software updates. I wouldn't call either of those two programmers "affordable", and you have to be patient to pick one up on eBay. The older parallel port interface BP-1200 and BP-1400 device programmers probably have the same bipolar PROM support as the BP-1610, and can more often be found at somewhat reasonable prices on eBay, but software updates for new devices were discontinued for those non-USB interface programmers several years ago.
Re: Burnable, patched Microvax-2000 SCSI-boot EPROM images?
On Tue, Sep 21, 2021 at 9:00 AM Jonathan Stone via cctalk wrote: > > One of the reasons I got the 2000s is to format MFM drives for an RQDX3 (I > don't have any PDP-11 CPUs). I have a CMD CQD-420 Qbus SCSi controller, and > an MTI almost-equivalent. I've seen Glen Slick's reverse engineering of the > PLD for the CDQ-200. I hope the newer MTI board "just works"; but if not, MFM > is a fallback. The MTI QTS-30 board I have is essentially the same thing as a CMD CQD-200 board, just with different firmware. It can be converted into a CQD-200/TM functional equivalent by swapping the firmware EPROMs and CSR decode PAL. I haven't seen an MTI version of the CMD CQD-420 board. The CQD-420 is more similar to the CQD-220A than the CQD-220, with the standard CSR address decoding being done in the QBC0420 ASIC instead of in the PAL. The CQD-220A / CQD-420 PALs only decode the "special" disk/tape CSR address when that is selected via the address selection DIP switches.
Re: VAXstation 100 ROM image
On Tue, Sep 21, 2021 at 9:10 AM Lars Brinkhoff via cctalk wrote: > > Hello, > > Does anyone have a (set of) ROM image(s) for the VAXstation 100? > It might be interesting to attempt an emulator. Did someone on the list buy this one? That was the only one that I have noticed for sale on eBay anytime recently. https://www.ebay.com/itm/294252478149 Rare Dec Vaxstation 100 Prototype Digital VAX Ended: Jul 07, 2021 Winning bid: US $256.00
Re: howto bitsavers BASIC-11 v2 disk image under simh
On Thu, Aug 12, 2021 at 5:29 PM Fritz Mueller wrote:
>
>
> > On Aug 12, 2021, at 3:31 PM, Glen Slick wrote:
> > If I translate the logical
> > sector order RX-02 disk image back into a physical sector order disk
> > image (dealing with track shifting, sector interleaving, and track to
> > track sector skewing) then RT-11 on SIMH is happy with the disk image.
>
> Ah, interesting... Where's the best place to look for more information in
> the RX02 RT-11 logical/physical mapping?
>
> Glen, if you wouldn't mind sending me a copy of your resulting
> simh-compatible image, I'd be happy to post it in an upcoming blog article
> for others who might find it useful as well...
>
> cheers,
> --FritzM.
One bit of information that I found helpful as a reference when I
looked at this quite a while ago was the 2.11BSD RX02 floppy disk
device driver source code, which can be viewed online here:
https://minnie.tuhs.org/cgi-bin/utree.pl?file=2.11BSD/sys/pdpuba/rx.c
In particular, the routine rxfactr(), which as the comment says it
calculates the physical sector and physical track on the disk for a
given logical sector.
I used that as a starting point to write a simple utility to read an
RX-02 disk image file in logical sector order and output an RX-02 disk
image file in physical sector order.
/*
* rxfactr -- calculates the physical sector and physical
* track on the disk for a given logical sector.
* call:
* rxfactr(logical_sector,_sector,_track);
* the logical sector number (0 - 2001) is converted
* to a physical sector number (1 - 26) and a physical
* track number (0 - 76).
* the logical sectors specify physical sectors that
* are interleaved with a factor of 2. thus the sectors
* are read in the following order for increasing
* logical sector numbers (1,3, ... 23,25,2,4, ... 24,26)
* There is also a 6 sector slew between tracks.
* Logical sectors start at track 1, sector 1; go to
* track 76 and then to track 0. Thus, for example, unix block number
* 498 starts at track 0, sector 25 and runs thru track 0, sector 2
* (or 6 depending on density).
*/
static
rxfactr(sectr, psectr, ptrck)
register int sectr;
int *psectr, *ptrck;
{
register int p1, p2;
p1 = sectr / 26;
p2 = sectr % 26;
/* 2 to 1 interleave */
p2 = (2 * p2 + (p2 >= 13 ? 1 : 0)) % 26;
/* 6 sector per track slew */
*psectr = 1 + (p2 + 6 * p1) % 26;
if (++p1 >= 77)
p1 = 0;
*ptrck = p1;
}
Re: howto bitsavers BASIC-11 v2 disk image under simh
On Wed, Aug 11, 2021 at 5:59 PM Paul Koning wrote: > > > On Aug 11, 2021, at 7:06 PM, Fritz Mueller via cctalk > > wrote: > > > >> ... > > > > Ah ha! Thanks much, Glen! > > > > simh is usually pretty good about padding out attached images, > > No, I don't think that is true. What is true is that recent versions of SIMH > will create full size container files for disk containers. But sufficiently > old versions did not, so it is not too strange to run into, say, an RK05 > image that's shorter than 4800 blocks. > > But those normally work; all that happens is that reading too far either > gives you zeroes or a read error, I don't remember which. Since the blocks > were never written they should be marked as unused in the file system and > nothing will read them, so that's fine. > > If there's an unused track at the start of a SIMH image file and in your copy > that was missing, that's a different case. Is that the issue? > > Or is the RX02 emulation different from regular disks? > > paul It's been a while since the last time I did anything with a SIMH PDP-11. I just fired up the simh-4.0-Current--2020-06-09-0912a927 version that I last used to take a look at these RX-02 disk images. As far as I can tell by default PUTR expects to work with logical sector order RX-02 disk images that are 512,512 bytes in size. The BASIC-11 RX-02 disk image available here is in logical sector order, but is less than 512,512 bytes in size: http://www.bitsavers.org/bits/DEC/pdp11/floppyimages/rx02/ PUTR appears to be unhappy with the disk image unless it is padded to 512,512 bytes in size. On the other hand as far as I can tell by default SIMH expects to work with physical sector order RX-02 disk images. If I mount the logical sector order RX-02 disk image that works with PUTR in SIMH, then RT-11 gives a "?DIR-F-Invalid directory" error. If I translate the logical sector order RX-02 disk image back into a physical sector order disk image (dealing with track shifting, sector interleaving, and track to track sector skewing) then RT-11 on SIMH is happy with the disk image.
Re: howto bitsavers BASIC-11 v2 disk image under simh
On Wed, Aug 11, 2021 at 8:57 AM Fritz Mueller via cctalk wrote: > > Hi folks, > > Could anybody spare a clue or some suggestions on how to access the contents > of: > > http://bitsavers.trailing-edge.com/bits/DEC/pdp11/floppyimages/rx02/BASIC-11_V2.1_RX02.DSK.zip > > under simh? I haven't had any luck mounting the contained BASIC.DSK e.g. on > simh RY under RT-11. Looking through a dump of the image, there seems to be > an "RT11A" signature. Tried putr under dosbox as well, but it seems to hang > mounting the image. > > Suggestions appreciated! > > --FritzM. > That BASIC.DSK image file has a size of 486,400 bytes. I don't know where that size would come from. A physical RX-02 floppy should have a sector size of 256 bytes, with 26 sectors per track, and 77 tracks, which would be a total of 512,512 bytes, or 505,856 bytes if the first physical track is ignored. Indeed, the other RX-02 floppy images available here do have a size of 505,856 bytes: http://www.bitsavers.org/bits/DEC/pdp11/floppyimages/rx02/ Hmm, maybe that BASIC.DSK image file was created by something that only copied the initial allocated logical sectors and ignored unused logical sectors at the end of the floppy, and maybe PUTR doesn't handle disk image files that are not the expected full size? Example of padding the 486,400 byte BASIC.DSK image file to a size of 512,512 bytes on a Windows system: FSUTIL FILE CREATENEW BLANK 26112 COPY /B BASIC.DSK+BLANK TEST.DSK C:\PUTR>DIR TEST.DSK Volume in drive C has no label. Volume Serial Number is 14CE-1A29 Directory of C:\PUTR 08/11/2021 12:55p 512,512 TEST.DSK C:\PUTR>PUTR PUTR V2.01 Copyright (C) 1995-2001 by John Wilson . All rights reserved. See www.dbit.com for other DEC-related software. COPY mode is ASCII, SET COPY BINARY to change (C:\PUTR)>MOUNT RX: TEST.DSK /RX02 /RT11 /RONLY (C:\PUTR)>DIR RX: Volume in drive RX is RT11A Directory of RX:\*.* 11-Aug-2021 BSOT0D.EAE12 04-Apr-1983 BSOT0S.EAE10 04-Apr-1983 BSOT1D.EAE 9 04-Apr-1983 BSOT1S.EAE 6 04-Apr-1983 BSOT0D.EIS12 04-Apr-1983 BSOT0S.EIS 9 04-Apr-1983 BSOT1D.EIS 9 04-Apr-1983 BSOT1S.EIS 6 04-Apr-1983 BSOT0S.FIS 7 04-Apr-1983 BSOT1S.FIS 6 04-Apr-1983 BSOT0D.FPU 7 04-Apr-1983 BSOT0S.FPU 7 04-Apr-1983 BSOT1D.FPU 4 04-Apr-1983 BSOT1S.FPU 3 04-Apr-1983 BSCLIN.OBJ 1 04-Apr-1983 BSCLLB.OBJ 5 04-Apr-1983 BSCLS .OBJ 6 04-Apr-1983 BSCLSN.OBJ 1 04-Apr-1983 BSCMP .OBJ 5 04-Apr-1983 BSERML.OBJ 8 04-Apr-1983 BSERMS.OBJ 5 04-Apr-1983 BSERR .OBJ 2 04-Apr-1983 BSE0 .OBJ16 04-Apr-1983 BSE1 .OBJ 8 04-Apr-1983 BSFUNC.OBJ 9 04-Apr-1983 BSKEYS.OBJ 6 04-Apr-1983 BSOT0D.OBJ12 04-Apr-1983 BSOT0S.OBJ 9 04-Apr-1983 BSOT1D.OBJ 9 04-Apr-1983 BSOT1S.OBJ 6 04-Apr-1983 BSPAT .OBJ 2 04-Apr-1983 BSPR0 .OBJ 3 04-Apr-1983 BSPR0N.OBJ 3 04-Apr-1983 BSPR1 .OBJ 7 04-Apr-1983 BSPR1N.OBJ 1 04-Apr-1983 BSPTRD.OBJ 6 04-Apr-1983 BSPTRS.OBJ 6 04-Apr-1983 BSRSQ .OBJ 2 04-Apr-1983 BSRSQN.OBJ 1 04-Apr-1983 BSR0D .OBJ 9 04-Apr-1983 BSR0S .OBJ 8 04-Apr-1983 BSR1D .OBJ 4 04-Apr-1983 BSR1S .OBJ 3 04-Apr-1983 BSSUB .OBJ 2 04-Apr-1983 BSSUBN.OBJ 1 04-Apr-1983 BSX0A .OBJ11 04-Apr-1983 BSX0B .OBJ 8 04-Apr-1983 BSX1A .OBJ 8 04-Apr-1983 BSX1B .OBJ 7 04-Apr-1983 BSX2 .OBJ 7 04-Apr-1983 SUDTCM.OBJ 2 04-Apr-1983 SUEID .OBJ 1 04-Apr-1983 SUE1ID.OBJ 1 04-Apr-1983 SUIMP .OBJ 3 04-Apr-1983 SUIOID.OBJ 1 04-Apr-1983 SUIOPO.OBJ11 04-Apr-1983 SUIOPR.OBJ 4 04-Apr-1983 SUOPT .OBJ 5 04-Apr-1983 SUO1ID.OBJ 1 04-Apr-1983 SUR1ID.OBJ 1 04-Apr-1983 SUXID .OBJ 1 04-Apr-1983 SUX2ID.OBJ 1 04-Apr-1983 SUCNFG.BAS 3 04-Apr-1983 SUCNF1.BAS 7 04-Apr-1983 SUCNF2.BAS 4 04-Apr-1983 SUCNF3.BAS 4 04-Apr-1983 SUCNF4.BAS 4 04-Apr-1983 SUCNF5.BAS 5 04-Apr-1983 SUCNF6.BAS 5 04-Apr-1983 SUCNF7.BAS 5 04-Apr-1983 SUCVT .BAS 6 04-Apr-1983 SUCVT1.BAS14 04-Apr-1983 SUCNFG.DAT 7 04-Apr-1983 BSASM .MAC 5 04-Apr-1983 BSCLI .SAV 2 27-Mar-1987 BSMAC .MAC10 04-Apr-1983 BASIC .SAV53 04-Apr-1983 YSTART.OBJ 1 30-Mar-1987 ZSTART.OBJ 1 30-Mar-1987 BSASM .OLD 5 04-Apr-1983 BSCLI .OLD 5 04-Apr-1983 BSMAC .OLD10 04-Apr-1983 BSCLIN.SAV 2 27-Mar-1987 BSASM .OBJ 1 27-Mar-1987 POSITI.LST 7 02-Apr-1987 XSTART.OBJ 1 30-Mar-1987 BSCLI .OK1 9 01-May-1987 JOYSTI.OK1 2 01-May-1987 CNC .OK1 1 01-May-1987 < UNUSED >12 ACMOTO.MAC 2 13-May-1987 WINDOW.MAC 4 13-May-1987 POSITI.MAC 2 13-May-1987 JOYSTI.MAC 2 13-May-1987 SPEEDS.OLD 2 13-May-1987 < UNUSED > 1 XSTASP.OBJ 1 13-May-1987 YSTASP.OBJ 1 13-May-1987 ZSTASP.OBJ 1 13-May-1987 XDIREC.OBJ 1 13-May-1987 YDIREC.OBJ 1 13-May-1987 ZDIREC.OBJ 1 13-May-1987 ACMOTO.OBJ 1
Re: PC floppy disk sets avaialble free
On Mon, Aug 9, 2021, 11:17 AM John Foust via cctalk wrote: > At 11:23 AM 8/9/2021, Al Kossow via cctalk wrote: > >sometimes I wonder why I even bother putting this s*it up > > Well, actually... it said "Pathworks V5.1 (35 disks) plus LAN Mgr Setup." > > So is it 5.1 or is it the 4.1 you have on Bitsavers? > > An ISO of a 5.1 CD is at > https://vetusware.com/download/Pathworks%205.1/?id=8935 > if that's a real site. > > - John > There is also a Compaq PATHWORKS 32 Version 7.2. 2000 May AG-R36UE-BE.iso.zip (112 Mb) CD image available here: http://www.vaxhaven.com/CD_Image_Archive >
Re: Multi-Micro-Channel bus systems, and thoughts on the Computer Society Digital Library.
On Sun, Jul 25, 2021, 6:43 AM Chris Zach via cctalk wrote: > Read that Personal Systems magazine from 1992 that was recently posted > and enjoyed the article on the PS/2 295 system. I never heard about that > one, the biggest PS/2's I worked on were the 95 systems with 486 > processors back at Covington. > > One thing that popped out: The 295 was a multi-processor-ish system with > two MCA busses. Granted they were decoupled with each processor having > its own MCA bus but it got me to thinking: Were there other systems of > that time that could use two MicroChannel busses? > 7013-595 IBM RS/6000 Deskside Server Model 595, Announced 1996/10/08, Available 1996/11/08 Model Abstract 7013-595 The IBM* RS/6000 Model 595 deskside server is a powerful uniprocessor that is based on the POWER2 Super Chip (P2SC) implementation of the POWER Architecture*. The Model 595 differs from predecessors by offering high-performance, dual Micro Channel* buses. Each bus is used to generate four Micro Channel slots and supports the high-speed, data streaming protocol. >
Re: HP 2100A Restoration
On Sat, Jul 17, 2021 at 2:28 PM johnr@grebnesor via cctalk wrote: > > Hello, > > I came across a web article in which you discussed restoring an HP2100A. I > spent many years working on this computer and have the front panel. I am > doing some work on it to produce a display for fun. I am replacing the > incandescent globes with LEDs and using a Raspberry Pi to control them. > > The question I have is, do you know an easy way to remove and insert globes > in the front panel switches please? The HP 2100A front panel uses T-1.75 Bi-Pin base miniature lamps. The last time I replaced some, if I remember correctly, I used Chicago Miniature CM7361 lamps for replacement. I forget if I was able to get a grip on them at all with needle-nose pliers to pull them out, or if I used something else. If you look for purpose built tools it appears that there are a couple of common styles. One style uses some sort of flexible plastic or rubber tube that is just the right diameter and wall thickness that it can be pushed on to the lamp, and then maintain enough friction on the lamp to pull it out when the tube is pulled out. Another style uses a metal tube that is split along its length that can be pushed on to the lamp when the halves of the tube are separated, then the halves of the tube can be pressed together to grip the lamp so it can be pulled out when the tube is pulled out. An example of the second style that shows up in a lot of lamp extractor searches is the Jonard S-339: https://jonard.com/s-339-lamp-extractor At somewhere around $30 for those tools I haven't been curious enough about buying one to see if it is suitable for removing and inserting HP 2100A front panel lamps.
Re: VT340 Emulation
On Fri, Jun 25, 2021 at 3:53 PM Grant Taylor via cctalk wrote: > > From my naive point of view, I wonder if it would be possible to build > some sort of USB device that has a traditional UART that has supporting > circuitry to connect to the host over USB. -- I say this because it > sounds like many ~> most ~> all (?) USB to RS-232 converters are doing > something inferior. > Of course that has been done in commercial products. For example I have some Inside Out Networks Edgeport / 4 devices (apparently later sold by Digi) that are implemented using a traditional ST16C654 quad UART and MAX3243E RS-232 transceivers, with an Intel 80930 microcontroller as the interface between the UART and the USB host. The Intel 80930 has an 80251 core integrated with a USB interface, and was one of the first microcontrollers available on the market. This device dates from 1997, so reasonably early in the USB game.
Re: Serial Multisession
> > Also supported by the VT420, VT510, VT520, VT525 > Actually as far as I can tell the VT510 does not support TD/SMP (Terminal Device/Session Management Protocol). No mention of multiple sessions in this VT510 manual as there are in this VT520 manual. http://www.bitsavers.org/pdf/dec/terminal/vt5xx/ http://www.bitsavers.org/pdf/dec/terminal/vt5xx/598-0013866_VT510_Installation_Nov96.pdf http://www.bitsavers.org/pdf/dec/terminal/vt5xx/EK-VT520-IN_VT520_Installation_and_Operating_Information_Apr94.pdf
Re: Serial Multisession
On Thu, Jun 24, 2021 at 1:41 PM Grant Taylor via cctalk wrote: > > Does anyone know anything about the "Serial Multisession" that the VT > LAN 40, and presumably other terminals, supports? > > I've not heard about it before and intend to do some research. But I > figured that it was an interesting enough topic, that is multiplexing > terminal sessions over a single serial link, to warrant further discussion. > https://en.wikipedia.org/wiki/TD/SMP TD/SMP, short for Terminal Device/Session Management Protocol, was a terminal multiplexer system introduced by DEC on their VT330/340 terminals in 1987. The terminal-side was referred to as SSU. TD/SMP allowed data from two separate host sessions to be sent to a compatible computer terminal over a single serial port. The format was patented and never described in depth, limiting it to DEC's own terminal servers and terminals. Also supported by the VT420, VT510, VT520, VT525 Terminal device session management protocol https://patents.google.com/patent/US4791566 https://patents.google.com/patent/US5165020 SSU software was available on OpenVMS
Re: MicroVAX 3300/3400
On Wed, May 26, 2021 at 2:35 PM Zane Healy wrote: > > Except for the DSSI cable strangeness, it’s a really nice chassis. Though > after a LOT of reading in the last 24 hours, may are right on it being a > mongrel. It also explains my confusion as to what it is. :-) > > https://www.zanesphotography.com/Private/MicroVAX/n-96z8NZ/MicroVAX > > This is probably the best of the photo’s of the cabling. > > https://www.zanesphotography.com/Private/MicroVAX/n-96z8NZ/MicroVAX/i-vFkfBQ2/A The 50-pin round cable that plugs into the M7624 KA640 CPU on one end and into the flat 50-pin ribbon cable on the other end, and the 50-pin ribbon cable with the two IDC connectors in the middle and the DSSI bulkhead connector on the other end might be the internal DSSI cabling removed from a BA215 enclosure. Maybe what happened is that someone scraped a MicroVAX 3300 and pulled the M7624 KA640 CPU and internal DSSI cabling out of the BA215 enclosure, and transplanted those into the B400X enclosure, plus added the external DSSI cable to connect the transplanted BA215 enclosure DSSI cabling up to the B400X M9715 DSSI bulkhead connector. Maybe someone here has a spare M7626 KA660 CPU that they could give you a good deal on to replace your possibly dead M7624 KA640 CPU, which would clean up the DSSI cabling at the same time. I don't think I have more M7626 KA660 CPUs on hand myself than BA215/BA430 enclosures to use with them.
Re: MicroVAX 3300/3400
On Wed, May 26, 2021 at 3:38 PM Jonathan Stone wrote: > > two points: > > 1. MS650-AA 8mb modules from a KA650 will work in a KA640. They won't work > with a KA655 or a kA660 (or a KN210_. Those need the MS650-BA, or the 16MB > MS650-BB, or the third-party 32MB modules. So if your KA640 is dead and you > want to upgrade, you will likely need new memory, too. (You likely know this > already.) > I've been wrong about that for several years. I have always assumed that an M7621 MS650-AA 8MB memory board was compatible with all of the M7620 KA650, M7624 KA640, M7625 KA655, and M7626 KA660 CPUs. I didn't realize until now that an M7621 MS650-AA 8MB memory board is only compatible with the M7620 KA650 and M7624 KA640 CPUs, and the M7625 KA655 and M7626 KA660 CPUs are only compatible with the M7622 MS650-BA 16MB memory board (or the less common MS650-BB 8MB version of the M7622). Unless I am also wrong about this, the M7622 MS650-B memory boards are compatible with all of the M7620 KA650, M7624 KA640, M7625 KA655, and M7626 KA660 CPUs. KA655 CPU System Maintenance, Order Number EK-306AA-MG-001 http://www.bitsavers.org/pdf/dec/vax/655/EK-306A-MG-001_655Mnt_Mar89.pdf Page 1-4 (Page 15 of the PDF) "NOTE: The KA655 CPU supports only the MS650-BA (16 Mbyte) memory module. The MS650-AA (8 Mbyte) is not supported because of its slower access speed." KA660 CPU System Maintenance, Order Number EK-398AA-MM-001 http://www.bitsavers.org/pdf/dec/vax/4000/EK-398AA-MM-001_KA660_CPU_System_Maintenance_Dec90.pdf Page 1-10 (Page 20 of the PDF) "1.4 MS650-Bn Memory Modules The MS650-BA and MS650-BB memory modules are quad-height, Q22-bus modules. Timing of the MS650-BA (16 MBytes) and MS650-BB (8 MBytes) modules is dependent upon the KA660 clock speed and CMCTL. The MS650-AA memory module may not be used with the KA660 system CPU."
Re: MicroVAX 3300/3400
On Wed, May 26, 2021 at 2:35 PM Zane Healy wrote: > > One question, do I need to worry about the batteries on the H3602-SA panel? > I can’t imagine that this would be causing any issue. > Yes, you do need to worry about the Ni-Cad battery pack on the H3602-SA panel. Remove it and throw it away. If it hasn't started leaking and causing corrosion yet it is only a matter of time before it does. I have removed all of the Ni-Cad battery packs from all of the VAX systems I have. > An interesting thing about the BA430 backplane is that in addition to > the M7626 KA660 CPU DSSI bus being present on the 50-pin connector, it > is also present on the C/D connectors, and the BA430 backplane routes > the DSSI bus on slot 1 C/D connectors to the DSSI storage device bays > without the need for a DSSI cable. > > I finally found that, in the “KA660 CPU System Maintenance” manual. What’s > interesting is that there is also a 50-pin header on the KA660, and I’m not > yet clear on why. :-) > The M7626 KA660 VAX 4000-200 was available in BA430 and BA215 enclosures. VAX 4000 Model 200 (BA215) Installation, Order Number EK-432AB-IN-002 https://manx-docs.org/collections/antonio/dec/MDS-2000-01/cd1/VAX/432ABIN2.PDF In the BA430 enclosure the KA660 DSSI bus is connected to the DSSI bus on the backplane through the KA660 C/D connectors, and nothing is connected to the 50-pin DSSI connector on the front of the KA660 module. In the BA215 enclosure the DSSI bus is cable based and connects to the 50-pin DSSI connector on the front of the KA660 module.
Re: MicroVAX 3300/3400
On Tue, May 25, 2021 at 8:33 PM Zane Healy via cctalk wrote: > > I just pulled out my blue box of fiche (VAX MDS), and verified I have the > B400X manual, which isn’t online. I’ll see about borrowing a fiche reader > tomorrow. I’ve never bothered to get one, I just borrow my Mom’s portable > reader, when I need it. > If you don't already have a copy of this one, it might be helpful: 400 Series Enclosures Illustrated Parts Breakdown, BA440, BA430, R400X, B400X https://vaxhaven.com/images/9/9d/EK-440AB-IP-002.pdf
Re: MicroVAX 3300/3400
On Tue, May 25, 2021 at 1:32 PM Zane Healy wrote: > > > It turns out that the oddness was the CPU Board, and a 16MB Clearpoint RAM > board. What I thought was the CPU, is really the header panel over the RAM > and TK70 controller. There is also a M9715 between the CPU and the > powersupply that I’d missed seeing. The cables to get to the DSSI connector > by the Powersupply are hanging out the front. Basically it’s a cable going > from the KA640 to a ribbon cable to a cab kit, then DSSI cable from that to > the connector next to the power supply. > Sounds like somewhat of a mongrel system. An M7624 KA640 CPU would typically be found in a 12-slot BA213 as a MicroVAX 3400, or in a smaller 6-slot BA215 as a MicroVAX 3300. As far as I can tell a 12-slot B400X is essentially exactly the same thing as a BA430, where it is a BA430 when used as a VAX 4000-200 with an M7626 KA660 CPU, and a B400X when used as a Q-bus and storage expander. An interesting thing about the BA430 backplane is that in addition to the M7626 KA660 CPU DSSI bus being present on the 50-pin connector, it is also present on the C/D connectors, and the BA430 backplane routes the DSSI bus on slot 1 C/D connectors to the DSSI storage device bays without the need for a DSSI cable. If I remember correctly the DSSI bus is only present on the 50-pin connector of the M7624 KA640 CPU, not on the C/D connectors, so a DSSI cable is needed with that CPU. The hidden M9715 board in slot 0 between the CPU slot 1 and the power supply provides termination power to the internal DSSI and SCSI buses of the BA430 / B400X backplane. It also has a connector which routes to the DSSI bus on the C/D connectors. In the BA430 nothing connects to the M9715 connector as the DSSI bus should be coming from the M7626 KA660 CPU C/D connectors. In the B400X there should be an external bulkhead DSSI connector with a ribbon cable to the M9715 connector. In both the BA430 / B400X there should be another external DSSI connector to the left of slot 12, which is the other end of the DSSI bus. So it sounds like you have a B400X with the M9715 internally cabled to the external bulkhead DSSI connector as usual, and the M7624 KA640 CPU internally cabled to an external bulkhead DSSI connector, and then an external DSSI cable between those two bulkhead connectors. If that is basically how the DSSI things were cabled up, did you also have a DSSI terminator on the bulkhead connector to the left of slot 12? Without checking this myself with a M7624 KA640 CPU you probably get some sort of errors somewhere if the end of the DSSI bus is not terminated. If you were to find an M7626 KA660 CPU you could do away with all of the DSSI cabling between the CPU and the M9715 (in addition to having a CPU that is around twice as fast).
Re: MicroVAX 3300/3400
On Tue, May 25, 2021 at 10:54 AM Zane Healy via cctalk wrote: > > One odd thing is that the KA640-A seems to plug into another board, before > the DSSI drives. I’m getting ready to dig into that, and find out what that > board is. > Is that an M9715 board plugged into the backplane between the CPU board slot and the power supply, or something else? Or is there a cable plugged into the DSSI connector on the M7624 KA640 adjacent to the memory bus connector that plugs into a some board and stops there, and then another cable from that board to the DSSI drives? Do the DSSI drives plug into the backplane, or do they have cables connecting to them?
Re: COMPAQ ISA PC to ethernent
On Thu, May 20, 2021, 7:02 PM Randy Dawson via cctalk wrote: > If anyone has ideas about boards or software to connect this original > Compaq to the net let me know! > Browsing the ebay, I do not find a PC 8 bit ethernet board but still > looking. > Then, the rest, a net set of tools in source would be great. Intel 8/16 LAN Adapter is one common choice.
Re: Looking for VAXSET Software Engineering Tools for VMS 4.x
On Sun, May 16, 2021 at 2:03 PM Zane Healy via cctalk wrote: > > What exactly is VAX/VMS V5.5-2H4? I’ve never been too clear on that. It’s > just V5.5-2 with added hardware support, isn’t it? https://wiki.vmssoftware.com/OpenVMS VIKING V5.5-2H4 July 26,1993 Limited Hardware Release based on V5.5-2. Includes support for VAX 4000 models: 100A, 500A, 600A, 700A. Also supports 2nd SCSI adapter, KZDDA, on MicroVAX 3100 Model 90. Also includes support for DEFTA (FDDI to TURBOchannel adapter) and DEFQA (FDDI to Q-bus adapter) and Tagged Command Queuing (TCQ) for StorageWorks RAID Array 110 Subsystem.
Re: Is this a new record?
On Thu, Apr 22, 2021 at 4:20 PM Josh Dersch via cctalk wrote: > > https://www.ebay.com/itm/164815576309 > > $9570 for a keyboard. There were several retracted bids around $5,500, $9,000, and $10,000 which were retracted immediately after they were placed. I wonder if that was bidders placing high bids just to probe what the current high bidder upper limit was before retracting their probe bid. That's one of the reasons why it isn't the best idea to place your true high bid early, and instead wait until the very end.
Re: PDP 11/23 for sale on Ebay
On Wed, Apr 21, 2021 at 8:18 AM Jeffrey S. Worley via cctalk wrote: > > There's a nice, working PDP 11/23 with 20 meg hdd and 1meg (!!) of ram, > with terminal screens indicating full operation. The asking price is > $900.00, but I imagine the fellow might negotiate. Shipping is gonna > be a fair penny. > I assume you mean this one: https://www.ebay.com/itm/154037992233 Item location: Winnetka, California, United States Item description: "This listing is for one DEC PDP 11/23 Computer preloaded with Micro/RSX v3.1 operating system. The unit includes a Seagate ST-225 hard drive, and DEC dual floppy drive model RX50. The CPU is a M8189 KDF11 full size board, and also includes two 512KB full size memory boards model M8067, for a total of 1024KB memory. The unit also has an IEEE GPIB card M7954 and a 4 line ASYNC Mux board with rear panel ports, model M3106. The controller is an RQDX-3 QBUS controller, model M7555. The CRT monitor is not included. The unit is in very nice condition and has been tested and verified to be in perfect working condition and ready for use. This unit is for local pickup only."
