Please try to empty FDCONFIG.SYS and FDAUTO.BAT, and re-add USEFUL
things piece after piece ... and supply shot of the crash ... "it
crashes AFTER the boot has finished" is NOT very informative.
--
RSA(R) Conference 2012
M
On Jan 15, 2012 6:04 PM, "Ralph Deffke" wrote:
>
> Thanx all,
>
> but as I said its impossible to figure out what driver is causing the
problem, the sequence doesn't seem to be logical to fix the problem.
> it crashes AFTER the boot has finished.
>
> I installed version 1,0 ( 0.87 beta ) with no p
Thanx all,
but as I said its impossible to figure out what driver is causing the problem,
the sequence doesn't seem to be logical to fix the problem.
it crashes AFTER the boot has finished.
I installed version 1,0 ( 0.87 beta ) with no problem.
tx
ralph
Op 14-1-2012 17:59, Ralph Deffke schreef:
> anybody any suggestions for the 1.1 version ?
First thing you can do is modify FDCONFIG.SYS (or CONFIG.SYS) text file
(EDIT C:\FDCONFIG.SYS) by commenting out the memory drivers, see if that
works:
DEVICE=C:\FDOS\BIN\JEMMEX.EXE then becomes:
;DEVICE=C:
Hi Ralph,
This may seem obvious, but have you tried loading each driver individually?
Also try changing the order you load them. If they are chaining interrupts,
there may be a conflict.
Hope this helps
Jeffrey
--
RS
Hi
after two nights booting in step mode I can't figure out what driver is causing
this problem.
FreeDOS boots well in the "NO DRIVERS" option
the message is
INTERRUPT divide by zero
9D49 C000 3A07 070F 01FC 0017 0111 0002 0008 1464 0070
I will try the 1.0 iso's to see if they w