Play with the xms= and ems= settings in dosbox.conf, if they don't
help load "loadfix" before running the installer.

Is this the program you are using? :

http://www.mobygames.com/game/windows/f-22-lightning-2

If so, then it looks like you are trying to run a Windows program under DOSBox.

MobyGames is wrong. It's a DOS game. Totally.

They're confused by that PIF shortcut with an icon. Guess that identifies it as 'windows game'

Its a dosgame, (and i tried it under windows).

the xms and ems settings? I have here in the config a "true". What other parameters can i try? ( I look in the readme, but )

And i tried loadfix, and still the same problem.

=false

still no luck, tried some varations.

No idea.
Maybe post a screenshot, that message about setup.exe missing
seems a bit odd. Any batch files around (install.bat)?

d:
Joystick [Dir]
Nova [Dir]
Vesa [Dir]
install.exe
readme.text

Nova [Dir]
install.bin
resource.res

and i started the install.exe file, and then i have the error message and now i´m in the Nova [Dir].

I have access to the Novalogic 1996 game F-22 Lightning II (which is a DOS game) that will install under Dosbox v0.70. However, Dosbox game play at even 640x480 with a Pentium IV 640 (3.2GHz) is quite slow. Since I had originally installed this for a young nephew I found a better performance solution...

I purchased on eBay the Novalogic 1997 game "F-22 Raptor", which was basically a re-release of the Novalogic 1996 DOS F-22 Lightning II using Win95 era DirectX version 5 and a software renderer. This is one case where dumping the DOS version for the Windows version makes sense.

The only advantage of the DOS F-22 Lightning II version is that screen resolution can go to 1024x768, where as the Windows 95 based F-22 Raptor is locked at 640x480, unless the multiplayer F-22 IBS upgrade is applied.

As an aside, the official Air Force name for the F-22 did turn out to be "Raptor" instead of "Lightning II". However, the new F-35 did pick up the "Lightning II" designation.

Hope this helps,

dvwjr

The error message is quite misleading, the problem is as simple as
that the installer needs a drive c: mounted.....

I have it and it works nicely.
Its not too slow, considering what is displayed 😀
(its even almost smooth here)