Timothy Daniels wrote
Rod Speed non-sequitured

Lying, as always.

....have fun explaining why ALL the documentation
of the ARC path naming convention fails to mention the
hard drive boot order at all when documenting the rdisk()
parameter. There has GOT to be a reason for that.

AND its a stupid way to implement a system anyway
because the boot.ini file would have to be changed
when the boot order is changed.

ALL the evidence points to the fact that its a terminal
stupidity that has been perpetrated in the Phoenix bios
and that it doesnt get mentioned just because the phoenix
bios is by far the least commonly used of the big 3.

All I did was report reality.

No you didnt. You reported what YOU see on a badly implemented
system and claimed that that proved that the rdisk() param is the boot
drive order number on all systems out there. That is just plain wrong.

What does it matter what some obscure specification says?

It matters because it proves that your claim that the rdisk() parameter
is ALWAYS the boot order sequence number is just plain wrong when
that spec for the boot.ini file, written by the designers of that boot.ini
file dont even mention the boot order sequence number with rdisk()

Do you run a spec or a PC?

Never ever could bull**** its way out of a wet paper bag.