Oracle Database Discussions

The Imagecfg tool is not provided in the support toolkit for Windows Server 2003. How do I then implement the /3 Gb switch for oracle.exe and tnslsnr.exe as has been recommended in Metalink notes 116076.1 and 46001.1?
Also does this not appear a bit confusing:

Note 1036312.6 states:

On Windows NT Server, Enterprise Edition 4.0, Microsoft provides the 4GT (4GB
RAM Tuning) support so an application can utilize up to 3GB virtual memory
instead of the 2GB limit as it used to be.
The Windows NT service pack 3 provides the same feature but is not officially
claimed in the SP3 readme.txt.
The Oracle 8.0.3 release and higher have already been enabled to take
advantage of the new feature.

However a more recently updated note (46001.1) states:

d) Configuring the Oracle process to make allocations greater than 2GB
----------------------------------------------------------------------
The Oracle database supports the 4GT tuning feature of Windows NT Server,
Enterprise Edition from release 7.3 onwards, allowing it to access up to 3GB
of virtual address space per instance. It may be the case that certain
releases / patch sets do not have the 4GT flag set even though the release
does support the feature. To check the executable has been correctly enabled
run :
imagecfg oracle.exe
oracle.exe contains the following configuration information:
Subsystem Version of 4.0
Image can handle large (>2GB) addresses
Stack Reserve Size: 0x100000
Stack Commit Size: 0x1000
For executables that do not have the flag set, run :
imagecfg -l oracle.exe
The above settings will only take affect if the boot.ini has been set up as
described in Note 46053.1.

So, do we really require to run the imagecfg utility (which is no longer provided in 2003 server support tool package) for versions higher than 8.1.7? Which tool should I then use instead of imagecfg for Windows Server 2003?