Boot.ini question

[Gerhard Fiedler]

You want me to spell it out for you?

If that would be possible... ?!?

 

[Gerhard Fiedler]

I am standing on my original point: it varies!

And I'm with you 100% on this

Gerhard

 

[Rod Speed]

Rod Speed wrote

Exactly why you shouldn't have quoted Microsoft's ARC path documents -
it's OBSOLETE!

No it isnt. AND NO ONE ELSE'S DOCUMENTIONATION OF
THE ARC PATH NAMING CONVENTION EVEN MENTIONS
ANY HARD DRIVE BOOT ORDER LIST EITHER.

There might just be a damned good reason for that, child.

AND you havent even established that getting the ordinal for
the rdisk() param from the hard drive boot order list is seen
with ANYTHING except that steaming turd of a bios in that
particular Dell system you are using yourself. And in fact
Antoine has rubbed your nose in the FACT that it isnt with
the Dell system he tried it with as well.

AND its a terminally stupid way to determine the ordinal
for the rdisk() param ANYWAY, because that means that
the rdisk() param in boot.ini cant be used WHEN THE DRIVE
DOESNT APPEAR IN THE HARD DRIVE BOOT ORDER LIST
AND YOU WANT TO BE ABLE TO BOOT AN OS FROM THAT.

That is left open to interpretation by manufacturers such as Dell, to
BIOS producers such as Phoenix Technologies, and to ROM chip producers
such as Intel.

Wrong again. The detail just isnt spelt out explicitly in THAT
particular KB article which has a VERY limited purpose. It
aint anything like the definitive statement of the ARC path
naming convention used in boot.ini, let alone saying anything
about who gets to determine how the ordinal is determined.
http://support.microsoft.com/kb/102873/EN-US/
has a much clearer statement about the rdisk() parameter and it says
[...........]
Z is the ordinal for the disk on the adapter and is usually a number
between 0 and 3.
---------------my comment
This is the rdisk parameter and that clearly says DISK ON THE ADAPTER
and says nothing about any hard drive boot order list what so ever.
---------------my comment

And the Microsoft document clearly states that the document
applies to:

• Microsoft Windows NT Advanced Server 3.1
• Microsoft Windows NT Server 3.5
• Microsoft Windows NT Server 3.51
• Microsoft Windows NT Server 4.0 Standard Edition
• Microsoft Windows NT Workstation 3.1
• Microsoft Windows NT Workstation 3.5
• Microsoft Windows NT Workstation 3.51
• Microsoft Windows NT Workstation 4.0 Developer Edition
• Microsoft Windows NT Advanced Server 3.1

Pity about
http://www.microsoft.com/resources/...0/server/reskit/en-us/prork/prbd_std_ccef.asp
which even someone as stupid as you should be able to work
out actually applys to 2K server, you silly little ****wit child.

Pity about
http://www.microsoft.com/resources/...Windows/XP/all/reskit/en-us/prmc_str_masc.asp
which even someone as stupid as you should be able to
work out actually applys to XP, you silly little ****wit child.

The document is as obsolete as you are

Pity you cant cite even a single document from MS or anyone else
that even mentions anything about the rdisk() parameter and any
hard drive boot list ordinal, and that you havent even established
that that is the way its done in anything but that particular steaming
turd of a bios in that particular Dell system you are using yourself.

Antoine has rubbed your silly little nose in the
FACT that it isnt even universal with Dells.

Keep desperately digging, child, you'll be out in china any day now, again.

 

[Timothy Daniels]

Timothy Daniels wrote:

