
This message just to inform you that my problem is solved:
In this case the solution was to enclose the contents of the environmental variable CLASSPATH in quotes (and reboot) before reentering the SETUP.EXE at the root of Disk1 (with the expanded content of the three disks exactly as delivered from OTN). A classpath with spaces in it does not work well with OUI for the 9.2.0.1 version.
Thanks to DutchDBA for hitting the nail on the head.

It has been a while but in one instance I found that the fix that is recommended for installing 817 on P4 machines (Note: 131299.1) also works for 9i - even though 9i is not mentioned in the note. That fix is to copy the install disk (I have found you only need to copy the first one) to disk and then rename symcjit.dll (symcjit.dll.old for example) and then retry the install.

I have found this to be pretty common on Windows 2000, don’t
think I’ve yet installed Oracle on Windows 2003, so your milage
may vary.
Try this: open up a terminal services (RDP) connection to the
server, and install it from that session.
Oracle does not support this, but, it is the only way I have
been able to install Oracle on several servers.
I have been over this with Oracle Support, they were happy
when I found a ’solution’ and dropped the matter.
HTH
Jared

There is a simple fix for installing on Pentium 4 machines that may work for you. After you have expanded your files into the different directories, do a search for symjit.dll (I’m not 100% sure on the name but this is real close). Once you’ve found it rename it to symjit.old. Next run the normal setup. This has worked for me numerous times.










