Make an ISO with Imgburn

[loninappleton]

As a mature forum I'm asking this question in Doom9 after getting the runaround (dead links, stupid test questions to even register etc.) elsewhere.

I have seen the Britec youtube on how to construct an ISO starting with the blank iso image loaded from the desktop.

Finding this image (a dead link with the you tube from Bitec made this impossible) is what I'm trying to do. Some say it's on a floppy disk or other arcane place. Why is this simple step so difficult to execute? And don't mention UBCD-- they are the ones who require unanswerable questions to register.

A simple downlload site for what I've seen called the

Bootable_NoEmulation.img

seems to be what I'm after.

If there are simpler solutions to making original ISOs without this foolish "find it" step, please advise.

[Wilbert]

A simple downlload site for what I've seen called the

Bootable_NoEmulation.img

seems to be what I'm after.
As I understand it, it is the floppy emulation image for the BIOS to boot the disc. Download link: https://docs.google.com/file/d/0B7Nj-XlaYRsSTXZJbmktYWZidmM/edit
I don't know if any technical specs of it are available.

[StainlessS]

Bit rusty on this but here's what I remember.

Sometimes goes by the name BOOTSECT.BIN (if found as a file), found as 2K boot sector on eg W2K/XP setup disks.
Looks for BOOTFIX.BIN in I386 directory and calls it if there (BOOTFIX.BIN
will ask 'Press and key to boot from CD' and if key not pressed will boot to hard drive
instead of SETUPLDR.BIN in I386). If BOOTFIX.BIN not found in I386 then will directly call
SETUPLDR.BIN instead to start the OS setup routine.
BOOTFIX.BIN sometimes deleted/renamed on alternate setup disks to remove the
'Press and key to boot from CD' prompt. (eg when a user has already elected to install a specific version
OS, he does not want to bother having to agree again).

The 4 chacter 'I386' in BOOTSECT.BIN (Hex/Ascii editor) is sometimes edited to make
an x-in-1 style multiple OS setup disk, the 4 char text gives a different
directory to the I386 where there is an alternate SETUPLDR.BIN (also edited if I remember correctly).
TxtSetup.sif is also edited in some way connected with multi-setup disks.
In an x-in-1 style setup disk, a different version/edited of the BOOTSECT.BIN is called via some other
boot loader, depending upon user selected OS to install (chain loaded, read into memory and jump to
execute the code).

http://en.wikipedia.org/wiki/El_Torito_%28CD-ROM_standard%29
See External Links via above Wikipedia link for specs.

Dont know if it's one of the places you've tried, but boot-land.net now apparently Reboot.pro http://reboot.pro/
used to be very good.

EDIT: something from years ago, related to Nero.

Create a BOOTable ISO file using the BOOTSECT.BIN file as the
El-torito no-emulation boot sector, & in Nero, tick the:-
DO NOT ADD THE ';1' ISO FILE VERSION EXTENSION.


EDIT: All of the above relates the the file that Wilbert linked. If you are not trying to eg make a W2K/XP style bootable
disk (I dont know off hand what eg W7 or W8 use), and you are instead looking to eg boot a live CD eg Live XP or whatever,
then suggest you seek help elsewhere. Last time I recall someone asking such questions he was barracked because
"everyone knows XP cannot be booted from read only media", I had to intercede and put them right that it can and is
bootable from CD or DVD or write protected SDCARD. The folk on this site generally dont know much about such things,
its not what they do. Best look into ISOLinux/SysLinux and the like. (link in Wikipedia link above).
Hiren used to have an interesting disk, with tools to dissect/change and re-create another ISO or USB bootable disk.
Generally, the least problematic USB devices to create as bootable, are 512MB or below (most likely to work in a range
of machines) EDIT:- Removed some complete twaddle.

I used to find BSCRIPT a flexible system for own use tool disks (CD/DVD only) and also CDShell which is later but not
quite to my liking (same guys that did BSCRIPT). BSCRIPT and CDSHELL could boot floppy images and run them from Ramdisk,
or chain load BOOTSECT.BIN to boot a setup disk, also had a rudimentry script language. CDShell later ceased development
as devs became involved with the proprietary 'EasyBoot' GUI menu driven setup disk creator.
EDIT: Bootable read-only XP, runs from ramdisk, or part of XP replaced with executable from read-only Embeddable XP (NTLDR.BIN I think, equiv to SETUPLDR.BIN on setup disk).

[Ghitulescu]

I remember the times when El Torito came to life.
Like with blu-ray of today, few details were known (also the internet was not as powerful as today) and a lot of misconceptions started and perpetuated (I see that even today) based solely on the reputation of some members, which were only assuming and deducting.

Maybe if the OP is more specific in what he's after ...

PS: new computers (at least with w9) have changed the booting process (again :) ) and they may not allow booting of other systems than the installed one (eg for replacing the budget w8 with a Linux).

[loninappleton]

