Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!rutgers!njin!princeton!udel!mmdf
From: V61%DHDURZ1.BITNET@cunyvm.cuny.edu (Ronald Lamprecht)
Newsgroups: comp.os.minix
Subject: MINIX-ST: can't boot MINIX from .IMG file after using FIXKEYS
Message-ID: <9288@louie.udel.EDU>
Date: 21 Feb 89 19:41:27 GMT
Sender: mmdf@udel.EDU
Lines: 24

In his article from  Mon, 20 Feb 89 16:34:53 GMT
Rainer Perske <PKP88%DMSWWU1A.BITNET@CUNYVM.CUNY.EDU> wrote:
>unchanged boot disk. But I have a german keyboard, so I ran FIXKEYS.PRG
>on a copy  of my boot disk.  If I create a MINIX.IMG  from this changed
>boot disk,  MINIX.PRG stops  with a  message: minix.img:  wrong format.

You ran into trouble with MINIX.PRG and your backup (copy) program :
MINIX.PRG checks the last bytes of the bootsector as
 Jack Dunn <jack@CSMUNIX.LARC.NASA.GOV> reported in his answer
FIXKEYS.PRG doesn't change anything within the bootsector. But most
intelligent copy programs don't produce an exact copy! They change the
serial ID located within the bootsector and adjust the checksum over
the bootsector by setting the last (!) word appropriated.
This makes sense, because GEMDOS will now detect a media change if you
use both disks afterwards and avoids writing onto the wrong disk.
But Minix uses a serial ID of 0 and doesn't use the last word of the
bootsector as checksum, because it stores its own information that is
checked by MINIX.PRG on this location.

Conclusion: use another stupid backup program.

Bitnet:  V61@DHDURZ1                               Ronald Lamprecht
UUCP:    ...!unido!DHDURZ1.bitnet!V61              Theoretische Physik
ARPAnet: V61%DHDURZ1.BITNET@CUNYVM.CUNY.EDU       (Heidelberg, West Germany)