Dell Dimension V333c & CTOS.

Please read the disclaimer first!

The gentle reader is reminded that a CTOS license would be required if you wanted to run CTOS on a PC.

Results of my expermenting with a Dell PC and CTOS.

CTOS III R1.3.1 wasn't able to correctly read the BIOS clock, it would set the clock back to the 1970's.  An s1.3.5x patch fixed this.

Was unable to get CTOS to boot a hard disk on the secondary IDE controller.  CTOS didn't support the second SCSI channel on an SGS7100 server either, so maybe it's a CTOS limitation?

I was only able to format the hard disk when it was the primary boot drive.  It could be the slave disk, but had to be selected as the boot drive in the BIOS.

CTOS correctly formatted the (1GB disk), and identified it as [D1].
(D0 was a DOS/Win95 disk).

The only problems I've found with the machine are:
* Celeron identified as 80486
* CTOS reported a Hardware ID (see this note)

The Hardware ID problem is significant as it could lead to BIOS corruption.  It would be prudent to remove the hardware id run files from a system if you were going to use it.
 
 

Disclaimer
This article is provided as is without any express or implied warranties.  While every effort has been taken to ensure accuracy of the information contained in this article, the author assumes no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein.
 

Dale 'Cat' Robinson - catfromdarwin@oocities.com
2 April 1999


This page hosted by  Get your own Free Home Page