up for sale is an Ethernet 10/100Mbps Card for Indigo2/MaxImpact
Brand New, Original, Never opened, Never Used!
Comes with manual and drivers, still enclosed within cellophane!
Phobos G160 are very rare nowadays
looking for 170 Euro + S/H
I can also give you a second hand (tested, working) SolidImpact GfX
for 30 euro, thus 200 Euro both, combined shipping to save your money
Located in Italy
(my parent's house)
Hi Who has experience with the TMS1000 in a lot of games. Want to dump
ram electronically (by 'test mode' ?) not decapping. Must be some new
software out there that can do this now, or am I daydreaming.
Thanks
Charles Harris
> it is not board-dependent - two different boards give incorrect read
> data for the same write values!! ... I wonder if the board is storing
> wrong values a _lot_, and the ECC is normally catching them?
Anyone have any idea what might be going on here?
I ask because I'm fixing to repair a broken MSV11-J for a list member, and the
combo of ECC and this might make it hard to track the problem down. (If only
one chip is dead, the ECC _should_ be able to 'paper over it'. So there are
probably two? But if I turn off ECC, to be able to find the bad chip, will I
get deceived by this other problem?)
Noel
> none of the other values used in that seemed to have a problem; but of
> course the program didn't include all 2^16 patterns. I suppose I should
> whip up a small program to try other values, and see if anything else
> does this...
And it does! Quite a few values come back wrong, when ECC is disabled - I'm going
to guess about 25% of the time. (Out of 0-020, 4 were wrong.)
And it is not board-dependent - two different boards give incorrect read data
for the same write values!! And the ones that were OK were OK on both. (And it
doesn't appear, from a bit of spot-testing, to be address-dependent.)
This is _very_ strange. There's nothing in the manual about 'disabling ECC
causes incorrect data to be returned' that I could see.
I wonder if the board is storing wrong values a _lot_, and the ECC is normally
catching them? (Maybe DEC did it this way to test the ECC hardware all the
time, and quickly catch failing ECC? But why doesn't the manual mention that?)
One thing I noticed is that while I was doing the 'which bit goes in which
chip' stuff, on some of the data lines, there was a lot of grup - some of it
fairly long pulses, and some spikes that looked like they might be hazard
outputs. I wonder if they are part of the cause?
I guess the next step is to set up a loop which stores one of the values which
always gives a bad output, and see what the board is actually writing into the
chip...
Very, very strange!
Noel
> I first have to tweak my 'scope loop program, to turn on memory mapping
So while doing that I just discovered what I _think_ (maybe I'm just not being
smart enough to see that it's somehow 'doing the right thing') is the wierdest
hardware bug I've ever seen.
Plug in an MSV11-J, disable ECC (store an '04' into the CSR), and then store
'0172344' into any location. Now read it back!
And it's not a bad RAM chip, which turning off the ECC is letting show
through, because I tried several boards, and they all do the exact same
thing. So either they've all got the same bad chip, or... :-)
I found this when my modified 'scope loop program (above) blew out, but none
of the other values used in that seemed to have a problem; but of course the
program didn't include all 2^16 patterns. I suppose I should whip up a small
program to try other values, and see if anything else does this...
Noel
> From: Glen Slick
> What signal were you probing on the M8186 KDF11-A board?
BDOUT; I'm triggering on that, and without any prints it wouldn't be easy to
find on the MSV11-J. Picking it up off the KDF11-A was the easy way to go.
> If you run the XXDP VMJAB0 diagnostic and there are failures, does it
> tell you which data bit and/or ECC bit positions have failures? I
> suppose it must, otherwise there wouldn't have been much point in the
> bit mapping exercise.
I dunno; I don't have it. There's also the built-in memory tester in the
bootstrap code in the EEPROM on the KDJ11-B, and according to EK-KDJ1B-UG-001
(pp. 4-24, -26) that prints the address and bad data when an error is
detected.
I have my own little memory diagnostic that I wrote which I tend to use (since
I know exactly what it's doing). I'll probably whip up a modified version to
check the ECC bits in the MSV11-J (in diagnostic mode, they can be
read/written).
The MSV11-J does have this feature where you can leave the ECC enabled on the
low 32KB (or optionally, the second 32KB) even when ECC is turned off for most
of the memory; that's so a diagnostic can live in that memory while testing
the rest. I think I'm probably going to ignore that, and plug in a small
memory card for the diagnostic to live in, since the MSV11-J can be set to
start at any 16KB boundary. That way I can test the entire MSV11-J without any
fancy dancing.
Noel
> From: Tor Arntsen
> So, here's how to see the updated page while not logged in:
Thanks for posting the 'fix'; the problem, and that workaround, are described
on the 'News' sidebar on the Main Page, but of course people going straight
to a URL won't see that - and since I'm always logged in, I often forget that
un-logged in visitors have this issue.
Maybe I should try and edit the CSS or something to include a note with
every page? (Any pointers on how to do that gratefully accepted! :-)
> Hopefully Tore S. or someone can figure out what's wrong with this
> Mediawiki version.
Alas, only Tore has the access needed to fix it (and the other current major
problem).
Noel
>> I'll add the info to the MSV11-J page on the CHWiki, once I have it.
> Alas, it's down at the moment ... but once it's back, I'll get them
> right up.
It's back, and I've added the chip info for the low 1MB bank:
http://gunkies.org/wiki/MSV11-J_QBUS_memory#Technical_information
I'll do the other bank 'soon' (I first have to tweak my 'scope loop program,
to turn on memory mapping, to get to the high bank). Here's my test rig, BTW:
http://ana-3.lcs.mit.edu/~jnc/tech/pdp11/jpg/MSV11JTester.jpg
Simple, but it did the job!
Noel
Hello,
Long story short, a while ago I cloned the hd of a Fuel I got given (6.5.16, original installation from an iconic car designer, Bertone), and all was ok. The original hd was then left in place but unpowered, the cloned was upgraded to 6.5.22 to maintain the classic applications. Fast forward to the present :
Had the smart idea to install an Audigy 2 zs pro ( the kind with the external box, and that takes current using a molex from the computer psu - I used the rail going also to the boot hd ), and the Fuel started acting weird ... not turning on unless pressing more than once the power button, one of the front fans speeding up and down and even stopping, Display Expander I/O errors ( I should note that from the moment I got the Fuel I had to disable env since the I2C on the V10 board is acting crazy ).
I managed to boot / use it a couple of times... then it didn't go past the Prom.
Removed the Audigy , after a while ( and 2 times left disconnected from the wall outlet for a bit ) it sort of restarted to power on consistently on pressing the button, but it always ended stopping at the prom splashscreen
Invoking a manual boot resulted in this
https://snag.gy/eMHafJ.jpg
after going in circles for a bit, had the brilliant idea of doing this from the prom sash :
https://snag.gy/eTzqEP.jpg
thus getting more puzzled... the boot drive appeared readable, so why the scsi hard errors.
Then I simply reconnected the original hd, and from that one boots with no issues... result, probably the last or both shutdowns while the Audigy was plugged were not so clean.
Ideally I would prefer not to clone + upgrade + readd programs again, and I think that repairing the damaged installation would be better especially in case it happens again in the future. I've tried to ask around, but I've not got any hint, and if there was something in an old neko thread... well, we all know that those are unavailable.
Bottom line, anyone ever got in this situation and has some tips on what to do ?
Thanks in advance,
Alessandro
hi guys
I am looking for instructions about *HowTo* compile a modern version
of GNAT on IRIX >= 6.5.20
2016-12-10 =dev-lang/gnat-gcc-4.9.3 - success - Linux/PPC32BE
2016-12-13 =dev-lang/gnat-gcc-4.3.5 - success - Linux/PPC32BE
2017-08-24 =dev-lang/gnat-gcc-4.3.5 - failure - Linux/PPC32BE
2018-03-24 =dev-lang/gnat-gcc-4.3.5 - success - Linux/PPC32BE
2018-03-25 =dev-lang/gnat-gpl-4.3.5 - failure - Linux/PPC32BE
2018-03-27 =dev-lang/gnat-gpl-4.3.5 - failure - Linux/PPC32BE
2018-03-28 =dev-lang/gnat-gpl-4.3.5 - failure - Linux/PPC32BE
2018-04-05 =dev-lang/gnat-gcc-4.3.5 - success - Linux/PPC32BE
I have successfully done it on Linux/PPC32-be (Apple PowerMac G4),
but:
- it was very very difficult
- the recipe for Linux doesn't work for Irix
anyone?
thanks
> I'm going to need this info real soon ... so I'll probably start on
> this later today if nobody has the info.
> ...
> write a two-instruction loop .. which writes a word with only a single
> '1' bit, hook up a 'scope ... to a DRAM input, and walk the bit through
> ... just disable ECC, and write all 0's to all the ECC bits
> ...
> I think that ... it'll go reasonably quickly, actually; the more bits
> I ID, the fewer values I'll have to try on each succeding DRAM chip.
That was pretty easy; thanks for knocking my brain into gear! :-) The first
couple of bits I had to fish around, but pretty quickly it became apparent
there was a system, and for the rest it was just 'confirm that this chip does
indeed hold that bit'.
I now have the chip<->bit table for the even words, and most of the ECC bits
for them (there are two that have resistor headers next to them, so I can't
easily get a DIP clip on them to see which is which), but I'm getting bored,
I'll do the odd ones tomorrow.
Probably they'll be very similar (the array looks like a mirror image of the
one for the evens). Also, I was using a 1MB card, so I only had the low bank
to worry about; so then I'll have to do the high bank - again, probably pretty
easy, from here.
The blasted card doesn't have the usual DEC Exx chip numbers, though! I had
to make up my own for it...
> I'll add the info to the MSV11-J page on the CHWiki, once I have it.
Alas, it's down at the moment (the server is actually up, but its DNS entry
has gone away again), but once it's back, I'll get them right up.
Noel
I realize it's been a while since this happened:
http://e4aws.silverdr.com/hacks/6500_1/
But, I have pulled my hacked reader out from mothballs to read a CPU
someone is sending, so I thought I would inquire if others have 6500/1
units that want read.
Jim
--
Jim Brain
brain at jbrain.comwww.jbrain.com
I have a machine that I'm just now bringing up. I have some boot software but it is TSS/A that is the accounting multi-user package. I'd really like the TSS/B floppies instead. I'd settle for images.
Dwight
---------- Forwarded message ---------
From: Pete Lancashire <pete at petelancashire.com>
Date: Tue, Jul 3, 2018, 2:18 PM
Subject: Re: Looking for Tektronix 4051 or 4052 Display Board
To: Monty McGraw <mmcgraw74 at gmail.com>
Yeah the two display boards went to Europe.
If anybody needs three perfectly good 11 inch CRTs, deflection yolks
excetera come to Portland Oregon and they're yours or have somebody pick
them up for you they're in the scrap pile and scrap is going in about a
month. Each CRT contains about $35 worth of gold.
On Tue, Jul 3, 2018, 2:12 PM Monty McGraw <mmcgraw74 at gmail.com> wrote:
> Pete,
>
> I'm in Texas near Houston.
>
> The Display Board is the vertical board to the left of the CRT. It has
> several cables at the bottom to pin headers and the cable to the neck of
> the CRT.
> It also has connectors to the power transistors that simply unplug when
> you remove the Display Board.
>
> Here is a picture of a display board:
> https://drive.google.com/file/d/0Bxd4qJinVzkNOFZacFZSYVJwaHc/view?usp=shari…
>
> Monty
>
> On Tue, Jul 3, 2018 at 4:01 PM, Pete Lancashire <pete at petelancashire.com>
> wrote:
>
>> Is 206 Washington ? I have the remains of a 4051 4052 and 4010 terminal
>> sitting outside in the scrap pile. Parts have gone to Europe but they're
>> still pieces left over
>>
>>
>> They were about 25 miles west of Portland Oregon.
>>
>>
>>
>> On Tue, Jul 3, 2018, 1:35 PM Ian Finder via cctalk <cctalk at classiccmp.org>
>> wrote:
>>
>>> These systems are rare enough that it's probably worth fixing instead of
>>> treating the board as a simple FRU. There are schematics on bitsavers for
>>> that board, and they are complete.
>>>
>>> On Tue, Jul 3, 2018 at 1:21 PM, Monty McGraw via cctalk <
>>> cctalk at classiccmp.org> wrote:
>>>
>>> > I've been repairing my Tektronix 4052.
>>> >
>>> > I've got the digital logic working - but the text and graphics are
>>> messed
>>> > up.
>>> >
>>> > I posted photos of the screens in my Tektronix 4052 troubleshooting
>>> thread
>>> > on vcfed.
>>> >
>>> > With a scope on the final X amplifier stage - it is oscillating - so I
>>> see
>>> > weird horizontal strokes instead of dots for text. I know from the
>>> service
>>> > manual that this circuit includes a feedback loop, and with the scope
>>> I see
>>> > oscillation all around the loop - so I haven't found the source.
>>> >
>>> > Does anyone have a spare Tektronix 4052 (or 4051) Display Board that I
>>> > could buy?
>>> >
>>> > Thanks,
>>> > Monty
>>> >
>>>
>>>
>>>
>>> --
>>> Ian Finder
>>> (206) 395-MIPS
>>> ian.finder at gmail.com
>>>
>>>
>
I believe that Mike Douglas has a utility program that you can get into a Northstar Horizon, and then it can receive a .DSK image sent from the terminal and it will write the disk for you in the Horizon.
It?s called PCtoFlop and I think he has it in his archive here:
http://deramp.com/downloads/north_star/ <http://deramp.com/downloads/north_star/>
Good luck!
smp
- - -
Stephen Pereira
Bedford, NH 03110
KB1SXE
> ------------------------------
>
> Message: 14
> Date: Tue, 3 Jul 2018 00:16:45 +0000
> From: dwight <dkelvey at hotmail.com>
> To: Fred Cisin <cisin at xenosoft.com>, "General Discussion: On-Topic and
> Off-Topic Posts" <cctalk at classiccmp.org>
> Subject: Re: Looking for North star software
> Message-ID:
> <MWHPR14MB160074267AEE4604C5918AE5A3420 at MWHPR14MB1600.namprd14.prod.outlook.com>
>
> Content-Type: text/plain; charset="us-ascii"
>
> I was thinking someone has already done this. If no, as you say, it is not an impossible task.
>
> The TSS/B is suppose to be their scientific package. It at least has BASIC in it. I have another disk marked CP/M in the same box. I should be able to put something together under CP/M.
>
> It is a North Star Horizon. There seems to be some images out there so I don't know how they are being captured.
>
> Dwight
>
>
I've been repairing my Tektronix 4052.
I've got the digital logic working - but the text and graphics are messed
up.
I posted photos of the screens in my Tektronix 4052 troubleshooting thread
on vcfed.
With a scope on the final X amplifier stage - it is oscillating - so I see
weird horizontal strokes instead of dots for text. I know from the service
manual that this circuit includes a feedback loop, and with the scope I see
oscillation all around the loop - so I haven't found the source.
Does anyone have a spare Tektronix 4052 (or 4051) Display Board that I
could buy?
Thanks,
Monty
The Moravian Galley in Brno has an exhibition on "Computer Art 1968".
The only actual computer is a very well-preserved German LGP-30. I
took a few photos of it yesterday... and got told off for handling the
paper tape, which only has some diagnostics on it: blocks of "lace"
alternating with unpunched blocks.
https://www.flickr.com/photos/lproven/albums/72157696907302261
It was used by Zde?ek S?kora in his early abstract art.
https://en.wikipedia.org/wiki/Zden%C4%9Bk_S%C3%BDkora
--
Liam Proven - Profile: https://about.me/liamproven
Email: lproven at cix.co.uk - Google Mail/Hangouts/Plus: lproven at gmail.com
Twitter/Facebook/Flickr: lproven - Skype/LinkedIn: liamproven
UK: +44 7939-087884 - ?R (+ WhatsApp/Telegram/Signal): +420 702 829 053
> From: Glen Slick
> There are 88 41256 256Kx1 DRAMs on a 2MB MSV11-J. Each 512KB bank has
> 22 256Kx1 DRAMs organized as 16 data bits plus 6 ECC bits.
Umm, I think the internal organization is paired banks (one for even word
addresses, one for odd); the manual talks about doing double-word reads
(although only one word gets transferred over the bus at a time, but the
PMI has some optimization for double-word cycles, IIRC).
> If someone was sufficiently motivated I suppose they could probe each
> of the 88 DRAMs while writing various bit patterns of data to various
> memory locations and work out the mapping that way. ... I'm not sure
> which would be more work, probing one or a small number of DRAMs at a
> time
Oh, that's an improvement on what I was thinking of as a fall-back, if nobody
has the info (which was to tie the outputs of individual DRAM chips high or
low - depending on how they implement their output stages - through a
suitably-sized resistor, and look to see what effect it had on writing and
then reading - all 0's or 1's, depending on the tie - still a lot less work
than pulling chips :-). Dunno why it wasn't obvious this would be easier! :-)
I would/will just write a two-instruction loop (in the PARs) which writes a
word with only a single '1' bit, hook up a 'scope (I'm too lazy to hook up a
logic analyzer :-) to a DRAM input, and walk the bit through the odd and even
words until I see it on the 'scope.
I thought about doing the ECC bits first, using the maintenance mode (to walk
a '1' through the ECC bits), to avoid getting confused by 1's being written to
them during the above process, but that would be a lot more work, since I'd
have to look at all the chips in the array to find the one that's getting the
'1' ECC bit.
It'll probably be a lot easier to just disable ECC, and write all 0's to all
the ECC bits while doing the data bit discovery (above); once those are done,
the remaining chips are known to be ECC, and I can walk a '1' through the ECC
bits to work them out.
> From a brief look at the manual it might be possible to use diagnostic
> modes to write specific ECC bit patterns and work out the ECC bit
> mappings as well.
Yup, that was my take too. Although I'm having to re-read the manual a few
times to fully grok how all the various mode bits interact!
> Might be very tedious, so might need lots of motivation.
I think that using the procedure above, it'll go reasonably quickly,
actually; the more bits I ID, the fewer values I'll have to try on each
succeding DRAM chip.
> If I ever get really bored some day maybe I'd take a look and try to
> see just how tedious it might be.
I'm going to need this info real soon (to hopefully fix a broken MSV11-J),
so I'll probably start on this later today if nobody has the info.
I'll add the info to the MSV11-J page on the CHWiki, once I have it.
Noel
Time to reveal a personal project related to vintage computing and
unrelated to my role at VCFed.
In the past two years, while getting neck-deep in the historic Lego 9700
"Technic Control Center" set, I learned that there is a TON of
information about this set (and about various related sets) -- but most
of that information is missing from the web or at best scattered.
What these programmable robotic sets all have in common is they're all
>from the 10 years BEFORE the modern Mindstorms series, and they run on
vintage computers!
I decided a few months ago to make a web site about it. I call the site
www.mindsbeforethestorm.com. The site is under construction but you can
visit now and see where it is going.
I'm asking for contributions to the project.
I make a very modest living through my work as a freelance tech
journalist and additionally through VCFed fundraising. Many of you will
also recall that a personal fundraiser is what enabled publishing of my
computer history book in 2015. That was a positive experience.
I do not plan to sell anything on this new site, only to offer helpful
information that isn't currently available or is very difficult to find.
As such, I cannot promise any Kickstarter-style rewards: I don't have
any ideas about what a good reward for this might be (open to
suggestions). Instead, I appeal to your altruism: fund this project
because it is a good thing.
Please visit my new site. If you think it exemplifies how the web should
be used, if you'd like to see it get finished, and if you would like me
to continue to be able to pay my rent and eat food, then please make a
contribution via https://fundrazr.com/61N3ef?ref=ab_74VRia.
Thanks,
-Evan
Hi, I'm looking for engineering info on the MSV11-J. I was unable to find any
prints online, or even a technical manual. (I have the User Manual, but it doesn't
have much detail.)
The main issue I'm after is working out which bits go into which chips. I
have some other QBUS memory boards with no documentation where I created the
mapping by just pulling chips, e.g.:
http://gunkies.org/wiki/Q-RAM_11
but, alas, on all the MSV11-J's I've seen, the DRAM chips are not socketed -
unlike QBUS memory boards by almost all the other manufacturers (e.g. National
Semiconductor, Camintonn, etc - in fact, pretty much everyone _except_ DEC).
Anyway, if anyone _does_ have an MSV11-J with the chips in sockets, I'd
_really_ appreciate hearing from them!
I'm not sure it's going to be possible to work it out from looking at board
traces, since the MSV11-J is ECC memory, and I expect all the data lines just
disappear into the two huge gate array chips.
Anyway, I would appreciate hearing from anyone with anything on the MSV11-J.
Noel
hi,
In 1990s Tektronix produced digital video X terminal and introduced
X server software based on VxWorks v5 (Windriver). Later they
introduced a new line of terminals, at some point a company called NCD
bought the Tektronix X11-terminals division and started to produce
their own line, called NCD-terminals with a software called
"NCD-bridge"
Anyway, both the 200-series and the 400-series of the Tektronix X11
terminals boot from a directory on a server via NFS or TFTP, either
way, you need to create a directory for the terminal to boot from, and
install a number of files.
These files are provided as "Tektronix XpressWare version 8.0 (or
later)". The 200-series can bootstrap from v7 ( one of the member of
my team owns an original CD), but the 200-series needs the v8 or later
(we don't have).
Unofficially, you might look for NCD, the Company who bought the
X-terminals division from Tektronix; they had (note the past tense)
some software in the form of patches, accessible by anonymous ftp.
There aren't any complete releases, but there were archives which
contains much that is useful to be found in the ftp, in particular
patches containing bits of version 8.1 of XpressWare; enough to form
the basis of a working installation.
Unfortunately, the archive is gone, no more available.
Let me know if you have the software or if you know where/how to find
it, otherwise, X11-terminals like X400 can't be functional.
Thanks
> From: Bill Gunshannon
> Anybody have any PMI memory modules they might let go for less than my
> first born male child?
The DEC PMI memories are the MSV11-J and (I think) the MSV11-R. The latter is
rare, but the -J's can be found. VARx sold me some -JE's a couple of years
back for a good deal less than their listing price:
http://www.varx.com/CAT/MEMORY-DEC_MSVXX.HTML
The other possibility is that Clearpoint made some PMI memories, which one can
occasionally find on eBait, etc: the QED1 (aka QED-F) and DCME-Q4E (they look
the same, so I'm not sure if they are actually different, or if the names were
just changed for marketing reasons).
Alas, I know of no documentation on either. (If anyone has any, _please_ share
it!) I am slowly trying to work out how to configure them (they can be
configured to run PMI or normal QBUS); contact me privately for what little I
have so far.
Noel
> From: Pete Turnbull
> Bill would want the -JD (2MB) version (the -JE version is 4MB so too
> big).
Err, the -JD is 1MB, and the -JE is 2MB (see e.g. EK-MSV1J-UG-001, pg. 1-3).
Noel
> From: Paul Birkel
> Same thing in this case.
The CPU looks to see a PMI signal that is generated by the KTJ11 - no signal
-> 11/83.
My impression is that except for the speed of the J11 (and the crystal), and
whether or not it came with the FPJ11, all four of the M8190 board variants
are otherwise identical. Whether it's a /73, /83 or /84 depends entirely on
whether it has/sees PMI memory and the KTJ11-B UNIBUS converter (and the
correct backplane, for the latter, of course).
> The 11/84 is an 11/83 extended by a Unibus interface to support legacy
> peripherals.
It has a special backplane which is mostly UNIBUS slots, with a few QBUS/PMI
slots on the front, and a 'special' slot in the middle into which the UNIBUS
adapter goes.
Noel
I missed the recent M8198+CIS chip auction on eBay, and subsequently
found myself with a new (for me) 11/23+. Does anyone have a CIS chip
they're interested in parting with? Contact me directly.
KJ
A couple of boards from an unknown computer came in and i am trying to get
them to a good home and not be scrapped. I was curious if anyone here knew
what they were out of. They were in the box with some small core memory
boards. If someone here wants to make an offer ill gladly take the ebay
listing down.
eBay http://www.ebay.com/itm/273330177351
It's almost time for Vintage Computer Festival West XIII! The show is
August 4-5 at the Computer History Museum in Mountain View, California.
You?ll find dozens of hands-on exhibits, incredible lectures, a huge
consignment sale, and much more -- plus the museum's own tours and
hands-on demos.
There is still time to register your exhibit, but it's tight! Go to
http://vcfed.org/wp/festivals/vintage-computer-festival-west/vcf-west-exhib…
ASAP to sign up. We also need more volunteers! Email erik at vcfed.org if
you can be a helper.
________________________________
Evan Koblentz, director
Vintage Computer Federation
a 501(c)3 educational non-profit
evan at vcfed.org
(646) 546-9999
www.vcfed.orgfacebook.com/vcfederationtwitter.com/vcfederation
> From: Paul Koning
> I believe the original concept was just a probe that would poke through
> the cable to contact the center connector. The drill came because the
> cable was too tough to penetrate without it.
No, the original 3 Mbit Ethernet also used a 'drill' (actually, a cylindrical
cutter which screwed into the thread of the tap housing; threading which was
then used to screw in the transceiver).
Anyway, there has to be a hole cut _through_ the cylindrical ground layer
(foil, or woven wire) around the center conductor. If you just stuck a probe
into the cable to the center conductor, it would short it out.
Noel
On Thu, Jun 28, 2018 at 8:26 PM, Bill Degnan via cctech <
cctech at classiccmp.org> wrote:
> I have always pointed my grant continuity cards in the same direction as a
> NPG card, with the traces to the left/facing the last slot of the
> backplane. I am 99% sure this is right but I was asked and I just want to
> be 100%...am I right? In particular the traces point away from the CPU
> cards, at least on an 11/40 and 11/05. Please just tell me I am not losing
> it.
>
If your system works properly, the grant cards are in the right way. If the
grant cards are installed wrong, or missing, it will cause serious
problems, and you're unlikely to be able to boot anything.
I don?t recall if I had any 3880 documents. I will ask how they would like to handle this type of request. There are many duplicates and they will need time to catalog the documents.
> the AMP coring tool ... doesn't screw in though ... I don't know if this
> is consistent with the original 3 mbit Ethernet, as I've never worked
> with that.
I was speaking of the gear used on the 3 Mbit. I don't recall the 10 Mbit
stuff at all.... I have this vague memory that the 3 Mbit cutter also had a
shoulder stop that prevented one going too deep.
Noel
Hi folks,
I know there's not much 6800 activity here, but I figure this would be worth a try.
Has anyone here ever seen or ever had fig-FORTH for the 6800 working?
I have a SWTPC replica system from Bob Applegate / Corsham Technologies, and I love it. It came with a complete 64K RAM, as well as the SWIBUG monitor, and the monitor code has been extended by Bob/Corsham to interface with an SD Card sub-system for floppy disk emulation. This provides the original terminal access to the machine with the simple system monitor, and also the FLEX OS for running programs. It is a blast to use.
Recently, I took a look around and found the fig-FORTH listing as originally published back in 1979, and also a Source Forge site that holds an electronic copy:
https://sourceforge.net/projects/asm...th_6800-stuff/ <https://sourceforge.net/projects/asm68c/files/fig-forth_6800-stuff/>
I've managed to get the source code to assemble with a cross-assembler supplied by Bob/Corsham. It does not produce an exact copy of the original code, because the code uses the JMP instruction pretty much exclusively, and the assembler substitutes a relative BRA instruction sometimes. So my code ends up being several bytes shorter because of saving one byte each time a JMP is replaced by a BRA. That said, it appears to me that the code matches up with the original listing otherwise.
So my problem is this: When I run the code on my system, fig-FORTH seems to sign on, and will accept input from the keyboard (double echos of each key typed) but it then does not proceed to interpret the command entered. The interesting thing I see by winding my way around in the code is that it has already properly performed a bunch of setup and produces the initial "Forth-68" sign on, and that has required it to already be using many of the Forth commands that were defined by machine language. This indicates to me that some of the command interpretation is working. The I/O from/to the terminal is by calls to the system monitor I/O routines, and that seems to be also working, despite the double echos of the typed characters. It just does not proceed to interpret what is typed in at all.
Of course, I have no idea if this code ever worked properly, or if I am encountering early buggy code. So I'm looking to see if anyone else has ever seen the fig-FORTH working on a 6800 system? Any pointers to good working code?
Thanks for listening!
smp
- - -
Stephen Pereira
Bedford, NH 03110
KB1SXE
hi
I have for sale, qty=1, SGI Silicon Graphics Phobos G160 for Indigo2 Impact
brand new, still closed in the box, unopened!
located in Italy (in my parent's house)
I will be happy to give it a new home
Folks,
Well I seem to be running around in circles. As it takes most of a weekend
to back up the P390 because of various things, I decided there must be a
quicker way. And there is!
1. Set up SD card in SCSI2SD as a single disk physical rather than
split to match the config on the RAID array. I still have the same number of
partitions but they are all on one LUN.
2. SD card can now all be seen by windows but as most partitions a HPFS
I can't mount them but I can use MS's DISK2VHD to image the card.
3. Install OS/2 in a VirtualBox and I can now mount the HPFS partitions
4. ZIP up drives and FTP to NAS box. Both are on same gigabit LAN so
its fast.
So I can now back up the server in a morning. Just need to script it and
test restore.
Dave.
From: Dave Wade <dave.g4ugm at gmail.com>
Sent: 26 May 2018 21:16
To: 'General Discussion: On-Topic and Off-Topic Posts'
<cctalk at classiccmp.org>
Subject: RE: Restoring a PC Server 500 P/390
Folks,
Well in case any one has the slightest bit of interest, I have now plugged
the RAID card back in and after replacing on of the drive carriers I can get
five of the six drives to spin up. Its now copying stuff to my Buffalo NAS
but as its 10Mbit LAN its not terribly fast. I think the NAS isn't very fast
either. It looks like zipping up the files and FTPing the ZIP files might be
the quickest way to go.
Dave
From: Dave Wade <dave.g4ugm at gmail.com <mailto:dave.g4ugm at gmail.com> >
Sent: 18 May 2018 22:31
To: 'Benjamin Huntsman' <BHuntsman at mail2.cu-portland.edu
<mailto:BHuntsman at mail2.cu-portland.edu> >; 'General Discussion: On-Topic
and Off-Topic Posts' <cctalk at classiccmp.org <mailto:cctalk at classiccmp.org> >
Subject: RE: Restoring a PC Server 500 P/390
I thought I had captioned that picture. It's the original RAID controller
which I am not using. If I plug it in it starts the disks in the RAID array
which takes ages, and steals the hard disk BIOS vector which I need for the
SCSI card that's running the system.
I didn't want to remove it fully as I need to label the cables feeding it.
One feeds the top drive bays, and the other the bottom so if I ever need to
put it back it I need to know which is which.
If I get some free time I will have a go at starting the disks in it and
repairing the RAID array, and perhaps copy the disks that are installed.
Dave
From: Benjamin Huntsman <BHuntsman at mail2.cu-portland.edu
<mailto:BHuntsman at mail2.cu-portland.edu> >
Sent: 18 May 2018 21:49
To: Dave Wade <dave.g4ugm at gmail.com <mailto:dave.g4ugm at gmail.com> >; General
Discussion: On-Topic and Off-Topic Posts <cctalk at classiccmp.org
<mailto:cctalk at classiccmp.org> >
Subject: Re: Restoring a PC Server 500 P/390
I gotta ask, what's the deal with the dangling card? That cracked me up!
Thanks for posting some pics!
_____
From: cctalk <cctalk-bounces at classiccmp.org
<mailto:cctalk-bounces at classiccmp.org> > on behalf of Dave Wade via cctalk
<cctalk at classiccmp.org <mailto:cctalk at classiccmp.org> >
Sent: Friday, May 18, 2018 1:46 PM
To: 'Guy Sotomayor Jr'; 'General Discussion: On-Topic and Off-Topic Posts'
Subject: RE: Restoring a PC Server 500 P/390
> -----Original Message-----
> From: Guy Sotomayor Jr <ggs at shiresoft.com <mailto:ggs at shiresoft.com> >
> Sent: 15 May 2018 21:39
> To: Dave Wade <dave.g4ugm at gmail.com <mailto:dave.g4ugm at gmail.com> >;
General Discussion: On-Topic
> and Off-Topic Posts <cctalk at classiccmp.org <mailto:cctalk at classiccmp.org>
>
> Subject: Re: Restoring a PC Server 500 P/390
>
>
>
> > On May 15, 2018, at 1:29 PM, Dave Wade via cctalk <cctalk at classiccmp.org
<mailto:cctalk at classiccmp.org> >
> wrote:
> >
> >
> > That's, in effect, what I did. Whilst there were Microchannel IDE
Controllers
> I have never seen one. There are no IDE interfaces on the "Planar" so
every
> thing must be on the MCA bus.
> > So I bought a BusLogic BT646 SCSI card on E-Bay. I also bought an
Adaptec
> card as a spare. I think I struck lucky with the BT646. It is a simple
SCSI/2 card,
> no raid but it does have a BIOS with support for two bootable drives and a
> >4GB drive option.
> > OS/2 has drivers for it so it works out of the box. The OS/2 boot disks
find
> the drive and install the proper drivers.
> > To compensate for the slower "narrow" drives I bought a SCSI2SD card
that
> puts an SD card on the bus. OS/2 just sees it as a up two four drives
> depending on how I configure it. At present I have two 4gb drives. The
card
> in it is 32gb so I can add 2 x 12gb drives or 1 x 24gb or some other mix.
The CD
> ROM sites on the same bus. I haven't tried the tape drive yet..
> >
>
Well I found an XGA2 card in the pile of bits so now I have 1024x768 display
resolution. I have swapped the CDROM for a SCSI DVD drive.
I managed to boot MTS and there are a few pics here:-
https://flic.kr/s/aHsmc1pkB1
<https://flic.kr/s/aHsmc1pkB1>
<https://flic.kr/s/aHsmc1pkB1> P390
flic.kr
Explore this photo album by Dave G4UGM on Flickr!
next job is to tidy up and re-assemble the case..
Dave
> Some time ago I acquired a PCI P/390 card (along with the various LIC
files). I
> went down the same path as you to build a P/390 system with OS/2 but I
> kept running into problems with OS/2 versions and supported hardware.
>
> I finally gave up and acquired a PCI based RS/6000 that I'll install AIX
on and
> have an R/390. ;-) I haven't had the time yet to make any progress on
it.
>
> But it's good to know that you've managed to do this if I decide to go
back
> and attempt the PC route again.
>
> TTFN - Guy
With the demise of Weirdstuff, I decided to visit Outback Equipment in
Gilroy this week. Jim Schuetz, formerly a partner at Weirdstuff is now
the Business Development Manager at Outback.
While there, I looked over the following DEC gear (includes several
non-DEC QBus cards that I'm not listing - as I have no idea what they
are). Here's the DEC gear available:
PDP 11/23 Plus (BC)
PDP 11/73A (BC)
PDP 11/23 Plus (BE) marked "Bad"
(3) QBus Zip Drive controllers
(1) M8043 DLVJ1-M (formerly DLV11-J)
(2) M8190 (AB) KDJ11
(1) M9081 (LF?)
(1) M7551 (AH?) MSV11-QA
(1) M8029 RXV21
There's more "stuff" that you can see from the pictures below. All the
PDP-11 "boxes" and boards look to be good cosmetically.
Photos here:
https://photos.google.com/share/AF1QipMAvVBdhz20-z7l6W9JXhBB0k3ggw0HWveHctE…
Jim would like to sell the above as a lot.
His contact info is:
jim at outbackequipment.com
Phone: 408-886-3733
Cheers,
Lyle
--
73 AF6WS
Bickley Consulting West Inc.
http://bickleywest.com
"Black holes are where God is dividing by zero"
Anyone live near this Hotel?? I am just getting home and am just now
seeing this.? Evidently, this is a rescue attempt, but I don't have a
bunch of detail as yet.
Jim
Hi Jim
I sent the below email to Peter yesterday. Have not heard from him.
It would be a pity if neither of you can arrange to get hold of this
stuff. Can you maybe provide backup if Peter can't make it?
W
Hi Peter
TRS-80 bits will be at the Watson Hotel. 440 57th Str. Hell's
Kitchen, NY 10019.
Fellow is called Marius Killian and he's there today and tomorrow
(24th and 25th). Sorry about short notice but I only came home last night.
Please make plan to pick up, or for hotel to hold for you. Let me know.
W
(x11 terminal) C3253A HP Envizex P-Series
Up for sale is a X-Terminal made by Hewlett Packard in 1995.
Tested, in perfect working conditions!!!
cpu: i960 @ 33Mhz (it's the fastest available on Envizex v1)
ram: 48MB (builtin + 16+16+8, the first two sims need to be equal)
rom: none (sorry, It doesn't have any font-rom, it loads fonts from tftp/NFS)
vram: 2MB
lan: 10Mbps BASET RJ45 (it also comes with an AUI port on the back)
kb/mouse: common PS/2 (F12 is a special key, but Envizex works on
common keyboards, HIL keyboards are also supported)
Media: floppy 3.5",1.44MB
Software included!
It comes with all the documentation, configuration-scripts, and
startup for Linux (sorry, I don't have HPUXv10.20/v11, I can't
test/adapt scrips).
The machine is perfectly working, it supports the X Display Manager
Control Protocol (XDMCP), you just need to power on your hardwired
terminal and be greeted with a login prompt. This purpose is easy to
be accomplished on HP terminals, especially if you use NFS instead of
tftpboot.
HP-net-stations can boot using either Network File System or Trivial
FTP, with NFS being the preferred method it's simpler.
During the final phase of startup, the bootup screen disappears and
the X station loads bin/modules.ld, which tells what can be optionally
loaded (but not executed), and then starts the X session by executing
the application that was specified by the user on config/autoexec.cfg
It supports all of the following:
XDM login
VUE
CDE Lite (its panel appears similar to the one you can see on HPUX)
mwm (simple windows manager)
twm (simple windows manager)
If you see one of first three login screens in the above list, you
just need to enter your login account and password.
80 euro + s/h
located in Switzerland