Search results

Do you mean like a Cipher 525? https://www.ebay.com/itm/125640041765 That one takes DC600A carts.

What were you using to program the flash on the PIC? MPLAB (the standard package) protects certain configuration words; if you zero them, you'll have a heckuva time programming the thing. Flash, has in addition to clock source, but also Device ID, etc.

As I've mentioned earlier, we used the MCBA accounting/inventory/payroll suite on an 8085 system. MCBA was acquired about a decade ago by Geneva Software: https://www.genevasoftware.com/AboutUs.aspx Serious stuff.

There have been several over the years. When I did the prototype, I used the serial port programmer (https://www.talkingelectronics.com/projects/Pic%20ProgrammerMkV%2012%20Parts/PicProgrammer-12Parts.html). However, a PICKIT2 USB unit also works and there are lots of far East clones of it...

Do you mean "why would anyone measure the current consumption of an AC circuit?" :rolleyes: I suspect that the rear section contains the current shunt and rectifier. This could also be the type of ammeter that uses a thermopile. There are also hot-wire ammeters, often used in RF measurement...

Does anyone know of any production code where the 86/87 code concurrency was used to any great advantage? I've written math packs using the 8087 (as well as emulating functionality), and all the stuff that I wrote was essentially single-threaded. I suspect this was the case for most of, if not...

I recall that the 8087 was really pushing state-of-the-art. In particular, the technique of storing 2 bits (4 values) per transistor in the microcode: https://www.righto.com/2018/09/two-bits-per-transistor-high-density.html

I did mention MicroSolutions UniDOS--there were a couple of versions of this; one that used the add-in board and another that used the host x86 CPU and software emulation. https://www.retrocmp.de/software/microsolution/unidos.htm I do have a UniDOS disk and may have even uploaded it years ago...

It looks to be quite a lot of overkill for a print spooler, what with 256KB of DRAM. Perhaps the PROM contents will give a hint.

Indeed. The -FP64 unit is particularly attractive and a 28 pin breakout board is available. Of course, if you're stuck on the idea of an 8087, this is irrelevant. I linked to the -V2 because I thought it remarkable that the job could be done with an 8 pin DIP.

Speedwise about the same; lower power dissipation, a few more instructions. All in all, I think the whole family of 8087,187,287 and 387 are bad match for Z80. If you really wanted to use an 8087, perhaps it might be best to simply include an 8088 to do the staging to the 8087 and transmit...

Oh man, the 8087 is so tied up in the 8086 architecture, using 8086 DMA as well as memory fetches by the 8086, each having its own different BIU, I'd think that there certainly must be easier ways to skin that cat. At about $150 for the 5 MHz version, it wasn't particularly cheap and ran...

Looking at the schematic, the 13V zener appears to be on the output of a regular voltage-doubler circuit. That is C120 is charged through D107 on one half-cycle of the AC input; on the other AC half-cycle, D106 charges C121 with the AC superimposed on the DC level that C120 has been charged to...

You might want to go over the traces with a magnifier--a hairline-cracked trace can drive you up the wall. The 10 ma is the amount of current that the diode is rated to pass. Usually, this means that the diode appears as nothing more than a reference for a regulator circuit. So you have...

I have a QIC (well, probably Iotamat) drive with a 6800 installed--I think that was standard for 3M on the early drives.

The convention in the CNC world is a 4-terminal block. No special standard connector. 4 terminals for full duplex, 2 for half.

Using an 8087 or 80C187 NPU with a Z80 would be a daunting task, probably involving just as much work to do the interface as putting required math functionality into a custom FPGA made for the purpose. If what you're looking for is, say, fast multiplies, TRW made some very fast multipliers back...

The buffer/spoolers were mostly intended for slow-speed printers (dot matrix/daisywheel) and for printer sharing back in the day. The buffering issue today is not even a consideration, since even low-end printers have multi-MB-sized buffers and the high-end ones have hard disks--and modern OS...

But that was my point--MOV syntax being exactly the same between MASM and DEBUG won't generate the same code in some instances. Note that there are special-cased "short" forms of MOV as well as long forms to accomplish the same thing. MASM will pick the short form, while DEBUG always uses...

There were also spoolers for CPM 80; I may have one locked away somewhere.