Hello,
I am having some trouble with my system and it logging errors during any ROM use. My system is setup up in the current manner:
IDE Primary Master: Seagate Cuda IV (40GB)
IDE Primary Slave: Toshiba 12xDVD-ROM - transfer mode UDMA
IDE Secondary Master: Seagate Cuda IV (80GB) - transfer mode UDMA
IDE Secondary Slave: Plextor 12x10x24 CD-WR - transfer mode PIO
SCSI Adapter: Adaptec 19160
SCSI Drive: Seagate X15 36LP (18GB) - transfer mode Ultra160
Boot sequence: FDD, SCSI, CDROM
I have the two IDE HDD's in removable bays and can turn off power to those HDD's depending upon the situation.
I run the computer in the following fashion:
OFF - IDE Primary Master: Seagate Cuda IV (40GB)
ON - IDE Primary Slave: Toshiba 12xDVD-ROM - transfer mode UDMA
ON - IDE Secondary Master: Seagate Cuda IV (80GB) - transfer mode UDMA
ON - IDE Secondary Slave: Plextor 12x10x24 CD-WR - transfer mode PIO
when booting to the X15 (the system is dual boot between the X15 and the 40GB IDE when it is turned on). When booting to the 40GB IDE I have the settings as follows.
ON - IDE Primary Master: Seagate Cuda IV (40GB)
ON - IDE Primary Slave: Toshiba 12xDVD-ROM - transfer mode UDMA
OFF - IDE Secondary Master: Seagate Cuda IV (80GB) - transfer mode UDMA
ON - IDE Secondary Slave: Plextor 12x10x24 CD-WR - transfer mode PIO
This is to conserve energy and hardware life, now to my problem when booting to the X15 everything seems and looks fine as long as I am not using the ROM drives no errors or anything. However as soon as I try and install a program from either the Toshiba or Plextor the error pile up quick. There are numerous Event ID: 11 errors stating that "The driver detected a controller error on \Device\Harddisk0\DR0" and just a couple Event ID: 5 error mixed in saying "A parity error was detected on \Device\Ide\IdePort1."
I do not know what could be the problem the 80GB IDE works fine and has no problems but these errors keep pointing to it, I know that this 80GB IDE drive is not the problem because I just purchased it new and does not produce any errors as long as no ROM activity is taking place.
I am having some trouble with my system and it logging errors during any ROM use. My system is setup up in the current manner:
IDE Primary Master: Seagate Cuda IV (40GB)
IDE Primary Slave: Toshiba 12xDVD-ROM - transfer mode UDMA
IDE Secondary Master: Seagate Cuda IV (80GB) - transfer mode UDMA
IDE Secondary Slave: Plextor 12x10x24 CD-WR - transfer mode PIO
SCSI Adapter: Adaptec 19160
SCSI Drive: Seagate X15 36LP (18GB) - transfer mode Ultra160
Boot sequence: FDD, SCSI, CDROM
I have the two IDE HDD's in removable bays and can turn off power to those HDD's depending upon the situation.
I run the computer in the following fashion:
OFF - IDE Primary Master: Seagate Cuda IV (40GB)
ON - IDE Primary Slave: Toshiba 12xDVD-ROM - transfer mode UDMA
ON - IDE Secondary Master: Seagate Cuda IV (80GB) - transfer mode UDMA
ON - IDE Secondary Slave: Plextor 12x10x24 CD-WR - transfer mode PIO
when booting to the X15 (the system is dual boot between the X15 and the 40GB IDE when it is turned on). When booting to the 40GB IDE I have the settings as follows.
ON - IDE Primary Master: Seagate Cuda IV (40GB)
ON - IDE Primary Slave: Toshiba 12xDVD-ROM - transfer mode UDMA
OFF - IDE Secondary Master: Seagate Cuda IV (80GB) - transfer mode UDMA
ON - IDE Secondary Slave: Plextor 12x10x24 CD-WR - transfer mode PIO
This is to conserve energy and hardware life, now to my problem when booting to the X15 everything seems and looks fine as long as I am not using the ROM drives no errors or anything. However as soon as I try and install a program from either the Toshiba or Plextor the error pile up quick. There are numerous Event ID: 11 errors stating that "The driver detected a controller error on \Device\Harddisk0\DR0" and just a couple Event ID: 5 error mixed in saying "A parity error was detected on \Device\Ide\IdePort1."
I do not know what could be the problem the 80GB IDE works fine and has no problems but these errors keep pointing to it, I know that this 80GB IDE drive is not the problem because I just purchased it new and does not produce any errors as long as no ROM activity is taking place.
Facebook
Twitter