msdos 6 disk with errors

msdos 6 disk with errors

[julius junghans]

hi
i tried to run msdos 6 with this tutorial
http://www.geocities.com/sunil_tt/dos.txt
but my old dos disk are not readable, probably they are to old
can someome send me a copy with a bootsektor ?

please mail back to juliusjunghans@gmx.de
i am not subscribed

Re: msdos 6 disk with errors

[Stas Sergeev]

Hello.

julius junghans wrote:
> i tried to run msdos 6 with this tutorial
> http://www.geocities.com/sunil_tt/dos.txt
Not the best instructions: boot
sector can be omitted as dosemu
can create the boot sector on
startup, so you need only a
system files. The "boot.blk" is
not even documented for that reason.

msdos 6 disk with errors

[julius junghans]

i tried to copy the files from an installed dos version to
~/home/user/dosemu/msdos
and edited the conf file to use that dir for an hdimage
but dosemu exits with :

./dosemu: line 386:  2712 Segmentation fault      $BINARY $MAINARGS
"${par[@]}" 2>$LOG

Re: msdos 6 disk with errors

[Stas Sergeev]

Hello.

julius junghans wrote:
> but dosemu exits with :
> ./dosemu: line 386:  2712 Segmentation fault
Check your system log for Oopses.
This was a long-standing bug of
the 2.4 kernels.

msdos 6 disk with errors

[julius junghans]

what are "Oopses" ?

cant find it with grep in my logs, my kernel is version 2.4.19

Re: msdos 6 disk with errors

[Stas Sergeev]

Hello.

julius junghans wrote:
> what are "Oopses" ?
Special kernel messages printed on
an error condition.
May contain the string "Oops",
"invalid operand", "stack segment"
etc - depending on an exception that
was raised by CPU.

> cant find it with grep in my logs
Then search for "Call Trace" string -
this should be common for any kind of
an oopses.
Search it in /var/log/messages (or
wherever your system logs are).

> my kernel is version 2.4.19
If it is -ac, then there is no that
bug, but if it is Marcelo's one -
then the bug is still there (but not
in 2.4.20-pre).

Re: msdos 6 disk with errors

[pesarif]

On Mon, 18 Nov 2002 00:56, Stas Sergeev wrote:
> Hello.
>
> julius junghans wrote:
> > what are "Oopses" ?
>
> Special kernel messages printed on
> an error condition.
but why do they cause the entire system to freeze, but only if you are in x?
alt+sysrq+b is the only kernel key that works.
alt+sysrq+[krsu] all do not work...nor does ctrl+alt+backspace.