RE: Mitsubishi Melcard (edge connect type)

2021-04-11 Thread D. Resor via cctalk
After digging a bit further and disassembling a card I have here which was 
defective and peeling apart.  I now know that this is a Seiko-Epson not a 
Mitsubishi Melcard.  Seiko-Epson are 40 Contact Traces.  Mitsubishi are 50 
Contact Traces.  I also found a data sheet from the p/n silk screened on the 
PWB of the card here:

https://www.datasheetarchive.com/pdf/download.php?id=11082c69f543ba2dc23ee78386ce2ce49debd2&type=O&term=EPC032IEC0

Thanks for giving me a shove in the right direction.

Don Resor

-Original Message-
From: cctalk  On Behalf Of D. Resor via cctalk
Sent: Sunday, April 11, 2021 5:09 PM
To: 'Alexandre Souza' ; 'General Discussion: 
On-Topic and Off-Topic Posts' 
Subject: RE: Mitsubishi Melcard (edge connect type)

I don't know.  I do know that Roland also used something similar though the 
length of some of the contact points are different from the Mitsubishi Melcard.

Don Resor

-Original Message-
From: cctalk  On Behalf Of Alexandre Souza via 
cctalk
Sent: Sunday, April 11, 2021 10:38 AM
To: Chuck Guzis ; General Discussion: On-Topic and Off-Topic 
Posts 
Subject: Re: Mitsubishi Melcard (edge connect type)

Isnt that the epson card standard?

Enviado do meu Tele-Movel

Em dom, 11 de abr de 2021 14:37, Chuck Guzis via cctalk < 
cctalk@classiccmp.org> escreveu:

> On 4/11/21 7:08 AM, D. Resor via cctalk wrote:
> > Does anyone recall what kind of hardware/software was used to 
> > read/write
> the
> > early Mitsubishi Melcard EPROM cards with the PCB edge connector
> contacts?
> >
> >  It was explained to me by someone that a EPROM programmer could be 
> > used, however I've never seen a socket which fits the edge card 
> > connector of
> these
> > cards.
>
> I don't know if it's exactly what you're looking for, but there's a 
> potload of information on Bitsavers, starting with PDF page 115:
>
>
> http://www.bitsavers.org/pdf/mitsubishi/Mitsubishi_VLSI_MOS_Memory_RAM
> _ROM_and_Memory_Cards_Jan91.pdf
>
> --Chuck
>
>




RE: Mitsubishi Melcard (edge connect type)

2021-04-11 Thread D. Resor via cctalk
I don't know.  I do know that Roland also used something similar though the 
length of some of the contact points are different from the Mitsubishi Melcard.

Don Resor

-Original Message-
From: cctalk  On Behalf Of Alexandre Souza via 
cctalk
Sent: Sunday, April 11, 2021 10:38 AM
To: Chuck Guzis ; General Discussion: On-Topic and Off-Topic 
Posts 
Subject: Re: Mitsubishi Melcard (edge connect type)

Isnt that the epson card standard?

Enviado do meu Tele-Movel

Em dom, 11 de abr de 2021 14:37, Chuck Guzis via cctalk < 
cctalk@classiccmp.org> escreveu:

> On 4/11/21 7:08 AM, D. Resor via cctalk wrote:
> > Does anyone recall what kind of hardware/software was used to 
> > read/write
> the
> > early Mitsubishi Melcard EPROM cards with the PCB edge connector
> contacts?
> >
> >  It was explained to me by someone that a EPROM programmer could be 
> > used, however I've never seen a socket which fits the edge card 
> > connector of
> these
> > cards.
>
> I don't know if it's exactly what you're looking for, but there's a 
> potload of information on Bitsavers, starting with PDF page 115:
>
>
> http://www.bitsavers.org/pdf/mitsubishi/Mitsubishi_VLSI_MOS_Memory_RAM
> _ROM_and_Memory_Cards_Jan91.pdf
>
> --Chuck
>
>



Re: Anyone know ancient versions of XLC?

2021-04-11 Thread David Schmidt via cctalk

On 4/9/21 3:23 PM, Nemo Nusquam wrote:

On 2021-04-08 00:32, Ben Huntsman via cctalk wrote:

I know this is a strange place to ask, but it's as good a place as any.
Anyone on here used IBM's XLC in very old versions?

Anyone know what the argument -qdebug=austlib does?


I have the docs for IBM C Set++ 3.1 for AIX (1993) and it is not there.?
As you probably know, the Austin lab was known for HPC s/w so they may
have shipped special debug versions.


[..]

I used xlc in the early 90's at IBM in the Raleigh networking lab, along 
with the excellent xcdb debugger - Austin's debug libs weren't a part of 
our repertoire.  There was plenty going on that was deeper and closer to 
the iron in Austin, so it could be just about anything.


