Date: Tue, 7 Feb 1995 03:03:15 -0400 (AST)
From: Bill Davidson <bdavidson AT ra DOT isisnet DOT com>
Subject: Re: Ladybug
To: Long Doan <ldoan1 AT osf1 DOT gmu DOT edu>
Cc: ld AT netrix DOT com, djgpp AT sun DOT soe DOT clarkson DOT edu



On Mon, 6 Feb 1995, Long Doan wrote:

> > ../paging.h since they were in the current dir ($DJGPP/go32/fs), not in 
> > the parent dir.
> 
>   The ought to be unzipped into the parrent dir only to rebuild go32, but 
> the problem is go32's sources changed with the maintanace releases...
> 
For blockheads like me that ought to be made clear in the docs; I just 
unzipped them where they were.  Of course, that had the side effect of 
creating a new subdirectory $DJGPP/go32/fs/fs!

> It seems like gcc tried to use the NPU that your machine doesn't have. 
> You might try to use the emulation package (emu387???) to fix that problem.
> I have no problem rebuilding ladybug.
Hmmm... I do have a 387 (ever since my first 8087 I won't be without a FPU!).

>   I rebuilt ladybug (and ladydpmi) on my 386SX16, 4MB, and 11M of free HD 
> space. The rebuild went fine (except that it's "quite" slow (It took me 
> almost 20 mins to rebuild the whole thing.) :-<
Well, my 386SX motherboard is pretty old and I have long suspected that 
there are either hardware or BIOS related "features" that love to break 
PM code!  (see my earlier posts on problems with running info.exe while 
any [EX]MS using programs were loaded)  New motherboard should arrive in 
a couple of days and I will try again just for the heck of it.
Bill Davidson
bdavidson AT ra DOT isisnet DOT com