test-drb November 2007

test-drb@ccmp.vtda.org

229 participants
508 discussions

MIT provides MULTICS source and documentation (DPS-8 simulation)

by aek＠bitsavers.org

> The I/O > on a full blown system is where a modern system might have emulation > problems This is exactly where simulation has been hung up for years. The mass storage and terminal system is complex, with microcoded controllers for tape and disk and dedicated front end processors for terminal/network I/O. KL10 simulation is a cakewalk compared to this (and the KL10 was no small feat of programming). I've dug up some additional information Olin Siebert didn't have, but there is still a lot of internal Honeywell HW/SW documentation on the I/O that hasn't been found. This whole issue has been bounced around on the Multics mailing list and alt.os.multics for years.

18 years

*updating* 8088's

by ajp166＠bellatlantic.net

> >Subject: Re: *updating* 8088's > From: Sridhar Ayengar <ploopster at gmail.com> > Date: Thu, 22 Nov 2007 14:28:30 -0500 > To: General Discussion: On-Topic and Off-Topic Posts <cctalk at classiccmp.org> > >Allison wrote: >>> Subject: Re: *updating* 8088's >>> From: "Chuck Guzis" <cclist at sydex.com> >>> Date: Tue, 20 Nov 2007 16:38:01 -0800 >>> To: "General Discussion: On-Topic and Off-Topic Posts" <cctalk at classiccmp.org> >>> >>> On 20 Nov 2007 at 16:27, Fred Cisin wrote: >>> >>>> Wasn't the PS/2 30 an 8086? (can't remember for sure) >>> Initially. A later version used the 286. The model 25 was, as far >>> as I'm aware, always an 8086. >> >> The model25 was 8088 powered and I think a few others of that series. > >Definitely not. 8086 or better. None ran an 8088. The one I have has an 8088, model 8530-002. Well actually I pulled the board out to use the case for an SB180 with Adaptec SCSI/MFM adpator, a Miniscribe 20mb disk plus reusing the 3,5" disk and power. Made a nice case for that. Been stripping the PCs board since. Must of had a strange one. ;) > >Peace... Sridhar

18 years

*updating* 8088's

by ajp166＠bellatlantic.net

