25xtreme error

[barrat1]

I have a brand new western digital 80 gigabyte 5400 rpm hard drive I am trying to load 25xtreme on it. I have tried all combonations of how the dirve is hooked up (Pri master/slave and sec master/slave). I keep on getting an error "unable to open destination device for writing". I boot up from the cd and login. Then I execute the 25xtreme program. It starts up and asks the questions. It then comes to the point about asking for the hd location and I input the proper value here according to how the drive is hooked up. It then tells me that it is unable to open destination device for writing. I used quanlock program to see if the HD was lock but I still get the error I used two different computers and ISO image. Am I missing a step somewhere:confused:

[BubbleLamp]

The target drive cannot be Pri Master.

If it was Pri Slave, you'd need another device on the chain to be master, did you have another drive attached?

Same thing if it was Sec Slave. IDE requires one of the devices to be master, you can't just have a slave.

Pri Slave=hdb
Sec Master=hdc
Sec Slave=hdd

Good luck.

[barrat1]

ok I have tried it in two computers, I have had the HD set as primary slave, sec. master and sec slave and I have had a second HD in the computer and tried all combination. I still get this error

restore failed: unable to open destination device for writing

cannot continue--processing aborted

I also tried formating the HD

one of my computers is a compaq 5461 with 256 ram the other is a Athlon 1900xp on a ASUS A7v266-e with raid with 256 ddr

I have also down loaded the 25xtreme ISO two times and burn it seems to be working.

I have also checked the BIOS on my 1900xp to make sure the HD are set right.

I did unplug one CD-ROM drive so I have only one on the computers. I also tried different HD. When I log in I hit enter and then type 25xtreme. I must be doing somthing easy wrong

[DarkWing]

You do not need a ide master on the cable to set one as slave unless you use cable select. Do not use cable select, hard set your drives as either master or slave.

It is most likely your cd. Do not use Nero to burn the cd, use CDRWin or Adaptec.

As bubblelamp stated, do not place a hard drive on primary slave, the cdrom can go there no problem.

Good luck.

[BubbleLamp]

Originally posted by DarkWing
You do not need a ide master on the cable to set one as slave unless you use cable select. Do not use cable select, hard set your drives as either master or slave.

It is most likely your cd. Do not use Nero to burn the cd, use CDRWin or Adaptec.

As bubblelamp stated, do not place a hard drive on primary slave, the cdrom can go there no problem.

Good luck.

Not to start a p***ing match, but unless they changed the IDE spec, a chain needs a master to work, since only one unit controls the chain. If a drive is set to slave, it's going to be waiting for commands from the master, no? :confused:

[barrat1]

Ok I burn a new cd with CDRWIN V4 and I used Easy CD creator 5 I still get the same error in both computers with all combination IDE

[superzap]

It could be the WD drive. They can be problematic. What is the suffix in the part number? JB has a 8MB buffer and the BB has a 2MB. The JB models won't work in a UTV but I'm not sure about the DTiVo.
Does windoze recognize the drive? And I guess you tried different combinations of the HD jumpers?

[BubbleLamp]

If you press SHIFT and the up arrow you will be able to see the boot messages. See if the system is seeing and identifying your drive at all.

What do you have the BIOS set for for the drive? If it's AUTO, then does the size seem right in the BIOS? Have you tried setting the drive type to none, and letting the Linux probe the hardware?

[barrat1]

When I turned off AUTO in BIOS I still get the error. When AUTO is on, the HD comes up right. When the HD is set as primary slave and I boot from the CD the HD comes up as hdf. I do not know if this could be the problem.

[DarkWing]

I really hate to disagree with you Bubblelamp, you've helped me so much, and I too don't want to get in a pi**ing match :)

Perhaps a third person can break the tie, hehe

[BubbleLamp]

Originally posted by barrat1
When I turned off AUTO in BIOS I still get the error. When AUTO is on, the HD comes up right. When the HD is set as primary slave and I boot from the CD the HD comes up as hdf. I do not know if this could be the problem.

Bingo! How the heck is it coming up as hdf? Do you have 2 separate IDE controllers? (A total of 4 cable connectors.)

[T_RJ]

Use your ASUS A7v266-e but remove the raid card.

