PDA

View Full Version : Plus Hardcard 20 revisited



Druid6900
May 3rd, 2014, 06:34 PM
Well, I have one of these things that a client wants me to get going for them and we know they are famous for NOT working after all this time.

Trixter says the ROM bits "evaporate" after a while and that may be.

On boot, it comes up with 1701 - Disk Controller #0 error, 1701 - Disk Controller #1 error.

Using a NEC DOS 3.3 bootable diskette and some Plus 40 software from Trixter, when I run the Divide.com software, it says there is no hardcard.

Now, in some of the threads about this beast, there are some mention of people having the disk set for it, but nothing actually shows up.

My question is; DOES anyone actually have dumps of this software and, if so, can I get them so I can tell the client, if necessary, that I tried everything?

TIA

Druid

modem7
May 3rd, 2014, 08:20 PM
On boot, it comes up with 1701 - Disk Controller #0 error, 1701 - Disk Controller #1 error.

Well, I have one of these things that a client wants me to get going for them and we know they are famous for NOT working after all this time.
Could be stiction. If you get desperate, try the stiction hints that have been mentioned in these forums.


Using a NEC DOS 3.3 bootable diskette and some Plus 40 software from Trixter, when I run the Divide.com software, it says there is no hardcard.
So, the question is, is that because of the fault, or because the Plus Hardcard 40 software is specifically looking for a Hardcard 40 (rhetorical question)?


Now, in some of the threads about this beast, there are some mention of people having the disk set for it, but nothing actually shows up.
My question is; DOES anyone actually have dumps of this software and, if so, can I get them so I can tell the client, if necessary, that I tried everything?
Back in 2009, Mike Brutman wrote,
Try this: http://www.brutman.com/plus_hardcard20.zip
It is an original diskette for this hard card. The label says "80286 Compatible Software and Hardcard 20 Installation Programs."

I've put a copy of that ZIP file at: http://www.minuszerodegrees.net/software/plus_hardcard20_disk.zip

I see an Epson document about the Hardcard 20 at https://files.support.epson.com/pdf/psb/psb.s-0035.pdf

Stone
May 4th, 2014, 03:09 AM
I've got a Quantum Hardcard EZ 170 MB if you're interested in that. It works great.

http://www.vintage-computer.com/vcforum/showthread.php?29567-Quantum-Hardcard-EZ-170-mb

Druid6900
May 5th, 2014, 06:02 AM
Could be stiction. If you get desperate, try the stiction hints that have been mentioned in these forums.


So, the question is, is that because of the fault, or because the Plus Hardcard 40 software is specifically looking for a Hardcard 40 (rhetorical question)?


Back in 2009, Mike Brutman wrote,
Try this: http://www.brutman.com/plus_hardcard20.zip
It is an original diskette for this hard card. The label says "80286 Compatible Software and Hardcard 20 Installation Programs."

I've put a copy of that ZIP file at: http://www.minuszerodegrees.net/software/plus_hardcard20_disk.zip

I see an Epson document about the Hardcard 20 at https://files.support.epson.com/pdf/psb/psb.s-0035.pdf

Well, since it has just been shipped to me from California, through two postal services, I'm guessing it's been banged around enough to take care of any stiction in a safe manner, but, I might baked it a bit :-)

I really don't know if it's a software problem (rhetorical answer....)

Yes, I saw that link to Mike's site, but, it was no longer operating.

Thanks for the file and the article, Modem7, I'll take a look at both and see what Idefiantlywith. I'll definatly report back on any result and will look for any further flashes of inspiration.

Druid6900
May 5th, 2014, 06:04 AM
I've got a Quantum Hardcard EZ 170 MB if you're interested in that. It works great.

http://www.vintage-computer.com/vcforum/showthread.php?29567-Quantum-Hardcard-EZ-170-mb

Thanks Stone.

If I am unable to repair it and the client still wants to persue it, I'll point him in your direction.

Druid6900
May 10th, 2014, 12:17 PM
Well, still no luck yet.

I think it might be, as has been mentioned, the ROMs.

However, I did find zips of the ROMs, but, I don't have the hardware to burn them.

