On Saturday 01 September 2001 05:59, [EMAIL PROTECTED] wrote:
> ERROR: IMAGE /data/dosemu/hdimage.dos622 header lacks magic string - cannot
> autosense!
> ERROR: IMAGE /data/dosemu/hdimage.dos622 header lacks magic string - cannot
> autosense!
>
> So it is lacking a magic string that should be in the expected/detected 128
> byte header? The floppy access failed probably because the user woudn't be
> on the floppy group I think, so it is not relevant.
>
I had exactly the same problem a while ago. It appears that in Dosemu-1.0.2,
you can no longer make images esp. when the documentation and relevant
executables have been removed! Of course, I'm sure that dosemu-1.0.2 can
still read those images if you've made them with an earlier version. Here are
some sniplets of the old manuals (from 1.0.1) that may help you:
README.txt:
4.3. Making a bootable hdimage for general purpose
You may also use './mkdexe' do generate a _normal_ bootable hdimage,
it then has the advantage, that you no longer need to fiddle with a
DOS boot disk. I succeded to make a bootable hdimage with FreeDos,
MSDOS-6.2 and also WINDOWS'95 (yes, that can be booted with the
DOSEMU-own MBR ;-) I did not test other DOSes, but I guess, they also
will work, as long as you pass the correct system file names to
'mkdexe' (-i, -m options)
Example: Given you have a bootable DOS-partition in /dev/hda1, then
this ...
# cd ./dexe
# ./mkdexe myhdimage -b /dev/hda1 -o noapp
will generate a direct bootable 'myhdimage' from your existing DOS
installation. You need not to make a boot floppy, nor need you to
fiddle with fdisk /MBR and sys.com any more. Using -o confirm you may
also edit the configuration files before they are put onto the
hdimage.
Further more, there is a script on top of mkdexe: setup-hdimage, which
helps more to firsttime install DOSEMU's hdimage. It prompts for
needed things and should work on most machines.
# cd /where/I/have/dosemu
# ./setup-hdimage
_________________________________________________________________
4.4. Accessing hdimage files using mtools
In the ./dexe directory there is also a script, that allows you to
directly access the hdimage's files, even without changing your
/etc/mtools.conf. The usage of this script is:
USAGE:
do_mtools device mcommand [ arg1 [...] ]
where is:
device = DOS-partition such as '/dev/hda1'
or a DOSEMU hdimage
mcommand = any valid mtools comand
argX = any valid mtools argument.
NOTE: for the DOS drive use 'W:'
example:
do_mtools /var/lib/dosemu/hdimage mcopy W:/autoexec.bat -
_________________________________________________________________
dosemu-HOWTO.txt:
3.2. How can I access the hdimage from Linux?
Use mtools. With a line in /etc/mtools.conf like
drive n: file="/var/lib/dosemu/hdimage" MTOOLS_SKIP_CHECK=1 \
MTOOLS_LOWER_CASE=1 MTOOLS_NO_VFAT=1 partition=1 offset=128
you can use the mtools on the hdimage, like "mdir n:". "mcopy
n:/config.emu /tmp" copies the config.emu file from the hdimage to
/tmp/config.emu. You can edit it there and copy it back. Use a drive
letter you find sensible. "N:" is only an example.
3.4. Creating your own hdimage file.
The easy way is to use mkdexe - see README.txt for details. The
old-fashioned way (I don't know why anyone would want to do it that
way any more but here it is, just in case) is as follows:
There is an extra util program called mkfatimage16 which allows for
creating a hdimage file headers. The full information is in the
manpage (man/mkfatimage16.1) included in your distribution.
To create a hard disk image file with a geometry corresponding to that
of a real hard disk of 32 megabytes run:
mkfatimage16 -k 32768 > hdimage
This is probably too large for most needs; if you need this much
space, consider using the disk redirector."
Usually it is a good idea to format the drive after it.
_________________________________________________________________
I personally, have given up on the idea of images because you can just boot
from the relevant partition (using direct partition access) or use a folder
containing DOS (or just make a symlink to your DOS drive and set $_hdimage to
the path of your symlink).
George
-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
