Hello!
We just located an old Motorola VME "minicomputer" with an MVME188 single
board computer. Being a real vintage computing enthusiast, I decided to try to
get the thing working, running OpenBSD. However, before I can do that, I need
to reprogram the NVRAM in it. I figure if there were some documentation on how
to do this, and how to actually use the machine someone here might have it!
Any information on the board, the MVME332/333/376/328 would be much
appreciated.
Cheers.
Phil
Stupid question, but does anyone know if the SCSI BIOS format utility on
Adaptec 29160 or 2940 cards does bad block checking and reassignment?
I've got a 1GB Fujitsu SCSI drive here that has one dodgy block right in
the middle of the disk (according to the Linux badblocks util, which
still has a couple of passes to run).
Unfortunately I want the disk for my Tektronix, and I think bad block
mapping under Linux is only done at the filesystem level, rather than
Linux being able to low-level format the drive and map blocks out that
way.
I'm a bit wary of the Adaptec BIOS utility - hopefully it won't trash
the drive...
cheers
Jules
hi,
I designed many of the Sritek boards. You may contact me for some
assistance.
Madhav S. Kavuru, PhD
(mskavuru(a)hotmail.com)
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
My Data I/O 29B seems much more happy. All tin contacts cleaned with deoxit
and all gold contacts cleaned with progold. Reseated all the chips (some
were loose) and it appears to work fine for reading anyway. I'll check the
power supply and calibration then try to program a chip.
My current issue du jour is with Promlink. I can use version 3.4 just fine.
I want to use version 6.10 though, MUCH easier on the eyes. However, any
time I try 6.10 (with the high speed cpu patch), it chokes on "error sending
Device Identification enable/disable command, is this a 29B unipak?"
I thought my unipak was a model 2. It's not, it's just a straight unipak. I
believe the device id feature is present on unipak 2 and 2b, and not present
in just a unipak. From what I can tell, promlink v6.10 insists that the
device identification feature be turned on. There is a setting to disable
device ID checking in promlink, but either that setting doesn't work at all,
or, it tries to send a disable device id command to the 29B, which won't
understand it with a unipak, hence the error.
Any known way around this? My 29B is firmware v 06 if that helps.
Thanks!
Jay West
Jules Richardson wrote:
>
>Looking at the raw disk image I've saved, I've worked out where the
>partition table is within the image (it's at offset 0x280). Most of the
>stuff preceding it is zeros, except for a few flags and one place that
>seems to be total size of the disk in blocks *including partition table
>data*.
If you have a saved image you should be able to try and mount it using a
'loopback' file system on linux. No doubt that's what you tried.
did you try any of the bsd parition programs, liked parted? who knows.
All I remember is that sometimes we had to boot from a floppy and
humm... that ran some sort of fsck? it's been a while. We never
replaced a hard disk or tried to fool with one.
I'd guess I'd be suprised if the file system was anything other than
system 5 ufs. As I recall those systems were pretty vanilla unix wise.
I don't think they had any bsd-isms in them (but I may be wrong).
it might be interesting to hack up a copy of an old sys v fsck and open
the image in read-only mode. that way you could fool around with
various offsets and try to find the super block.
once you know where the partition starts, and assuming you did a block
copy under unix (so the blocks are in the right order), you might be
able to grab an old copy of "sash" or something like that and get it to
read the file system. at least then you could "ls".
just some random notions.
In the end, I think I'd write a program to transform the image into a
new image which had a modern partition map pointing to the super block
and then get linux to mount it. easy for me to say :-)
-brad
I have an Apple LocalTalk RJ-11 Connector DIN-8 M1657Z/A with manual for
anyone who wants it. I'm sure some Apple collectors out there could use
one of these. US only please -- I don't want to pay more for
international postage.
Thanks,
-- Michael
Pat has lost interest in DEC collecting. I spoke to him when
I was down there a few months ago. Here is an exerpt from a
mail msg from him.
Since however, one of us, The famous John R. Wisniewski, from
DEC, has passed away, and due to the economics in the present
time following 911, when everyone lost so much money and the
purse strings have become very tight, we are not able to continue
to seek grants or raise funds for a permanent place to store and
show these, so at some time in the future, the entire collection
will probably be liquidated.
--
I will forward his current email adr through private email to
Emanuel.
> Anyone have any old technical white papers on the MOS 6507, I know its
> just a slight variant of the 6502, but I would like to look over the
> original technical specifications for the chip, pinouts, opcodes,
> instruction set, etc...
There are no specific documents on it. It's in the MCS650x data sheet.
It's just a 6502 die in a smaller 28-pin DIP package with not all of the
pins bonded out. Specifically, A12 through A15, RDY, /NMI, SYNC, SO,
three NC pins, and one Vss pin are not available.
The pinout is:
/RES 1 28 Ph2 out
Vss 2 27 Ph0 in
Ph1 out 3 26 R/W
/IRQ 4 25 D0
Vcc 5 24 D1
A0 6 23 D2
A1 7 22 D3
A2 8 21 D4
A3 9 20 D5
A4 10 19 D6
A5 11 18 D7
A6 12 17 A11
A7 13 16 A10
A8 14 15 A9
I'm looking for the Synertek 6516 data sheet, and Synertek technical
notes 34 and 40. The 6516 was to be a 16-bit extension of the 6500
family, years before the 65802/65816. Synertek published a data sheet
in mid 1978, but the part was never put into production.
