linux-msdos.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Clipper, again
@ 2004-03-26 17:30 Peter B. Steiger
  2004-03-29  3:24 ` James B. Hiller
  0 siblings, 1 reply; 2+ messages in thread
From: Peter B. Steiger @ 2004-03-26 17:30 UTC (permalink / raw)
  To: dosemu

I downloaded the latest CVS yesterday to see how well Clipper handles
protected mode, and found that the record locking problem still exists: 
On a very large application, when it goes to lock a record for editing,
the application hangs.  On another test program with the exact same
locking mechanism, it works perfectly.

What debug flags should I put in to track where the problem begins?  I
tried debugging everything, but the resulting log is something like 20
megabytes and I still don't know what to look for or where to find the
point at which the crash occurs!  Maybe I would be better off using
dosdebug to isolate the moment the application freezes, but I'm even
stupider in that area... I don't know what commands would show me what
is going on during the application.

I think I mentioned once before that the problem does not occur when I
use freedos, only when I boot to the native Win98 partition. 
(correction... I just installed an old MSDOS 6.22 system disk and found
the same lockup occurs when I boot to that OS as well).

If you (Bart) like, I can put both the "good" and "bad" EXEs on a web
page for downloading, but they are very large... over 4MB each. 

-------
Peter B. Steiger
Cheyenne, WY



^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Clipper, again
  2004-03-26 17:30 Clipper, again Peter B. Steiger
@ 2004-03-29  3:24 ` James B. Hiller
  0 siblings, 0 replies; 2+ messages in thread
From: James B. Hiller @ 2004-03-29  3:24 UTC (permalink / raw)
  To: Peter B. Steiger; +Cc: linux-msdos

Hi.

> I downloaded the latest CVS yesterday to see how well Clipper handles
> protected mode, and found that the record locking problem still exists: 
> On a very large application, when it goes to lock a record for editing,
> the application hangs.  On another test program with the exact same
> locking mechanism, it works perfectly.
[snip]

I'm seeing something peculiar going on that I've not had happen before,
and it may be related, or not.

First, this appears to be totally unrelated to the various behaviors I
reported before - trying to boot straight from a DOS partition, and that
failing, probably due to a very large root directory; and then weird
stuff going on where a .dbf seemed to be getting corrupted, and then after
a few days, it was all magically ok.  Since then, I have completely
stripped out autoexec-invoked redirection to the DOS partition via linux,
and now have just an hdimage-based startup that has always (since like
0.68.1) worked just fine.

The problem I'm now having is that xdosemu seems to rarely start
successfully.  I invoke it, and I get:

Linux DOS emulator 1.2.1.0 $Date: 2004/03/06$
Last configured at Sun Mar 14 11:49:18 EST 2004 on linux
This is work in progress.
Please test against a recent version before reporting bugs and problems.
Submit Bug Reports, Patches & New Code to linux-msdos@vger.kernel.org or via
the SourceForge tracking system at http://www.sourceforge.net/projects/dosemu
 
DPMI-Server Version 0.9 installed
 
Starting Windows 95...
 
And then it hangs (this isn't really trying to start Win95 - this is just the
DOS that I have had around).  Prior to version 1.2.X, it would always start
fine - after this line, I would get a quick blast of the Win95 splash, and
then a DOS prompt.

Once in a very great while, I get it now, but rarely.  Usually it hangs, and
the CPU is consumed until I kill it.

If I try to start just regular dosemu (from an xterm still), I get:

   Note that DOS needs 25 lines. You might want to enlarge your
   window before continuing.


   Now type ENTER to start DOSEMU or <Ctrl>C to cancel
Linux DOS emulator 1.2.1.0 $Date: 2004/03/06$
Last configured at Sun Mar 14 11:49:18 EST 2004 on linux
This is work in progress.
Please test against a recent version before reporting bugs and problems.
Submit Bug Reports, Patches & New Code to linux-msdos@vger.kernel.org or via
the SourceForge tracking system at http://www.sourceforge.net/projects/dosemu

DPMI-Server Version 0.9 installed

Starting Windows 95...

[dosemu EMS 4.0 driver installed]
"Welcome to dosemu 1.2.1!"
C:\>

and all is good.

When I did get xdosemu up last, a couple nights ago, I had my own little
dbase/clipper app running (which has always been just fine), and the thing
hung while sitting on a view that it had been on for well over an hour.
I had been away from the machine, come back, and it was ice.

So my point is:

a.  I'm having startup hang problems that I never seemed to have before
about 1.2.0, for xdosemu.

b.  The problem may in some way be related to Mr Steiger's problem - he
may just be getting into his app and it's happening, but I'm not getting
that far.

c.  I too would benefit from any advice on good debug toggles to use to at
least get me through troubleshooting the startup and getting that stable.

I don't think I'm doing anything wrong on my side, since I'm using the DOS
I've been using ever since I put Win95 on my machine, and it has always
worked fine; and I got rid of the lredirs that had been evidently causing
problems previously, as well as the attempt to boot directly from the DOS
partition.  And since regular dosemu seems to work fine, the matter seems
to be something that only affects xdosemu's startup.

Thanks!

jbh

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2004-03-29  3:24 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-03-26 17:30 Clipper, again Peter B. Steiger
2004-03-29  3:24 ` James B. Hiller

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).