From:	"Florian X" <dos DOT fire AT aon DOT at>
Newsgroups:	comp.os.msdos.djgpp
References:	<39e43af7 DOT sandmann AT clio DOT rice DOT edu>
Subject:	Re: Announce: CWSDPMI r5 public beta
Date:	Thu, 12 Oct 2000 16:32:34 +0100
X-Newsreader:	Microsoft Outlook Express 4.71.1712.3
X-MimeOLE:	Produced By Microsoft MimeOLE V4.71.1712.3
Lines:	47
Message-ID:	<39e5cf29$0$108184@SSP1NO25.highway.telekom.at>
NNTP-Posting-Host:	212.183.94.139
X-Trace:	newsreader01.vienna.highway.telekom.at 971362089 108184 212.183.94.139
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Hi!

Why is cwsdpmi.exe 7Kb bigger than the old one?

bye, florian
www.drdos.org
www.seal.de.vu

Charles Sandmann schrieb in Nachricht <39e43af7 DOT sandmann AT clio DOT rice DOT edu>...
>After a short limited release beta with no reported problems, I'd like to
>make CWSDPMI r5 available to anyone wanting to test the new release.  The
>binary distribution is available from:
> ftp://clio.rice.edu/djgpp/csdpmi5b_BETA.zip
>The source files, a detailed list of changes, and directions for building
>CWSDPMI with the free Borland compilers are in the same directory.
>
>The only major new feature in r5 is the embedded stub option,
>which is only recommended for single executable distributions where
>a separate CWSDPMI is not acceptable.  Large memory support is fixed
>for systems with over 128Mb of memory.
>
>Unless there is something horribly wrong with this release, I will update
>it on the basis of feedback on October 21 and create the final release.
>
>If you do find a problem - please follow this procedure:
> 1) Test with r4 and see if this is a new problem.  Test to see if the
>    problem is reproducible.  If it's neither I probably can't fix it.
> 2) Send an email to me with the following information:
>  - the EXACT version of DOS you are running.  Send the output from
>    the VER command.
>  - config.sys lines dealing with HIMEM.*, EMM386.*, or other memory
>    managers.  Include lines for ram disks or disk caches, or other
>    utilities which may use memory above 1Mb.  Send size and date
>    information for all of these drivers/images.
>  - autoexec.bat lines for utilities using memory above 1Mb.
>  - mem /d
>  - output from CWSPARAM -v if you have modified parameters
>  - machine type (Intel/AMD etc, chip type and speed, memory type)
> 3) Find the minimum configuration which is reproducible.  Yes, I know
>    this takes time, but if you don't do it, I can't reproduce it or
>    fix it.  Ideally this will be 3 lines or less CONFIG.SYS, no
>    autoexec.bat, and be on a version of DOS/memory managers I have.
>    Test letting the image auto-load CWSDPMI, pre-loading it before
>    running the image.  Any difference?  Try disabling UMBs.  Try
>    changing the location or size of the swap file.

- Raw text -