jaewide.blogg.se - Dos 7.1 boot disk iso

This not only took vast amounts of time waiting for the disc to burn but it also meant perhaps fiddling with the boot order in the BIOS and if you didn’t have any rewritable media, every burn would cost you money. I'll hang on to the ISO just so that I can try it again if you manage to solve this.Not too many years ago if you wanted to try out the latest Linux distro, test to see if a repair CD you downloaded worked or whether your custom made Windows install disc could boot, you had to burn the content to CD or DVD and then reboot your computer to try it out. You may have to ask the Ghost people on how to deal with it.ĮDIT: Please let me know if you finally figure out how to deal with that. One thing is for certain: this is *not* a DOS image. I haven't dealt with these issues for decades, and I don't even remember how to deal with them. Volumes/NO NAME/cddvdimg.bin: DOS floppy 1440k, x86 hard disk boot sectorĪnd this is as far as I could go.

The most interesting file in there seems to be the "cddvdimg.bin", which the 'file' command returns:.

rwxrwxrwx 1 socratis staff 1474560 cddvdimg.bin rwxrwxrwx 1 socratis staff 42566 IBMDOS.COM rwxrwxrwx 1 socratis staff 44656 IBMBIO.COM rwxrwxrwx 1 socratis staff 31198 EHELP.HLP rwxrwxrwx 1 socratis staff 19 CONFIG.SYS rwxrwxrwx 1 socratis staff 134 AUTOEXEC.BAT Total 1 socratis staff 16384 5 root admin 170 7 Dec 12:59.

Mounting the "OSBOOT.IMG" seems to contain parts of a DOS-like installation, in a "disk" called "NO NAME":.

OSBOOT.IMG: x86 boot sector partition 1: ID=0x4, active, starthead 1, startsector 63, 48132 sectors, code offset 0xeb

If I mount the above mentioned ISO, it mounts as a volume called "GHBOOTCD", and it contains a single file "OSBOOT.IMG", for which the 'file' command returns:.

Ghost_11_5_boot_disk.iso: ISO 9660 CD-ROM filesystem data 'GHBOOTCD ' (bootable) The 'file' command returns (really strange label):

The "ghost_11_5_boot_disk.iso" crashes with a Guru meditation, no matter what I throw at it.