home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.os.ms-windows.misc:3060 comp.os.ms-windows.programmer.misc:1863 comp.os.ms-windows.setup:1282
- Newsgroups: comp.os.ms-windows.misc,comp.os.ms-windows.programmer.misc,comp.os.windows.programmer.tools,comp.os.ms-windows.setup
- Path: sparky!uunet!munnari.oz.au!mel.dit.csiro.au!yarra!bohra.cpg.oz.au!daavid
- From: daavid@bohra.cpg.oz.au (Daavid Turnbull)
- Subject: Re: Full screen DOS box freezes (Dos box scheduler problem?)
- Message-ID: <1992Sep15.133259.20836@bohra.cpg.oz.au>
- Organization: Computer Power Software
- References: <markg.7.716174532@county.lmt.mn.org>
- Date: Tue, 15 Sep 1992 13:32:59 GMT
- Lines: 68
-
-
- In article <markg.7.716174532@county.lmt.mn.org> markg@county.lmt.mn.org (Mark Gilbert) writes:
- >
- > Occaisonally when I am running Sage Professional Editor in a full-screen DOS
- > box, the editor freezes for a few seconds. It resumes if I hit alt-
- > enter to put the DOS box in a Window.
- >
- > Does anyone know why a full screen DOS box would freeze momentarily?
- >
- We have had a similar problem which we have thus far spent over a man
- month trying to track down.
-
- Our problem occurs when when out Windows app (TODAY for Windows) executes
- a vanilla dos program via WinExec() which then proceeds to hang. More
- often than not pulling the task manager out of the desk top and "switching"
- to the task will restart it. This problem does not happen all of the time
- but consistantly stops our regression suite and is thus, for us, is a major
- headache.
-
- Microsoft, through there Online Access support in Australia have been unable
- to give us any usefull clues despite persistant effort on their part.
-
- There are a number of factors that should have made this problem easy to
- track.
-
- 1) We have four similarly configured boxes (all Zenith 486-25e, 12 to 16
- Mb of ram, tiga or tseng video etc.) and the problem reliably occurs on
- three of these boxes but not the fourth. (Mine ;-))
-
- 2) The problem is easily reproducible with the aid of our regression test
- suite. (It occurs on about the 15th test in the suite which is about 20
- minutes in.) N.B. The problem usually does not occur in any of the
- preceeding or 40 or so following tests which also execute the same vanilla
- dos app, often repeatedly.
-
- 3) The problem is manifested usually on the 4th invocation of the dos app
- by the Windows app.
-
- On this basis we have assumed that the problem is due to configuration/
- environment and have systmatically tried to massage the environment of
- one of the failing boxes towards the one that works. We have managed to
- make matters worse with this approach but have been unable to determine
- a reliable workaround. The box that works has 16 Mb of ram, a tiga
- video card with 1Mb of processor and 1Mb of video memory. It differs
- from it's most similar rival only in terms of the memory on the video
- card but as a consequence also in terms of the associated high res
- drivers. (The extra memory for the tiga card has been ordered.)
-
- Microsoft suggested using the Windows 3.1 ddk which has support for
- debugging the dos box scheduler... we are awaiting its arrival.
-
- The four boxes are connected via ethernet/Netware v3.11.
-
- .... So if any of you Windows sleuths have any suggestions or for that
- matter would like some more information.... go for it - I am all ears/
- email.
-
- The successful suggestion will be posted widely and its author duely
- acknowledged.
-
- close to desparation, daavid
-
-
- --
- Daavid Turnbull
- daavid@bohra.cpg.oz +61 3 823 0222 (fax) +61 3 824 8068
- uunet!munnari!bohra.cpg.oz!daavid
- CP Software Export Pty Ltd ACN 006 640 133
-