Re: Boot.ini question
- From: "Rod Speed" <rod.speed.aaa@xxxxxxxxx>
- Date: Fri, 3 Feb 2006 10:05:32 +1100
Timothy Daniels <TDaniels@xxxxxxxxxxxxx> lied
Rod Speed wrote
Timothy Daniels <TDaniels@xxxxxxxxxxxxx> lied
Forget it. Rod's motive is to obuscate.
Lying, as always.
That's why the above paragraph is gibberish
You did manage to work out what I was proposing, liar.
- it's meant to confuse, not clarify. This is evident from his
insistance that one boot.ini file be used for the entire experiment.
What a terminal fuckwit you have always been, child.
If one were to change the boot order such that a different
hard drive moved to the head of the hard drive boot order,
I CLEARLY SAID THAT THE DRIVE AT THE TOP OF THE
BOOT ORDER SHOULD NOT BE CHANGED AND THAT
ONLY THE DRIVES BELOW THAT SHOULD BE SWAPPED.
And that is exactly what I did.
Lying, as always. You not only had a boot.ini on EVERY drive,
you ALSO changed the drive at the top of the boot list.
Breathe deeply, count to 10, and read the description of the experiment
again.
Dont need to, it stays *** no matter how often its read.
And its better to hold your breath when reading *** too.
You'll see that for each of the 3 HDs, I used the same boot.ini file to
boot each of the 3 HDs.
Pity I said to have JUST ONE BOOT.INI FILE ON THE DRIVE
THAT STAYS AT THE TOP OF THE LIST AND ISNT EVER
SELECTED IN THE MENU THE BOOT.INI PRESENTS.
Then I rearranged the HDs below the head of the hard drive boot order and
re-did the procedure. Then,
in changing the head of the hard drive boot order to do the whole
process over again, your proposed scenario was implemented.
IOW, your proposed experiment was a subset of what I did,
Yes, but I clearly didnt specify that subset to
CONFUSE anyone, you silly little pathological liar.
but you don't recognize that what I did was just your own proposed
configuration and procedure done on a larger scale.
Irrelevant to your lie that my test was to CONFUSE.
IOW, your own proposed experiment proved you to be wrong.
No it didnt with your pig ignorant claim that the rdisk() param
ALWAYS refers to the boot order sequence number.
It certainly does apply to that very badly designed steaming turd
you are using if you arent actually lying about what gets booted,
but you havent proven a damned thing about any other system.
And since you are clearly a pathological liar, I wouldnt believe
what you claim you are seeing on that system of yours either.
I'd want to see someone else agree that they get that fucked
result on another Dell or Phoenix biosed system first.
.
- References:
- Re: Boot.ini question
- From: Antoine Leca
- Re: Boot.ini question
- From: Timothy Daniels
- Re: Boot.ini question
- From: Rod Speed
- Re: Boot.ini question
- From: Timothy Daniels
- Re: Boot.ini question
- Prev by Date: Re: SATA RAID5 disk replacement: same type of disk?
- Next by Date: Re: Boot.ini question
- Previous by thread: Re: Boot.ini question
- Next by thread: Re: Boot.ini question
- Index(es):
Loading