It actually mounts the image file, but you did not specify a drive letter on the imdisk command line so you did not get one. So it doesn't mount it, just creates file.still cant go back to gui and mount because in use by another process? I think some extra is happening though because I cant mount the file afterwards says its in use Just as I posted I found an example in diddy's G4D guide. (From command line -s 1440K would give you correct floppy size.) So, just type 1440 in the size box and tick "kilobytes" and you will get a virtual "1.44 MB" floppy. Note that "1.44 MB" is just a "name", it is actually not 1.44 MB in size but rather 1440 KB.
I would say that you are on the right track, you just need to create a 1.44 MB floppy image.
Again probably because I am creating them wrongly!! Again I can mount a standardġ.44 bootable.ima in a virtual machine Vbox) and check to see if they boot but if I try my imdisk created ones they error and wont load. I guess its because I'm probably not creating a Standard image format as defined by pre made or application created images.ġ.) Can (and how) do I make a floppy image using IMDSIK that is as compatible with other applications (in my case BIOS update floppy creating tools) and also to test them. Making tool error's when it tries to find a "bootable diskette". I can format it, edit it, add remove files, boot from it in G4D.however the HP bios I create a blank file C:Temp\TEST.IMA, mount as before* and give a size of 2 (mb) (cant see -yet- how to make 1.44). I recently experimented with imdisk in trying to "seed" a blank image floppy (instead of downloading or creating one in virtual floppy driver) which the HP util then would see as a "physical" floppy and complete the process as above. *At this point I have a "standard" "1.44.Bootable.IMA" which does the job nicely and its mounted in imdisk (set as removable media) and type as floppy and DL as A: Which I boot from USB using G4D to update BIOS's. HP usually have a tool that looks for a floppy, formats it, puts the files on there, I then have a. This gets troublesome at times and I'm wanting to simply my process chain to perhaps a 1 stop shop solution.įor example.I often need to update BIOS images for updating machines at work. However for creating images I tend to have a few programs that make up a manufacturing process ending up in a desired result. I often use imdisk for editing images (mostly floppy).
0 kommentar(er)
