DOS ain't dead

Does anyone have a copy of PC Doctor 3 or anything equivalent for DOS? I remember seeing the link once but I can't find it anymore.

> Does anyone have a copy of PC Doctor 3 or anything equivalent for DOS? I
> remember seeing the link once but I can't find it anymore.

PC-Doctor for DOS
HWiNFO (for DOS)
BTTR software: System information, benchmarks

I am talking about the free version that used to be downloadable from IBM (version 3 or something.) Does anyone even have a copy around? Thanks.

> I am talking about the free version that used to be downloadable from IBM
> (version 3 or something.) Does anyone even have a copy around? Thanks.

From what I have read IBM's version is produced by PC Doctor, Inc (as per earlier link). It also appears that it is licensed/included with the Hardware Management Console "HMC Recovery CDs", i.e. if you own an IBM server.

These links will return the manuals for IBM's version/relevant ftp links for your review:
Google: ibm.com PC Doctor
Google: ftp_software_ibm_com PC Doctor

I suspect you may be able to find an appropriate licensed verison under:
ftp://ftp.software.ibm.com/systems/support/
ftp://ftp.software.ibm.com/software/

I'm not that famliar with PC Doctor but would recommend Martin Malík (REALiX)'s HWiNFO (for DOS) as a good alternative particularly as unlike IBM's version there are no grey usage areas if you don't own IBM servers (I do).

There is also NSSI: http://www.navsoft.cz/products.htm

Ah thanks for the recommendations. I will try them out. I am talking about an older version that is completely free (I think it came in a 3 disk download version) and designed specifically for PC's.

I just tried HWINFO. Not bad except it requires 580K of free DOS conventional memory!?

PC Doctor 3.x had a detected many IBM PC specific features such as writing text via BIOS, DOS or video memory that seem to be missing from modern testers. Maybe I can dig it out from somewhere.

> I just tried HWINFO. Not bad except it requires 580K of free DOS
> conventional memory!?
I hadn't spotted that requirement. Although I use it to be honest I haven't tried it on any really old hardware/low spec machines etc.

> such as writing text via BIOS, DOS or video memory that seem
> to be missing from modern testers.
Interesting. Out of curiosity what is it that you are interested in testing? And why? I ask because I have written various old and new code which detects all sorts of text IO, e.g. is an ANSI.SYS compatible driver installed etc as part of a massive BBS door unit I wrote back in the 90's. I'm slowly working to unifying all sorts of code into RJDOS but in a modula way. That project remains my focus (and will do) and as I want RJDOS to be a shell which allows us to dig into a PC's setup to a certain extent I'm always interested in hearing of requirements. I'm not planning to add speed testing code though.