> >Subject: Re: *updating* 8088's > From: Sridhar Ayengar <ploopster at gmail.com> > Date: Fri, 23 Nov 2007 04:02:14 -0500 > To: General Discussion: On-Topic and Off-Topic Posts <cctalk at classiccmp.org> > >Allison wrote: >>>>>> Wasn't the PS/2 30 an 8086? (can't remember for sure) >>>>> Initially. A later version used the 286. The model 25 was, as far >>>>> as I'm aware, always an 8086. >>>> The model25 was 8088 powered and I think a few others of that series. >>> Definitely not. 8086 or better. None ran an 8088. >> >> The one I have has an 8088, model 8530-002. Well actually I pulled >> the board out to use the case for an SB180 with Adaptec SCSI/MFM >> adpator, a Miniscribe 20mb disk plus reusing the 3,5" disk and >> power. Made a nice case for that. Been stripping the PCs board >> since. > >I've never owned a -002, but I have a -021 in the pile somewhere that >definitely has an 8086. The IBM Internal sales spec sheet I have here >shows the -002 having an 8MHz 8086. > >> Must of had a strange one. ;) > >If it was an 8088, you did indeed. 8-) No question on that. One of the few parts not stripped, have way to many of them and they are mostly useless to me. The 8087 however I did save. Allison >Peace... Sridhar

18 years

Documentation for the AT&T Sceptre Videotex terminal

by classiccmp＠memory-alpha.org.uk

Hi, >....remap "Caps Lock" to be "CTRL" on my Model M's (along >with swapping ~ and ESC). Those are two of the things I detest the most about "modern" AT-style keyboards. "ESC" should be top left and "Ctrl" should be immediately below the "TAB" key. Oh, and most importantly, "Return" *SHOULD* be "J" shaped (or at least horizontal) rather than these annoying vertical ones we're subjected to nowadays....I'm forever hitting "#" by mistake, even to this day. Other than that they're OK; though I'd rather have the function keys down the left hand side of the keyboard where they belong! :-) >....If you use a keyboard long enough, you'll actually get used to >its key placement just fine, no matter how annoying it is at first, >I guess. With the sole exception of the "Return" key, I agree with you 100%. TTFN - Pete.

18 years

FD400 drive troubleshooting

by rcini＠optonline.net

All: As you all know from previous posts, I?m having trouble with the drive system on my IMSAI. While I wait to receive a memory board and some other stuff from a friend of mine, Herb Johnson gave me some new energy in looking at the existing iCOM Frugal Floppy system. This system uses Pertec FD400 drives. One works perfectly, the other one has consistent CRC errors as evidenced by the CRC light on the drive cabinet, and BDOS errors reported by CP/M. I ensured that the spindle is engaging the diskette hub, and I also cleaned the heads using a wet cleaning diskette. Is there any common failure mode on this model of drive that I should start tracking down? I looked over the maintenance procedures for the drive and many if the tests allude to a diagnostics program that can manually control the spindle and head stepping. None of the iCOM manuals I have provide diagnostics code for manually controlling the drives in this manner. Before I start coding, does anyone have diagnostics code I can use? I found some code in the SIGM archive (for the iCOM 3712 controller) but it doesn?t seem to work properly with this controller. Thanks. Rich -- Rich Cini Collector of Classic Computers Build Master and lead engineer, Altair32 Emulator http://www.altair32.com http://highgate.comm.sfu.ca/~rcini/classiccmp

18 years

FD400 drive troubleshooting

by ajp166＠bellatlantic.net

> >Subject: FD400 drive troubleshooting > From: "Richard A. Cini" <rcini at optonline.net> > Date: Wed, 21 Nov 2007 19:54:46 -0500 > To: "Discussion: On-Topic and Off-Topic Posts" <cctalk at classiccmp.org> > >All: > > As you all know from previous posts, I?m having trouble with the drive >system on my IMSAI. While I wait to receive a memory board and some other >stuff from a friend of mine, Herb Johnson gave me some new energy in looking >at the existing iCOM Frugal Floppy system. > > This system uses Pertec FD400 drives. One works perfectly, the other one >has consistent CRC errors as evidenced by the CRC light on the drive >cabinet, and BDOS errors reported by CP/M. I ensured that the spindle is >engaging the diskette hub, and I also cleaned the heads using a wet cleaning >diskette. Get in there and scrub the head with a swab. I found the wet disks didn't cut it long ago. Make sure the spindle speed is good and not irregular. Try swapping drives A and B and se if the problem moves with the drive or not. Just to make sure you not having a issues with something else. > > Is there any common failure mode on this model of drive that I should >start tracking down? Everyone I'd seen either had fallen apart mechanically (broken hubs, doors or other plastic) or the drive motor had gone noisy or mechanically flakey. NOTE: those motors often had bronze (oilite) bearings that dried out and then became oval or other wise out of useful shape. It was a side effect of lot of hours and the belts side tension. Result is the motor speed is uneven. I've seen bad boards too, usually tossed the board and salvaged from another mechanical pig. > I looked over the maintenance procedures for the drive >and many if the tests allude to a diagnostics program that can manually >control the spindle and head stepping. None of the iCOM manuals I have >provide diagnostics code for manually controlling the drives in this manner.. There maybe diags but your on you own to find them. > Before I start coding, does anyone have diagnostics code I can use? I >found some code in the SIGM archive (for the iCOM 3712 controller) but it >doesn?t seem to work properly with this controller. What controller (CHIP on the FDC board)? Allison > Thanks. > >Rich > >-- >Rich Cini >Collector of Classic Computers >Build Master and lead engineer, Altair32 Emulator >http://www.altair32.com >http://highgate.comm.sfu.ca/~rcini/classiccmp

18 years

Documentation for the AT&T Sceptre Videotex terminal

by classiccmp＠memory-alpha.org.uk

Hi, > So, uhm, am I the only person here that actually quite *liked* >the ZX81 keyboard? I never actually *liked* it, though I didn't especially dislike it either. And it was certainly streets ahead of the Spectrum's keyboard; *THAT* is one of my all time most hated keyboards....makes my flesh creep just thinking about it....uuuurghhh....<shudder>. TTFN - Pete.

18 years

*updating* 8088's

by ajp166＠bellatlantic.net

> >Subject: Re: *updating* 8088's > From: "Chuck Guzis" <cclist at sydex.com> > Date: Tue, 20 Nov 2007 17:01:14 -0800 > To: "General Discussion: On-Topic and Off-Topic Posts" <cctalk at classiccmp.org> > >On 21 Nov 2007 at 0:52, Ensor wrote: > >> I spent many happy hours running CP/M programs "under" MS-DOS on my V30 >> machine. >> >> Anyone remember the name of the program which facilitated this? > >Nope. Haven't a clue. 22nice and there were a few others. Allison > >Cheers, >Chuck

18 years

Access to IOPAGE Registers using PDP-11 Opearting Systems

by bqt＠softjar.se

ons 2007-11-21 klockan 12:00 -0600 skrev "John A. Dundas III" <dundas at caltech.edu>: > Jerome, > > I can speak for RSTS with some authority, RSX with somewhat less authority. > > At 9:17 PM -0500 11/20/07, Jerome H. Fine wrote: > >I doubt that RSX-11 or RSTS/E allow a user access to the IOPAGE > >even via PREVIOUS DATA space. Can anyone confirm this assumption? > > Address space in the I/O page for RSTS jobs (processes) was not > directly available. The APRs are always controlled by the OS. It > MIGHT be possible for a privileged job to use PEEK/POKE SYS calls to > access the I/O page in the way you suggest but it would be > particularly difficult. I thought RSTS/E had some way of remapping the address space as well. Can't you remap parts of your memory to some shared region, for example? > RSX had a bit more flexibility (opportunity) in this regard. I > believe you can set up a CRAW$ (create address window) directive in > either Macro or Fortran to achieve the desired result. Yes with reservation. CRAW$ (create address window) is as a part of doing dynamic remapping of your address space. However, CRAW$ always required a named memory partition. You cannot create an address window to an arbitrary memory address. Also, the memory partitions have protections and ownership associated with them. On most systems, CRAW$ cannot get you access to the I/O page, simply because normally you don't have an address space and a partition associated with the I/O page. But if such a partition is created, then CRAW$, in combination with MAP$ would allow you to access the I/O page. The same thing can also be achieved even without CRAW$/MAP$, since you can specify mapping that your task should have already at task build time, with the COMMON and RESCOM options to TKB. Johnny

18 years

Fwd: [alt.sys.pdp11] further collection reduction - TU80 availabl

by legalize＠xmission.com

This message has been forwarded from Usenet. To reply to the original author, use the email address from the forwarded message. Date: Thu, 22 Nov 2007 17:16:11 -0600 Groups: alt.sys.pdp11,comp.sys.dec,comp.os.vms,comp.sys.dec.micro From: "Lee K. Gleason" <lee.gleason at comcast.net> Subject: further collection reduction - TU80 available for free Id: <cL6dnat5DsemkNvanZ2dnUVZ_jWdnZ2d at comcast.com> ======== Free for pickup in Houston, Texas, near TC Jester and the North loop. This is a 9 track, reel to reel tape drive, it comes in a half height rack. It accepts tapes up to full size 2400 foot. Speed 25 IPS start/stop mode, 100 IPS streaming mode. Density is 1600 BPI. This TU80 was lightly used, and then stored in the back bedroom for the last 12 years or so. It was working when I stored it, don't have anything to test it with now. Here's your chance to own a piece of computing history! -- Lee K. Gleason N5ZMR Control-G Consutlants lee.gleason at comcast.net

18 years

← Newer
1
...
15
16
17
18
19
20
21
...
51
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

test-drb November 2007