As I understand it, it is the floppy emulation image for the BIOS to boot the disc. Download link: https://docs.google.com/file/d/0B7Nj-XlaYRsSTXZJbmktYWZidmM/edit
I don't know if any technical specs of it are available.

I'm still reading the responses but this might be the needed object
for Imgburn. I will try it soon after I catch up on the thread.

There are a number of other programs out there such as Magic ISO etc. Do these incorporate this file image step? I know from other reading that No_Em is not a data file, more like a file specification.

The goal is to be able to do a BIOS upgrade completely independent of running a loader from within Windows XP or other OS.

[Groucho2004]

The goal is to be able to do a BIOS upgrade completely independent of running a loader from within Windows XP or other OS.
Which BIOS? Video Card? Motherboard? Why not follow the BIOS update instructions of the manufacturer?

Generally it is advisable to boot from a CD or USB stick that has all required files (BIOS upgrade utility, bios image) usually running good old DOS. There are plenty of guides and also ready made disk images available.
Edit: first google hit (http://www.biosflash.com/e/bios-boot-usb-stick.htm) on the subject.

[nhakobian]

All the motherboards I have had in the last 5 or so years have had the ability to upgrade the BIOS from a special environment within the BIOS itself. You put the file on a flash drive (or CD), hit the right button on the BIOS splash screen, and it updates it without dealing with booting to DOS. Are new motherboards being sold that don't have this functionality?

[StainlessS]

Ultra ISO (my fav), Power ISO and MAGIC ISO, do I believe all have such functionality. (Ultra ISO related to EasyBoot mentioned earlier, same guys I think).

WinISO another tool but not as good (or did not used to be).

I used to use ISOBUSTER too but dont recall what for (free/proprietary).

I used also to use CDMage (thats without an 'I', to extract boot images, I think, and exploration, I think can also find and
in some cases correct corruption in ISO image).
CDImage is for Windows Unattended setup stuff.

Floppy Image Editing, WINImage (free/proprietary), or VirtualFloppy.

EDIT: There is actually an ImageBurn thread in DVD Burning Forum on-site.
The author is quite likely to have some idea what ImageBurn does (as in thread title).
EDIT: Forget above, author not around since 2012.

[loninappleton]

It makes sense that DOS should figure into it.

As an experiment, I will load (on a scratch disk for experimentation) Clonezilla which is Linux based and see what it turns up.

But would not your DOS image require auto exec files and such things that I have forgotten?

[hello_hello]

I'm not sure why you need an ISO image.

If you have Nero Burning ROM (or whatever it's called) run it, select either CD or DVD at the top, then select CD (Boot) or DVD (Boot). I don't think you need a boot image. You can load the Bootable_NoEmulation.img file though. As you create a new compilation by selecting CD or DVD (Boot) from the list, a Boot tab will appear. The "Image File" section within will probably contain a Nero boot image. You can click on Browse to load the Bootable_NoEmulation.img file instead. When you do, you need to select All Files (*.*) at the bottom of the browse window. Nero defaults to only looking for image files with a ima extension, not img, but it will load img files.
Once that's done, click on New to create the new compilation, add you drivers and burn the disc.

For bootable discs from ImagBurn, change the Mode to Build, select the Advanced tab, then the Bootable Disc tab. I've never created a bootable disc with ImgBurn so I don't know if a boot image is required, but you can load the Bootable_NoEmulation.img file under the Bootable Disc tab. Once that's done add your drivers to the compilation, switch to write mode, burn away.

You didn't answer the question in the VideoHelp forum as to whether you can see the PCI card in Device Manager when Windows is running. If you can't, odds are it's not working properly and a bootable disc with drivers won't make any difference. Some older MBs are particularly fussy when it comes to PCI cards, especially if they're bootable. I recall adding an IDE PCI card years ago and the computer refused to boot from it. If I connected an optical drive to it the computer wouldn't boot at all, which was somewhat ironic given I bought the card to run an optical drive.

You should also try booting the PC without any devices connected to the card initially to make sure the card itself is showing up in Device Manager before connecting drives to it. It's possible the card doesn't play nice with one of the drives and if you're using the ATA connector.... make sure you're using the right connector on the cable and the drive is jumpered as Master, and if that doesn't work, try it as Slave.

[StainlessS]

Here is a couple of Floppy images, if you wish to experiment.
MenuetOS: http://www.menuetos.net/
Complete Graphical OS on a floppy written in Assembler. (incl games & demos + more).

MemTest86: memcheck util: http://www.memtest.org/#downiso

What I just did: (am doing right now)
Select: WriteFiles and folders to disk. (via Ez Pick)

Select source: Hilited a few files (otherwise seemingly empty cd/dvd). 'Click Add Selected' and exit.

OPTIONS: MODE 1/2048

FILE SYSTEM: ISO 9660 + UDF (UDF Revision 1.02: I used DVD Re-Writable, quicker for experiment) CD use ISO 9660 (+ Joliet, longer names).

LABELS: 'TEST'. for all available.

ADVANCED: File/Folder name Length: 2 - 31 characters (I did not have anything longer in files)
Ticked 'Dont Add ';1' Version number to Files.

BOOTABLE DISK:
Make Image bootable = Yes.
Boot Image = M6409969.IMG
Emulation Type: Floppy 1.44MB
Platform ID: 80x86

DONE, WORKS OK. Boots to MenuetOS. Selected files available in windows.


MenuetOS changed since last I tried it.

Suggest change to "Make a BOOTABLE ISO in ImgBurn".

EDIT:
But would not your DOS image require auto exec files and such things that I have forgotten?


Yes, you need a stripped down version of MSDOS, PCDOS or FREEDOS, and add to it. (eg W95/8 boot disk)

A real 100% solid non virtual floppy drive is very handy to have for prototype purposes (people will laugh at you
if you ask if they sell them).

EDIT: I think IBM has some free to download tools as floppy images, that have stripped down PCDOS on board.
EDIT: Try google eg:- "floppy image site:ibm.com"
comes up with 24,000+ links, have not checked them out. (perhaps add 'img' for 2000 links, maybe better luck)
EDIT: Here link for some kind of firmware update on PCDOS floppy image, scrub off their firmware update using eg VirtualFloppy,
and add your own. http://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=migr-5093850

EDIT: The MenuetOS floppy image linked above is 64 bit version, I think there is/was a 32 bit version.

[Groucho2004]

All the motherboards I have had in the last 5 or so years have had the ability to upgrade the BIOS from a special environment within the BIOS itself.
Same here but I guess there's a reason for the OP to require a solution for the "ancient" update method.

[fvisagie]

EDIT: I think IBM has some free to download tools as floppy images, that have stripped down PCDOS on board.

It's been a while since I lost myself in this world, but isn't it perhaps the HP Drive Key Boot Utility (http://h20565.www2.hp.com/portal/site/hpsc/template.PAGE/public/psi/swdDetails/?lang=en&cc=us&swItem=MTX_UNITY_I23839) you have in mind?

What I also found very useful at the time was the GRUB4DOS/WinGRUB boot manager.
http://sourceforge.net/projects/grub4dos/
https://gna.org/projects/grub4dos/
It seems gna.org might be the more recent project home.

[StainlessS]

fvisagie,
The OP was asking about needing some form of DOS or not, the link posted contains a floppy image including PCDOS
which is what the OP wants.

Grub/WinGrub, is something else, ie Boot Controllers (myself I still prefer the old reliable XOSL v1.x [must live within first 128GB]).
Reliance on Win Boot controllers is fraught with problems, a self contained boot controller (ie not reliant upon linux either) is better.

Your link to HP USB key utility is broken, see here: http://www.bootdisk.com/pendrive.htm
That is a good tool, but not for ISO, USB only. Perhaps the OP may prefer to go the USB way, I like to have both options,
either way he may still want a bootable floppy image containing some form of DOS.

EDIT: From memory, above linked BootDisk.com is very good resource.

[fvisagie]

Your link to HP USB key utility is broken

Apologies, fixed.

[minaust]

Same here but I guess there's a reason for the OP to require a solution for the "ancient" update method.
Because he has a ancient motherboard?

[minaust]

I've run into this a few tomes, and here's what has worked for me:

HP/Compaq has a couple of useful flash drive utilities. One is hpflash1.zip. It's all over the net, and download links and pointers and guides can be found here (http://answers.microsoft.com/en-us/windows/forum/windows_7-security/how-can-i-make-a-ms-dos-boot-disk-on-a-cdusb-for/9fd9067a-d327-4ba5-8aca-0f33501b87a4) and here (http://www.sevenforums.com/tutorials/46707-ms-dos-bootable-flash-drive-create.html).

The other is in the link to the HP Drive Key Boot Utility (http://h20565.www2.hp.com/portal/site/hpsc/template.PAGE/public/psi/swdDetails/?ac.admitted=1406194144431.876444892.492883150&cc=us&lang=en&swItem=MTX_UNITY_I23839) posted by fvisagie above and repeated here. That utility (if I remember correctly) will either make the flash drive bootable with a Linux partition, or alternately, use a DOS floppy as a source for boot files. A problem with using a floppy image as a USB boot is they tend to create a partition that is 1.44mb in size, which is too small for a modern BIOS image. But this util allows you to partition the USB stick as a hard disk, therefore you have the entire stick's space. Handy. If you don't have a floppy, download VFD21 (https://code.google.com/p/pwnageos/downloads/detail?name=vfd21-050404.rar&can=2&q=) (Virtual Floppy Disk), which is free and open source. VFD has the useful ability to load and save floppy images in several popular formats.

Something I haven't tried but seems workable is to format a USB stick with FreeDOS (http://goebelmeier.de/bootstick/).

As my dear departed father would say, "There's more than one way to skin a cat..." :)

Hope this helps.