Microbotics Starboard 2 jumper settings?

[save2600]

Hey Motrucker... you ever take a pic of your Starboard by any chance?

[save2600]

@save2600

     In a word, no. It's not the batteries, so I'll have to bite for a new camera this week. As soon as I do, I'll get the photo(s) up. Sorry for not keeping you all up to date.

Great, thanks! I wonder if the jumpers you have installed only pertain to the RAM's parity? And then there's another couple of pins that might be a jumper on the opposite side of the board. I measured +5v through it, so wonder if that's supposed to be for an LED tap? I did place a jumper across 'em, but no change.

I've successfully brought LoadWB's old Starboard back to life. Well, kinda. RAM is now acknowledged, but am having trouble with the SCSI side of it. Too many variables to tell right now (I'm using an external SCSI CD box with two ports, one is not terminated and I'm going from SCSI I to SCSI II through an adapter), but plan on playing around with this more today.

As an aside... the clock configuration and its software is goofy as hell in this thing. Does not allow you set anything past 2010. LOL!  So I guess that's not much use anyway, unless there's something to be found on Aminet for it or something.

[save2600]

Do you have the original Microbotics SCSI software.

Yes, version 1.5 and it's weak as hell. :lol:

BTW: using their memory test software, it does appear I have some bad RAM after all. Damn! Time to swap all these other chips now and see what's what.

-edit-

So yeah, looks like this thing has some bad RAM somewhere. No way of determining what chip(s) though besides a ton of swapping, testing, swapping, etc. Screw that noise. I've already messed around with this thing enough as it is. Anyone have 2mb of RAM laying around? Takes 32 pieces of 256kx1 chips to make 1mb.  :lol:

[save2600]

Version 1.5 and no, it doesn't show a map of the board indicating which chips are bad. Didn't the DKB Insider software do that though? Doesn't help me here, but what a helpful concept.