On Friday 27 March 2009 15:45, Michael Robinson wrote:
> packet driver has updated via fdupdate no problem. I'm at square
> zero on figuring out why the 486 crashes on fdupdate but does fine
> with say arachne.
Hi,
Are you sure that it's really FDUPDATE which crash? Note, that FDUPDATE doesn't
On Fri, 2009-03-27 at 11:04 +0100, Eric Auer wrote:
> Hi Michael,
>
> >>> Something specific to my hardware on my 486 DX2 66 must be causing
> >>> fdupdate to crash, but there seem to be no diagnosis tools to find
> ...
> >> First try to boot without loading (J)EMM386, a common cause of
> >> prob
Hi Michael,
>>> Something specific to my hardware on my 486 DX2 66 must be causing
>>> fdupdate to crash, but there seem to be no diagnosis tools to find
...
>> First try to boot without loading (J)EMM386, a common cause of
>> problems is a bad default EMM386 configuration which makes UMB
>> spac
On Thu, 2009-03-19 at 10:25 +0100, Eric Auer wrote:
> Hi!
>
> > Something specific to my hardware on my 486 DX2 66 must be causing
> > fdupdate to crash, but there seem to be no diagnosis tools to find
> > out what that is. Please rectify this problem. I want something
> > that detects resource
Hi!
> Something specific to my hardware on my 486 DX2 66 must be causing
> fdupdate to crash, but there seem to be no diagnosis tools to find
> out what that is. Please rectify this problem. I want something
> that detects resource conflicts, flaky memory, etcetera.
First try to boot without l