Hang your wd on the secondary Ide controller as master put the CD ROM on the primary controller as slave
.
Boot the machine and go in to Setup reset everything to default values.

Set the pc to boot from cdrom.


reboot with the xtreme cd.

Post your results.

[BubbaJ]

3rd person breaking pissing match:

The BIOS can be configured in such a manner as to allow a drive set to slave to work without a master. Basically, the master just gets to decide when the slave is allowed to talk. If the BIOS determines that there is no master, ovbiously, it can talk to the slave at will.

[BubbleLamp]

Bubba, you know I hold you in the highest esteem. So while it's technically true the BIOS can talk to the drive, the IDE spec requires a master on the bus.

Drives are selected by the DRV bit in the Drive/Head Register (see 7.2.8), and by a jumper or switch on the drive designating it as either a Drive 0 or as Drive 1. When DRV=0, Drive 0 is selected. When DRV=1, Drive 1 is selected. When drives are daisy chained, one shall be set as Drive 0 and the other as Drive 1. When a single drive is attached to the interface it shall be set as Drive 0.

These are the parts that makes it impractical for a single slave to work:

6.3.4 DASP- (Drive active/drive 1 present)
This is a time-multiplexed signal which indicates that a drive is active, or that Drive 1 is present. This signal shall be an open collector output and each drive shall have a 10K ohm pull-up resistor. During power on initialization or after RESET- is negated, DASP- shall be asserted by Drive 1 within 400 msec to indicate that Drive 1 is present. Drive 0 shall allow up to 450 msec for Drive 1 to assert DASP-. If Drive 1 is not present, Drive 0 may assert DASP- to drive an activity LED. DASP- shall be negated following acceptance of the first valid command by Drive 1 or after 31 seconds, whichever comes first. Any time after negation of DASP-, either drive may assert DASP- to indicate that a drive is active.

6.3.13 PDIAG- (Passed diagnostics)
This signal shall be asserted by Drive 1 to indicate to Drive 0 that it has completed diagnostics. A 10K ohm pull-up resistor shall be used on this signal by each drive. Following a power on reset, software reset or RESET-, Drive 1 shall negate PDIAG- within 1 msec (to indicate to Drive 0 that it is busy). Drive 1 shall then assert PDIAG- within 30 seconds to indicate that it is no longer busy, and is able to provide status. If Drive 1 is present, then Drive 0 shall wait for up to 31 seconds from power-on reset, software reset or RESET- for Drive 1 to assert PDIAG-. If Drive 1 fails to assert PDIAG-, Drive 0 shall set bit 7 to 1 in the Error Register to indicate that Drive 1 failed. After the assertion of PDIAG-, Drive 1 may be unable to accept commands until it has finished its reset procedure and is Ready (DRDY=1). Following the receipt of a valid Execute Drive Diagnostics command, Drive 1 shall negate PDIAG- within 1 msec to indicate to Drive 0 that it is busy and has not yet passed its drive diagnostics. Drive 1 shall then assert PDIAG within 5 seconds to indicate that it is no longer busy, and is able to provide status. Drive 1 should clear BSY before asserting PDIAG-. If Drive 1 is present then Drive 0 shall wait for up to 6 seconds from the receipt of a valid Execute Drive Diagnostics command for Drive 1 to assert PDIAG-. If Drive 1 fails to assert PDIAG-, Drive 0 shall set bit 7 to 1 in the Error Register to indicate that Drive 1 failed. If DASP- was not asserted by Drive 1 during reset initialization, Drive 0 shall post its own status immediately after it completes diagnostics, and clear the Drive 1 Status Register to 00h. Drive 0 may be unable to accept commands until it has finished its reset procedure and is Ready (DRDY=1).

I just took a bootable drive with WinXP on it and jumpered it as master. As expected, it booted. I jumpered it for slave, and I get 'No boot device available'. Now since all the signals go to both drives on the chain, the only real problem is that there is no master to tell the controller that the chain is ready.

[DarkWing]

Don't do this with XP, 2000 or NT, they don't like to be moved.

[BubbaJ]

Most of the computers I have put together since 1998 support recognising and booting from slaves. It is in fact the default configuration that I use. (it makes it easy to stick a diagnostic drive configured as master in and not have to do anything in the bios for it to boot)