try this newer build of dosbox: http://cvscompile.aep-emu.de/dosbox.htm

Wow - the CVS version actually seems to run the program!

Finally - after 11 years - a way to run this program....

Thanks!

Chris

kekko wrote:

try this newer build of dosbox: http://cvscompile.aep-emu.de/dosbox.htm

Your link is no longer valid! I have the same problem using OS386.exe today ... DOSbox just sits their, what to do?
The code I'm trying to execute is "OS386 HIGHKERNEL YES LOWRESERVE 1000" from the old DOS days. 😀
I'm using DOSbox v. 0.74 ... need some help/ideas!!!

Thanks, Phil

Wow, an eight-year thread bump.

Have you tried the SVN Daum build of DOSBox?

Jorpho wrote:

Wow, an eight-year thread bump.

Why not lock threads automatically after a while of inactivity?

There's nothing necessarily wrong with it; it's just pretty remarkable.

OptimalDesigns wrote:

Your link is no longer valid! I have the same problem using OS386.exe today ... DOSbox just sits their, what to do?
The code I'm trying to execute is "OS386 HIGHKERNEL YES LOWRESERVE 1000" from the old DOS days. 😀
I'm using DOSbox v. 0.74 ... need some help/ideas!!!

It occurs to me you should also try changing the CPU type in dosbox.conf.

Jorpho wrote:

Have you tried the SVN Daum build of DOSBox?

Never heard of it ... got a link address?

Thanks,
Phil

😒
https://www.google.ca/search?q=svn+daum

But try changing your CPU type first.

Jorpho wrote:

But try changing your CPU type first.

Should the cpu type be of the PC that created my App that I'm trying to run -or- my present PC?

I have tried both ... I'm back to a setting of 'auto'.

Phil

The CPU type should be set to what is expected by the program you're trying to run. The first post in the thread suggests 386, 386_slow, or 386_prefetch might work, but you might as well try 486_slow and pentium_slow, too.

Jorpho wrote:

The CPU type should be set to what is expected by the program you're trying to run. The first post in the thread suggests 386, 386_slow, or 386_prefetch might work, but you might as well try 486_slow and pentium_slow, too.

I'm working with a DOS compiler that was created in or before 1991. So I thought '386_slow' mite do it for my Apps but the Apps are up and running fine ... lots of timing problems that required 'pause' stmts to get around them. 🙁

Downloaded the VCN DOSbox program you recommended. Just getting started on it.

Thanks, Phil

OptimalDesigns wrote:

Downloaded the VCN DOSbox program you recommended. Just getting started on it.

Nogo ... it seems that once OS386.exe starts or tries to start, DOSbox freezes. This happened to me when first working with OS386 on my 1991 PC. Once I got my Config.sys and AutoExec.bat files set right OS386 ran fine.

OS386.exe (from what little I know) converts 16 bit words to 32 bit words so EMM386 memory only. So XMS memory or any other may cause OS386 trouble. Any ideas on CONFig settings for DOSbox?

Thanks, Phil

Try running it without the HIGHKERNEL parameter.

ripsaw8080 wrote:

Try running it without the HIGHKERNEL parameter.

That seems to have at least gotten me past starting OS386.exe up. Need lots of testing to be sure.

Thanks for the idea.
Phil

ripsaw8080 wrote:

Try running it without the HIGHKERNEL parameter.

Not finished testing yet, but It worked so far with "\os386\OS386 HIGHKERNEL NO LOWRESERVE 1000". This is the 1st step and won't know if it worked right until step 4 or 5. But sure is lookin' good!

Thanks, Phil
PS: problem now is a missing library, glide2x.???. as shown by DOSbox status window. Here is message:

1Press any key to continue . . .
2DOSBox version SVN-Daum
3Copyright 2002-2013 DOSBox Team, published under GNU GPL.
4---
5GUI: Press Ctrl-F10 to capture/release mouse.
6     Save your configuration and restart DOSBox if your settings do not take eff
7ect.
8CONFIG:Loading primary settings from config file C:\Users\Phil\AppData\Local\DOS
9Box\dosbox-SVN-Daum.conf
10D3D:Error when initializing pixel shader support. Disabling shaders.
11PIT: Hacks disabled
12forcerate I got ''
13
14D3D:Error when initializing pixel shader support. Disabling shaders.
15MIDI:Opened device:win32
16ISA Plug & Play BIOS enabled
17VGA BIOS occupies segment 0xc000-0xc7ff
18Glide:LFB access: read-write
19Glide:Unable to load glide2x library, glide emulation disabled
20WinPcap has to be installed for the NE2000 to work.
21D3D:Device is lost, locktexture() failed...
22D3D:Device is lost, locktexture() failed...
23D3D:No texture to draw to!?

Is OS386.exe causing this error by any chance?

Responded on your cross-post here...
Re: DOSbox messages in Status Window ... missing a Library!

And it's unrelated to OS386.exe.

OptimalDesigns wrote:

ripsaw8080 wrote:

Try running it without the HIGHKERNEL parameter.

That seems to have at least gotten me past starting OS386.exe up. Need lots of testing to be sure.

Well I'm now on 2nd step, Compiling, and it seems to freeze again with "HIGHKERNEL NO LOWRESERVE 1000". Hmmm, wonder if upping lowreserve to 10,000 mite solve my present problem. Here is what os386's DESTATUS.exe program says about the kernel with "LOWRESERVE 1000".

1Protected Mode Kernel Status,
2Copyright(c) 1990, Ergo Computing, Inc.
3
4Kernel status: 
5--------------
6
7  OS version                    2.1.06
8
9  Total protected mode memory     15532032 (  ed0000 hex)
10                  starting at      1245184 (  130000 hex)
11  Low memory allocation                  0 (       0 hex)
12  Low reserve                      1024000 (   fa000 hex)
13  Protected-mode portion of kernel is loaded in low memory

Made another run with " LOWRESERVE 10000" and rec'd the following status report:

1  Total protected mode memory     15532032 (  ed0000 hex)
2                  starting at      1245184 (  130000 hex)
3  Low memory allocation                  0 (       0 hex)
4  Low reserve                     10240000 (  9c4000 hex)

No change in compiling run ... ideas how to get this thing running?

Thanks, Phil

Jorpho wrote:

😒
https://www.google.ca/search?q=svn+daum

It worked!!!

My last problem was with the compiler eating up time and building a huge OBJ file ... 30 sec. got a 2+ mb file! That was with the original DOSbox. But with 'svn' version it ran as it should on the first try! Nice.

Thanks for your help.
Phil