On 26/07/2010 19:22, J.G.Harston wrote:
> Rick Murray wrote:
>>> ".bbc" - Russell format
>>> ".bas" - Text
>>> "." - Acorn format
>> No, very *BAD* to use *.bas - double click on those, I'll have the fun
>> of watching Visual Basic trying to load a tokenised BASIC code. :-)
"Well, don't do that, then," said the helpdesk techie.
> .bas is the standard extension for textual representation of BASIC (*any*
> BASIC) code. If some application decide to stupidly associate themselves
> with it and try to execute it, that's their stupid fault.
I'm with Jonathan. .bas is the accepted extension for all sorts of
BASIC files, and using something else is only going to cause confusion
elsewhere. Double-clicking is supposed to "run" a file or cause it to
be executed; if the only BASIC interpreter you have is the VB executable
and it tries to load the file you double-clicked, well that's because
the doubler-clicker was daft enough to do an inappropriate thing :-)
The appropriate thing, if you want to edit a file, would be to
right-click and select "open with" -- assuming we're talking about a
Windows OS. Or use whatever weird combination of key and mouse performs
"open" rather than "run".
--
Pete Peter Turnbull
Network Manager
University of York
This message has been forwarded from Usenet. To reply to the
original author, use the email address from the forwarded message.
Date: Mon, 26 Jul 2010 21:12:41 +0200
Groups: alt.sys.pdp11
From: "Walter F. J. Mueller" <w.f.j.mueller at gsi.de>
Org: Technische Universitaet Darmstadt
Subject: VHDL implemenentation of a PDP-11/70 available on OpenCores
Id: <i2kmn9$vhj$1 at lnx107.hrz.tu-darmstadt.de>
========
A VHDL implementation of a PDP-11/70 with MMU but without FPP,
and a basic set of UNIBUS peripherals is available under GPL
on OpenCores, see
http://opencores.org/project,w11
The core is FPGA proven, boots UNIX 5th edition and 2.11BSD Unix.
The I/O sub-system is emulated via a backend server which currently
communicates via a serial port with the FPGA board.
Walter
Hi
There is a DEC manual the size of VMS manual ring binder for sale on
Ebay. I would really like to have it! The seller wont ship
internationally, but I'm in Sweden.
Would anyone like to be my proxy? I'll bid and pay the seller but I need
someone to receive it in United States and ship it to me. Obviously I'll
pay for shipping to Sweden and a bit extra for the trouble.
Please contact me offlist.
Kind Regards,
Pontus.
For the cost of shipping:
S-100 "Micro Systems" magazines
Issues 1/1 (Jan 80) through 3/4 (Jul 82).
Issue 1/3 is missing.
I am in southern California 92656
I think (bigger than 50% chance) that I recognize the seller and the origin of the machines, and I think it's very likely that some of the machines have some specialized communications hardware that was for some period very hard to get at and may even still be worth considerable $ to those in need of it, if the cab kit and remote mux distribution panel is present. But to anyone outside that industry it's very unlikely the board itself would be considered wanted at all, and I think it's 99% likely that the seller is not including the remote mux distribution panel, it often gets trashed in the "decommisioning".
It's a little sad to see machines "parted out" in a way that separates the Unibus backplane board from the part of the peripheral that's actually needed in industry, but this "parting out" phenomenon is so widespread on E-bay and those who do it tell me that it's the only way to make money. So PDP-11's get chopped off the actually interesting and valuable system they control, and as a result neither end is desirable by itself.
Yeah, and in the description he says:
Any offers below $450 for single systems will be rejected.
Nice.
On Sun, Jul 25, 2010 at 9:38 AM, Zane H. Healy <healyzh at aracnet.com> wrote:
> If I read that right, that's $550 per system.
>
> Zane
>
>
>
> At 11:23 AM -0400 7/25/10, Patrick Finnegan wrote:
>>
>> Someone should try to snap these up:
>>
>> http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=140431577078
>>
>> I doubt scrap value is over (or even near) $50/each, so maybe you can
>> deal with the guy if you're willing to pick them up.
>
> --
> | Zane H. Healy ? ? ? ? ? ? ? ? ? ?| UNIX Systems Administrator |
> | healyzh at aracnet.com ? ? ? ? ? ? ?| OpenVMS Enthusiast ? ? ? ? |
> | ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?| Photographer ? ? ? ? ? ? ? |
> +----------------------------------+----------------------------+
> | ? ? ? ? ? ? ? ? ? ? My flickr Photostream ? ? ? ? ? ? ? ? ? ? |
> | ? ? ? ? ?http://www.flickr.com/photos/33848088 at N03/ ? ? ? ? ? |
>
"Jerome H. Fine" <jhfinedp3k at compsys.to> wrote:
> >Johnny Billquist wrote:
>
>>> >> My reference to a specific "feature" is with respect to the actual
>>> >> details of
>>> >> the RTS in question. For RSTS/E, the RTS to handle RT-11 EMT requests
>>> >> does not support even all of the RT-11 EMT requests which the RT11SJ
>>> >> monitor in RT-11 supports. For example, the .CStatus request is ignored
>>> >> and the .SaveStatus request return the "dev:filnam.typ" and [PPN] for
>>> >> the
>>> >> file in question rather than the five Channel Status words used in an
>>> >> RT-11
>>> >> environment. So there are significant differences between the RT-11 RTS
>>> >> under RSTS/E and an actual RT11SJ monitor running under a PDP-11
>>> >> instruction set (specified so as to include both a DEC CPU and an
>>> >> emulator
>>> >> such as SIMH).
>> >
>> > Yes. And RTEM-11 will also behave slightly differently that vanilla
>> > RT-11 for some of those calls. And assuming there is a product called
>> > RTEM, which runs under VMS, it too will behave differently than RT-11.
>> > However, RTEM-11 and this RTEM will not necessarily behave the same
>> > way, since RTEM-11 and RTEM are different products, and different
>> > implementations, written by different people (assumingly) at different
>> > times.
>
> Agreed! The problem is that I have been unable to locate any
> documentation for which RT-11 EMT requests are handled by
> the RTEM-11 RTS along with the differences between RT-11
> and the RTEM-11 RTS.
*sigh* Still not an RTS... RTEM-11 is a program, not an RTS. There is no
RTS concept in RSX.
> The RSTS/E RTS system for RT-11 EMT requests is fairly well
> documented in the RSTS/E documentation. The only areas which
> are a bit hazy is when the [PPN] (at offset zero in the Common
> Area) is not specified (left at zero). If the [PPN] is included, then
> it is used correctly along with the file name that is specified.
>
> But for RTEM-11, I don't have any documentation at all.
The obvious answer is that this is documented in the manual that came
with RTEM-11. Now, you just need to find someone who has it... (not me)
>> > RTEM-11 is not an RTS. RTEM-11 is a product that ran (runs) under RSX.
>> > If I were to make a qualified guess, I'd suspect that RTEM-11 is a
>> > program that you start just like any other program under RSX. That
>> > program then looks like an RT-11 environment, so you can run RT-11
>> > programs inside that.
>> > RTEM-11 will catch EMTs and other traps, and do something appropriate
>> > to those traps. It's not difficult to catch traps in an RSX program.
>> > Exactly what it does, and how, is another issue. And that is something
>> > you are asking about, and which I cannot answer, and it seems noone
>> > else can either, since noone around here have RTEM-11, or have used
>> > it. As I said, I think Megan mentioned that she had used it, but she's
>> > the only one I know of who have admitted to any knowledge about this
>> > product.
>
> I suspect that Megan is no longer available for help.
I have not seen or heard from her for a long time. You know anything?
>>> >> On the
>>> >> other hand, I doubt that anyone will be likely to even test the
>>> >> RTEM-11 handling
>>> >> portion of the code, so I am probably going to just assume that what
>>> >> works for the
>>> >> RT-11 RTS system under RSTS/E will also suffice for the RTEM-11 RTS
>>> >> under
>>> >> RSX-11.
>> >
>> > Not an RTS, but anyway, you are most probably very correct in the
>> > assumption that no one will test you code under RTEM-11.
>
> That should make the situation fairly simple. I will ask anyone who
> actually
> does run under RTEM-11 to contact me if it does not work. Since I will
> be 72 years old in a few days, and I doubt that the code will be finished
> very soon, they won't have many years to check in.
Do that. I very much doubt you'll get any response though.
>>> >> That is what I had assumed, however, I am curious how RSTS/E decides
>>> >> which RTS to use - or none at all as the case might be.
>> >
>> > Are you not reading what I am writing?
>> > This is an attribute of the file. You *tell* which RTS a program
>> > should run under. Normally you do not need to do this explicitly,
>> > since every file always have an RTS associated with it, and it's
>> > normally already correct, so no need to change it.
>
> I have access to both V7 and V10.1 or RSTS/E. However, I have not found the
> program in V10.1 which copies files from RT-11 files structures to
> RSTS/E file
> structures.
And this has just about nothing to do with the question on how RSTS/E
determines which RTS a program runs under, but anyway...
As I've said before, I know about FIT. If DEC replaced FIT with
something else in RSTS/E V10, then you just have to search around in the
system. Look at the help files. That's usually a good place to start
searching. Read the manuals. I think the V10 manuals are online
somewhere as well.
I don't have any better answer off my head, and I am not going to
install RSTS/E to figure this out for you. You can do the work yourself.
It shouldn't be hard.
But by now it should be obvious that no one around here is offering the
answer so you'll have to figure it out yourself.
> Under V7, RSTS/E has a program named FIT which I use to copy
> a program from an RX02 device to an RL02 device. Based on your description,
> FIT must attach the RT-11 attribute to the file during the copy.
Yes, it's a fairly good assumption that FIT will create all copied files
>from an RT-11 formatted disk on the RSTS/E system assigned to the RT11
RTS. Assigning any other RTS to the files would probably be a mistake,
since the files most probably are coming from an RT11 system.
> It would be appreciated if you could confirm that I finally have it
> correct.
If you mean the guess that FIT would copy the files and assign them to
the RT11 RTS, then yes. That is most likely correct. It might even be
that FIT is an RT11 program itself as well...
>>> >> Well, I am having difficulty finding the "new" program under V10.1 of
>>> >> RSTS/E.
>>> >> I finally managed to figure out how to MOUNT the RL02 drives I am
>>> >> "using"
>>> >> (don't forget that all the code is being run under SIMH or E11) under
>>> >> V7 of
>>> >> RSTS/E when I am running V10.1 of RSTS/E. Since FIT had already copied
>>> >> to file to the RL02 drives, I could then used PIP to copy the program
>>> >> in I am
>>> >> testing to the correct [PPN] on the DU0: drive which is being "used"
>>> >> to run
>>> >> V10.1 of RSTS/E. A bit inconvenient, but fortunately faster than on
>>> >> a DEC
>>> >> system.
>> >
>> > That sentence makes no sense. Either you are running RSTS/E V7, or
>> > RSTS/E V10, you cannot run RSTS/E V10 when you are running RSTS/E V7,
>> > or vice versa. You'll have to reboot the machine in order to run
>> > another version of RSTS/E.
>
> AGREED!! When I tested the program under V10.1 of RSTS/E, the only
> way I managed to copy the program after booting V10.1 of RSTS/E on the
> DU0: device was to MOUNTed the RL02 device which had the program I
> wanted to test. The RL02 device had previously been booted to V7 of RSTS/E
> and FIT had been used to copy the program from the RX02 device to the RL02
> device.
>
> So YES, two boots were required, the first to copy the program from the RX02
> device (with an RT-11 file structure) to the RL02 with a RSTS/E file
> structure
> using FIT under V7 of RSTS/E. Then I SHUTUP V7 of RSTS/E, booted the
> DU0: device which has V10.1 of RSTS/E, MOUNTed the RL02 and copied
> the program from the RL02 to the DU0: device. Since this will not be done
> except for testing, it is acceptable.
Aha. So what you actually are saying is that you booted RSTS/E V7,
copied the files from an RT11 formatted disk into the RSTS/E system. You
then booted RSTS/E V10, and accessed the files previously copied.
Yes, that would work just fine.
>> > With ODT linked in to the program, just as you mentioned that people
>> > normally did with RT11 in the past as well.
>> >
>> > The same type of development cycle is still what people use to this
>> > day. You build a special debug version, which you run through the
>> > debugger, and when you are happy, you build a new, leaner version,
>> > without debug support.
>
> I agree that this was also done in the past with RT-11.
And is still done to this day in RSTS/E and RSX. And while exactly the
same, something similar is done in Unix systems, Windows systems, VMS
systems, and any other system I can think of.
The reason being that for debugging you don't want a compiler to
optimize things, and you want to include symbol tables in the compiled
image for debugging purposes, while you do not want that stuff for the
finished program, since it takes space and makes the program slower
(symbol table and non-optimization).
Modern systems however, usually allows the debugger to be dynamically
attached to a running program so you don't have to include that bit
already at the link stage.
>> > I'm not sure how you use that device driver under RT11, nor how useful
>> > it actually is...
>
> However, by V05.04 of RT-11, DEC developed the SD(X).SYS device
> driver which allowed a program to have a BPT instruction without the
> requirement to include ODT as part of the code. If the user LOADed
> SDX.SYS prior to executing the program with the BPT, but without
> ODT included, the code in SDX.SYS initialized the required VECTOR
> to trap the BPT instruction when SDX.SYS was LOADed. The code
> in SDX.SYS then performed all of the functions that ODT supported
> (and a few others as well) without adding any extra code to the program
> being tested. It is even possible to place a BPT in the monitor code
> and test those instructions as well.
Ok. So, no symbol table stuff, and no possibility to add breakpoints,
watchpoints and other stuff in the program until you hit atleast one BPT
in the code which cause the code in SDX to be called?
> Based on some of the comments in the SDX.SYS source file, it looks
> like it is also available under both RSTS/E and RSX-11. However,
> since I have almost no knowledge of RSTS/E and even less of RSX-11,
> I can't even begin to speculate why those comments are in the source
> file.
I dare say that it would be impossible to do the same in RSTS/E or RSX.
The reason is that the BPT vector that the CPU uses is set up by the
operating system, and is always used. Any program running does not use
that vector, but has a dynamically installed debug vector defined as a
part of the system image, or set up by a system call by the running
program. You do not, and can not, access the hardware related things
directly in RSX or RSTS/E and hope that anything will contiue to work.
The hardware BPT vector is used by the executive debugger in RSX (XTD),
which is a OS debugger somewhat similar to ODT, but specifically
designed to debug the OS. It is always there, and if you mess with that,
you are going to be sorry. When a user program executes a BPT
instruction, the kernel gets called. It checks wether the program have
installed a debug handler, and if so, that handler is being called in
the context of the user program. If no debug handler have been installed
for that program, the program aborts. You can have any number of
programs running in parallel, all with their own installed debug
handlers, which can actually be different debuggers that have nothing to
do with each other. How on earth do you think a common device driver
could ever handle such a situation?
RT11 is a single user system, where the OS do so much less for you that
this concept is even possible. For more complex systems, you cannot do
things this way.
Johnny
Last night I finally had time to assemble my Deviceside USB->5.25"
floppy interface. I decided to do it all slick-like and put the drive
in the shell of an old Sony USB CDRW. I have two examples of the TEAC
FD-55GFR drive laying around, which is the drive recommended on the
developer's site. I attached one to the ext drive carrier and
powered on. The drive head started seeking back and forth, not the
full travel of the disk, maybe 1/4 of it. It made a loud, steady
click and flashed the panel light of the bay, as if it was drawing too
much power from the little PSU. However, I went ahead and hooked it
up and read disks (DOS 1.2mb, AppleDOS and C64 1541) to images. I
haven't fully tested the images yet but they didn't error out during
the read. The DOS one was mountable in WinImage, the C64 one in CCS64
(don't have an Apple II em handy.)
Still bothered by the noise, I attached a Panasonic JU-475-4 drive
instead. It was quiet, no blinking light. I imaged the same disks
with that drive and that appeared to work fine, too.
Does anyone know the FD-55GFR well? It seems to have an auto-sense
mech of some kind, and one of the two I have has a spring-eject (the
other may have had it too but the spring is missing?) It seems likely
that it would click continuously, searching for a disk. Maybe this is
normal behavior for this drive and it seems loud because it's open?
It does the head-seek continuously whether there is a disk inserted or
not, lever-down or not. This seems bad to have happening on top of
the exposed disk surface. Or, again, maybe it's normal for this
drive?
The easy solution is go with the Panasonic and not worry about it.
But I'd like to stick to the developer's recommended drive unless I
can be sure the Panasonic is 100% compatible too.
-j
--
silent700.blogspot.com
Retrocomputing and collecting in the Chicago area:
http://chiclassiccomp.org
Not exactly retro in its build, but it might interest folk hereabouts.
http://www.linusakesson.net/chipophone/index.php
The Chipophone is an electronic organ whose guts have been replaced
with a pair of microcontrollers to make it into a 1980s-style 8-bit
synthesizer, for playing classic videogame chiptunes live. It helps
that its creator is an excellent player of such things.
For example, Rob Hubbard's /Spellbound/ from 1986:
http://www.linusakesson.net/chipophone/spellbound.php
--
Liam Proven ? Profile & links: http://www.google.com/profiles/lproven
Email: lproven at cix.co.uk ? GMail/GoogleTalk/Orkut: lproven at gmail.com
Tel: +44 20-8685-0498 ? Cell: +44 7939-087884 ? Fax: + 44 870-9151419
AIM/Yahoo/Skype: liamproven ? MSN: lproven at hotmail.com ? ICQ: 73187508
I have a mint condition Diablo 630 ECS printer that I purchased NEW a couple of years ago. Yes, new. It still had the shipping tie-downs on the carriage. I've never done anything with it other than run the self-test so it's time to let it go. Before I put it up on eBay, I thought I'd mention it here. It also comes with 12 daisy wheels and the optional automatics sheet feeder which is still sealed in plastic. If someone is willing to come pick it up, I'll let it all go for $100.00. (That's less than what I paid for the daisy wheels.) I'm located in Southern New Hampshire (USA). I've got pictures, if anyone's interested.
-Mardy
On 7/22/10, Jim Leonard <trixter at oldskool.org> wrote:
> On 7/22/2010 12:48 PM, Ethan Dicks wrote:
>> If I were to take this for a spin, I could probably come up with an
>> Adaptec 1542A (guessing it won't work with a 1542C).
>
> 1542C was preferred, actually.
Excellent. For an ISA card, it's not that uncommon. I bought one
when they were brand new and really liked it (I think I was upgrading
>from a 1542B at the time). The BIOS-accessible formatter and surface
tester was really, really handy.
-ethan
I have the first 6 issues of Borland's Turbo Technix available for the cost
of postage. Bimonthly issues run from November/December 1987 through
September/October 1988.
Please reply offlist.
Jack
Anyone have a copy of or knows where I can get a copy of:
"IBM 4321/4331 Processors Compatibility Features," IBM GA33-1528, any
revision?
Revision 3 was published in September 1982.
Contact off line please
Tom
Somebody gave me this a couple of years back and it's been sitting on a shelf ever since. Now it's time to clean off the shelf. If someone wants it before I haul it off to the landfill, please let me know. I never tried it, but the person that gave it to me said that it was working for them. Local pickup in Southern New Hampshire (USA). If someone wants it bad enough and can't pick it up, I'm willing to pack it up and ship it for them.
-Mardy
At 11:16 AM 7/20/2010, Liam Proven wrote:
>All fair points, but then, who ever used serial ports to connect mass
>storage? (I know there was a serial port hard disk for the first ever
>Mac, but that was from complete lack of any alternative.)
I can think of the Commodore 64- 1541 drive and the external floppy drive
for the Tandy Model 100.
At 11:21 AM 7/20/2010, Ray Arachelian wrote:
>Works beautifully under VMWare Fusion. And when I did have to use
>windows, it worked nicely under VMWare server.
I was referring to ESXi, the small-to-medium enterprise version.
At 12:00 PM 7/20/2010, Ethan Dicks wrote:
>Generic cables? The ends are generic, sure, but there's A, B, mini A,
>several types of mini B (one dominant, but hardly unique), and then
>there's USB 1.1 vs USB 2.0 in terms of cable ratings (but will a USB
>1.1-marked cable pushed to 2.0 speeds really be too noisy or is that
>just marketing?) I have no less than 5 flavors of USB cables lying
>around the house, though two of the 5 are the most common.
Plus the variations and quirks in terms of the power requirements for
various devices. There's wall transformers with USB connectors that
don't supply enough power for some devices, some PC ports that don't
supply enough power, some hubs that that don't, some devices that
come with dual USB connectors in order to suck more amps, etc.
- John
I am experimenting with using Hummingbird Exceed to get a DECWindows
environment running on my PC. I have managed to get this to work using XDM,
but there are some other things about Exceed that I don't really understand
and would like to explore.
The first is that Hummingbird offers an option to use something called
PCX$SERVER. I have not been able to find out much about this and was
wondering if someone might tell me what this is and where I might find it?
The second is that Hummingbird also seems to offer DECnet as a transport,
but I don't see how to set this up on the PC side and again the docs I have
don't say anything on this. Does anyone know how you might do this?
Thanks
Rob
Hi folks,
> If it was developed on the Lisa, would they have used LisaPascal?
Actually the answer is in:
http://www.folklore.org/StoryView.py?project=Macintosh&story=3rd_Party_Deve…
It was done using the "Lisa Monitor development environment" which was command line based with a UCSD p-system style command structure (early Mac programmers considered MPW to be the PorkShop).
-cheers from julz @P
Hi folks,
> If it was developed on the Lisa, would they have used LisaPascal? There's a
> Lisa emulator out there -- I might play with it this weekend and see if it
> works.
www.folklore.org has lots of juicy stories about early Mac development.
In 1981 they were using Lisas for development (obviously).
MacPaint development details:
http://www.folklore.org/StoryView.py?project=Macintosh&story=MacPaint_Evolu…
The following article explains that "Macintosh development in the early
days (circa 1983-1985) was done using the Apple Lisa computer and its Lisa
Workshop development environment."
http://www.folklore.org/StoryView.py?project=Macintosh&story=3rd_Party_Deve…
I remember using (the interpreted) MacPascal in 1986. There weren't any
Mac-hosted Pascal compiler environments that could fit into <=512Kb
(128K Macs could support 256KBit DRAMs).
I'm really wondering how easy it would be to convert MacPaint so that it
can be compiled in, say, MPW Pascal / 68K.
-cheers from julz @p
Found the link below this morning, mostly assembly with some Pascal as
to be expected. Hopefully more will show up.
Looks like there's a nice history there as well.
http://www.computerhistory.org/highlights/macpaint/
> Still the question remains: how best to read cartridge tapes with
> faulty belts and sticky drive capstans?
Even 20 years ago, it was de rigueur to disassemble the cartridge
and replace worn or stretched or deformed rubber parts with new
or at least better components from a "donor cartridge".
When the decay had left little rubber fragments in the path you had
to take the cart apart to remove/clean them before reading anyway.
Twenty years ago, only the worst (due to extreme ozone exposure or
physical wear) carts needed this. Today the issue is that all the
donor cartridges may be 20 or 30 years old too.
Tim.
Serious question: We have a number of paper tapes which have been stored
in paper boxes for quite some time. I would like, if at all possible, to
move these into the kind of storage containers in which many of our tapes
already live. These are transparent stable plastic with a lid, divided into
8 sections of Just the Right Size(TM) to hold fanfold paper tape.
There is probably no one who makes these any longer, but on the off chance
that I am wrong about that, does anyone know (a) who might make these, or
(b) what they are called, so that I can try to find them using one of the
large search engines, or (c) have a supply of them stashed with which the
current owner is willing to part?
Thanks,
Rich
Rich Alderson
Vintage Computing Sr. Server Engineer
Vulcan, Inc.
505 5th Avenue S, Suite 900
Seattle, WA 98104
mailto:RichA at vulcan.com
mailto:RichA at LivingComputerMuseum.orghttp://www.PDPplanet.org/http://www.LivingComputerMuseum.org/
If it was developed on the Lisa, would they have used LisaPascal? There's a Lisa emulator out there -- I might play with it this weekend and see if it works.
------Original Message------
From: Cameron Kaiser
Sender: cctalk-bounces at classiccmp.org
To: CCTalk
ReplyTo: CCTalk
Subject: Re: MacPaint and QuickDraw source code released
Sent: Jul 22, 2010 11:02 AM
> I've never used Think Pascal, but I did use Think C (LightSpeed C) a
> lot. I wonder if you could port it to Think Pascal... I would think you
> could. Or maybe it would "just build" using MPW.
Glancing cursorily, I think MPW would have a fit. The .rsrc file also needs
to be turned into a proper resource fork.
My instinct would be to try to pre-process it. I agree THINK Pascal would be
the logical, closest first target.
--
------------------------------------ personal: http://www.cameronkaiser.com/ --
Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckaiser at floodgap.com
-- The moon may be smaller than the Earth, but it's farther away. -------------
Rich
-----------------------------
Richard A. Cini, Jr.
Managing Director
Wells Fargo Capital Finance
New York, NY 10017
(P) (212)-545-4402
--------------------------
Sent from my BlackBerry Wireless Handheld
This email is subject to a disclaimer, please click on the following
link or cut and paste the link into the address bar of your browser.
https://www.wellsfargo.com/com/disclaimer/uswfbnap
I am looking for a set of boot proms that would enable me to boot from the RL01 that is connected to my PDP8/A
That is, if such a boot prom actually exists.....
And as a side note : why is the 8/A so unloved ?
Big RL01 disk, 128k memory, fpp processor, all in one case. Try that with another -8 !
Jos
On 21 Jul 2010, at 22:22, cctalk-request at classiccmp.org wrote:
> Message: 23
> From: Richard <legalize at xmission.com>
>
>
> In article <4C46A57E.15148.5E8BCB at cclist.sydex.com>,
> "Chuck Guzis" <cclist at sydex.com> writes:
>
>> [...] Almost all cartridge DC-
>> style tapes are recorded "serpentine" style--i.e. start in one
>> direction, shift the head, reverse, etc...
>
> This is news to me. Every cartridge tape I've ever used recorded data
> to the end and then stopped. I don't recall seeing any mechanism for
> shifting the tape head in HP264x terminals with DC100 cartridges nor
> in Tektronix 4051 terminals with DC300 cartridges.
>
>> So the spooling scheme had better work. I'm not aware of any 32-
>> channel (for example) QIC heads.
>
> QIC tapes are something different from DC300 and DC100 tapes.
I always though QIC was an abbreviation for Quarter Inch Cassette. I'm fairly sure I've used DC300s and they were cassettes full of quarter inch tape with a constant peripheral speed drive band inside so no need for variable speed spool motors.
Roger Holmes
At 09:15 AM 7/20/2010, Ethan Dicks wrote:
>I really do not like USB. It takes hundreds of cycles and more to
>move a simple message, it's a host-based, not bi-directional design,
>and it's only available on somewhat newish kit.
What drives me crazy is the lack of debugging of the stack. When
it's not working on contemporary Windows kit, there's no way I've
found to help understand what's not really working.
This morning, I plugged a client's thumb drive into their laptop, and
the logical drive seemed to disappear at random. I switch connectors,
thinking it's a wonky physical connector, no difference. Just unreliable.
Another stunner was that vmWare didn't support native USB on the host.
They're accomplishing thousands of other miracles, but can't virtualize
USB enough for me to connect a drive to a virtual appliance?
(I think this is fixed in last month's major release.)
I'm often trying to connect client hard drives to backup machines via
USB-to-SATA/IDE adapters, and when the drive won't seem to wake-up
or show up, there's no way to debug where it is failing.
I suspect some of the opacity is deeper in Windows at the logical
Disk Management level, with layers of "Disk 1" numbering, logical drives
and partitions and SCSI emulation, a registry that records every
drive fingerprint ever connected to it (really), etc.
Last week, a client's thumb drives weren't being recognized. I had to
reinstall Windows. I think Windows was failing at the very top layer,
at the moment where a recognized device was known to be hard drive,
but it couldn't show it as a logical drive.
And yet so many built-in media-readers for CF/SD cards will show
logical drive letters to the OS when there's nothing inserted.
My desktop shows four. Why?
- John
made you look:
http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=120596128607&ssPageName=…
Canon CX-1. Not in the greatest condition, but it's the first time I've seen one offered. 6809 based. My Canon AS100 has something in the way of a native debugger also (haven't turned it on in over a year).
starting bid was 25$. Ended at about 235$. And I had thought that no one even knew it existed.
For those who use Firefox, Chrome, etc. browswers that support FTP you can also:
ftp://bickleywest.com/pdp8a_bootrom/
and right click on the files...
Cheers,
Lyle
---------- Forwarded Message ----------
Subject: Re: Looking for PDP8/A RL01 boot proms.
Date: Wednesday 21 July 2010
From: Lyle Bickley <lbickley at bickleywest.com>
To: cctech at classiccmp.org
On Wednesday 21 July 2010, Jos Dreesen wrote:
>
> I am looking for a set of boot proms that would enable me to boot from the RL01 that is connected to my PDP8/A
> That is, if such a boot prom actually exists.....
>
> And as a side note : why is the 8/A so unloved ?
>
> Big RL01 disk, 128k memory, fpp processor, all in one case. Try that with another -8 !
>
> Jos
>
>
I've uploaded the two bootroms you need to boot a RL01 on a PDP-8A using a KM8 (M8317). You'll need to burn the images into 82s126 chips. I've also uploaded the corresponding level 8A schmatics/manuals which have this level of ROM described (IIRC on the third page of the KM8 portion of the schematics).
You can pick up the images and manual by:
ftp bickleywest.com
user: anonymous
pswd: (email address)
cd pdp8a_bootrom
...
bye
Cheers,
Lyle
--
Lyle Bickley, AF6WS
Bickley Consulting West Inc.
http://bickleywest.com
"Black holes are where God is dividing by zero"
-------------------------------------------------------
--
Lyle Bickley, AF6WS
Bickley Consulting West Inc.
http://bickleywest.com
"Black holes are where God is dividing by zero"
>
> I have a bulky Unisys EVG-500-COL 17" monitor that is taking up space. It
> has a 9-pin VGA connector and 5 BNC plugs on the back. It needs to warm up
> to work properly. I am not sure whether to keep it or just take it to the
> tip. What do people here think?
Well, alas I agree that monitors can be a right pain to store, being
large, heavy, and often not easy to stack things on top of.
I think I would keep the monitor if it fitted into one of the following
categories.
1) It is the origianl monitor for a particular classic computer (so I
would keep the special monitors used on PERQs, and the HP-badged NEC
mono monitros used with the HP86B, etc)
2) It does something that modern monitors don't (supports a particular
scan rate, for example)
3) It has something interesting about the design.
Any others?
-tony
Hey;
I was reading something the other day about being able to hand-clock a
Z80, that it was so stable (due to not using dynamic registers,
apparently) that with the appropriate debounce circuit you could literally
manually step it through instructions.
Is this as rare as it sounds?
Has anyone -tried- hand-clocking a Z80?
- JP
Hampton, Iowa
Hi Jeff,
Interesting article. I am a big fan of the ez80f91. I find the data throughput rate so efficient that it's hard to over tax the CPU. I've built some pretty elaborate hardware/software systems using it! One thing I've been curious about and I want to try this myself some time. I wonder if anyone's ever built an LCD controller using the ez80? I believe it should be possible to get VGA quality out of it.
Regards,
Rick Jasper
For the cost of shipping:
S-100 "Micro Systems" magazines
Issues 1/1 (Jan 80) through 3/4 (Jul 82).
Issue 1/3 is missing.
I am in southern California 92656
I was looking for something totally different on the web (always the way...)
and I came across the Elenco MM-8000 kit. It appears to be in current
production (and is not _that_ expensive, $120 or so). It's a kit to build
(as in solder up a PCB) a single-board 8085-based computer with a keypad
and even front panel switches.
OK, it's OT (in that it's not 10 years old), but it certainly seems to have
the feel of a classic evaluation board.
Has anyone here tried it?
-tony
--------------------------------------------------------------------
mail2web.com ? Enhanced email for the mobile individual based on Microsoft?
Exchange - http://link.mail2web.com/Personal/EnhancedEmail
Al writes:
> I have been using conventional drives for 1/2" tape recovery.
> John Bordyuik's web site at one point described the system he uses,
> which has a modified M4 data tranport fitted with an IBM 3480 16 track
> magnetorestrictive head and modified read electronics. In either case
> the tape transport is conventional.
His current website is different than the old one but he's got
some good techie tidbits mixed in with technical whiz-bang and
very satisfyingly shows recovered data and graphical representations
of analysis techniques and post-processing for application
specific data, along with a heavy sales pitch at:
http://www.johnbordynuik.com/sites/default/files/tech_briefing.pdf
Tim.
Hello,
I recently acquired my first DEC PDP. It is a VT103 (VT100 terminal with
a PDP 11/23 inside). It came with a pair of cartridge disk drives (HEAVY!)
that are RK05 compatible, a DEC RX02 (pair of 8" floppy disk drives), boxes
of manuals, 3 DEC operating systems, software, and an extra VT100.
While the DEC operating systems are OK, I am actually interested in using
the machine to (finally) go through "Lions' Commentary on Unix" (Unix V6),
using software downloaded from http://www.tuhs.org/. (Lions' book here):
http://www.amazon.com/dp/1573980137/
After I do that, I want to move up to Unix v7, 2.9BSD, and try other Unix
distros available for the PDP.
My concern is that the 18-bit PDP 11/23 does not have enough memory.
It currently has 128KB installed, with a maximum of 256K possible after a
memory board upgrade (M8067, MSV11-PK = 256KB). How far do you estimate I
can get with just 128KB memory? Can I get through Lions' book?
I am looking at adding wires to the backplane to make it a 22-bit machine,
and using a quad height qbus memory board, M7551 (available in 1MB, 2MB and
4MB sizes). However, I am not ready to dive in and start modifying the qbus
backplane for 22-bit addressing just yet. So my question is:
Rather than invest in a 256KB memory board designed for the 18-bit qbus,
can I install a 22-bit 1MB, 2MB or 4MB memory board in the 18-bit system,
and just use the first 256KB for now? Also, is the VT103 backplane
compatible with a quad-height memory board? (It only has dual-height
cards installed at the present time).
Parts inventory:
- VT103, with:
- 4x4 qbus backplane, 18-bit. The manual says "two H803s (2x4 connector
blocks, stacked vertically in a 4x4 configuration)". I know there are
possible issues with "straight" vs. "serpentine" slots, but I have not
got that figured out yet on the VT103.
- M8186 KDF11-A CPU (Newer revisions of KDF11-A's are 22-bit capable).
http://world.std.com/~mbg/pdp11-field-guide.txt
says: "(Prior to etch rev. C, 18-bit addressing only. ...)"
I could not find revision information on the M8186 board, but "146 CA"
is stamped into one of the red plastic handles. I can email close-up
photos to anyone who wants to take a look and determine if this is a
rev C or later board capable of 22-bit addressing.
- M8043 Quad Serial board. This doc says it is 22-bit compatible:
http://www.ibiblio.org/pub/academic/computer-science/history/pdp-11/hardwar…
- M8029 (RXV21) floppy disk board (18-bit DMA only). -Will this be a
problem with Unix v6 or 2.9BSD if running with 22-bit addressing?
- M8208 "VT103 Maintenance Module" (Unknown if 22-bit compatible).
- Xylogics C510 (formerly called "Wizard 1") cartridge disk controller
board, with 18-bit addressing, connected to a pair CDC 9427H "Hawk"
disk drives (one disk drive is DOA, but the other is OK).
- 3rd party memory board (128KB), Christlin Industries, Inc.
So, initially I want to run a 22-bit memory board (M7551) in an 18-bit
VT103 qbus backplane, and access only the first 256KB of memory using
18-bit addressing. Is this possible? Thank you for your help.
Scott M.
"Jerome H. Fine" <jhfinedp3k at compsys.to> wrote:
> >Johnny Billquist wrote:
>
>>> > >"Jerome H. Fine" <jhfinedp3k at compsys.to> wrote:
>> >
>>> >> I would not assume anything until I actually had tested the presence
>>> >> or absence of a
>>> >> specific "feature".
>> >
>> > What have any features have to do with this?
>> > I'm telling you that RTEM-11 will not, and never have been capable of
>> > running on a VAX.
>> > If there was a RTEM product for the VAX, it would have to be a
>> > separate product, with a separate code base from RTEM-11, since you
>> > cannot write a RT-11 emulator of any kind in PDP-11 mode on a VAX. It
>> > will have to be VAX code. And thus, it can not be the same product as
>> > a RT-11 emulator program written to run under RSX.
>
> I agree that it is obvious that the RTS code will be written in the native
> instruction set of the system under which the RTS is running. That means
> that the RTS system under RSTS/E executes PDP-11 instructions and
> uses RSTS/E EMT requests. As you state, under VMS and a VAX,
> VAX instructions are used. And if I may push the envelope a bit, under
> SIMH, x86 instructions are used if we agree to call SIMH or E11 a RTS
> of a different kind, although the more descriptive name is emulator.
No. Now you are mixing and confusing things again.
First of all, let's make clear that RTS is a RSTS/E specific concept.
Don't use it outside discussions of RSTS/E.
As RTS is a RSTS/E specific thing, any code written to implement an RTS
is *always* written in PDP-11 machine code. You could possibly write it
in some supported high level language under RSTS/E, but I don't think
any actually is supported for doing this. The one possibility I can
think of would be PDP-11 C for RSTS/E, which might allow you to do
something like this. Otherwise, an RTS must be written in MACRO-11.
The RTS does not do anything until a trap happens. Be that from an EMT,
an illegal memory reference, or whatever. At that point, the RTS is
called at a specific address, and the RTS can then do whatever it feels
like, and either abort the running program, or else let it continue.
The PDP-11 compatibility mode on some VAXen allows the PDP-11
instructions to be executed without any other layer involved. They are
executed by the microcode of the CPU. But not all instructions are
implemented. If an unimplemented instruction is executed, the CPU traps
back to VAX mode, and to a trap handler.
Something like simh is like the microcode of the CPU. However, the
microcode in this case looks just like x86 assembler. This is nothing at
all like what an RTS under RSTS/E is doing. The microcode executes all
instructions that have been implemented, and if an unimplemented
instruction occurs, some kind of trap happens. On a VAX, this will be a
trap back to VAX mode, and a trap handler. Under simh, it will be
handled just like on any other PDP-11. Ie. you'll get a trap in PDP-11
mode, to the trap address for illegal instructions. (Check out the
processor handbook for a PDP-11 if you want more details on this.)
Now, it should be pretty obvious that this is not the same thing as what
un RTS do. An RTS depends on the PDP-11 specific behaviour when a trap
occurs. A VAX does not follow that behaviour. A PDP-11 emulator like
simh do. So, you can run RSTS/E on simh, but you cannot run RSTS/E on a
VAX. Furthermore, you can have an RTS under RSTS/E which emulates the
RT-11 system calls. You cannot even run that RTS on VMS.
> My reference to a specific "feature" is with respect to the actual
> details of
> the RTS in question. For RSTS/E, the RTS to handle RT-11 EMT requests
> does not support even all of the RT-11 EMT requests which the RT11SJ
> monitor in RT-11 supports. For example, the .CStatus request is ignored
> and the .SaveStatus request return the "dev:filnam.typ" and [PPN] for the
> file in question rather than the five Channel Status words used in an RT-11
> environment. So there are significant differences between the RT-11 RTS
> under RSTS/E and an actual RT11SJ monitor running under a PDP-11
> instruction set (specified so as to include both a DEC CPU and an emulator
> such as SIMH).
Yes. And RTEM-11 will also behave slightly differently that vanilla
RT-11 for some of those calls. And assuming there is a product called
RTEM, which runs under VMS, it too will behave differently than RT-11.
However, RTEM-11 and this RTEM will not necessarily behave the same way,
since RTEM-11 and RTEM are different products, and different
implementations, written by different people (assumingly) at different
times.
>>>>>>> >>>> >> I don''t know if Megan Gentry is still around or perhaps Allison
>>>>> >>>> or >> one of the
>>>>>>> >>>> >> other DEC fellows. Perhaps they might at least know something
>>>>> >>>> about >> which
>>>>>>> >>>> >> hardware and operating system(s) supported RTEM?
>>>> >>>
>>>>> >>> > I definitely remember (and probably still have some mail
>>>> >>> somewhere) > from Megan mentioning that she used RTEM-11 for RT-11
>>>> >>> work, running on > RSX machines. Possibly even an 11/74.
>>> >>
>>> >> I don't have enough information about RSX to know if RTEM-11 was
>>> >> supported.
>>> >> However, ...
>> >
>> > I'm telling you that it is. Just google for it, and you will find the
>> > documentation from DEC that is still on the net about this product.
>> > It's actually really simple. Go to "www.google.com". Type in "rtem-11
>> > rsx" in the search field, and hit enter.
>> > The first hit will be
>> > http://www.google.se/url?sa=t&source=web&cd=1&ved=0CBcQFjAA&url=http%3A%2F%…,
>> > which is "RSX-11M Optional Software Cross Reference Table", which
>> > lists what version of various software is compatible with RSX-11M V4.0
>> > and V4.1. Among these, you'll find RTEM-11 V1.0 and V1.1. More
>> > "supported" than that is hard to get.
>
> Thank you for the reference. Although this does make my goal of having
> the code
> support running the program under the RTEM-11 RTS even more difficult.
RTEM-11 is not an RTS. RTEM-11 is a product that ran (runs) under RSX.
If I were to make a qualified guess, I'd suspect that RTEM-11 is a
program that you start just like any other program under RSX. That
program then looks like an RT-11 environment, so you can run RT-11
programs inside that.
RTEM-11 will catch EMTs and other traps, and do something appropriate to
those traps. It's not difficult to catch traps in an RSX program.
Exactly what it does, and how, is another issue. And that is something
you are asking about, and which I cannot answer, and it seems noone else
can either, since noone around here have RTEM-11, or have used it. As I
said, I think Megan mentioned that she had used it, but she's the only
one I know of who have admitted to any knowledge about this product.
> On the
> other hand, I doubt that anyone will be likely to even test the RTEM-11
> handling
> portion of the code, so I am probably going to just assume that what
> works for the
> RT-11 RTS system under RSTS/E will also suffice for the RTEM-11 RTS under
> RSX-11.
Not an RTS, but anyway, you are most probably very correct in the
assumption that noone will test you code under RTEM-11.
>>>>>>> >>>> >> In addition, RSTS/E also supported RT-11 programs via the
>>>>> >>>> SWITCH RT11
>>>>>>> >>>> >> capability. However, only the RT-11 EMTs which are used by a SJ
>>>>> >>>> are >> supported
>>>>>>> >>>> >> by RSTS/E. At least there is quite reasonable documentation as
>>>>> >>>> well >> as the ability
>>>>>>> >>>> >> to test and actually run RT-11 programs under RSTS/E up to the
>>>>> >>>> latest >> versions
>>>>>>> >>>> >> of RSTS/E. RT-11 EMTs for mapped RT-11 monitors (RT11XM) are
>>>>> >>>> not >> supported
>>>>>>> >>>> >> not are multi-terminal EMTs. Also, probably the latest RT-11
>>>>> >>>> EMTs >> for file status
>>>>>>> >>>> >> information are also not supported under RSTS/E.
>>>> >>>
>>>>> >>> > The correct technical term is that RSTS/E have a RT-11 *run time >
>>>> >>> system*. An RTS in RSTS/E provides an environment under which you
>>>> >>> can > get a specific behaviour. So you had RTSes for RT-11, RSX,
>>>> >>> BASIC+, > TECO, DCL and some other stuff. Some RTSes were also KBMs
>>>> >>> (keyboard > monitors), meaning you could "switch" to them, and get
>>>> >>> an interactive > command line interpreter with that. But the RTS
>>>> >>> mostly implemented > system calls. However, there were RTSes which
>>>> >>> didn't implement any > system calls, and only gave you the basic
>>>> >>> calls RSTS/E itself > provided, and mostly focused on being a KBM,
>>>> >>> such as DCL.
>>> >>
>>> >> I apologize for my lack of familiarity with the terminology. Your
>>> >> description
>>> >> is what I was attempting to say.
>> >
>> > :-)
>> >
>>> >> Actually, my testing seems to show that RSTS/E supports being able to
>>> >> run RT-11 programs even if the RT-11 RTS is not activated. For example:
>>> >> RUN MACRO
>>> >> is possible if the RTS is normal RSTS/E or RT-11. This might be
>>> >> based on the
>>> >> file type. RSTS/E may determine that MACRO.SAV is an RT-11 program and
>>> >> support the RT-11 EMT requests. Or RSTS/E may support naked RT-11 EMT
>>> >> requests from any program. That is something I should test.
>> >
>> > No, you are confusing things, and making wild guesses.
>> > What do you mean by "activated"? There is no activation. If an RTS is
>> > installed, it will always be used for programs that are marked as
>> > requiring that RTS. This is an "attribute" of a file. Whenever that
>> > file is run, it is run under the indicated RTS. If you try to run a
>> > program that requires an RTS that don't exist I would suspect that
>> > you'll get an error.
>
> That is what I had assumed, however, I am curious how RSTS/E decides
> which RTS to use - or none at all as the case might be.
Are you not reading what I am writing?
This is an attribute of the file. You *tell* which RTS a program should
run under. Normally you do not need to do this explicitly, since every
file always have an RTS associated with it, and it's normally already
correct, so no need to change it.
When a file is created, it is created by a program. That program is
running under an RTS. And so, the new file will by default also be
associated with that RTS. So when you run LINK.SAV to create a new
runnable file, LINK.SAV will create your file, and since LINK.SAV runs
under the RT11 RTS, your new program created by LINK.SAV will also be
marked as associated with the RT11 RTS. Now, this is obviously correct,
so you do not need to think about it.
If you instead run TKB.TSK, that program runs under the RSX RTS. And
TKB.TSK will create a new runnable task for you. A pretty good and
obvious guess is that that program is a RSX task, and as such, you want
it to run under the RSX RTS. And since TKB is an RSX task, it runs under
the RSX RTS, and files created by TKB will thus also be associated with
the RSX RTS. Once again, right without you having to think about it.
Would you ever want to force a program to run under another RTS
(probably a bad idea, but anyway...) you can change this with the PIP
program.
Now, I hope I've made it clear enough this time.
>> > Also, if you type "RUN MACRO", how do you know that you are even
>> > running the RT-11 version? RSTS/E normally also have an RSX RTS
>> > available, and an MACRO.TSK, which is MACRO-11 running under the RSX RTS.
>
> When MACRO.SAV is run (under the RSTS/E RTS or any other RTS or under
> any other operating system including RT-11 and TSX-Plus, it is simple to
> just
> type <RETURN> at the "*" prompt to obtain the version number and so identify
> which program is being run.
RSTS/E is *not* an RTS. RSTS/E is the operating system. RT-11 the
operating system is never an RTS. There is an RT11 RTS under RSTS/E, but
that is only relevant when you are running RSTS/E as the operating system.
If you type just "RUN MACRO", how do you even know it's invoking
MACRO.SAV? There is also a MACRO.TSK normally under RSTS/E, since you
might also want to compile things in RSX flavour. Both are MACRO-11,
based on the same code base, and actually even generating the same
object files. However, the system calls they make are specific to the OS
they are built for, so they are not the same binaries.
MACRO.SAV *always* runs under the RT11 RTS. If you were to try and run
MACRO.SAV under any other RTS, you would crash and burn hard and fast.
Note that what KBM you have switched to have nothing to do with this.
You can switch to basic, DCL, or RSX for all that you want. If you then
run MACRO.SAV, it will still run under the RT11 RTS. It *must*, or it
won't work.
>>>>> >>> > All exeutable files have an RTS associated with it, and when the >
>>>> >>> program is run, it is run under that RTS, which then handles all
>>>> >>> EMTs > and so on when the program executes them.
>>> >>
>>> >> Does the file type trigger the use of that RTS?
>> >
>> > Unless my memory have totally rotted away, the answer is no. The RTS
>> > associated with a file is an attribute of the file, just like file
>> > protection. There is a switch to PIP that you can use to check, and
>> > set, the RTS.
>> > That said, all RTS have a default file extension as well, and I think
>> > that is used to search for runnable files if you just type "RUN MACRO"
>> > for example.
>
> That answer helps quite a bit. Thank you!
So, if you have access to a RSTS/E system, now type "HELP PIP", and find
out how you see and set the RTS for a program.
>>> >> I do have a question. With V7 of RSTS/E, the FIT program is able to
>>> >> copy files from a drive with an RT-11 file structure (such as an RX02)
>>> >> to the RSTS/E file structure. My initial testing with V10.1 of RSTS/E
>>> >> shows that (at the very least the distribution which I am using) does
>>> >> not
>>> >> have a FIT program. Is there some other method of making a copy of
>>> >> a file on an RX02 with an RT-11 file structure to a device with a RSTS/E
>>> >> file structure?
>> >
>> > Either FIT, or some "new" program that does the same thing, I'd guess.
>> > I'm no expert on RSTS/E, and my experience is old. I mostly ran RSTS/E
>> > between V7.1 and V9.0, with the majority of my time in the V7-V8
>> > timeframe.
>
> Well, I am having difficulty finding the "new" program under V10.1 of
> RSTS/E.
> I finally managed to figure out how to MOUNT the RL02 drives I am "using"
> (don't forget that all the code is being run under SIMH or E11) under V7 of
> RSTS/E when I am running V10.1 of RSTS/E. Since FIT had already copied
> to file to the RL02 drives, I could then used PIP to copy the program in
> I am
> testing to the correct [PPN] on the DU0: drive which is being "used" to run
> V10.1 of RSTS/E. A bit inconvenient, but fortunately faster than on a DEC
> system.
That sentence makes no sense. Either you are running RSTS/E V7, or
RSTS/E V10, you cannot run RSTS/E V10 when you are running RSTS/E V7, or
vice versa. You'll have to reboot the machine in order to run another
version of RSTS/E.
>>> >> Also, is it possible to run an RT-11 program under a DEBUG mode? It
>>> >> would be much easier to check out the code if that is possible. At the
>>> >> moment, I can check most of the code under RT-11. However, the
>>> >> portion which runs in a different manner under RSTS/E as opposed to
>>> >> RT-11 since RSTS/E does not support all RT-11 EMT requests in the
>>> >> same manner as RT-11.
>> >
>> > What do you mean by "debug" mode???
>
> I am not sure if RSX-11 has an SD(X).SYS device driver like RT-11 which
> handles the BPT instructions placed in a program running under RT-11 when
> the user wants to stop a program in the middle of running and check out the
> code. The SD(X).SYS device driver under RT-11 supports the features that
> the ODT subroutine handles without the requirement for that subroutine to be
> part of the program which is being tested. Under TSX-Plus, there is a
> so-called
> debug option which invokes the same sort of support. Since the SD(X).SYS
> is written as a device driver in RT-11 (starting with around V5.4 of
> RT-11 if
That is called a debugger, and yes, there are several debuggers for both
RSTS/E and RSX. Normally you have to link them into the runnable image
in order to be able to access things in the running program though.
If the debugger is not linked in to the program, the program will
normally abort if it executes a BPT instruction.
Since you do mention this concept in your text, you should be familiar
with it. ODT is one of the debuggers availabe, and I believe it's the
only one shipped with RSTS/E by default.
> I remember correctly), debugging a program under RT-11 became much easier
> since ODT was no longer inserted into the program being tested.
>
> I was hoping that RSTS/E has the same sort of feature available, but
> that does
> not seem to be the case. But then how did users debug their programs under
> RSTS/E?
With ODT linked in to the program, just as you mentioned that people
normally did with RT11 in the past as well.
The same type of development cycle is still what people use to this day.
You build a special debug version, which you run through the debugger,
and when you are happy, you build a new, leaner version, without debug
support.
I'm not sure how you use that device driver under RT11, nor how useful
it actually is...
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
in particular a nice crt-chassis, etc.
I was perusing the vintage computer marketplace a few weeks back, and someone had some of that very stuff. I think it may even have been Erik. In any event I don't know how to contact anyone on that site anymore, because someone gummed up the works LOL.
please let me know. Much obliged.
Hi Guys,
I am mostly a Lurker here and very much enjoy and will continue to enjoy
reading the posts here. However I am feeling a need to thin down my
collection some that I have been accumulating over the last 10 years. I
am looking for people to show up here with some cash and a truck and to
haul away some of my prized possession's. I don't have any blinking
light DEC machines anymore or anything ultra rare like a Lisa but I do
have a large assortment of PDP 11/23 and other QBus equipment. As well
as a decent sized collection of regular PDP 11 Unibus and mass buss
boards. I also have many different types of workstations such as Dec
Professionals , Rainbows and 3100 and 4000 series gear. Also a virtual
pile of peripherals. Also some smaller stuff like KayPro , Osborne etc.
Also much software as well and a couple nice televideo terminals. Now I
did pay good cash money for all of this and its all been stored in a
climate controlled clean area. So anyone who wants a instant collection
or just wants to come by and kick the tires and do some dealing please
e-mail me at fsmith at ladylinux dot com.
Please try and keep communications off list as this is not really
applicable I feel.
Thanks!!
Fran (Mid Alantic USA)
Will writes:
> The US truly is (was?) the land of standardized parts.
And the even better part, is there are so many standards to choose from!!!
Occasionally I get to even use Whitworth threads here at work :)
Tim.
This is not strictly on-topic, but I thought it might be of interest.
I for one, and a lot of former Psion-owning acquaintances, have long
bemoaned that there is no modern equivalent of the classic
keyboard-driven PDA available today.
Which is why I was rather interested by this device:
http://digitalchunk.com/kddi-sharp-android-iso1-smartbook.htm
--
Liam Proven ? Profile: http://www.linkedin.com/in/liamproven
Email: lproven at cix.co.uk ? GMail/GoogleTalk/Orkut: lproven at gmail.com
Tel: +44 20-8685-0498 ? Cell: +44 7939-087884 ? Fax: + 44 870-9151419
AOL/AIM/iChat/Yahoo/Skype: liamproven ? LiveJournal/Twitter: lproven
MSN: lproven at hotmail.com ? ICQ: 73187508
On 7/11/2010 1:00 PM, "Andrew Lynch"<lynchaj at yahoo.com>
>
> Hi! Just out of curiosity does anyone know of any home brew ISA bus 68K
> boards?
>
Didn't Circuit Cellar do something like this in a series of articles?
KJ
On 7/19/10, Chuck Guzis <cclist at sydex.com> wrote:
> On 19 Jul 2010 at 8:00, Steven Hirsch wrote:
>> Reminds me of
>> the DEC Rainbow (wasn't that system deliberately crippled to prevent
>> it from being able to format blank media?).
>
> If the Amlyn disks use an embedded servo, formatting one is a
> mechanical issue--you need to periodically offset from the central
> track axis a bit one way or the other to write a servo burst. Not
> easy to do wth a conventional read/write drive.
That's one issue I recall with the transition from RK05 to RL01 as
"inexpensive" cartridge media in the DEC world. The RK05 has a
manually-aligned external positioner, and the RL01 (and RL02) uses
embedded servo data. One advantage to the RK05 technique is that you
can format packs that have been bulk-erased (since the platters only
contain data, not positioning info) One advantage to the RL01 is that
you don't have to be quite as precise with head alignment (you have to
be close enough for the embedded servo data to be legible, then, IIRC,
the positioner circuit can lock on the rest of the way).
There was another method that was acceptable for multi-surface packs -
a servo surface. It's not worth dedicating an entire surface to
positioner data if you only have two surfaces - you get a poor
space-to-cost ratio. If you have 4-8 surfaces, it's more practical to
give up a surface (vs a loss of some space for embedded servo info).
An advantage of a servo-surface pack is that you can easily format the
data surfaces as long as you leave the servo surface untouched.
I've heard of a field service device for writing servo data on a wiped
RL pack, but I've never seen one in person.
-ethan
Has anyone else on the list seen one of these? I picked up a Vista V1200
disk system for Apple 2 that uses this type of drive. The mechanism takes
a plastic cartridge with five 5.25" floppy disks. The diskettes appear to
be conventional SS format with a couple of extra punchouts to mate with
the loader mechanism. Electrical interface is compatible with 8" floppy
drives (interface card was also sold for that purpose).
I'm not able to turn up any information about the drive and am wondering
how the diskette select/load scheme is intended to work. There are
at least a couple of possibilities:
- Treat the physical diskettes as portions of a single logical floppy and
select diskette by track range (first diskette 0-39, second 40-79, etc.)
- Treat each physical diskette as a logical drive and use binary select
lines on interface to choose.
Anyone have documentation on the drive mechanism or the Vista product?
Steve
--
Is the keyboard still available for purchase? Please advise. Thank you.
Linda Whetton
Environmental Resources Division
125 S. State Street, Room 6107
Salt Lake City UT 84138-1147
Tel: 801-524-3880
Fax: 801-524-3858
EM: lwhetton at usbr.gov
"Jerome H. Fine" <jhfinedp3k at compsys.to> wrote:
> >Johnny Billquist wrote:
>
>>> >> I suspect that the most likely possibility is that RTEM and RTEM-11
>>> >> are used.
>> >
>> > Huh? If you are suggesting that they would be the same, I can assure
>> > you they could not.
>
> I would not assume anything until I actually had tested the presence or
> absence of a
> specific "feature".
What have any features have to do with this?
I'm telling you that RTEM-11 will not, and never have been capable of
running on a VAX.
If there was a RTEM product for the VAX, it would have to be a separate
product, with a separate code base from RTEM-11, since you cannot write
a RT-11 emulator of any kind in PDP-11 mode on a VAX. It will have to be
VAX code. And thus, it can not be the same product as a RT-11 emulator
program written to run under RSX.
>> > A very common misconception these days seems to be that VAXen with
>> > PDP-1 compatibility could run PDP-11 programs. That is only true in a
>> > very limited sense. Only the basic PDP-11 instruction set is supported
>> > by the VAX, and only the user mode stuff. EMTs, as well as any other
>> > kind of traps, interrupts, and so on, was *not* supported.
>> > When you execute an EMT in PDP-11 mode on a VAX, it will trap back to
>> > VAX mode. No possibility to have a PDP-11 trap handler.
>
> The absence of a PDP-11 trap handler under VMS compatibility mode on a VAX
> is definitely one possible situation. However, I suggest that it may
> also be possible
> for RTEM under VMS on a VAX to handle some of the SJ RT-11 EMT requests.
Definitely. But the code that catches the trap, and does something will
have to be VAX code, and not PDP-11 code.
You cannot write a trap handler in PDP-11 code on a VAX, no matter how
much of the PDP-11 compatibility that exist in the VAX hardware. The
PDP-11 compatibility mode simple does not extend to that stuff. Period.
>>> >> In addition, I also suspect that both Johnny and Ethan are correct in
>>> >> that RTEM
>>> >> was supported under both RSX and VMS on an older VAX which allowed
>>> >> compatibility mode.
>> >
>> > It would have to be totally separate products in that case.
>
> AGREED!!
Thank you. Now we can proceed.
>>> >> I don''t know if Megan Gentry is still around or perhaps Allison or
>>> >> one of the
>>> >> other DEC fellows. Perhaps they might at least know something about
>>> >> which
>>> >> hardware and operating system(s) supported RTEM?
>> >
>> > I definitely remember (and probably still have some mail somewhere)
>> > from Megan mentioning that she used RTEM-11 for RT-11 work, running on
>> > RSX machines. Possibly even an 11/74.
>
> I don't have enough information about RSX to know if RTEM-11 was supported.
> However, ...
I'm telling you that it is. Just google for it, and you will find the
documentation from DEC that is still on the net about this product. It's
actually really simple. Go to "www.google.com". Type in "rtem-11 rsx" in
the search field, and hit enter.
The first hit will be
http://www.google.se/url?sa=t&source=web&cd=1&ved=0CBcQFjAA&url=http%3A%2F%…,
which is "RSX-11M Optional Software Cross Reference Table", which lists
what version of various software is compatible with RSX-11M V4.0 and
V4.1. Among these, you'll find RTEM-11 V1.0 and V1.1. More "supported"
than that is hard to get.
>>> >> In addition, RSTS/E also supported RT-11 programs via the SWITCH RT11
>>> >> capability. However, only the RT-11 EMTs which are used by a SJ are
>>> >> supported
>>> >> by RSTS/E. At least there is quite reasonable documentation as well
>>> >> as the ability
>>> >> to test and actually run RT-11 programs under RSTS/E up to the latest
>>> >> versions
>>> >> of RSTS/E. RT-11 EMTs for mapped RT-11 monitors (RT11XM) are not
>>> >> supported
>>> >> not are multi-terminal EMTs. Also, probably the latest RT-11 EMTs
>>> >> for file status
>>> >> information are also not supported under RSTS/E.
>> >
>> > The correct technical term is that RSTS/E have a RT-11 *run time
>> > system*. An RTS in RSTS/E provides an environment under which you can
>> > get a specific behaviour. So you had RTSes for RT-11, RSX, BASIC+,
>> > TECO, DCL and some other stuff. Some RTSes were also KBMs (keyboard
>> > monitors), meaning you could "switch" to them, and get an interactive
>> > command line interpreter with that. But the RTS mostly implemented
>> > system calls. However, there were RTSes which didn't implement any
>> > system calls, and only gave you the basic calls RSTS/E itself
>> > provided, and mostly focused on being a KBM, such as DCL.
>
> I apologize for my lack of familiarity with the terminology. Your
> description
> is what I was attempting to say.
:-)
> Actually, my testing seems to show that RSTS/E supports being able to
> run RT-11 programs even if the RT-11 RTS is not activated. For example:
> RUN MACRO
> is possible if the RTS is normal RSTS/E or RT-11. This might be based
> on the
> file type. RSTS/E may determine that MACRO.SAV is an RT-11 program and
> support the RT-11 EMT requests. Or RSTS/E may support naked RT-11 EMT
> requests from any program. That is something I should test.
No, you are confusing things, and making wild guesses.
What do you mean by "activated"? There is no activation. If an RTS is
installed, it will always be used for programs that are marked as
requiring that RTS. This is an "attribute" of a file. Whenever that file
is run, it is run under the indicated RTS. If you try to run a program
that requires an RTS that don't exist I would suspect that you'll get an
error.
Also, if you type "RUN MACRO", how do you know that you are even running
the RT-11 version? RSTS/E normally also have an RSX RTS available, and
an MACRO.TSK, which is MACRO-11 running under the RSX RTS.
There is no RSTS/E RTS, by the way.
>> > All exeutable files have an RTS associated with it, and when the
>> > program is run, it is run under that RTS, which then handles all EMTs
>> > and so on when the program executes them.
>
> Does the file type trigger the use of that RTS?
Unless my memory have totally rotted away, the answer is no. The RTS
associated with a file is an attribute of the file, just like file
protection. There is a switch to PIP that you can use to check, and set,
the RTS.
That said, all RTS have a default file extension as well, and I think
that is used to search for runnable files if you just type "RUN MACRO"
for example.
> I do have a question. With V7 of RSTS/E, the FIT program is able to
> copy files from a drive with an RT-11 file structure (such as an RX02)
> to the RSTS/E file structure. My initial testing with V10.1 of RSTS/E
> shows that (at the very least the distribution which I am using) does not
> have a FIT program. Is there some other method of making a copy of
> a file on an RX02 with an RT-11 file structure to a device with a RSTS/E
> file structure?
Either FIT, or some "new" program that does the same thing, I'd guess.
I'm no expert on RSTS/E, and my experience is old. I mostly ran RSTS/E
between V7.1 and V9.0, with the majority of my time in the V7-V8 timeframe.
> Also, is it possible to run an RT-11 program under a DEBUG mode? It
> would be much easier to check out the code if that is possible. At the
> moment, I can check most of the code under RT-11. However, the
> portion which runs in a different manner under RSTS/E as opposed to
> RT-11 since RSTS/E does not support all RT-11 EMT requests in the
> same manner as RT-11.
What do you mean by "debug" mode???
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
> I ran across a DEC OBA11-VA (attached to a dual TU58 drive) while sorting
> my junk room. Anyone have a link to documentation or any information on it?
The BA11-VA was a small Q-bus enclosure with power supply.
Most often, in the "SB11' system, it enclosed an LSI-11/03 equipped with a MXV11 and sometimes extra serial lines like DLV11J and sometimes a GPIB card (IBV11?) or general purpose parallel I/O.
If yours had TU58's attached it was probably used like a small industrial/scientific controller or data logger or development system.
Sometimes they had custom applicatons burnt into the EPROM in the MXV11, other times they just used a regular bootloader and booted RT-11 from TU58 which than ran the application.
Look inside and see if you've got IBV11's or other I/O type cards.
Up through the 90's similar small desktop Q-bus chassis were sold by MTI and Andromeda for similar purposes (although by the 90's with more modern peripherals than the TU58!) I traveled with an Andromeda Q-bus system a lot in the 90's.
Tim.
--- On Wed, 7/14/10, Andrew Lynch <lynchaj at yahoo.com> wrote:
> I'll continue researching and hopefully something will turn
> up.? If any of
> our German/European colleagues have access to the PC Par
> 68000 article in
> "mc" from 1989 and would be willing to scan I would greatly
> appreciate it as
> it seems to be the most practical solution at the moment.
Weren't you the OP? I done said Radio Electronics had a series on building
a 68K box w/ISA slots. I perused the 1st installment this morning, and yep
it'll run an MDA card (CGA probably too), and stock floppy controllers, as
well as hard disk controllers. What more could you want! Keep in mind though
the original developer is on these lists somewhere, and wants big bucks for
the (more or less complete) kit. So you'll have to contact him if you want
to use his firmware. I don't have the entire set of installments, but
presumably (though don't quote me) the artwork was available right in the
magazine.
[AJL>]
Hi Chris,
Would you please tell me which Radio Electronics like year, month, had the
68K circuit. If the design is proprietary then it is probably not a usable
design. What you are describing sounds like a 68K motherboard in the PC or
AT format. My plan is to place the 68K SBC on an ISA board starting with an
ISA prototyping board. If you or someone else would please scan the article
it sounds very interesting whether it would be useful for my project or not.
I've found a good circuit with a complete schematic and description. It has
some firmware and appears complete. Also it is public domain hardware and
free (speech -- GPL) software so it is an ideal home brew project. It makes
sense to me to do a little research and select an established home brew 68K
project and use it as a base to extend to the ISA board rather than reinvent
the circuit entirely.
Thanks and have a nice day!
Andrew Lynch
On 7/19/10, Tony Duell <ard at p850ug1.demon.co.uk> wrote:
>> market for blank diskettes and cartridges. Reminds me of the DEC Rainbow
>> (wasn't that system deliberately crippled to prevent it from being able to
>>
>> format blank media?).
>
> Only (AFIAK) by DEC not supplying a formatter program with early versions
> of the OS. The hardware was quite capable of formatting blank disks.
In the case of the Rainbow, the hardware was capable of formatting
media, but ISTR some other DEC controllers didn't have bits left over
in a CSR or didn't have enough command packet varieties to include a
media format request or some other design limitation that was left out
for various reasons, not primarily to force users to buy pre-formatted
media, but since DEC had been selling pre-formatted media for years
(RX01, RX02, RL01, RL02, TU58...) (vs older devices that *could* be
user-formatted - RK05, DECtape, etc) it was believed at the time that
users wouldn't complain enough to make a more complicated (and
expensive) solution necessary.
I think for the most part, they were right - there might have been
some grumbling about the cost of media, but commercial customers were
used to paying for places to store their bits. Home users were
another market entirely, and I don't think that it went over as
smoothly when trying to sell expensive disks to that crowd.
I remember complaints from the later RX50 era that I don't remember
>from the RX01 era vis-a-vis buying pre-formatted media. The
difference lies, I think, more with the audience than the technology
on this one.
-ethan
"Jerome H. Fine" <jhfinedp3k at compsys.to> wrote:
> >Johnny Billquist wrote:
>
>>> > >Ethan Dicks <ethan.dicks at gmail.com> wrote:
>> >
>>>> >> >On 7/14/10, Jerome H. Fine <jhfinedp3k at compsys.to> wrote:
>>> >>
>>>> >>> In addition, does anyone know of any systems currently running
>>>> >>> which support RTEM-11 features which allow RT-11 programs
>>>> >>> to run in that environment? My assumption is that VMS on a VAX
>>>> >>> supported RTEM-11 at some point, but perhaps (if I am correct)
>>>> >>> the RTEM-11 support was not continued with
>>>> >>> more recent versions of VMS on the VAX and most definitely VMS on the
>>>> >>> Alpha. Can anyone comment on these questions?
>>> >>
>>> >> Based on the vague reference at
>>> >> http://s-and-b.net/help?key=RTEM~Release_notes&title=VMS Help&referer=
>>> >> and what I know of VMS and DEC hardware, I'd think that RTEM-11 would
>>> >> require a VAX processor with "compatibility mode", i.e., a "VAX-11"
>>> >> processor. The primary models would be the 11/78x, 11/750, 11/730 and
>>> >> 11/725 (I don't recall if the VAX 86xx still had "compatibility mode"
>>> >> or not, but it should be easy to check). MicroVAXen and such did not
>>> >> have it, and Alpha processors certainly did not have it.
>>> >>
>>> >> That being said, I have no experience with RTEM-11, but I would be
>>> >> surprised to learn it ran on a machine made after about 1986 or so.
>> >
>> > RTEM might be something else than RTEM-11, which was a software
>> > product for RSX. Just google for RTEM-11, and you'll find some
>> > references for it.
>> >
>> > However, I wonder about RTEM for VAX. It's certainly possible, but I
>> > can't find any other reference to it, and DEC's old SPDs, especially
>> > those with software version compatiblity matrixes, are usually pretty
>> > good as a way of finding out what software existed.
>> >
>> > As for PDP-11 compatibility in VAXen, yes, the 86x0 machines have
>> > that. Those were the last, however.
>> >
>> > For all other VAXen running VMS, if you wanted to run RSX software,
>> > you needed a PDP-11 emulator product for VMS, which was available, in
>> > addition to the RSX additions for VMS, which was also a separate
>> > product. That thing was supported up until fairly recently, though.
>> > But again, that's for RSX stuff...
>
> I suspect that the most likely possibility is that RTEM and RTEM-11 are
> used.
Huh? If you are suggesting that they would be the same, I can assure you
they could not.
A very common misconception these days seems to be that VAXen with PDP-1
compatibility could run PDP-11 programs. That is only true in a very
limited sense. Only the basic PDP-11 instruction set is supported by the
VAX, and only the user mode stuff. EMTs, as well as any other kind of
traps, interrupts, and so on, was *not* supported.
When you execute an EMT in PDP-11 mode on a VAX, it will trap back to
VAX mode. No possibility to have a PDP-11 trap handler.
> In addition, I also suspect that both Johnny and Ethan are correct in
> that RTEM
> was supported under both RSX and VMS on an older VAX which allowed
> compatibility mode.
It would have to be totally separate products in that case.
> I don''t know if Megan Gentry is still around or perhaps Allison or one
> of the
> other DEC fellows. Perhaps they might at least know something about which
> hardware and operating system(s) supported RTEM?
I definitely remember (and probably still have some mail somewhere) from
Megan mentioning that she used RTEM-11 for RT-11 work, running on RSX
machines. Possibly even an 11/74.
> In addition, RSTS/E also supported RT-11 programs via the SWITCH RT11
> capability. However, only the RT-11 EMTs which are used by a SJ are
> supported
> by RSTS/E. At least there is quite reasonable documentation as well as
> the ability
> to test and actually run RT-11 programs under RSTS/E up to the latest
> versions
> of RSTS/E. RT-11 EMTs for mapped RT-11 monitors (RT11XM) are not supported
> not are multi-terminal EMTs. Also, probably the latest RT-11 EMTs for
> file status
> information are also not supported under RSTS/E.
The correct technical term is that RSTS/E have a RT-11 *run time
system*. An RTS in RSTS/E provides an environment under which you can
get a specific behaviour. So you had RTSes for RT-11, RSX, BASIC+, TECO,
DCL and some other stuff. Some RTSes were also KBMs (keyboard monitors),
meaning you could "switch" to them, and get an interactive command line
interpreter with that. But the RTS mostly implemented system calls.
However, there were RTSes which didn't implement any system calls, and
only gave you the basic calls RSTS/E itself provided, and mostly focused
on being a KBM, such as DCL.
You can write you own RTS if you want to, and one think that have been
at the back of my mind is if it wouldn't be pretty easy to write a Unix
RTS for RSTS/E, so that you can run a bunch of Unix binaries under
RSTS/E as well.
All exeutable files have an RTS associated with it, and when the program
is run, it is run under that RTS, which then handles all EMTs and so on
when the program executes them.
> Probably in the same manner as RSTS/E, if RTEM is supported under VMS on an
> older VAX, the most likely only the RT-11 EMTs which are used by a SJ are
> supported.
Yes, RTEM-11 would most likely just provide a simple RT-11 environment,
such as SJ. As I said before, I can't really find any proper information
about any RT11 environment for VMS... But if it existed, it would
probably be just SJ as well.
Johnny
personally I love old monitors. This ones seems especially instersting being it has BNC jacks.
I'd stick it in the closet, or in the yard inside 2 or 3 very sturdy plastic bags. If Adrian gets his way, there won't be a single one left in the entire UK!
> From: Steven Hirsch <snhirsch at gmail.com>
> Subject: Amlyn Minipac diskette changer
>
> Has anyone else on the list seen one of these? I picked up a Vista V1200
> disk system for Apple 2 that uses this type of drive. The mechanism takes
> a plastic cartridge with five 5.25" floppy disks. The diskettes appear to
> be conventional SS format with a couple of extra punchouts to mate with
> the loader mechanism. Electrical interface is compatible with 8" floppy
> drives (interface card was also sold for that purpose).
>
> I'm not able to turn up any information about the drive and am wondering
> how the diskette select/load scheme is intended to work. There are
> at least a couple of possibilities:
>
> - Treat the physical diskettes as portions of a single logical floppy and
> select diskette by track range (first diskette 0-39, second 40-79, etc.)
>
> - Treat each physical diskette as a logical drive and use binary select
> lines on interface to choose.
>
> Anyone have documentation on the drive mechanism or the Vista product?
I had a very similar unit for the Apple 3. As I remember it looked like a single 6MB drive to the OS. I don't think that would have been possible on Apple 2. Earlier I had a 5MB ICE hard drive on an Apple 2 which looked like 35 floppy disks to DOS. It might have looked different under UCSD Pascal, maybe you could have a single large file, but its a long time ago, I just can't remember.
Hi,
I realize that this is a really long shot, but would you still happen to have the Quadlink setup? A friend of mine has been looking for one forever! Thanks,
Mark E.
I have created a YouTube account and uploaded a short video showing the
simulator running a small program:
http://www.youtube.com/watch?v=walWU2MQ2OM
Sorry about the lack of video quality, but I'm sure you'll get the idea.
If you want to know more, you can get the FETOM Y24-3360-1 from
Bitsavers (or a mirror!) There is a front-panel layout on p6-2 of this
manual, which may help in deciphering the panel lamps.
The program being run is The "Indian" Problem on p73 of the Introduction
to System/360 Assembler Language manual SC20-1646-6, also on Bitsavers.
It is loaded at address 100.
I am in the process of readying the VHDL files for release - tidying up
and adding GPL headers at the moment. They should be available within
the next week or two.
--
Lawrence Wilkinson lawrence at ljw.me.uk
The IBM 360/30 page http://www.ljw.me.uk/ibm360
I am now the proud owner of a Nimbus motherboard.
Anyone w/a technical manual? Does it use standard floppy drives? It seems to have onboard video ports, so I'm thankful for that at least.
I found some warez here:
http://www.theoldcomputer.com
I arrived at specific Nimbus files (about 5, including DOS 3.1 - will run on the N-186?) by googling (everything is categorized as a *rom*, it being the worlds biggest bloodiest rom site), so you might be better off using that back door.
So help me out guys. Need to get this bad boy operating.
a picture (or 2) might help Sharon :)
IIRC, the *8085* in the System 23/Datamaster wasn't identified as such. It had some sort of IBM house number. Haven't opened mine in a while, but that's what I remember.
Be specific about what you mean by p/s issues. And if that's the case, you're advised to test the voltages under load...but not the motherboard load/s.
Perhaps you have a repackaged Datamaster. Mine unfortunately is *unavailable* for perusal at this present time. I do believe there are other people on the list that have one, but they don't seem to participate these days. Mine is buried beneath about 12 other machines (was I supposed to put it on top? It weighs ~95 lbs yer know).
Can a C1541 or C1571 attached to a C64 read floppies from other
Commodore computers such as the VIC-20 or C16? Since the floppy
drive is basically a computer attached to the C64 by a serial cable,
I tend to think it can, but I don't believe I've ever seen anything
on this, and I know I've never tried. I've never had a floppy drive
attached to any of my VIC-20's, back when it was my only computer, I
only had a cassette drive.
Zane
--
| Zane H. Healy | UNIX Systems Administrator |
| healyzh at aracnet.com | OpenVMS Enthusiast |
| | Classic Computer Collector |
+----------------------------------+----------------------------+
| Empire of the Petal Throne and Traveller Role Playing, |
| PDP-10 Emulation and Zane's Computer Museum. |
| http://www.aracnet.com/~healyzh/ |
Thanks for the interesting replies. If anyone is interested in an N8VEM
68K project please contact me. Basically this would be a simple 68K system
for a simple bus like ECB, S-100, or ECB. Nothing fancy or complex just 2
layer boards, all DIP construction, common parts, nothing programmable other
than an EPROM. I am thinking just CPU, RAM, ROM, and a dual latch to
communicate with the main board CPU but am open to other ideas.
I'll continue researching and hopefully something will turn up. If any of
our German/European colleagues have access to the PC Par 68000 article in
"mc" from 1989 and would be willing to scan I would greatly appreciate it as
it seems to be the most practical solution at the moment.
Thanks and have a nice day!
Andrew Lynch
You probably need to know the SRM commands to turn on the Serial
port. You might take a look on Hoff's website. I ran my 434au via
the Serial port, same with the XP1000's. While I have VMS compatible
graphics cards, it is more convenient with how I use them.
Zane
At 1:18 PM +0100 7/17/10, Rob Jarratt wrote:
>I recently acquired a 433au and I want to access it through the serial port.
>I am not having much luck with this and wonder if there might be something
>odd about the serial port. I would also like to find a manual for the
>machine and my web searches have not turned up anything. Does anyone have a
>PDF of the 433au's manual?
>
>Thanks
>
>Rob
--
| Zane H. Healy | UNIX Systems Administrator |
| healyzh at aracnet.com | OpenVMS Enthusiast |
| | Photographer |
+----------------------------------+----------------------------+
| My flickr Photostream |
| http://www.flickr.com/photos/33848088 at N03/ |
On 17 July 2010 16:13, Rob Jarratt <robert.jarratt at ntlworld.com> wrote:
> I have a bulky Unisys EVG-500-COL 17" monitor that is taking up space. It
> has a 9-pin VGA connector and 5 BNC plugs on the back. It needs to warm up
> to work properly. I am not sure whether to keep it or just take it to the
> tip. What do people here think?
Personally, I disposed of about 2 dozen such screens to ComputerAid
last month. I suspect that any made before 2002, they just recycled.
:?(
--
Liam Proven ? Profile & links: http://www.google.com/profiles/lproven
Email: lproven at cix.co.uk ? GMail/GoogleTalk/Orkut: lproven at gmail.com
Tel: +44 20-8685-0498 ? Cell: +44 7939-087884 ? Fax: + 44 870-9151419
AIM/Yahoo/Skype: liamproven ? MSN: lproven at hotmail.com ? ICQ: 73187508
I have a bulky Unisys EVG-500-COL 17" monitor that is taking up space. It
has a 9-pin VGA connector and 5 BNC plugs on the back. It needs to warm up
to work properly. I am not sure whether to keep it or just take it to the
tip. What do people here think?
Regards
Rob
I recently acquired a 433au and I want to access it through the serial port.
I am not having much luck with this and wonder if there might be something
odd about the serial port. I would also like to find a manual for the
machine and my web searches have not turned up anything. Does anyone have a
PDF of the 433au's manual?
Thanks
Rob
I'm sitting in the Tesla room waiting for the IPv6 session to start. We'll see how much stamina I have on Sunday.
Jim
Evan Koblentz <evan at snarc.net> wrote:
>
>>> American Bombe: How the U.S. Shattered the Enigma Code (Sunday, 1pm, Lovelace Room)
>> I'm out in the midwest, so there's no chance of going to this - but I'd be curious to see the above. Any chance anyone is filming these things?
>
>I don't know. Go to www.thenexthope.org and inquire there.
>
>PS -- our MARCH booth will have some special guests -- Crunch is
>stopping by, and David Ahl might come, too.
Chris W Tucker jetrigger at gmail.com
never shipped two powerbooks (about $500 worth)
I'd complain on the LEM feedback list, but it doesn't work
and they won't accept any comments on the main mailing list
lemswap at googlegroups.com
On Tue, 22 Jun 2010 23:16:00 +0100
"Rob Jarratt" <robert.jarratt at ntlworld.com> wrote:
> The machine came without a keyboard or mouse and I think I need at
> least a keyboard to get it to boot.
If no keyboard is connected the machine defaults to serial console on
the first serial port. (IIRC this is the DB25 one.) 9600 8n1. Before
investing money in a keyboard and mouse you should check if the machine
lives at all via the serial console.
--
tsch??,
Jochen
Homepage: http://www.unixag-kl.fh-kl.de/~jkunz/
Hi all --
If anyone's going to HOPE in NYC this weekend (who isn't already on the
MARCH mailing list), here are some on-topic things to see and do:
MARCH will have a demo booth Saturday from approx. 10am - night.
And there are many on-topic lectures, including mine/Bill Degnan's:
Friday:
Get Lamp Screening and Discussion (Friday, 11pm, Tesla Room -- by
friend-o'-MARCH Jason Scott)
Introduction to the Chip Scene: Low Bit Music and Visuals (Friday, 11pm,
Lovelace Room -- same guys who played VCF East 6.0.)
Saturday:
T+40: The Three Greatest Hacks of Apollo (Saturday, 10am, Lovelace Room)
Vintage Computing -- Evan/Bill (Saturday, noon, Lovelace Room)
The Telephone Pioneers of America (Saturday, 8pm, Bell Room)
2600 Meetings: Yesterday, Today, and Tomorrow (Saturday, 10pm, Lovelace
Room)
Sunday:
Cats and Mice: The Phone Company, the FBI, and the Phone Phreaks
(Sunday, noon, Tesla Room)
Simpsons Already Did It - Where Do You Think the Name "Trojan" Came From
Anyway? (Sunday, noon, Lovelace Room)
American Bombe: How the U.S. Shattered the Enigma Code (Sunday, 1pm,
Lovelace Room)
Ethan Dicks <ethan.dicks at gmail.com> wrote:
> On 7/14/10, Jerome H. Fine <jhfinedp3k at compsys.to> wrote:
>> In addition, does anyone know of any systems currently running
>> which support RTEM-11 features which allow RT-11 programs
>> to run in that environment? My assumption is that VMS on a VAX
>> supported RTEM-11 at some point, but perhaps (if I am correct)
>> the RTEM-11 support was not continued with
>> more recent versions of VMS on the VAX and most definitely VMS on the
>> Alpha. Can anyone comment on these questions?
>
> Based on the vague reference at
> http://s-and-b.net/help?key=RTEM~Release_notes&title=VMS Help&referer=
> and what I know of VMS and DEC hardware, I'd think that RTEM-11 would
> require a VAX processor with "compatibility mode", i.e., a "VAX-11"
> processor. The primary models would be the 11/78x, 11/750, 11/730 and
> 11/725 (I don't recall if the VAX 86xx still had "compatibility mode"
> or not, but it should be easy to check). MicroVAXen and such did not
> have it, and Alpha processors certainly did not have it.
>
> That being said, I have no experience with RTEM-11, but I would be
> surprised to learn it ran on a machine made after about 1986 or so.
RTEM might be something else than RTEM-11, which was a software product
for RSX. Just google for RTEM-11, and you'll find some references for it.
However, I wonder about RTEM for VAX. It's certainly possible, but I
can't find any other reference to it, and DEC's old SPDs, especially
those with software version compatiblity matrixes, are usually pretty
good as a way of finding out what software existed.
As for PDP-11 compatibility in VAXen, yes, the 86x0 machines have that.
Those were the last, however.
For all other VAXen running VMS, if you wanted to run RSX software, you
needed a PDP-11 emulator product for VMS, which was available, in
addition to the RSX additions for VMS, which was also a separate
product. That thing was supported up until fairly recently, though.
But again, that's for RSX stuff...
Johnny
> Were there any ISA boards released with the Motorola 88000-series CPU
on them?
But of course! Opus Systems, like Definicon, put a couple of different
CPUs on full-length ISA cards that would be added to or bundled with PCs
to create a lower cost workstation in the latter half of the 80s. Opus
delivered products using the Nat Semi 32000 family, later developed the
Personal Mainframe Series 8000 using an 88k chipset, and eventually did
it again with SPARC. We had one of these 88k boards in a Compaq DeskPro
on a researcher's desk in 1991 and he was quite pleased with it.
If one of these 32k or 88k systems/boards should need a new home, feel
free to give me a shout. ;^)
/Los links!!/ - All of the following shortened links go to Google Books.
Initial announcement in InfoWorld, February 1989:
http://tinyurl.com/opus8000
A few more details, October 1989: http://tinyurl.com/opus8000-2
Opus' 32332-based Series 200 announcement: http://tinyurl.com/opus200
--S.
Hello. I sent this request initially to PDP8-Lovers list, but I send the
same request here in the confidence of some help.
I am cleaning one PDP8E box with some boards inside. Previously to do some
cleaning of the internal boards, I tried to fire up the computer yesterday.
In appeareance nothing is wrong no strange smells, no burns, no clouds, no
boom!, etc...)
But... I don't have the front key :-)
One ACE xx2247 is needed. I don't have one available, and is impossible for
me to get one in my country (Spain).
I would be grateful is someone could provide me one, or even a couple.
Contact me off list if you want to discuss details.
Regards
Sergio
"Jerome H. Fine" <jhfinedp3k at compsys.to> wrote:
> I have fixed some of the bugs in a program which runs under RT-11
> (obviously using the
> PDP-11 instruction set - since actual DEC PDP-11 hardware can be
> replaced by either
> other compatible hardware on an emulator such as SIMH or E11).
>
> The bugs were causing problems when the program was run under VBGEXE,
> especially
> when the program was run as a system job.
>
> The requirements for the changes and additions to the RT-11 code have
> been determined.
>
> However, the same program is expected to run under RSTS/E (using SWITCH
> RT11),
> TSX-Plus (which is fully compatible) and RTEM-11. It is this last
> expectation for which I
> have been unable to find any documentation, let alone any ability to
> test the program. Does
> anyone who is reading this know where there might be documentation
> available concerning
> how RTEM-11 handles RT-11 EMT requests? In addition, does anyone know
> of any
> systems currently running which support RTEM-11 features which allow
> RT-11 programs
> to run in that environment? My assumption is that VMS on a VAX
> supported RTEM-11
> at some point, but perhaps (if I am correct) the RTEM-11 support was not
> continued with
> more recent versions of VMS on the VAX and most definitely VMS on the
> Alpha. Can
> anyone comment on these questions?
As far as I know, RTEM-11 will not run under VMS.
It was a product for RSX-11M (only). Long since retired now, and I don't
have any details on it. However, I seem to remember that when you do an
-11M SYSGEN, you still get a question for some RTEM-11 support to be
included in the system.
As expected, it will trap RT11 EMTs, but exactly what it will do for
specific EMTs, and in which cases it might differ from RT11, I have no
idea. It's probably also not compatible with any "recent" changes to
RT11, just so that you know...
Johnny
I have fixed some of the bugs in a program which runs under RT-11
(obviously using the
PDP-11 instruction set - since actual DEC PDP-11 hardware can be
replaced by either
other compatible hardware on an emulator such as SIMH or E11).
The bugs were causing problems when the program was run under VBGEXE,
especially
when the program was run as a system job.
The requirements for the changes and additions to the RT-11 code have
been determined.
However, the same program is expected to run under RSTS/E (using SWITCH
RT11),
TSX-Plus (which is fully compatible) and RTEM-11. It is this last
expectation for which I
have been unable to find any documentation, let alone any ability to
test the program. Does
anyone who is reading this know where there might be documentation
available concerning
how RTEM-11 handles RT-11 EMT requests? In addition, does anyone know
of any
systems currently running which support RTEM-11 features which allow
RT-11 programs
to run in that environment? My assumption is that VMS on a VAX
supported RTEM-11
at some point, but perhaps (if I am correct) the RTEM-11 support was not
continued with
more recent versions of VMS on the VAX and most definitely VMS on the
Alpha. Can
anyone comment on these questions?
Jerome Fine
Hi,
I've started playing around with this old XT/AT compatible machine I've
had for a while, called the Microbyte PC-230. It's designed locally in
South Australia. My question regards the OS installation.
A thoughtful person has uploaded the installation disks to
driverguide.com but they're not images, but ZIP files of the contents of
the install disks. It seems the install program checks the disk label or
something similar to see if the correct disk is in the drive. I don't
know the disk label or anything else about the original disks so I can't
install the OS on the hard drive. The original hard drive is a 20MB
Miniscribe which has developed bad sectors, so I've installed a 511MB
DEC badged hard drive. The system has the odd feature of having on-board
SCSI. It's an 8086 (NEC V30).
I've had a poke through (or peek as it were) the INSTALL.EXE file on
disk 1. There are a heap of null-terminated strings towards the end of
it. Just after the message which says to insert disk 1 it has the string
"\MBSCO1". I can only assume this is the disk label, but setting the
disk for that doesn't let the program continue. Even setting the disk
with a backslash in Linux doesn't help. After the second insert disk
message there's a "\MBSCO2" string too. Perhaps I'm missing something.
Any thoughts?
Alexis.
I believe that the project you are interested in is the one done by Ingo Cyliax at Indiana University. He developed (for a class I believe) an ISA form factor board that had a MC68030. At one time I had all the artwork & schematics (I may still??). A search brought up a couple of references, but the page at Indiana University seems to have been taken down. It was a pretty good system, including interfaces for keyboards and mice (I believe). It DID have ISA slots, and the ROM software worked against a standard IDE/Serial/Parallel board set, booting the disk. The memory was fixed at 4 megs (I may be wrong at this), and used the synchronous interface of the MC68030. The ISA portion used the async interface for the ISA timing, and an interrupt multiplexer multi interface chip (MC68901??) to handle the keyboard I/O.
The web site also included a frame buffer that used an alternate interface that was provided for. I believe that there was an edition of Minix that ran on it as well. I suspect that with a little work 68k Linux ought to work, as the MC68030 has an MMU.
Maybe someone can use this information to access the Wayback machine and get a proper pointer.
Hope this helps.
> Date: Tue, 13 Jul 2010 01:30:35 -0600
> From: Ben <bfranchuk at jetnet.ab.ca>
> The MMU bit reminded about DACK GROUNDED. I think that was the news
> letter I saw on the web. Guess what ! All about hooking a 68000 to
> a apple II for numeric processing.
> The news letter may be easier to find than a 68020.
The Mac LC used a 68020. I'm not sure whether it was socketed or soldered
though. The LC was more or less free not too many years ago. I'm not
sure what availability is like now.
Really, it's a kindness to take the 68020 out of an LC. The LC only had
a 16 bit wide data bus. Just senseless.
Jeff Walther
Hi! Just out of curiosity does anyone know of any home brew ISA bus 68K
boards?
I've seen numerous home brew 68K projects of varying styles but none meant
to plug into the PC/AT ISA bus. I tried Google but nothing obvious turned
up. Ideas/URLs appreciated.
Thanks and have a nice day!
Andrew Lynch
PS, something like this but with more detail
http://john.ccac.rwth-aachen.de:8000/as/pcpar.html
I have a couple of boards, clearly DEC, with numbers X020 and X030.
They are both hex height - pretty standard, with the cast metal
bracket holding the board ejectors. The X020 board is marked DATA PATH
and the X030 board is marked CDC DISK CONTROL. Are these for the DEC
badged CDC 97xx drives?
--
Will
For those who follow my Mosaic-CK project, version 2.7ck9 is out, which
improves the basic NCSA Mosaic rendering core with improved horizontal
positioning, makes image loads asynchronous, adds a Dock icon and better
integration with Mac OS X, and fixes a lot of bugs.
For those who don't, it's my little playground and historical preservation
of NCSA Mosaic, updated to build and run on modern operating systems, with
both an alternative renderer to actually be vaguely useful as a basic
browser and the classic renderer to show people just how far we've come.
Binary available for Mac OS X 10.4+. Should build on just about anything
with gcc 2 or better and X11R5 or higher. I'm slowly working on getting my
Solbourne S3000 back in shape so I can build binaries on that too (they
would likely be generically SPARC compatible, but this probably builds on
SunOS already anyway).
http://www.floodgap.com/retrotech/machten/mosaic/
--
------------------------------------ personal: http://www.cameronkaiser.com/ --
Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckaiser at floodgap.com
-- He is rising from affluence to poverty. -- Mark Twain ----------------------
> -----Original Message-----
> From: Andrew Lynch [mailto:lynchaj at yahoo.com]
> Sent: Saturday, July 10, 2010 5:49 PM
> To: 'cctalk at classiccmp.org'
> Subject: 68K ISA project
>
> Hi! Just out of curiosity does anyone know of any home brew ISA bus 68K
> boards?
>
> I've seen numerous home brew 68K projects of varying styles but none meant
> to plug into the PC/AT ISA bus. I tried Google but nothing obvious turned
> up. Ideas/URLs appreciated.
>
> Thanks and have a nice day!
>
> Andrew Lynch
>
> PS, something like this but with more detail
>
> http://john.ccac.rwth-aachen.de:8000/as/pcpar.html
[AJL>]
Hi! Thanks for the replies. Please let me further clarify what I am
looking for. As part of the N8VEM project I do research into what sorts of
designs are possible and practical for home brew constructions. Part of
that is researching what sort of home brew/hobbyist designs have gone before
to see what has been done and how it was designed and constructed.
Commercial solutions are available however they are typically proprietary
and lack the important schematics and/or other design information I need.
I am not aware of any 68K home brew projects for the ISA bus with the
exception of the PCPAR68000 mentioned in the 1989 mc article. Would anyone
have access to that article or other similar 68K ISA bus projects?
Similarly home brew S-100 68K type projects would also work although not the
commercial CompuPro or Cromemco 68K boards.
Thanks and have a nice day!
Andrew Lynch
sorry to post offtopic, but I know we have a few apple users here, and I
was hoping for some insigts into taking an powermac g5 2,7ghz dual
apart, I brough it home last week along with an g4 quicksilver 2002. So
we still a few years to go for them.
The powermac g5 is running very hot on the memory controler heatsink u3,
but it seem that part is actual placed on the backside of the mainboard,
and cooled by a heatpipe that connects to the aluminium case, but as its
running at 65 to 76 degree celsius, I am a bit worried.
Regards Jacob Dahl Pind
Hi,
what exactly is a Mohawk Data Sciences (MDS) Series 21? There's almost
nothing on the net about that system apart from one small article in the
July 1978 issue of Computer. Is it worth saving?
Christian
I'm pondering making two types of P112 kits . First there is the complete
kit and then there would be a partial kit. The partial kit contains the
board, surface-mounts already mounted, and memory chips with boot rom
already burned in. How many of you would be interested in a partial kit
rather than a complete kit? I'm not sure of the prices yet.
--
David Griffith
dgriffi at cs.csubak.edu
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
On 7/2/2010 01:00 PM, cctech-request at classiccmp.org wrote:
>Date: Fri, 02 Jul 2010 11:08:37 +0200
>From: Johnny Billquist <bqt at softjar.se>
>Subject: Re: yet another pdp-11 in fgpa
>To: cctalk at classiccmp.org
>Message-ID: <4C2DAC95.1020900 at softjar.se>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>allison <ajp166 at verizon.net> wrote:
>
> > On 06/30/2010 11:27 AM, Johnny Billquist wrote:
> >> > I'll reply to this one last time, and then I'll give up.
>
>(I can't seem to keep out, can I? :-) )
>
> > I can't add too much to this regarding what parts and what DEC
> > designators applied
> > but here are memories of the time frame.
> >
> > The first multiprocessor 11/70 was built with existing hardware and a few
> > wire wrap and jumper mods. Memory said there were 4 total, three
> inside DEC
> > and one at CMU that they hacked together possibly with DEC help.
>
>CMU did multiprocessor PDP-11s before DEC did, I think. However, they
>went about it differently than the 11/74 (or whatever you want to call
>it). Search for C.MMP and similar stuff on the net for more information
>about CMUs multiprocessor PDP-11 projects.
>
>The 11/74 systems were designed and built inhouse, although they might
>have talked with CMU to get help, experience and whatnot. Reportedly
>more than three systems were built. Rumors have it that they even had
>some systems out to external customers for test, but all systems were
>returned at the end of the tests (even though there is a persistent
>rumor about Ontario Hydro keeping their).
>
>I think I know of/heard of three systems that were in use inside DEC
>long after the system was officially cancelled. We had, of course,
>CASTOR:: which was the RSX engineering system, and which was up and
>running as late as 2002 (2005?) or so. This was a 4-CPU system.
>Then we had POLLUX::, which I think was a 2-CPU system. Not sure, but I
>think it might have been DECnet engineering who had it. The third I've
>heard about is PHEANX:: which might have been POLLUX:: after a move to
>field service, and possibly also using bits and pieces from other
>places inside DEC.
>
>As far as I know, all of these systems, as well as the ones gone out on
>field test, were KB11-CM cpus. So, no CIS option ever made it out of
>prototypes, nor any KB11-E.
>
>The boards from the 11/74 systems that were returned were allegedly used
>in plain 11/70 machines inside DEC afterwards. They were, after all,
>plug compatible with the normal 11/70 systems. The KB11-E boards would
>not have been that, though.
>....<snip>
I've been amused by the directions that this thread has taken over time...
My memory of the specifics of models and features is weak, as I had
moved on from DECnet-RSX to DECnet-DOS.
This website has a slightly different cut:
http://www.village.org/pdp11/faq.pages/never11s.html
What I seem to remember was that CASTOR:: and POLLUX:: were the names
when they ran
those systems as dual CPUs in ZK. And they put the two together when
they wanted to run the quad.
But that could have changed over time. We were free to move node names around.
The picture on http://www.miim.com/faq/hardware/multipro.html#castor
is definitely of Brian McCarthy, a senior member of the RSX
development group and that looks like the lab I've seen (only once
that I remember)
When DECnet-RSX development was in LKG (earlier TWO) circa 1980-early
90s, ELROND:: was our dual 11/74.
When the multiprocessor project was dropped, we continued to run our
dual as the primary development timeshare.
Otherwise FS would just downgrade the system into something they
would maintain like an 11/70.
I do remember those ugly no switch panels that Field Circus installed
on all our high end systems
do they could do remote diagnostics.
Ohhh, Google finds that Bitsavers has EK-70MP-TM, PDP-11/70
Multiprocessor Manual (Preliminary)
http://www.bitsavers.org/pdf/dec/pdp11/1174/EK-70MP-TM_PRE_1170mp_Prelim_Te…
Dave.
> Date: Mon, 5 Jul 2010 21:29:29 +0100 (BST)
> From: ard at p850ug1.demon.co.uk (Tony Duell)
> Subject: Re: Conecting new printer to a 286
> To: cctalk at classiccmp.org
> Message-ID: <m1OVsIF-000J48C at p850ug1>
> Content-Type: text/plain
>
>>
>> On 5 Jul 2010 at 7:59, Glen Slick wrote:
>>
>> > Yes, you are confused. Tony's problem statement to which I replied
>> > was capturing print data from a vintage PC to a USB capable host PC,
>> > not printing from a vintage PC directly to a USB printer device.
>>
>> Well, to be sure, you can get DIP packages like the Elexol USBMOD4
>> parallel-to-USB transfer module that would entail little more than
>> wiring up a cable.
>>
>> But there are so many scrapped PCs available with USB and
>
> As I have said many times, that depeends on where you are...
>
>> (bidirectional) parallel ports, what would be the point of building
>> anything?
>
> You;ve not seen my workbench ;-). I doubt I could find space for a PC +
> monitor+keybaord alongide any classic machbine I was working on.
>
> Quite apart from the fact that the simpler something is, there less there
> is to go wrong....
>
> -tony
> ------------------------------
Seems to me all you'd need is a stock off-the-shelf Parallel>Serial
converter feeding into a Serial<>USB converter, no?
I use that setup for various things; PrtScn capturing PC BIOS setup screens
for reference, debugging by judiciously inserting LPRINTs of key variables
to save or display on a second screen, etc., and even for printing to serial
printers from a parallel port... ;-)
m
> Date: Tue, 6 Jul 2010 13:52:34 -0700 (PDT)
> From: Fred Cisin <cisin at xenosoft.com>
> Subject: Re: Conecting new printer to a 286
>
> On Tue, 6 Jul 2010, MikeS wrote:
>> Seems to me all you'd need is a stock off-the-shelf Parallel>Serial
>> converter feeding into a Serial<>USB converter, no?
>
> AND another PC.
>
> That will work fine for transferring files from a non-USB computer to a
> USB computer. Although many of the off-the-shelf Parallel>Serial
> converters make assumptions about the computer's parallel port and are not
> always reconfigurable for all.
>
> The original post was about how to connect a 286 computer to a "modern
> printer".
> The 286 machine does not have a USB port.
> Off the shelf Serial<>USB converters will NOT work unless they are
> connected to a computer with USB. They will NOT work connected to a USB
> printer without a computer that has USB.
> kk
>
>
> ------------------------------
Umm, yes, that's all quite obvious but I was commenting on Tony's
suggestion below; considering that most inexpensive "modern printers" can no
longer print ASCII, this is probably the way you'd have to go anyway:
[QUOTE]
> Um, I'm confused. The FT245R is a slave device. Would it not
> require a host controller to interface to a USB printer? The FT245
> ISTR always looks like a communications device.
It would, if you wanted to connect it straight to the printer. My idea
was a device to let you get the data off the classic machine onto a
modern PC, and then format/print it from there. In which case a slave USB
device is what is needed.
-tony
[/QUOTE]
m
Hi,
I have three Fujitsu SMD disk drives that came from a Nixdorf machine and
I'm looking for a way to read the data (sector based would be good
enough). Recently I got hold of a Multibus SMD controller with a Nixdorf
label and I hope this will lead me to some conclusions about the low-level
format. It's an Interphase SMD 2190 (not a 2180) which is built around an
i8085. As I understand it the format differs from controller to
controller, is that right? Of course it would be much easier if I could
just hook up the drives to a Xylogics 7053 or 451 on a VME based SUN
machine...
So the big question is, has anyone a manual of or information on the
Interphase 2190? Would it be feasible to put the controller into an Intel
MDS800 (I know, but it's the only "real" Multibus machine we have
here...) ?
Christian
Thinning out the collection a bit pending a move. If anyone has any
interest in the High Level Hardware Orion 1/10 computers (Clipper
CPU, NetBSD) I have several of these systems collected over
many years, and really only need to keep a couple (one to use,
one as a backup).
If anyone has any interest in these machines, send me an email
of list. Based in the UK. Collection only on these items sorry,
they are bulky and heavy.
I'd just check eBay for an old HP Deskjet for under $35 or if Letter Quality isn't important, there are lots of old Dot Matrix printers there too.
I keep an old IBM Graphics Printer (Epson MX-80), HP Deskjet 500 and an HP LJ IIIP around for printing off classic computers like my TRS-80, Atari, Amiga and other systems.
Al
Does anyone have a working (hopefully, I know it's asking a lot) Apple
2C power supply? I can build one up if I weren't lazy, but I really
would just like to get it going with a regular supply. Also will try to
hook up and bootstrap over a copy of apple dos, assuming the ADT Pro
will bootstrap me.
The Apple 2e now has a super serial card waiting, so that project will
proceed when the paying work clears later this week. I will have to
find my serial kit and organize it a bit, but that will be a good exercise.
Again, I don't know looking over the thread if I asked, if anyone could
also spare or point at a cpm card for the 2e? I am a bit ahead of
myself in asking for that, but I do have a number of boxes of CP/M disks
in the pile with the ones I got with that system.
I wish I weren't working on paying work over the 4th, but you work when
those who pay want you to.
Jim
> There's no standard on-disk format for SMD drives, unfortunately.
Within the DEC-compatible SMD world, many controllers (especially the Massbus-emulating)
offered lowest-common-denominator compatibility with DEC RM03/RM05/RP05 packs
in CDC 9762/CDC 9766/Memorex 677-51 drives.
There are some delicate hooks between the software device drivers, Massbus registers, and the low level format that made it desirable to keep this lowest-common-denominator there even for SMD drives that had geometries nothing like the 9762/9766/677-51.
But in the Sun/VME world I know of no such lowest-common-denominator standard.
Tim.