I am not sure if anyone is interested, but I've scanned the manual
for the Trend
HSR500 and HSR500P optical paper tape readers. If I've got the
permissions right,
then you can get it from my google drive on :
https://drive.google.com/open?id=0B5uNCTLB4VsqRU9TWDIzWnZYaU0
It's a large file, I don't think the scanner software has heard of
compression!. If anyone
can make it a more reasonable size, feel free...
This is a proper manual with schematics, parts lists, adjustment info, etc.
I've also scanned the circuit diagrams for the Trend Paper Tape Station, here
https://drive.google.com/open?id=0B5uNCTLB4VsqemRFMnVNb0l5WU0
The Paper Tape Station is a rack unit containing an HSR500 reader, power supply,
GNT34 punch and a driver card for the punch. Those diagrams are for
the punch driver
and power supply, you need the HSR500 manual as well.
Let me know if it all works...
-tony
Hi folks,
I'm at the point of troubleshooting this 8085 board where I need to test all
the RAM.
The code loops at an IN looking for....something. Based on other assembly
programs I've looked at the code is very similar to eg a disk controller
looking for a READY signal from a drive. Trouble is I have no idea what's
expected to be at I/O port 0xE3. If it was one of the peripheral chips I'd
expect a chip select line to go low. The 74LS139 that does chip select is OK
- I've tested it off-board and all traces going to it buzz out OK.
The code uses upper RAM as a scratch pad so what I'd like to do is replace
the $0000 ROM with an EPROM containing RAM test code. I've found incomplete
examples that need to be tailored so before I go reinventing the wheel has
anyone got a working example I can use? Warnings of things I should and
shouldn't do?
RAM is at $8000-$FFFF, and at least some of it is ok since the stack pointer
is up at 0xF0B3 and I can trace the code by watching which addresses it's
reading.
Cheers!
--
Adrian/Witchy
Binary Dinosaurs creator/curator
Www.binarydinosaurs.co.uk - the UK's biggest private home computer
collection?
I am working on the disassembly and commenting of the 98228A disk ROM for the 9825T, and my disassembler flagged two instructions as invalid. They are used inside a routine that copies blocks of words from various banks of the ROM into low RAM. The first, bit pattern 070113, is used immediately after a dir (disable interrupt) instruction. The second, bit pattern 070117, is used immediately before an eir (enable interrupt) instruction. The ?invalid? instructions do not match any instructions described in the 9825A patent, nor are present in the 9835 or 9845 assemblers instruction descriptions. From the surrounding code, it doesn?t appear that these instructions reference any of the user visible CPU registers, but are used in some way that enhances the effect of dir/eir and ensures the block copy is not interfered with.
Anyone have any ideas? Possibly a DMA request ignore/resume pair?
Hey all,
Is anyone out there familiar with disassembly of the Data General DG One
portable? I have one of the EL models - it looks so cool! - and the hard
drive is stuck. I want pull it out and repair it, but I've reached an
impasse. I have the machine disassembled and the HD case is accessible, but
there is no obvious way to remove it. I don't like to just force things,
for obvious reasons. Thanks to anyone with some advice. -- Ian
--
Ian S. King, MSIS, MSCS, Ph.D. Candidate
The Information School <http://ischool.uw.edu>
Dissertation: "Why the Conversation Mattered: Constructing a Sociotechnical
Narrative Through a Design Lens
Archivist, Voices From the Rwanda Tribunal <http://tribunalvoices.org>
Value Sensitive Design Research Lab <http://vsdesign.org>
University of Washington
There is an old Vulcan saying: "Only Nixon could go to China."
Friends,
tu58fs 1.1 now supports oversized TU58 tape images, with capacity up to
32MB instead of 256KB.
This was easy to made for XXDP. Under RT-11 the DD.SYS driver must be
patched and reinstalled, tu58fs now handles this
automatically.
The GITHUB release at https://github.com/j-hoppe/tu58fs/releases
contains 2 new demos:
"demo_xxdp_oversize" packs the whole XXDP25 RL02 disk content onto an
emulated tu58
"demo_rt11_oversize" boots a full RT-11 installation from TU58, and
mounts a 2nd tape full of games.
Docs at http://retrocmp.com/tools/tu58fs were updated.
And I feel pretty empty now ... hope you love it!
Joerg
I know it's a "newer" PC compatible machine, but I was wondering if
anyone had a 20MB PC110 Palmtop and could tell me (or send me pics) of
the 16MB RAM upgrade. I have a non working unit here I can liberate the
4MB module from, and I believe I can replace the RAM ICs with larger ones.
The DRAMs on the board are HM51W16160ATT7, which are 70nS FP DRAM
1Mbx16 I assume there are similar 4Mbx16 DRAMs I could solder in
(A0-A11 Row/Col)
Jim
--
Jim Brain
brain at jbrain.comwww.jbrain.com
Hi,
I recently acquired an old Sun3 with a Fujitsu Eagle disk. This disk has
SunOS 3.5 on it. Parts of the installation were missing, though. I wanted
to build a new kernel with SCSI support and extracted the sys stuff
>from a 3.5EXPORT release tape. My machine however runs plain 3.5.
I can build a new kernel, but some things won?t worked like allowing
logins when a password is set.
Is there anyone out there who could provide me with a tar of /usr/sys
>from a complete working SunOS 3.5 running on sun3?
As a second question: The SunOS boot disk is a Fujitsu Eagle that
often reports errors. I have a second Eagle that I might use as a backup,
but I would have to reformat the second disks. How can I do that with
SunOS 3.5? There is no ?format? command apparently.
thanks,
Dennis
--
Don't suffer from insanity...
Enjoy every minute of it.
> From: Paul Koning
>> When did V7 come out, BTW?
> The files on the SYSGEN tape have a timestamp of 26-Sep-79, so "Fall
> 1979" sounds right.
Ow. I was looking for something a lot earlier than that. I used RSTS-11 in
the '72-'74 timeframe, so it's a version from that era I'd like to have. Any
idea what version that would be - and if it's still extant?
> I've used the V4A kit (DECtapes) to build that ... (There's a V4A
> sysgen manual on Bitsavers too ...)
When was that one?
>> It would be really nice to have sources - are they gone forever?
> Some still exist. I know someone who has a RSTS source kit, not sure
> which version. I have pieces of source.
OK, better than nothing.
> A complication with all of this is the question of licensing. There's a
> hobbyist license for RSTS to build and run it, but whether that carries
> over to making sources available is an interesting question. I'm not
> sure who to ask these days, either.
Hmm. I guess technically HP owns it now?
Noel
> > > Apple is slightly different -- the licence for Mac OS X stipulates
> > > that you're only allowed to run it on Apple-branded hardware. This is
> > > somewhere between rare and unique, though, and it has recently been
> > > relaxed slightly to permit use of hypervisors.
> >
> > EULAs have the same value as toilet paper and should be used for the same
> > purpose.
> >
> > Legally, they can and have been enforced. So their value is not nil
> > when it comes to screwing up someone.
I was always under the impression that EULAs existed, at this point, solely to scare corporate/commercial users into license compliance in order to avoid lengthy and draining court expenses, since they've been shown to be entirely unenforceable on individuals since the 90s. That's why Adobe stopped trying to prevent piracy of Photoshop on a single-user basis long ago, as an example. License compliance is irrelevant for individual users and particularly so for long obsolete software, i.e. anything that might reasonably be emulated. Even emulating a more recent video game system such as the Wii would be impossible to prevent given that the courts have decided that it is acceptable to create backups of software that you own and the original creator cannot prevent you from using that backup on a different platform than originally intended (recent example being ripping a CD you own and listening to it on an mp3 player, or more distant example, creating mixtapes for your personal use).
Not that it would prevent you from having to deal with a court case, but in virtually every case I'm aware of over the last decade or so it's usually just been a cease and desist letter to show the company still intends to maintain copyright, but actually taking someone to court for emulation would be catastrophic for any corporation's public image and virtually guaranteed to be thrown out.
> From: Paul Koning
> I wrote a simple program to strip off those two bytes everywhere, and
> the result was a set of V7 kit tapes that work nicely.
Any chance you could provide those 'ready to run' tape images back to
BitSavers, so other people don't have to replicate what you did?
> Trying to remember how to do a V7 installation with no docs was
> interesting...
Any chance you could write up some notes covering what your rememaber/did, for
anyone else who'd like to try running RSTS-11?
(I'd upload them to the Computer History wiki, if you like - I've, alas, not
had any luck getting in touch with the Webmaster there about getting other
people accounts...)
When did V7 come out, BTW?
And in looking around BitSavers a couple of days ago for RSTS-11 stuff, I
didn't think I found much in the way of sources, just the binaries. Did
I miss any?
It would be really nice to have sources - are they gone forever?
Noel
Gents,
I'm looking at a set of RSTS V7 magtape images (a release kit) which have an odd format that gives SIMH fits.
In the container formats I'm used to, each tape block image is preceded and followed by the data length as a 4-byte value. In SIMH that's rounded up to even, in E11 format it's not, but apart from that this is how things work.
The V7 tape images don't match that format. It looks like each block contains not just the data but also 2 more bytes, and the data length value represents that extra 2 bytes. So the tape label is 16 bytes, not 14, and the data blocks are 514 bytes, not 512.
Does this ring any bells? Where do those extra bytes come from? Can SIMH be told to deal with this or does it require a repair program to fix the format?
paul
(n.b.: Sorry for the "wanted" spam from me. I think this is the last
one for a while!)
I have access to a friend's AT&T 3B2 Model 400 for exploratory and
reverse-engineering work, but I would really like to get a system
of my own.
To that end, if you have an AT&T 3B2 you'd like to part with, please
drop me a line. Happy to pay fair market prices, or consider some
trades if you prefer that (I have a lot of DEC Qbus stuff)
I'm also still looking for more documentation. I especially wish I had
schematics, and any docs related to writing drivers. Anything that
would be useful in documenting the 3B2 internals would be lovely.
Thanks!
-Seth
I am currently rack-mounting my PDP8/e and its peripherals. And of course I want
to have the peripherals power up when I turn on the CPU. I have an 861 power
controller in the rack, but you can't just link that to the power
control sockets
on the CPU, DEC changed the wiring at some point...
Let me explain.
The 3 pin power control sockets on the 861 and just about every other power
controller and all my PDP11s carry the following 3 signals : Ground, On/ (ground
to turn the unit on) and Off/ (ground to force the unit off, e.g. for
an overheat
shutdown).
The 3 pin sockets on the PDP8/e CPU are not wired quite in parallel. One pin
is ground. Another pin is On/ (as above). But the middle pins are linked via the
frontpanel switch and overheat thermostat. The normal thing to do is to put
a jumper in each socket so that one side of the switch is grounded, the other
goes to On/. If you have more overheat thermostats in peripheral boxes, they
can be linked into the chain. There is a mains output on the PDP8/e PSU that
was (according to the printset) used to operate a contactor directly to power
up the peripherals.
A moment's thought made me realise you could use a normal power controller
with the PDP8/e. The only disadvantage is that the overheat switch in the
power controller would not shut down the CPU. Since I don't run my machines
unattended that is no great loss.
What I did was to cut a normal DEC power control cable (with the 3 pin plug
one each end) in half. Call the 2 halves 'CPU' and 'Pwr'
Then wire as follows :
CPU/Green (Gnd) - Pwr/Green (Gnd)
CPU/Red (On/) --->|--- CPU/Black (Switch)
Pwr/Red (On/) --->|--- CPU/Black (Switch)
Pwr/Black (Off/) : Not connected
Now plug the ends into the power controller and one of the CPU
power control sockets (make sure you have them the right way
round). In the other CPU power control socket fit the jumper plug
that links the middle pin to ground.
The idea is that when the CPU switch turns on, both the CPU On/
line and the power controller On/ line are pulled to ground via the
diodes. The diodes prevent the voltage from one power switching
circuit ending up in the other.
The diodes can be just about anything that will carry the power
relay coil current. I used 1N4007's as I happen to have them to
hand. I built it in a spare telephone junction box with 6 pairs of
terminals. One set of terminals carries the cables. The other
set carries the diodes and a wire between the 2 ground wires.
Needless to say construction is not critical. It's very low speed,
it's about 24V (and isolated from the mains) at < 1A.
-tony
I have a very nice SWTPC 6800 for sale. Please see the ad on the VCF
forums for complete information.
If you have inquiries, please do send them directly to me via e-mail.
Thanks!
Sellam
> From: Alfred M. Szmidt
> System 46 for the MIT CADR is licensed under a 3-clause BSD license --
> start hacking. ;-) You even have an emulator for the MIT CADR.
Everyone seems to have blown right past this, but it might be important.
Does anyone know if the Lambda matches the CADR? Or did they make changes
('improvements')? I always had the impression that it was basically a CADR
clone.
A CADR emulator, running the MIT code, would certainly be OK.
Noel
Hi folks,
Clear one problem and hit another is just what I expect to happen with this
Executel :)
After last weekend's little breakthrough my little machine is now hitting a
loop that LOOKS like it's waiting for an RST6.5 interrupt*, but at the same
time the A9 line is doing this:
http://www.binarydinosaurs.co.uk/STCExecutelOddTraceA9.jpg
(scale doubled for ease of viewing)
That doesn't look normal to me, but all 8 chips that touch A9 check out OK
and there's nothing odd resistance wise.
Before I start chasing my tail again I thought I'd ask first...
(*for anyone interested RST6.5 is triggered by the TS1/TS2 status lines from
the MR9735 teletext decoder and should be constantly active while video is
being output. At one point Tony suggested this chip needs to be initialised
and there is indeed a control word that can be passed to it to turn it on
and off which makes me wonder if there's another memory bit stuck somewhere)
Cheers!
--
Adrian/Witchy
Binary Dinosaurs creator/curator
Www.binarydinosaurs.co.uk - the UK's biggest private home computer
collection?
Hello,
amongst other panels and things (CDC 6600 dead start panel, PDP-15
frontpanel) I got this one:
http://up.picr.de/28257957bg.jpg
I *guess* it also comes from the CDC 6600 but I'm not sure. Can anyone
identify it?
Christian
I have at least one 11/44 for sale, at least one 11/24 for sale. I can
configure them as needed within reason. They can be packed and shipped as
freight carrier of your choice or pickup in IL. or IN. Please contact me
off list.
Also the following parts:
M7090
M7094
M7095
M7096
M7097
M7098
$300/SET (several available)
70-15672 backplane $70
M7093 FP11-A make offer
M7819 DZ11 board only $50
Any quantity boards ship for $10 within US.
Thanks, Paul
Next milestone reached:
tu58fs 1.0 now supports the RT-11 file system, additional to DOS11/XXDP
(phew!)
And its easier to use: I also precompiled binaries f?r Linux x64, Win32
Cygwin, ARM Beaglebone Black and RPi.
Also some batch files show typical usage, XXDP/RT-11 tape and disk
images are included.
Docs on http://retrocmp.com/tools/tu58fs
Precompiled releases at https://github.com/j-hoppe/tu58fs/releases
The RT-11 filesystem has the special features of "extended directory
entries" and "file prefixes". These are fully supported by tu58fs, but I
never heard of real-life usage. Anybody can talk about it, or has RT-11
images with dir extension and/or file prefixes?
best,
Joerg
> From: Mark Matlock
> I also tried an 11/40 but the SET CPU NOEIS in Simh gave me an error
In Ersatz-11, an -11/40 without EIS works properly (i.e. it doesn't :-):
that's how I recognized his booting error! ;-)
> From: John Forecast
> Depending on the state of your EIS board you may want to stay with the
> original un-mapped system - I suspect that the baseline mapped system
> will always try to use the "sob" instruction.
No matter; SOB is part of the baseline instruction set in the -11/40. The EIS
board adds only MUL, DIV, ASH and ASHC.
Noel
I used Lyle's updated version to show Spacewar on my PDP-8/a during this
weekends retro event "RetroGathering" in Sweden. It works great!
I did two modifications to the code:
1. Use digital IO instead of the switch register so I could use hand
controls to let the audience play the game.
2. Fixed a bug so that timer interrupts is turned on if the DK8-EP
programmable real time clock is used.
/Anders
>
>I just updated D.E. Wrege's Spacewar as follows:
>
>1. Correctly supports slow monitors attached to a VC8/E interface by
>correcting mistakes made in the VC8/E driver code. The code now follows
>DEC's recommended method of waiting on the VC8/E.
>
>2. Starts up with spaceships (as opposed to UFO's) per the original
>Spacewar! by Steve Russell.
>
>3. Now supports the DK8-EC Crystal Clock
>
>Items 1 & 2 were released by me previously - but support for the
>DK8-EC is brand new.
>
>The new source and listing can be picked up via anonymous FTP to
>bickleywest.com and the pdp8_spcwar directory.
>
>> Bill, Paul,
>> I have been tinkering with old versions of RSX11M (back to V2) on
>> non-mapped CPUs, primarily PDP-11/05 as I hope to get mine running soon. On
>> Simh
>> with the CPU set as a PDP-11/05 which does not have EIS (I also tried an
>> 11/40 but the SET CPU NOEIS in Simh gave me an error so I couldn't be sure
>> if it was disabled) I was able to boot the baseline distribution for RSX11M
>> V4.0 on a RL02 distribution. See details below on the config I tested.
>> RSX11M is a pretty capable multitasking, multiuser system and would be good
>> fit for the PDP-11/40.
>
> RL02 or RL01? I have only RL02 drives (2). Are you saying you can
Bill,
My first PDP-11 system was a PDP-11/24 (256KB) with 2 RL02s. It ran
RSX11M V4.0 and collected RS232 data from lab instruments and
provided a programming environment and handled 3 or 4 users ok. Later
we added a KT24 and went to 512KB. With 2 RL02s one was a system disk
and one was a user/data disk. The utility BRU allowed you to make a copy
of the system disk, but to backup the data disk, one has to boot BRUSYS.SYS
which is a memory resident only RSX11S system that RSX11M includes so
you can remove the system disk and make a disk to disk copy of the non-bootable
user disk. Actually, BRUSYS.SYS is small and you can have the user disk boot block
point to it for convenience.
> 1) Use simH to set up the environment
RSX11M especially in small memory systems should be customized to your hardware.
If you have extra DL or DZ terminal ports or other hardware you will need to do this.
You can use the RL02 disk emulation, but have 4 of them for convenience so you don't
to swap disk images during the process. Once you have SYSGENed an RSX11M system
you are happy with then the RL02 disk image file needs to be transferred to an RL02
pack.
> 2) Port to RL02 image disk
This is the tricky part. RSX11M+ can run a TCP/IP stack and the disk image could
be FTPed to it from the Linux or Windows system running Simh. M+ could mount the
disk image file and BRU the image to a physical disk (if the M+ system had an RL02
Drive). I don't have RL02s and don't know anyone who does. Also, you might find
a Baseline RSX11M disk someone has which can be copied and booted.
> 3) Take image put on actual RL02?
Since we are unlikely to find a SYSTEM to do that then, the other way
would be with PDPGUI from Jorge Hoppe. His PDPGUI program can load via ODT
a small driver to write to an RL02 and then transfer a disk image over the console
port. It would take quite a while but it can be done.
http://retrocmp.com/pdp-11/pdp11gui/disk-images-readwrite
This assumes you have ODT and I don't know if an 11/40 does. The !1/05
doesn't either but Jorge found that a M9312 bootstrap card with ODT ROMs
will enable ODT on an 11/05 so it should work on an 11/40?
http://retrocmp.com/how-tos/interfacing-to-a-pdp-1105/194-interfacing-with-…
> I agree that it would run on the PDP 11/40 without EIS, but so far I have
> not been able to get it onto an image that will write to actual RL02
> disks. I was playing around with this yesterday.
>
> I was also working on getting Fortran onto a RT11 disk and in general
> building a dual drive system that has a programming environment with enough
> space to save program and a dataset.
RT11 would work very well on two RL02s as well. In fact, one can get by with two
RX02s. It is a much simpler operating system.
> I have a lot of RSX11/M manuals and docs here, compared with RT11 I'd love
> to use RSX. Are tools made for RSX compatible with RT-11, I am reading up
> to see how these compare, what levels they're on...is RT11 like DOS and RSX
> like "Windows" that sits on top of it, etc. I know RSX is not a GUI, just
> making an analogy. I am researching all of this, up to this point I had
> only dabbled in RT11.
RT-11 and RSX11M are quite different internally. RT-11 is a single user monitor
that was extended to multiuser with some later version and via the TSX operating system.
TSX is more like your Windows analogy.
The RSX11M executive was written from the ground up with conditional assembly code that can be
customized for your hardware so any code for hardware not needed can be left out.
When you do a SYSGEN you actually compile the assembly source for much of the
operating system and then link (TasK Build, TKB) it. Utilities come in object libraries and can be modified
a bit when linking.
Also, many of the features of the OS can be left out if you don't need them. It was designed
to have executive calls that were compatible with RSX11M and IAS which ran only on large
systems. Much of the same languages can be run on RSX and RT11 (Fortran, Basic, Macro, APL)
and RSX can read RT-11 tapes and disks with the utility FLX.
Good Luck,
Mark
>
> Thanks
>
> Bill
Hello folks,
I have a PDP-8/e where I've tested all the boards in a friend's PDP-8/e and they are all generally ok with the exception of the M8310 which did not work in his machine.
I started to do some very rudimentary analysis of the what isn't working. I did the following.
7100 CLA clear AC
7040 CMA (complement the AC)
7040 CMA
7040 CMA
7040 CMA
The complementing worked fine. I set the switch to AC and single stepped through the little program and watched the all 12 lights alternate on and then off. So far so good.
I then did this:
7100 CLA
7001 IAC (increment AC)
7001 IAC
7001 IAC
7001 IAC
And nothing happened, no incrementing of AC took place. So I may be onto something here. I then looked at the link bit which I believe is viewed by setting the switch to STATUS and looking at bit 0 "LINK"
I did the following program:
7100 CLA (Clear Link)
7020 CML (complement Link)
7020 CML
7020 CML
And I found that the link was not alternating. The lamp was lit at all time unlike the same test with the CMA. I then read in the Maintenance Manual Volume 1 on page 4-7, Item 11 which gives the following symptom "CPMA, MB, PC, or AC do not increment" And the likely cause of "CAR IN L is always high to the adder. It should be generated for ..." and presents a series of events that should cause the CAR IN L to assert.
Now two questions.
1) It appears that CPMA, MB and PC all do increment but the AC does not. Does this help me to narrow down which of the events a. through f. listed might be my problem?
2) Is the link bits inability to complement help narrow down the issue?
3) Might anyone know what the fault is?
4) Are there any other steps you might suggest I take to further narrow down the fault?
Thanks
Eugene
>> On Feb 2, 2017, at 11:19 PM, william degnan <billdegnan at gmail.com> wrote:
>> ...
>> I am curious to see what OS's run on an 11/40 without the EIS card other
>> than RT-11. I am researching this. I have always wanted to learn more
>> about batch-11.
>
> You mean DOS/BATCH? Yes, that would run on that machine, it's an 11/20 OS. So would the pre-Batch version of DOS-11 (V4).
>
> Another OS that would run on your machine (as well as an 11/20) would be RSTS-11 (V4, or I suppose V3 if you can find that), the predecessor of RSTS/E that didn't use the MMU.
>
> It may be that some flavors of RSX-11/M or /S can be built with no EIS, since it's supposed to be possible to build a non-MMU version at least of /S. But I don't know the specifics (no RSX experience).
>
> paul
Bill, Paul,
I have been tinkering with old versions of RSX11M (back to V2) on non-mapped CPUs, primarily PDP-11/05 as I hope to get mine running soon. On Simh
with the CPU set as a PDP-11/05 which does not have EIS (I also tried an 11/40 but the SET CPU NOEIS in Simh gave me an error so I couldn't be sure if it was disabled) I was able to boot the baseline distribution for RSX11M V4.0 on a RL02 distribution. See details below on the config I tested. RSX11M is a pretty capable multitasking, multiuser system and would be good fit for the PDP-11/40.
Best,
Mark
sim> sho cpu
CPU 11/05, idle enabled, autoconfiguration enabled
64KB
sim> sh rl
RL RL11, address=17774400-17774411, vector=160, 4 units
RL0 2621KW, attached to rsxm32.rl01, on line
write enabled, RL01
RL1 2621KW, attached to excprv.rl01, on line
write enabled, RL01
RL2 2621KW, attached to mcrsrc.rl01, on line
write enabled, RL01
RL3 2621KW, attached to rlutil.rl01, on line
write enabled, RL01
sim> b rl
RSX-11M V4.0 BL32 28.K (BASELINE)
>RED DL:=SY:
>RED DL:=LB:
>MOU DL:RSXM32
>@DL:[1,2]STARTUP
>* PLEASE ENTER TIME AND DATE (HR:MN DD-MMM-YY) [S]: 17:52 04-FEB-80
>TIM 17:52 04-FEB-80
>* ENTER LINE WIDTH OF THIS TERMINAL [D D:132.]: 80.
>SET /BUF=TI:80.
>@ <EOF>
>dev
DL0: Mounted Loaded Type=RL01
DL1: Loaded Type=RL01
TT0:
NL0:
TI0:
CO0: TT0:
CL0: TT0:
LB0: DL0:
SY0: DL0:
>ins $pip
>pip /li
Directory DL0:[200,200]
4-FEB-80 17:52
BLDLAINIT.CMD;1 14. 22-JAN-82 10:19
SGNBLDDRV.CMD;1 19. 22-JAN-82 10:19
SGNKLAB.CMD;1 70. 22-JAN-82 10:19
SGNSTAND.CMD;1 4. 22-JAN-82 10:19
SYSGEN.CMD;1 85. 22-JAN-82 10:19
SYSGEN2.CMD;1 79. 22-JAN-82 10:19
SYSGEN3.CMD;1 52. 22-JAN-82 10:19
Total of 323./323. blocks in 7. files
All ?
??????????????? I?m trying to test a Cromemco 16FDC controller?long story but it?s part of a QDOS project. I?m looking for recommendations on a 5.25? disk image I could use for testing. The system is simple ? 16FDC, CompuPro RAM17 (with $C0 block disabled), and a Z80 card. The 16FDC RDOS ROM works, so I can issue commands but I need to test the disk interface part.
??????????????? Any recommendations would be appreciated. Thanks!
Rich
--
Rich Cini
http://www.classiccmp.org/cinihttp://www.classiccmp.org/altair32
where do you get a thing like that to convert IBM keyboard for the
Amiga's use?
we have a Amiga with toaster we need a keyboard for, Prefer the real
Amiga one but....
In a message dated 2/4/2017 7:21:14 P.M. US Mountain Standard Time,
ian.finder at gmail.com writes:
I ordered a PS/2 -> amiga adapter for the fine folks at the MADE in
oakland:
https://www.yelp.com/biz/the-museum-of-art-and-digital-entertainment-oakland
But I fear it may not arrive in time for their 2/27 show.
Is there anyone local who could loan these good folks an Amiga 2K or 3K
keyboard?
I'm remote and cannot do so.
--
Ian Finder
(206) 395-MIPS
ian.finder at gmail.com
I ordered a PS/2 -> amiga adapter for the fine folks at the MADE in oakland:
https://www.yelp.com/biz/the-museum-of-art-and-digital-entertainment-oakland
But I fear it may not arrive in time for their 2/27 show.
Is there anyone local who could loan these good folks an Amiga 2K or 3K
keyboard?
I'm remote and cannot do so.
--
Ian Finder
(206) 395-MIPS
ian.finder at gmail.com
> From: Jon Elson
> Any time you see really narrow glitches, especially when they are one
> LA sample wide, you have no idea what they actually look like. The LA
> detects that the pulse was there at the instant it sampled it, but you
> don't know whether it was 5 ns wide, or 70 ns wide ... You also don't
> know whether they were full-amplitude pulses or runts that just barely
> crossed the logic threshold of the analyzer.
Which is why I always prefer to work with an LA _and_ a 'scope: the 'scope
lets me see what the signals look like, how much noise/etc there is, etc,
etc, while the LA can do other things - better triggering, capture longer
time periods, etc.
(Now they have those fancy new digitial 'scope with capture capability, and
you can get the best of both worlds with one box, but I guess they are still
kind of pricy.)
But you can probably pick up an old 'scope for not much money on eBait. I
can't imagine working on anything without one.
Noel
Evening folks,
I have two so-called Logic Analysers, both cheap Chinese clones of other
more expensive units that hook up to the host via USB2 and stream readings
direct to software, in one case the open source Sigrok and in the other
genuine Saleae Logic.
I'm getting different and inconsistent readings out of both of them whilst
sampling at 25MHz which should be more than enough for this 6MHz Executel
I'm working on. Both of them are good for spotting dead or stuck outputs but
I still can't get a good set of readings from eg all points on a single
address line. Tonight I replaced all four ROM sockets and ROM chips, tested
each individual line for resistance (0.5 ohms on all apart from an
occasional 0.4 and 0.6) but still get ghost readings.
Is it me or the cheap clones?
Whilst looking for better quality units I came across a couple of 'proper'
HP/Agilent analysers, a 1663A 34 channel and 1661A 102 channel which seem
complete apart from the chip leg grabbers. Am I right to assume some of you
might have experience of these beasts?
Forums seem to mostly think the streaming USB units aren't worth anything
for more than a few channels but I'm still a relative beginner to all of
this. I really need to watch all 16 lines of an address bus and externally
clock it as Tony has suggested.
Any insights appreciated!
--
Adrian/Witchy
Binary Dinosaurs creator/curator
Www.binarydinosaurs.co.uk - the UK's biggest private home computer
collection?
We have one last 60-minute spot to fill for the Friday (March 31) tech
classes at VCF East. Any topic is fair game if it has wide appeal and
makes people into better vintage computing hobbyists. The topics thus
far are here: http://vcfed.org/wp/classes/. Email me ** off-list ** if
you'd like to volunteer. (Please avoid "someone should teach XYZ"
messages -- we know what * should * be taught, we need people to DO it. :)
________________________________
Evan Koblentz, director
Vintage Computer Federation
a 501(c)3 educational non-profit
evan at vcfed.org
(646) 546-9999
www.vcfed.orgfacebook.com/vcfederationtwitter.com/vcfederation
> From: Paul Koning
> Another OS that would run on your machine (as well as an 11/20) would
> be RSTS-11 (V4, or I suppose V3 if you can find that)
I'd love to have an old RSTS-11, is there any variant around?
> didn't use the MMU
Huh? He's got an MMU (I think): it's the EIS he's currently struggling with.
Noel
Can someone please fix the mailing list software? This has been
reported every once in a while by a bunch of people for over ten
years.
These are a just the last bounces I got:
20-Jan cctalk-request at classiccmp [78] confirm fd5d1f938a6c920c61c094802694d0194e87f1a4
25-Jan cctalk-request at classiccmp [78] confirm e01809296377d0fd3033b4ab27394ca7dc0fae71
31-Jan cctalk-request at classiccmp [78] confirm 38290c8a992491eda604beff5a06ff20cd7e85f5
> From: William Degnan
> I was able to get the extended three cables
Excellent!
> I can put the M7238 EIS card on a riser so I can probe for faults
I'm all agog to hear what you find out!
> and maybe if I am lucky boot XXDP+. With the EIN installed I can't boot
I thought the machine basically just totally froze if you tried inserting the
KE11-E, and removing the jumper to enable it? Oh well, that severe a fault
should be fairly easy (sic) to track down.
> From: Paul Koning
> DEC's PDP11 architecture handbook doesn't appear to confirm that.
> Either that or the model differences table is sloppy.
The next page (B-4) says "The KE11-E .. provides MUL <etc>" and has an
"x" under "35/40".
Noel
> From: Allison
> for laughs I wandered over to:
> http://ftp.math.utah.edu/pub/mirrors/minnie.tuhs.org/PDP-11/Boot_Images/
> To see if the copy of V6 on RL02 is still there.... yep it is. and it
> runs on a 11/23 just fine
Yes, that's another copy of the Shoppa disk.
So, I looked at that system, to see how it dealt with the clock issue on an
11/23 (in /sys/ken/main.c, if anyone else is interested). While looking, I
noticed something that made it extremely unlikely that it would boot on an
11/40. Sure enough, attempting to boot the /unix on it on a (simulated) -11/40
blows out.
There are a couple of other unix loads on that pack image (oldunix, unix.tmp,
etc), but all the ones I looked at had the same issue (only tried booting the
'unix' one, though); they're probably all for the same machine, so have the
same configuration issue.
V6 Unix was pretty persnickety about the hardware configuration it ran on;
while it was possible to create builds that would run on almost any
configuration, on 'vanilla' V6 that really only applies to the /40/45/70
era. And even then you still had to re-build the system to match your actual
hardware configuration, almost all the time.
The advent of the /23 (with no CSW, and no KW11-L/P), made things more
complicated. (The clock is pretty key - Unix needs one - several things,
e.g. parts of the teletype drivers, require real-time delays provided by the
clock. I've never tried to run Unix without a working clock, I'm not sure if
it would run without slowly grinding to a halt as stuff waited for clocks
delays that never happened.(
With a little work, a suite of 'universal boot' versions (one for each type of
disk controller - RK05/RL02/RX02 etc) could have been created that would boot
and run on any pretty much CPU/etc configuration - at least, well enough to
build one that did exactly match the hardware configuration at hand. (The one
on the Shoppa disk is close, from what I could see.)
I don't think anyone ever bothered, though (in part because it was much more
of a PITA to test them all, BITD, with only real hardware).
Noel
> From: William Degnan
> my focus has been on just getting an 11/40 hardware working
Rightly and properly so...
> I suppose I should be happy with RT-11 given my circumstances.
Unix really is a significant improvement, we really need to make sure you can
run it. Don't worry about the OS image issue, I can crank them out like
sausages, and we already have all the bits we need (V6 RL driver, bootstrap,
etc).
> It's not possible with the 3 over the back cables to put the 7238 on a
> riser card to probe signals as easily.
Really? DEC specified BC08R-01 cables, which _should_ be long enough to allow
it to be put on an extender. Does your machine have the -01's, or have they
been replaced with little shorty ones?
If the latter, if you can't find any -01's, it should be possible to locate
some generic 40-pin cables, which should work (old IDE cables should work,
but not the new ones, which have a key that will prevent the connectors from
going in, in this application).
Also, it should not to be too hard to whip up some: the connectors and the
flat cable are pretty easy to find - although not the ground-plane backed
kind - do anyone know of a source for that? Anyway, the regular kind of flat
cable ought to work well enough for debugging.
Noel
Hi,
I am looking to swap or buy the following HP-Integral IPC (portable HP-UX box) interface boards:
- HP-IL interface
- 1 MB memory board
Does anybody have a manual for the HP-IL interface board?
Could offer HP 9000 interface or memory boards.
Martin
Hi,
Can someone identify this circuit board? It's some sort of magnetic core
memory. I've had this for ages and I've always wondered what it is and
where it comes from.
http://lookpic.com/O/i2/366/iAFq4mLF.jpeg
Best regards
> From: Allison
> for laughs I wandered over to:
> To see if the copy of V6 on RL02 is still there.... yep it is.
There are actually plenty of builds out there that run on RL11s, e.g.:
http://www.tuhs.org/Archive/PDP-11/Distributions/other/Tim_Shoppa_v6/
includes "A V6 RL02 bootable on a 11/23. Kernel is built for a 11/23, 2
RL02's, and 2 RX02's"; and my V6, running under Ersatz-11, is also an
RL-based system.
The real issue with mixing and matching kernels and disks is that since the
RL was not a standard device (as far as 'mkconf' went), the RL's can have
different major device numbers on different systems.
This does not stop the system from _booting_, since internally there will be
consistency, but consistency between the OS and file system is another
matter: e.g. trying to mount another drive (or any other use of /dev/rl? or
/dev/rrl?) may not work, since the device inodes for /dev/rl? might have the
wrong major device numbers in them.
> and it runs on a 11/23 just fine
Must be a slightly modified V6 - totally stock V6 will panic when it can't
find a clock (unless there's a BDV11), or NXM when it tries to touch the
switch register.
And for machines with no BDV11, I had to turn the clock off while booting;
the first time I tried to boot on a simulated 11/23, my totaly stock vanilla
V6 apparently took a timer interrupt during the boot process and went wayyyy
South, totally smashing the file system in the process. Not sure how the one
above dealt with this...
Noel
> From: Phil Blundell
> I suspect it would probably not be all that hard to write some
> sort of preprocessor to convert such code
Really? Check out:
http://minnie.tuhs.org/cgi-bin/utree.pl?file=V6/usr/sys/ken/pipe.c
(Needless to say, none of the 'int *' things are actually pointers to
integers!)
In particular, what will lines like this:
sleep(ip+2, PPIPE);
do, depending on what 'ip' is declared as?
Noel
> Jim Stephens
> The listings I've read of early unix have ... mixed c + assembly
Not V6 (the subject of the current discussion); the C compiler of that era
couldn't inline assembler.
_ALL_ of the assembler in V6 is in one of _two_ files:
l.s - per system, hardware configuration dependent
m40.s - Startup, and machine language support for all low-level OS
or functions such as stack switching, etc; the latter option
m45.s supported both the -11/45 and -11/70
Noel
> From: William Degnan
> was there ever UNIX made for the PDP 11/40 and RL02, or was it only run
> on RK05? Wouldn't all of the C and wake calls, etc issues have been
> solved then?
You're mixing up two _TOTALLY_ different things.
Unix V6 will happily run on _ANY_ block device, all you need to do is write a
driver for it. The rest of Unix V6 doesn't know ^%$^%$ about the device, all
it know is that there's this thing that can store, and read back, blocks 0-N.
The _only_ interface between the rest of Unix, and the driver, is through a
file called c.c which just contains entries for functions to read and write
blocks, etc.
(You can even run Unix - painfully - on a DECTape drive.)
Adding support for RL drives to Unix V6 involves i) writing an RL driver, and
ii) editing that file c.c to add _one line in a table_ to hook the driver
into the rest of the OS. (And there's a edit to something called l.s which
holds interrupt vectors, to all the RL vector.) THAT'S IT.
Editing c.c and l.s was No Big Deal. To customize Unix to one's particular
hardware configuration, you _had_ to change those two files, and every V6
site in the known universe tweaked those files. _WITHOUT EXCEPTION_.
Unix V6 doesn't give a *&^*&^* what disk drives its using. As long as there's
a driver for the controller.
The stuff about wake() calls is a totally different subject, it's all about
how the code in V6 Unix cuts a lot of 'C' corners (e.g. using an 'int *' as a
pointer to a struct - something that would horrify modern compilers) because
it's in very early C.
Noel
> From: Paul Koning
> Yes, GCC should do that correctly. ... Dealing with the output might be
> a nuisance ... You may need some post-processing to cast the output
> into the syntax that V6 "as" expects.
Actually, dealing with the _input_ is going to be a PITA (so my suggestion
was, in retrospect, not really a plausible one). The problem is that V6 is
written in an early dialect of C, one which I am sure would cause GCC would
toss its cookies, if fed to it.
Some things, like "a =+ b;" would be easy to fix; likewise "int a 1;" instead
of "int a = 1;". But the Unix kernel is shot through with places where are
int is used as a structure pointer, etc, without benefit of a cast (casts
weren't invented until later). And a lot of stuff like that.
Noel
> From: William Degnan
> if possible can you help me to link in m40.o instead of m45.o?
Sure; tomorrow, though, not tonight.
Just to check, you have 128KB of memory, and 2 RL02 drives, right? That will
make it all really easy, if so.
Like I said, I'll make you a mini-disk that will be quick to load with GUI11,
with only the only files on it the few you need to be able to boot: the Unix
system, /etc/init, /bin/sh, etc. Once it has booted, you can 'mount' your
existing RL pack, and copy the Unix system over to that one, then you should
be able to boot off that one.
Noel
PS: I was thinking of fixing 'mkconf' (it currently doesn't properly handle
the /dev/tty device, etc), but whoever wrote it was really lazy! 'nswap' and
'swplo' aren't even parameterized, let alone being things you can override
with inputs. So the dude who did the RL disk just changed the numbers for the
RL - so his mkconf now doesn't work properly for RK drives! Might as well just
edit c.c and l.s directly - that's what I always did! ;-)
Anyway, I might fix it at some point, but... not for tomorrow.