In case anyone can use them, I'm uploading them here.

OK, I'm NOT uploading them here since they are too large. Anyone have a place where I can upload them?

Plush20A.zip is version 3.31 and is for the 1986 version of the Hardcard 20 and Plush20B.zip is version 5.91 and is for the 1987 version.

I also have a zip of the Plus Hardcard 20 Installation/Utility disk with zip and image versions.

I have the 3.31 version, just in case anyone wants to burn me a set :-)

Druid

modem7
May 10th, 2014, 03:30 PM
However, I did find zips of the ROMs, but, I don't have the hardware to burn them.
In case anyone can use them, I'm uploading them here.
OK, I'm NOT uploading them here since they are too large. Anyone have a place where I can upload them?
Plush20A.zip is version 3.31 and is for the 1986 version of the Hardcard 20 and Plush20B.zip is version 5.91 and is for the 1987 version.
Those are sure to be the same ones at http://ibm-pc.org/firmware/other/plus%20hardcard/?ND
Because they may be useful for others, I will add a pointer to those at http://www.minuszerodegrees.net/rom/rom.htm


I think it might be, as has been mentioned, the ROMs.
One of the two ROMs (type 2764) is the BIOS ROM.
That one at least is probably good, because a look in HC20U115.BIN within PLUSH20A.ZIP confirms that it is what displays the "Disk Controller #0 error".
A CRC comparison of HC20U115.BIN to a file copy of the BIOS ROM in your card would prove whether the BIOS ROM is corrupt or not.
The BIOS ROM appears in your computer's address space, and so for the comparison, you could use something like DEBUG (or Mike Brutman's ROM capture tool) to create a file copy of the card's BIOS ROM.

The second ROM (type 27128) will not be appearing in your computer's address space. What could be done to get a file copy (for comparison purposes) would be to put that ROM into the BIOS ROM socket of a card that accepts a 27128.

Chuck(G)
May 10th, 2014, 03:58 PM
You can certainly post the ROM images here--they're miniscule. What you can't post is the 600+K JPEG.

Druid6900
May 11th, 2014, 05:54 AM
Those are sure to be the same ones at http://ibm-pc.org/firmware/other/plus%20hardcard/?ND
Because they may be useful for others, I will add a pointer to those at http://www.minuszerodegrees.net/rom/rom.htm

Yup, those would be the ones. I didn't want to mention where I got them in case whomever owns the site doesn't want links to it.
Thanks for the link Modem7.



One of the two ROMs (type 2764) is the BIOS ROM.
That one at least is probably good, because a look in HC20U115.BIN within PLUSH20A.ZIP confirms that it is what displays the "Disk Controller #0 error".
A CRC comparison of HC20U115.BIN to a file copy of the BIOS ROM in your card would prove whether the BIOS ROM is corrupt or not.
The BIOS ROM appears in your computer's address space, and so for the comparison, you could use something like DEBUG (or Mike Brutman's ROM capture tool) to create a file copy of the card's BIOS ROM.

The second ROM (type 27128) will not be appearing in your computer's address space. What could be done to get a file copy (for comparison purposes) would be to put that ROM into the BIOS ROM socket of a card that accepts a 27128.

A good suggestion, and maybe someone will, for interest's sake, but, I'm just going to have the set burned because of the age of these chips.

The controller and drive both seem to be functioning correctly, so, since the firmware 'evaporation' seems to be a common malady of these drive, chances are good that this will fix it up. I'm sure the client will be happy.

Druid6900
May 11th, 2014, 06:00 AM
I would have just uploaded the .bin files themselves, but the zip contains useful information such as a picture of the card and the device they were burned with.

With Modem7 offering a link to the same files, it works out nicely.

PCFreek
September 30th, 2014, 02:36 PM
I'm just going to have the set burned because of the age of these chips.

The controller and drive both seem to be functioning correctly, so, since the firmware 'evaporation' seems to be a common malady of these drive, chances are good that this will fix it up. I'm sure the client will be happy.

I realize that this thread is fairly old, but... Did burning the ROM chips correct your problem? I have the same hardcard with the same "Disk Controller #0 Error"......