Member Avatar for Ritesh_4

Hello,
I have to install Oracle Developer 2000 R2.1 on a Windows 8.1 (x64) machine to run an application developed by a third party developer, but my installation keeps on crashing. Tried running in Windows XP SP3 compatibility mode still same result.

The error is as follows:
"D2KQT10.ins(54): 'Statement' expected when ';' found"

And this occurs while executing the following:
"C:\ORANT...\d2kr20qt.exe"

Tried same install on a Windows 7 and a Windows 10 machine, and both installed correctly, except for some warnings on 10, which still completed the install. However on 8.1 it fails completely after displaying the above error message.

Any fix for this pls?

  • 2 Contributors
  • 6 Replies
  • 2K Views
  • 1 Month Discussion Span
  • Latest Post Latest Post by rproffitt

Dani AI

Generated

You already found the core issue, : Developer/2000 R2.1 uses a 16‑bit installer/runtime in places, so it needs NTVDM. 64‑bit Windows (including 8.1 x64) has no 16‑bit subsystem, so compatibility mode will not help. The cryptic D2KQT10.ins parser error is just a symptom of the installer failing before it can properly initialize. is spot‑on that the only reliable path on modern hardware is to run a 32‑bit Windows OS.

Practical way forward that has worked for teams still running Forms/Reports from this era:

  • Create a clean 32‑bit VM (Windows 7/8.1/10 x86). When you launch the 16‑bit installer, Windows will prompt to add NTVDM automatically (or enable it under Windows Features on x86).
  • Keep Developer/2000 R2.1 in its own ORACLE_HOME separate from your existing 1.3.2 install. Avoid spaces in the path (e.g., C:\ORANT). After install, set env vars so the intended home is first on PATH and TNS files are predictable.

Example (run in an elevated cmd in the VM):

setx ORACLE_HOME C:\ORANT
setx TNS_ADMIN C:\ORANT\NET80\ADMIN
setx NLS_LANG AMERICAN_AMERICA.WE8MSWIN1252
setx PATH "%ORACLE_HOME%\BIN;%PATH%"

If you must stay on a 64‑bit host, install the app inside the 32‑bit VM and deliver it to users via RDP/RemoteApp or a published shortcut. That keeps the legacy stack contained and maintainable. Also, snapshot the VM right after a known‑good install so you can recover quickly.

One more tip: mixing multiple Oracle homes on the same machine is a common source of odd errors. Even on x86, keep each version isolated, verify PATH order, and use TNS_ADMIN to point every shortcut and service to the same tnsnames.ora.

Recommended Answers

All 6 Replies

Member Avatar for Ritesh_4

- Yes have Oracle Developer 2000 (1.3.2) installed to run another application. Will have a look at the link provided above.

Edited by Ritesh_4
Member Avatar for Ritesh_4

I eventually found out the root of the problem. I was using a 64-bit OS, which does not have the NTVMD feature, while same installation done on a Windows 10 32-bit saw the OS automatically download and enable the NTVDM feature, which then proceeded with completing the installation of the Developer 2000 R2.1 setup. After googling, I found that 64-bit OS do not support this NTVDM feature at all. A pity Microsoft overlooked a feature like this on the 64-bit platforms.

Member Avatar for rproffitt

Isn't that NTVDM which is to run 16 bit apps on 32 (and some 64) bit Windows?

Maybe you think it faulty to leave such old support out but here I agree it has to go. Just a few years ago I ran into some app that would not run on a patched up XP SP3 but would on plain XP. It took some digging but it was another removal of 16 bit support.

Yes, the year 2000 was when you could expect 16 bit app support. Today? Don't count on it.

Member Avatar for Ritesh_4

Ya NTVDM which provides a virtualized 16-bit environment for those apps needing it. Unfortunately, only 64-bit OS are affected, and they are the ones which are mostly in use in work places these days. So to basically run a 32-bit OS on a machine having 8-cores and 8GB RAM would be a waste of resources, but will have to eventually run the 32-bit in a VM to get the application running. Don't talk about upgrading to a newer Oracle version, else the big bosses will get heart attacks. LOL!

Member Avatar for rproffitt

Then that's your answer. Tell them only 32 bit OSes are supported. I know companies that do that since they are loathe to update their apps.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.