Yes, replaced some LE's stubs (from Watcom DOS4GW) and it seems it's working under DOSBox. It's astonishing to see a ms-dos game loading that bears a 2005 year statement printed on screen. 😁

eL_PuSHeR wrote:

Yes, replaced some LE's stubs (from Watcom DOS4GW) and it seems it's working under DOSBox. It's astonishing to see a ms-dos game loading that bears a 2005 year statement printed on screen. 😁

I was thinking the exact same thing! 😁

what has changed since 7.1? performance improvements?

The ZIP file has a file called changes.txt
Although the last version 7.2 is missing from there, 7.3 is mentioned with a list of updates (from 7.1?).
However, all of the updates use internal technical lingo, so it's hard to tell what actually changed that the average user should care about.

Green flying pigs in delta formation emmigrating to the south, reduction of universal matter into poly-singularity due to permatutional permutation, and generally the end of the world are the suggested symptoms. Beyond that there are no known bugs at this time.

Sounds like something from the Hitchhikers Guide to the Galaxy. Looks like I need to spend some time in the poetry appreciation chair.

DOS32A seems to work pretty well - I tried it with many games including Worms, Blood, etc. and they all improve the performance. Not by much, but every bit helps.

I just rename the dos32a.exe to dos4gw.exe and overwrite the original file - or is there a way that works better ?

If the stub is embedded into the executable you can try the SB.EXE (enclosed in the DOS32A package).

Open a CMD.EXE window

SET DOS32A=<path where you installed DOS32A>
SB /R <exe to replace stub>

The SET DOS32A= command is redundant: since v7.33 none of the tools require the environment variable to be set.

I think that isn't true. SB doesn't work for me if I don't specify a SET variable.

I have DOS32A in the C:\DOS32A folder. Executables are located in the BINW folder (inside DOS32A one). I guess that you don't need to set the DOS32A variable if you copy dos32a.exe and sb.exe to the folder where you want to replace a LE stub. But I find it rather untidy. 😁

Or you could just add the DOS32A folder to your PATH variable.

Right. To clarify: "none of the tools require the environment variable to be set" means that the compulsory SET DOS32A= command is no longer *required*, solving the ever annoying "... You need to reinstall DOS/32 Advanced DOS Extender on this computer" copy prevention message. The tools are still dependent on the files needed to complete requested operations. In particular, SB is dependent on dos32a.exe, stub32a.exe and stub32c.exe (depending on the switches used). SC is dependent on SB and all its prerequisites. SS may need config files from d32 folder. All of the tools will perform file checks at the point when those files are used, meaning that certain operations can be completed without some or all of prerequisites being available.

The "best way" of using DOS32A is of course the one which works best for *You*. The mini-tutorial at the top of the page is supposed to work for most people on most systems, without the nuisance of going through the process of lerning the "whys," "hows," and "whens."

Does Moo2 and fallout use DOS/4GW ?

Anonymous wrote:

Does Moo2 and fallout use DOS/4GW ?

don't know, but if you type SB MOO2.EXE it will show dos extender, or it will say Standard DOS Executable if there's no dos extender

I am pretty sure Fallout uses DOS4GW.

It's just i tried to sb -r those games and the result is a little unsable under dosbox. Moo2, especially chrashed almost immediatly natively under XP home and did eventually chrash under dosbox after aplying dos32/a. Works normally without modifications (but very slow under dosbox).

DOS32a isn't a solution for all games, for those it works it works great but some games it doesn't work well at all. In those cases use the original DOS4G. I'm in the process of compiling a list of games that do not work well with DOS32A, not done yet tho.

Anonymous wrote:

It's just i tried to sb -r those games and the result is a little unsable under dosbox. Moo2, especially chrashed almost immediatly natively under XP home and did eventually chrash under dosbox after aplying dos32/a. Works normally without modifications (but very slow under dosbox).

DOS/32A is not perfect, sorry. What is the error message when moo2 crashes in WinXP? Normally there will be "DOS/32A run-time (6001): ..." followed by plenty of numbers, what do these say?

Sorry. The message it sends when it crashes is
(translated)
The NTVDM CPU encountered the following illegal instruction
CS:03ff IP:0214 OP:617272

And it changes.
I think this is useless for your purposes since it doesn't apperar to come from
dos/32a. I tried redirecting the output of ORION2 to a file, but it is still empty after the error.

Anonymous wrote:

Sorry. The message it sends when it crashes is (translated) The NTVDM CPU encountered the following illegal instruction CS:03ff […]
Show full quote

Sorry. The message it sends when it crashes is
(translated)
The NTVDM CPU encountered the following illegal instruction
CS:03ff IP:0214 OP:617272

You are running the game natively. I think he meant information how it crashes in DOSBOX.

Mirek