What operating system are you on? And what dosbox version
did you use?

2nd reality is picky about the path, try something like
D:\2NDREAL or a shorter/longer one. It should work completely,
especially those flying balls.

I'm on Windows XP Pro and I have DosBox 0.63. And I didn't mention any problems with 2nd reality 😁. 2nd reality and it's patch + their suggested dosbox config works perfectly. Nothing's wrong with that.
It's 'Into the shadow by Triton' and 'Panic' and 'Unreal' by 'Future Crew' that's got problem(s).

Try the CVS in my sig.

Either gulikoza or Ykhwong's and report back.

I remember having the same prob with the vector balls section of Unreal. I can't remember for sure what fixed it, but I think it was either setting fullfixed = true, or using a CVS version.

cvs version (vasyl submitted a patch for it).

Mixed 2nd reality and unreal demos, sorry 😉

Into The Shadow requires strickt segment limits, dosbox ignores
those limits completely. Don't think this will ever be added
as it greatly decreases all kinds of memory access.
Thus they'll overwrite a lot of memory (callbacks) and crash.
Otherwise it seems to run fine, maybe i can put up a modified
dosbox compile if you want.

Panic doesn't work in the CVS because of a timer irq loop
(gets stuck, but this part seems to work in 0.63).

panic seems to loose track of the vretrace

it doesn't like the dstroy fix for the timers

At one point it switches between mode0/mode3 timers (this is
with a working timer.cpp) several times.

yeah. I figured that much out
if you change the mode back to pit[latch]mode then it works as well although it doesn't make much sense.
It doesn't mind the deactivate part which dstroy wants
So We can fix it, although I don't understand the fix totally

this fixes panic

1Index: timer.cpp
2===================================================================
3RCS file: /cvsroot/dosbox/dosbox/src/hardware/timer.cpp,v
4retrieving revision 1.34
5diff -u -r1.34 timer.cpp
6--- timer.cpp   9 Feb 2006 11:47:49 -0000       1.34
7+++ timer.cpp   26 Feb 2006 14:07:09 -0000
8@@ -224,7 +224,12 @@
9                        pit[latch].read_state  = (val >> 4) & 0x03;
10                        pit[latch].write_state = (val >> 4) & 0x03;
11                        Bit8u mode             = (val >> 1) & 0x07;
12+                       if (mode > 5)
13+                               mode -= 4; //6,7 become 2 and 3
14+
15                        /* Don't set it directly so counter_output uses the old mode */
16+                       /* That's theory. It breaks panic. So set it here again */
17+                       if(!pit[latch].mode) pit[latch].mode     = mode;
18 
19                        /* If the line goes from low to up => generate irq. 
20                         *      ( BUT needs to stay up until acknowlegded by the cpu!!! therefore: )
21@@ -234,8 +239,6 @@
22                         * counter_output tells if the current counter is high or low 
23                         * So actually a mode 2 timer enables and disables irq al the time. (not handled) */
24 
25-                       if (mode > 5)
26-                               mode -= 4; //6,7 become 2 and 3
27                        if (latch == 0) {
28                                PIC_RemoveEvents(PIT0_Event);
29                                if (!counter_output(0) && mode)

Okay, I guess I'm back after a long absense 😀
I tried both gulikoza and ykhwong's release and here's the results:

- Unreal is now fully functional. The vector balls reminded me of alot of Amiga demos 😀.
- Panic now stalls at panic logo screen 🙁.

And if it's not much trouble for you see if you can do a little release for 'Into the Shadow.' And I also wonder if any other similar DOS apps try to access the memory that way (like Into the shadow). Generally I wish I knew how the unprotected mode + the old x86 processors worked in detail. System programming has always been my long lost dream 😁.

Never seen any game that uses it, but ITS has a more or less valid
reason to do this (vesa bank switching).

> Generally I wish I knew how the unprotected mode

In this case it's plain protected mode which has configurable segment limits.

The attached build should be able to run Into the Shadows
with the normal core and the dynamic core. It shouldn't be
used otherwise.
If you're missing some dlls, try to get them from
www.dll-files.com or somewhere else (sdl from some other
dosbox release should work fine).

Please let me know if something doesn't work (or if it works 😀 )

Hmmm, it says the program cannot run because the application configuration is incorrect. Any hints?
Thanks alot for the build btw 😀. If this works, I'm going to keep this release. I wonder if a DOSBox 'protected mode' version would be a good major side release with DOSBox itself. 😜

Hm, maybe those msvc optimizations were too much. Maybe
i'll compile it with an older version.

> I wonder if a DOSBox 'protected mode' version would be a good major
> side release with DOSBox itself

Dosbox fully supports the protected mode, just segment limits are
ignored because of speed reasons.

Next try, updated the attachment above. Same compiler,
different optimizations, maybe that works (what cpu do you have?)

Tried again... same error, different form. It says
-----------------
'C:\program files\Dosbox-0.63\dosbox.exe'
This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem'.
-----------------

Now just to make sure I'm doing this right, I copied over everything from dosbox_its.rar in my Dosbox directory, even overwrote the SDL.dll (which I thought shouldn't be needed if the versions are the same.)
I have NO service pack installed and I have Win XP pro.
My CPU is p4 2.4 GHZ and I have 512 ram.
It may be also important to note that I have MS Visual Studio 2003 .NET installed as well.
btw, do you think packing Dosbox is really necessary? 😜
I don't mind if the executable is 100 ks or 3.0 megs 😁. I just want to it to work 😀.

Try running "depends" on dosbox.exe to see which .dll's it's erroring out on.

You have *no* service packs installed and run Windows XP?!?! May I recommend downloading SP2 then the 50-100MB of updates available from Windows Update when you're next online!

I downloaded the DOSBox version attached and the ITS demo. Startup took around 5 seconds are discovering the soundcard. With a cycles count of approx 15000 (Pentium-M 2Ghz) and a completely standard DOSBox config (just ran the downloaded exe) it ran fine for me.