
6. Wanted
Click here to contact us.
- Information about bugs in the program (we found many, but we don't have
hundreds of computers to test everything !), wrong and inexact test results,
suggestions for improvement.
- Computers with uncommon hard- and software, e.g.
RapidCAD or IBM386SLC CPUs, SCSI
controllers, old memory managers (QEMM 5, 386Max, ...), ...
- Documents about Disney Sound Source
If you are able to start Windows from the DOS prompt but don't understand
the following: don't care, this are terms that are only understood by those who
really know much about the inner parts of computers.
Some CPUs can be distinguished by the reset ID, but as this ID code is not
always available, I'm looking for other routines to separate these CPUs.
- Separation 386SX/i386SL
- Detection of 38600SX, 38605SX, 38600DX, 38605DX (all manufctured by Chips &
Technologies)
- Routine that discriminates more FPU
manufacturers than IIT and Cyrix (e.g. ULSI).
- Routine for Weitek Abacus x167 and Cyrix EMC87 FPU
detection.
- All PCI Vendor IDs that I don't know. Start INSIDE with the switch
/PCIVendors to see which IDs are already
included in INSIDE.
- Routine for detection of Gravis UltraSound without "blind" writes
to the GUS memory, hoping that no other hardware behaves strange.
- All information (documents, text files, ...) concerning the specified and
not specified PC hardware.
- Routine for identification of network cards, especially the NE2000 card
- All you can get to know about a PC's inside without looking in ...
Borland/Turbo Pascal and assembler routines are no problem for me, C/C++
routines are a little bit more difficult for me to understand (depends on the
programming style).
Documentation: Copyright © 1997 by Hendrik Foken
Program:
Copyright © 1997 by Alexander Foken