In the Microsoft document "How to Determine the ARC Path"
(http://support.microsoft.com/default.aspx?scid=kb;en-us;155222)
it is stated:


"A typical ARC path might be:


multi(0)disk(0)rdisk(0)partition(2)\WINNT="My Server 4.0"


"The rdisk parameter is defined as Harddisk<X> on the
TargetDevice line, where <X> is a variable that represents
the drive ordinal. Note that the rdisk parameter is not used
when SCSI replaces multi in the ARC path."


Clearly, "rdisk()" refers to the position of the physical hard,
but it does NOT state how that position (i.e. the "drive ordinal")
is derived.


Yes, but the boot order list doesnt even get a mention, and when the
ARC path naming convention originated at a time when there wasnt
even a hard drive boot order list in most if any bios, it should be
obvious to even someone as stupid as you that it was never intended
to be the ordinal in the hard drive boot order list that didnt even exist.

Exactly why you shouldn't have quoted Microsoft's ARC path
documents - it's OBSOLETE!

That is left open to interpretation by manufacturers such as Dell, to BIOS producers such as Phoenix Technologies, and to
ROM chip producers such as Intel.


Wrong again. The detail just isnt spelt out explicitly in THAT
particular KB article which has a VERY limited purpose. It
aint anything like the definitive statement of the ARC path
naming convention used in boot.ini, let alone saying anything
about who gets to determine how the ordinal is determined.

http://support.microsoft.com/kb/102873/EN-US/
has a much clearer statement about the rdisk() parameter and it says

[...........]

Z is the ordinal for the disk on the adapter and is usually a number between 0 and 3.

---------------my comment
This is the rdisk parameter and that clearly says DISK ON THE ADAPTER
and says nothing about any hard drive boot order list what so ever.
---------------my comment

And the Microsoft document clearly states that the document
applies to:

• Microsoft Windows NT Advanced Server 3.1
• Microsoft Windows NT Server 3.5
• Microsoft Windows NT Server 3.51
• Microsoft Windows NT Server 4.0 Standard Edition
• Microsoft Windows NT Workstation 3.1
• Microsoft Windows NT Workstation 3.5
• Microsoft Windows NT Workstation 3.51
• Microsoft Windows NT Workstation 4.0 Developer Edition
• Microsoft Windows NT Advanced Server 3.1


The document is as obsolete as you are, sock puppet.

*TimDaniels*

Try this one.
http://www.microsoft.com/resources/...Windows/XP/all/reskit/en-us/prmc_str_masc.asp

Exactly! The document *still* says nothing about how the "rdisk()"
ordinal is to be determined. Here is what it says:

"Y Specifies a physical hard disk attached to drive controller W.
For ATA controllers, this number is typically between 0 and 3.
For SCSI controllers, this number is typically between 0 and 7,
or 0 and 15, depending on the adapter type. The first valid
number is 0."

So, given that and previous vacuums, Phoenix and Dell gave
it a meaning that made sense, met Microsoft's vague requirements,
and which was useable and convenient.

*TimDaniels*

 

[Rod Speed]

Rod Speed wrote

What MS intended in the misty past is that "rdisk()" specify
a hard drive and that it's related to some "adapter ordinal".
It doesn't say how that ordinal is to be determined.

Lying, again. MS actually uses the description
'Z is the ordinal for the disk on the adapter'

Even someone as stupid as you should be able to
work out that there is no mention what so ever of
any hard drive boot order list or any ordinal IN THAT.

Since then, Phoenix and/or Dell decided that the ordinal would be
thehard drive boot order

You aint even established that when Antoine has rubbed
your nose in the fact that it isnt in a different Dell system.

- which in the *default* case is derived from the IDE channel no. and
the Master/Slave settings of the hard drives.

Pity that the default is completely irrelevant when the user
can change the order in the boot order list. That is the
WHOLE POINT OF HAVING A BOOT ORDER LIST.

AND that determining the ordinal from the boot order list
requires that the boot.ini be edited when any change is
made to the location of a particular drive in that list.

AND that when the ordinal is determined from the hard
drive boot order list, you cant even have a reference to
a drive WHICH ISNT IN THE BOOT ORDER LIST, so
you cant boot from it using boot.ini

It makes no sense to bind one's thinking and
expectations to vague and obsolete documents.

Nothing obsolete about the XP documentation
of the ARC path naming convention, liar.

Time and technology move on,

And only a terminal ****wit determines the ordinal for the
rdisk() param from the hard drive boot order list for the
reasons listed above, you silly little pig ignorant clown.

 

[Rod Speed]

Huh?

Village eejut mode baits no hooks, ****wit.

Reams of puerile attempts at a troll that fools
absolutely no one at all, flushed where they belong.

 

[Rod Speed]

Exactly. I'm so glad you agree with me.

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

Thanks Roddles, for helping debunk Fiddlers 'point' with us.

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

 

[Timothy Daniels]

"Gerhard Fiedler" faked it:

Tim didn't say "on /my/ machine, the rdisk number seems to be
equivalent to the position in the hard disk boot order list" -- he
claims this to be the case on /all/ machines. Which I seriously
doubt, and it seems I'm not alone with this.

On Feb 1, in the thread "Boot.ini question", I posted:

"ABSTRACT

"This experiment shows that the Phoenix Technologies BIOS
exposes the hard drive boot order to ntldr such that the para-
meter "rdisk(x)" in the boot.ini file corresponds to the hard
drive having a displacement "x" from the head of the hard
drive boot order, where "x" is a positive integer starting with 0.

"HARDWARE

"Dell Dimension XPS-R450 with a Phoenix Tech BIOS,"


On Feb 2, in the thread "meaning of 'rdisk()' in boot.ini file",
I posted:

"ABSTRACT

"This investigation shows that the "rdisk()" parameter
in the boot.ini file represents a hard drive in terms of
its displacement from the head of the hard drive boot order
in the BIOS. The value of n in "rdisk(n)" expresses this
displacement, where n is an integer value starting with 0,
and where "rdisk(0)" represents the hard drive which is at
the head of the hard drive boot order, i.e. the hard drive
at zero displacement from the head of the hard drive boot
order. The BIOS used in the investigation was the Phoenix
Technologies BIOS as supplied in Dell Dimension desktop
PCs.

"HARDWARE

"Dell Dimension XPS-R450 with a Phoenix Tech BIOS,"


Those are very clear statements of my position, having far
more clarity than those of anyone else in the history of this
newsgroup. No one has yet matched them in thoroughness
or clarity of methodology. If they don't apply to all Dell
desktop PCs in the last 5 years, let someone show it with
equal clarity.

*TimDaniels*

 

[Timothy Daniels]

"Rod Speed" strained:

AND NO ONE ELSE'S DOCUMENTIONATION OF
THE ARC PATH NAMING CONVENTION EVEN MENTIONS
ANY HARD DRIVE BOOT ORDER LIST EITHER.

There might just be a damned good reason for that, child.

Yes, of course. Microsoft left it up to the BIOS producers
to define how the "adapter ordinal" is determined.

AND its a terminally stupid way to determine the ordinal
for the rdisk() param ANYWAY, because that means that
the rdisk() param in boot.ini cant be used WHEN THE DRIVE
DOESNT APPEAR IN THE HARD DRIVE BOOT ORDER LIST
AND YOU WANT TO BE ABLE TO BOOT AN OS FROM THAT.

Stupid is as stupid does. Since you don't *know* enough
to use the method, you don't use it. But Dell and Phoenix
Technologies figured that there existed a smarter brand of
user who would like the added flexibility and convenience.
I've reported my findings for *them*, not worn out sock
puppets.

*TimDaniels*

 

[Timothy Daniels]

Lying, again. MS actually uses the description
'Z is the ordinal for the disk on the adapter'

You're funny. Now define "ordinal for the disk on the adapter".

*TimDaniels*

 

[Timothy Daniels]

.... determining the ordinal from the boot order list
requires that the boot.ini be edited when any change is
made to the location of a particular drive in that list.

So? Removing the drive at the head of the hard drive
boot order requires editing, too, in your system,
because that's where your one and only boot.ini file
is.
If you have a boot.ini file in the secondary hard drive
that is appropriate if that hard drive is at the head
of the hard drive boot order and the "rdisk()" ordinal,
depends on the position in the hard drive boot order,
no editing is necessary when the primary hard drive
is disconnected or fails. It even allows one to have
entries with identical sets of ARC paths in several
partitions among several hard drives - any of them
would do for booting. You just have to know where
the partition you want to boot is. But of course, that
is too stressful for you to learn.

Your methods were learned in pre-MSDOS days when
you went in for remedial training, sock puppet. It's time
to reform your ossified ways.

*TimDaniels*

 

[Rod Speed]

:

Timothy Daniels wrote:

In the Microsoft document "How to Determine the ARC Path"
(http://support.microsoft.com/default.aspx?scid=kb;en-us;155222)
it is stated:


"A typical ARC path might be:


multi(0)disk(0)rdisk(0)partition(2)\WINNT="My Server 4.0"


"The rdisk parameter is defined as Harddisk<X> on the
TargetDevice line, where <X> is a variable that represents
the drive ordinal. Note that the rdisk parameter is not used
when SCSI replaces multi in the ARC path."


Clearly, "rdisk()" refers to the position of the physical hard,
but it does NOT state how that position (i.e. the "drive
ordinal") is derived.


Yes, but the boot order list doesnt even get a mention, and when
the ARC path naming convention originated at a time when there wasnt
even a hard drive boot order list in most if any bios, it should be
obvious to even someone as stupid as you that it was never intended
to be the ordinal in the hard drive boot order list that didnt
even exist.




Exactly why you shouldn't have quoted Microsoft's ARC path
documents - it's OBSOLETE!


That is left open to interpretation by manufacturers such as
Dell, to BIOS producers such as Phoenix Technologies, and to ROM
chip producers such as Intel.


Wrong again. The detail just isnt spelt out explicitly in THAT
particular KB article which has a VERY limited purpose. It
aint anything like the definitive statement of the ARC path
naming convention used in boot.ini, let alone saying anything
about who gets to determine how the ordinal is determined.

http://support.microsoft.com/kb/102873/EN-US/
has a much clearer statement about the rdisk() parameter and it
says [...........]

Z is the ordinal for the disk on the adapter and is usually a
number between 0 and 3. ---------------my comment
This is the rdisk parameter and that clearly says DISK ON THE
ADAPTER and says nothing about any hard drive boot order list what so
ever.
---------------my comment



And the Microsoft document clearly states that the document
applies to:

• Microsoft Windows NT Advanced Server 3.1
• Microsoft Windows NT Server 3.5
• Microsoft Windows NT Server 3.51
• Microsoft Windows NT Server 4.0 Standard Edition
• Microsoft Windows NT Workstation 3.1
• Microsoft Windows NT Workstation 3.5
• Microsoft Windows NT Workstation 3.51
• Microsoft Windows NT Workstation 4.0 Developer Edition
• Microsoft Windows NT Advanced Server 3.1


The document is as obsolete as you are, sock puppet.

Try this one.
http://www.microsoft.com/resources/...Windows/XP/all/reskit/en-us/prmc_str_masc.asp

Exactly!

Fraid not. Pity it blows your silly claim that the documentation
is OBSOLETE, completely out of the water, liar.

The document *still* says nothing about how the "rdisk()" ordinal is to
be determined.

Pity other MS documentation does, you pathetic excuse for a bullshit
artist.
http://www.google.com/search?as_q=rdisk+&as_epq=disk+on+the+adapter&as_sitesearch=www.microsoft.com

AND much more recent than NT too.

Here is what it says:

"Y Specifies a physical hard disk attached to drive controller W.
For ATA controllers, this number is typically between 0 and 3.
For SCSI controllers, this number is typically between 0 and
7, or 0 and 15, depending on the adapter type. The first valid
number is 0."

So, given that and previous vacuums,

Lying, as always. The only vacuum is the one between your ears, child.

Phoenix and Dell gave it a meaning that made sense,

Like hell they did. Its completely stupid to be using the hard drive boot
order list, because the boot.ini has to be edited when a drive is moved
in that boot order list, AND you cant refer to a drive that isnt in the
hard drive boot order list at all, so you cant boot from it, stupid.

AND you havent even established that that complete abortion is
even seen in all Dell systems, just that steaming turd of a bios
in your particular system. You havent even established that updated
bios for your system havent fixed that complete abortion either.

met Microsoft's vague requirements,

Lying, again. NOTHING 'vague' about 'disk on the adapter'

and which was useable and convenient.

A complete obscenity in fact.

Keep desperately digging, child, you'll be out in china any day now, again.

 

[Rod Speed]

Rod Speed wrote

Yes, of course. Microsoft left it up to the BIOS producers
to define how the "adapter ordinal" is determined.

Like hell they did.

AND if they had done that, someone would have actually
documented the use of the hard drive boot order list for the
ordinal AND NO ONE HAS ACTUALLY DONE THAT, not even Dell.

Stupid is as stupid does.

You're sposed to have your sig at the bottom of your post, child.

Since you don't *know* enough to use the method, you don't use it.

Pathetic, really. Pity about the situation where you NEED to boot
an OS from a drive which isnt in the hard drive boot order list.

With that steaming turd of a bios in YOUR PARTICULAR Dell,
you're ****ed, because you cant.

But Dell and Phoenix Technologies figured that there existed a smarter
brand of user who would like the added flexibility and convenience.

You're just plucked that stupid pig ignorant claim out of your arse, child.

If they had actually done that, THEY WOULD HAVE DOCUMENTED
THE USE OF THE HARD DRIVE BOOT ORDER LIST FOR THE RDISK()
PARAM. They didnt, so this is just another of your pathetic little drug
crazed fantasys, child.

I've reported my findings for *them*,

Completely useless, no one actually has one of those
steaming turds of a bios, and you originally claimed that
it applied to ALL systems, you silly little pathological liar.

 

[Rod Speed]

Rod Speed wrote

You're funny.

You're pathetic.

Now define "ordinal for the disk on the adapter".

Its should be obvious that its the enumeration of
the drive on the adapter in the master/slave sense,
particularly when it goes on to say 'usually between 0 and 3'
with two channels and 0-6 with a scsi adapter.

 

[Rod Speed]

Rod Speed wrote

So?

So that is completely ****ed. Its much better for the rdisk()
param to refer to the number of the disk on the adapter
instead. Then there is no need to edit the boot.ini when
the order in the hard drive boot order list is changed.

Removing the drive at the head of the hard drive
boot order requires editing, too, in your system,

No it doesnt. You just have an identical boot.ini on every
drive you will ever load ntldr etc from, with the comment
on the entry in the boot.ini line documenting which particular
OS copy will be booted when that entry is selected by
the use in the menu that ntldr presents at boot time.

because that's where your one and only boot.ini file is.

I never ever said that there should be just one EXCEPT
TO SIMPLIFY THINGS IN A PARTICULAR TEST CONFIG
to ensure that you are guaranteed to be using the boot.ini
you think you are using.

If you have a boot.ini file in the secondary hard drive
that is appropriate if that hard drive is at the head
of the hard drive boot order and the "rdisk()" ordinal,
depends on the position in the hard drive boot order,
no editing is necessary when the primary hard drive
is disconnected or fails.

And you have to have a DIFFERENT boot.ini file on
every drive you will ever allow ntldr etc to be loaded from.

Makes a hell of a lot more sense to have just
one boot.ini on every drive you will ever boot
in the sense of what ntldr etc is loaded from,
with the comment documenting the OS install
will be booted when that entry is selected in
the ntldr menu by the user at boot time.

It even allows one to have entries with identical sets of ARC paths in
several partitions among several hard drives

No it doesnt, because the rdisk() param changes with
where the drive is in the hard drive boot order list.

- any of them would do for booting. You just have to know where the
partition you want to boot is.

And that is completely ****ed when it should be setup
so the user just has to decide which of the OS installs
he wants to boot, and doesnt need to know anything
about where it is on the drives.

But of course, that is too stressful for you to learn.

Its got sweet **** all to do with what *I* learn.

The boot.ini is a system that allows someone who understands
the detail to set things up so any user can select from the
comments on the boot.ini menu and get what OS install
he wants to boot booted. He doesnt need to know anything
about where they are on the drives. No user will ever be
able to keep track of that shit for the rare situation where
one of the drives wont boot anymore and the system
AUTOMATICALLY boots the next drive in the hard drive
boot order list when the original can no longer be booted
by the bios, say because the MBR can no longer be read
by the bios.

Thanks for that completely superfluous proof that you
have never had a ****ing clue about what should be
done to allow any user to carry on regardless when
the shit hits the fan and there are still bootable OS
installs available to boot if he wants to do that.

Your methods were learned in pre-MSDOS days

Even a terminal ****wit such as yourself should have
noticed that there was no boot.ini in the pre-MSDOS
days, you pathetic excuse for a bullshit artist.

It's time to reform your ossified ways.

You clearly have never had a ****ing clue about what is
involved with configuring a system so anyone can use it.

 

[Rod Speed]

Gerhard Fiedler wrote

On Feb 1, in the thread "Boot.ini question", I posted:

Irrelevant to your pig ignorant PREVIOUS claim that the
rdisk() param ALWAYS referred to the entry in the hard
drive boot order list, you pathetic excuse for a bullshit artist.

You only did that test AFTER I rubbed your nose in the FACT
that your claim was just plain wrong, after initially claiming
that you couldnt understand what my test involved.

"ABSTRACT

"This experiment shows that the Phoenix Technologies BIOS
exposes the hard drive boot order to ntldr such that the para-
meter "rdisk(x)" in the boot.ini file corresponds to the hard
drive having a displacement "x" from the head of the hard
drive boot order, where "x" is a positive integer starting
with 0.
"HARDWARE

"Dell Dimension XPS-R450 with a Phoenix Tech BIOS,"


On Feb 2, in the thread "meaning of 'rdisk()' in boot.ini file",
I posted:

"ABSTRACT

"This investigation shows that the "rdisk()" parameter
in the boot.ini file represents a hard drive in terms of
its displacement from the head of the hard drive boot order
in the BIOS. The value of n in "rdisk(n)" expresses this
displacement, where n is an integer value starting with 0,
and where "rdisk(0)" represents the hard drive which is at
the head of the hard drive boot order, i.e. the hard drive
at zero displacement from the head of the hard drive boot
order. The BIOS used in the investigation was the Phoenix
Technologies BIOS as supplied in Dell Dimension desktop
PCs.

"HARDWARE

"Dell Dimension XPS-R450 with a Phoenix Tech BIOS,"

Those are very clear statements of my position,

Pity that that was AFTER your original pig ignorant claim
that the rdisk() param ALWAYS referred to the hard drive
boot order list, EVEN WITH SYSTEMS THAT DIDNT EVEN
HAVE A HARD DRIVE BOOT ORDER LIST AT ALL.

having far more clarity than those of anyone else in the history of this
newsgroup.

Just another of your pathetic little drug crazed fantasys/lies, child.

No one has yet matched them in thoroughness or clarity of methodology.

Just another of your pathetic little drug crazed fantasys/lies, child.

If they don't apply to all Dell desktop PCs in the last 5 years, let
someone show it with equal clarity.

Or they could just tell you to go and **** yourself instead.

 

[Timothy Daniels]

"Rod Speed" flailed:

AND if they had done that, someone would have actually
documented the use of the hard drive boot order list for the
ordinal AND NO ONE HAS ACTUALLY DONE THAT, not even Dell.

Dell just figured anyone could understand it.
But they didn't figure on there being sock puppets
from the stone age who thought it worked the old way.

*TimDaniels*

 

[Timothy Daniels]

Pity about the situation where you NEED to boot
an OS from a drive which isnt in the hard drive boot order list.

If the drive isn't on the hard drive boot order list,
it's because it doesn't have an MBR - so just
use fixmbr to *make* one. Jeez, you're such a
helpless sock puppet.

*TimDaniels*

 

[Timothy Daniels]

Its should be obvious that its the enumeration of
the drive on the adapter in the master/slave sense,
particularly when it goes on to say 'usually between 0 and 3'
with two channels and 0-6 with a scsi adapter.

Exactly! And *that*, is the *default* hard drive
boot order of the Dell/Phoenix BIOS. You can
use the old sock puppet way of defining "rdisk()"
by adhering to the DEFAULT hard drive boot order,
or you can do it the new more flexible and conveni-
ent way and have firmware control of that "adapter
ordinal" by adjusting the hard drive boot order
yourself via keyboard input to the BIOS. *Your*
way involves opening the case and shuffling
connectors and hard drives. The *new* way
just involves keyboard input. So go back to
your dusty sock puppet shelf and give your
Rectal Hand a rest.

*TimDaniels*

 

[Timothy Daniels]

"Rod Speed" twisted and turned:

Timothy Daniels wrote

No it doesnt. You just have an identical boot.ini on every
drive you will ever load ntldr etc from, with the comment
on the entry in the boot.ini line documenting which particular
OS copy will be booted when that entry is selected by
the use in the menu that ntldr presents at boot time.

On Feb 2, 503PM, in the thread "meaning of 'rdisk()' in boot.ini file",
I posted:

"As I explained, each bootable partition in my PC has a
generic boot.ini file that allows booting from ANY of 10
partitions in the system. That means if one HD fails, the
boot.ini file in any partition in any of the remaing HDs could
be used without editing a thing. All you have to know is where
the clone is that you want to boot. The boot.ini file doesn't
have to know anything - indeed, they're all the same. The
comments in each entry tell you the values of rdisk() and
partition(), and you just choose the one having the path
that you want. I'm sorry that this has never occurred to you,
but I'm happy to educated you on modern techniques."

Now I'm happy to see that you have adopted my modern
technique for yourself and that you're claiming it as your
own.

*TimDaniels*