AIX 3.2.5 was so much leaner and meaner than 4.x that came along next... 
I never did warm up to it the same way.


- David


Re: Mitsubishi Melcard (edge connect type)

2021-04-11 Thread Alexandre Souza via cctalk
Isnt that the epson card standard?

Enviado do meu Tele-Movel

Em dom, 11 de abr de 2021 14:37, Chuck Guzis via cctalk <
cctalk@classiccmp.org> escreveu:

> On 4/11/21 7:08 AM, D. Resor via cctalk wrote:
> > Does anyone recall what kind of hardware/software was used to read/write
> the
> > early Mitsubishi Melcard EPROM cards with the PCB edge connector
> contacts?
> >
> >  It was explained to me by someone that a EPROM programmer could be used,
> > however I've never seen a socket which fits the edge card connector of
> these
> > cards.
>
> I don't know if it's exactly what you're looking for, but there's a
> potload of information on Bitsavers, starting with PDF page 115:
>
>
> http://www.bitsavers.org/pdf/mitsubishi/Mitsubishi_VLSI_MOS_Memory_RAM_ROM_and_Memory_Cards_Jan91.pdf
>
> --Chuck
>
>


Re: Mitsubishi Melcard (edge connect type)

2021-04-11 Thread Chuck Guzis via cctalk
On 4/11/21 7:08 AM, D. Resor via cctalk wrote:
> Does anyone recall what kind of hardware/software was used to read/write the
> early Mitsubishi Melcard EPROM cards with the PCB edge connector contacts?
> 
>  It was explained to me by someone that a EPROM programmer could be used,
> however I've never seen a socket which fits the edge card connector of these
> cards.

I don't know if it's exactly what you're looking for, but there's a
potload of information on Bitsavers, starting with PDF page 115:

http://www.bitsavers.org/pdf/mitsubishi/Mitsubishi_VLSI_MOS_Memory_RAM_ROM_and_Memory_Cards_Jan91.pdf

--Chuck



Mitsubishi Melcard (edge connect type)

2021-04-11 Thread D. Resor via cctalk
Does anyone recall what kind of hardware/software was used to read/write the
early Mitsubishi Melcard EPROM cards with the PCB edge connector contacts?

 It was explained to me by someone that a EPROM programmer could be used,
however I've never seen a socket which fits the edge card connector of these
cards.

I've uploaded an image of the edge contact end of this type of card here:

http://www.hammondorganservice.com/downloads/images/melcard.jpg 

Seems these were also available in the SRAM variety as well.

Thanks
Don Resor









In search of RLX blade software

2021-04-11 Thread Camiel Vanderhoeven via cctalk
I’ve been given a couple of RLX blade server chassis loaded with blades (one 
with Transmeta Crusoe cpu’s, and one with Pentium III cpu’s). I hope you’ll 
allow me to count these as “vintage” because of their interesting origin: the 
Pentium III loaded chassis was part of a 768 node computer cluster at the 
Sanger Institute in the UK, and was used in the last stretch of the DNA 
sequencing computations for the Human Genome Project.

I’d like to build a compute cluster out of these, but I don’t have the rpm’s 
they supplied to customize Linux for their blades. Ideally, I’d hope to find a 
copy of their “Control Tower” blade management software, and their customized 
Linux installation images, but just the bare rpm’s would do for now. From the 
RLX platform guide, I’d hope to find:

kernel-*rlx*.i386.rpm
kernel-headers-*rlx*.i386.rpm
devfsd-*rlx*.i386.rpm
ucd-snmp-*rlx*.i386.rpm
net-snmp-*rlx*.i386.rpm
ucd-snmp-utils-*rlx*.i386.rpm
net-snmp-utils-*rlx*.i386.rpm
bootctl-*rlx*.i386.rpm
atftp-*rlx*.i386.rpm
lm_sensors-*-*rlx*.i386.rpm
lm_sensors-drivers-*-*rlx*.i386.rpm
lm_sensors-devel-*-*rlx*.i386.rpm
base-utils-*rlx*.i386.rpm
runctl-*rlx*.noarch.rpm
networkcfg-*rlx*.noarch.rpm
mgmtmode-*rlx*.noarch.rpm
namedcfg-*rlx*.noarch.rpm
dhcpdcfg-*rlx*.noarch.rpm
lilo-*rlx*.i386.rpm
grub-*rlx*.i386.rpm
rlx-clientpm-*rlx*.i386.rpm



This e-mail (including any attachments) may contain privileged, confidential, 
proprietary, private, copyrighted, or other legally protected information. The 
information is intended to be for the use of the individual or entity 
designated above. If you are not the intended recipient (even if the e-mail 
address above is yours), please notify us by return e-mail immediately, and 
delete the message and any attachments. Any disclosure, reproduction, 
distribution or other use of this message or any attachments by an individual 
or entity other than the intended recipient is prohibited.