I?ve received a Logical Machine Corporation (Lomac) DAVID system, which appears to be successor to the Lomac ADAM.
The system consists of the main box with an 8? floppy drive (labeled ?DAVID PROCESSOR?), a keyboard/monitor box (labeled ?DAVID DISPLAY?), and a printer.
I am looking for both documentation and software for this system. The first thing I need to sort out is how to connect the display and processor. The display has a single cable with a male DB-25 connector; the processor has a connector labeled ?DISPLAY?, but it?s a female DC-37 connector. If anyone ever had or worked with one of these, perhaps they remember if there was some kind of adapter in between.
Camiel
Hi everybody
I'm the proud owner of a PDP11/05 system with a couple of 8" floppy
drives. I believe they are likely to be RX01s.
Does anybody on the list have some boot media that they could provide. I
understand that the controller can't format the disks so I'm in a
frustrating state where I don't know where to start.
Doug Jackson
Canberra Australia.
You may want to have a peek at the sync separator I built for my 9000-340. The schematics are available over
at VintHp
I am also in the process of building a PS/2 and USB to HIL adapter: http://www.dalton.ax/hpkbd/hil/
As for disks. This is one option: http://www.dalton.ax/hpdisk/ Ansgar's HPDrive is another:
https://www.hp9845.net/9845/projects/hpdrive/
--
Med v?nlig h?lsning
Anders Gustafsson, ingenj?r
anders.gustafsson at pedago.fi | Support +358 18 12060 | Direkt +358 9 315 45 121 | Mobil +358 40506 7099
Pedago interaktiv ab, Nygatan 6 (kontor), Nygatan 7 B (kurslokal), AX-22100 MARIEHAMN, ?LAND, FINLAND
>>> <cctalk-request at classiccmp.org> 2020-05-26 20:00 >>>
Should I look at buying a monitor that can support the composite video sync and get an HIL keyboard (or build
an adapter)? Does the machine not support using a terminal over the serial port as a console at boot?
Hello!
I have an HP 9817 and its accompanying 9133D disk drive unit.
The disk drive seems like a rather large can of worms, so I've been ignoring it. I re-capped the 9817's power supply. It powers up and it passes all of its diagnostics according to the LEDs on the motherboard. I can see that it is outputting a picture on the composite video connector, but I don't have any displays that will accept the weird sync frequency that it uses. I also do not have an HIL keyboard to use with the machine.
I traced out the RS-232 TX and RX on the 50-pin serial connector on the back, and verified that it matched up with the hand-drawn schematics on the HP Museum website. Using that information, I build a serial cable. Unfortunately the machine does not appear to use this serial port as a "console" at power-up. I tried messing around with the DIPS switches according to the manual but none of the settings I tried resulted in the machine using the serial port at boot.
I noticed that one of the DIP switches will enable/disable a "remote keyboard" feature. Enabling it causes the machine to fail the power-on test with a "device not found" error code. I didn't write down the exact error code.
Should I look at buying a monitor that can support the composite video sync and get an HIL keyboard (or build an adapter)? Does the machine not support using a terminal over the serial port as a console at boot?
Thanks
The gcc VAX backend is in danger of being dropped if it doesn't get
converted from the older cc0 to the newer MODE_CC implementation.
John Paul Adrian Glaubitz <glaubitz at physik.fu-berlin.de> has started a
bountysource entry
https://www.bountysource.com/issues/91495157-vax-convert-the-backend-to-mod…
and asked for people to post it anywhere it might be found
interesting, in case anyone would like to add to the bounty, or
collect it :)
(I find it quite amusing to it mixed in between entries like "Optimize
NumPy SIMD algorithms for Power VSX")
You could easily argue that modern gcc is too big to be practical to
run on a VAX anyway, but making practical a requirement for
classiccmp.org would rule out _so_ much fun stuff :)
Thanks
David
Came in through vintagecomputer.net that I am passing along.
Anyone out there near Fairfield, IA and looking for three Apple Stylewriter
printers let me know and I will put you in contact with the woman who has
them. I was told that there was a few other things, but no computers.
They're pick up only. The woman asked that she be told
1) phone number
2) your location
Please contact me ONLY through https://www.vintagecomputer.net/contact.cfm
because this is the most reliable means of contacting me. I find Gmail
sends a lot of group posts and replies straight to the spam folder.
I do not know the donor nor do I know about the hardware. I don't know
the deadline for retrieving them. I do not know nuthin.
I will bundle together the persons who inquire and forward to her to decide
whom to contact.
Bill
On Sat, 23 May 2020, Boris Gimbarzevsky wrote:
> Thanks for that really detailed review of microprocessor history! A post to
> save.
But, read carefully the corrections that others made!
Such as Noel pointing out that I was mistaken in assuming that there was a
direct progression in 4004 -> 8008 -> 8080,
and Liam's discussion of the Commodore BASIC.
I never had a Commodore 64. But, I had an MSD drive for a C64 connected
to an IEEE-488 board in a PC.
> After your detailed discussion of the bizarre variety of early Intel
> microprocessors I now recall why I refused to have anything to do with PC's
> in late 1980's.
Well, there were advantages and disadvantages.
The Motorola approach produced a better product.
BUT, it meant that software was delayed for new products. It took a while
before the good third party software showed up for the Mac.
OTOH, the Intel processors were a series of little steps, so it was
usually almost trivial to upgrade code to a new series of processors. It
took Micropro less than a week to port their 8080 CP/M Wordstar to the
8088 PC. It then took them much longer than that to prepare new manuals.
Some internal structures had patches on top of patches. Such as
Segment:Offset memory addressing, and figuring out that the PC FDC could
not do a DMA that straddled a physical (not Segment:Offset) 64K boundary,
although Int13h didn't realize it and have a suitable error message - some
later versions of DOS had occasional mysterious problems with FORMAT that
were easily solved by adding or removing TSRs to move the location of its
TPA.
> I've never liked M$ software as it seems whenever they produce a good
> product, they dump it and come up with something far worse and stop
> supporting the old one.
"Oh, but it is DANGEROUS to use a product past its [arbitrary, marketing
chosen] SELL-BY date."
>> All of my knowledge of the following is third hand, and probably mostly
>> WRONG. If you are lucky, maybe some of the folk here who actually KNOW
>> this stuff will step in and give the right information.
>> Sequence is only approximate.
And, the REAL history is much more interesting AND WEIRDER than the
fictional variants.
--
Grumpy Ol' Fred cisin at xenosoft.com