Skip to content Skip to main navigation Skip to footer

What to Do when Image for Windows Setup Asks to Replace File CDBOOT.F35

Note: Starting with Image for Windows version 2.50, the installer will no longer ask to replace the CDBOOT.F35 file. Instead, CDBOOT.F35 and CDBOOT.IFD will automatically be replaced. Custom boot images should be named CDBOOT.INS instead of CDBOOT.F35.



Most users should answer "Yes" when prompted to overwrite CDBOOT.F35 during Image for Windows setup.  Doing so will ensure that you have the latest version of the CDBOOT.F35 file.  Having the latest version of CDBOOT.F35 will allow you to create bootable CD/DVD discs which in turn contain the latest version of Image for DOS.

You will only want to reply "No" to the CDBOOT.F35 overwrite prompt if you are using your own customized version of CDBOOT.F35.  (If you are running a custom version of CDBOOT.F35, you would know about it, since you would have had to set it up manually.)

If you are a registered user of Image for Windows, CDBOOT.F35 will automatically be updated to a registered copy when any of the following events takes place:

  • Your Image for Windows registration information is successfully applied (after having been typed/pasted into the Image for Windows registration window).

  • You run Image for Windows after configuring IMAGEW.INI with valid registration information.

  • You run Image for Windows at any point after either of the two events above have taken place.

What this means is that if you are a registered user of Image for Windows, you generally do not have to worry about CDBOOT.F35.  When upgrading to the latest version of Image for Windows, just overwrite CDBOOT.F35 when prompted (unless, as mentioned above, you use a custom version of CDBOOT.F35) and then use Image for Windows as you normally do.  Whenever you install a new copy of Image for Windows and have chosen to overwrite CDBOOT.F35, it will automatically become a full-use version the very first time you run Image for Windows.

If you are a registered user of Image for Windows, do not normally use Image for Windows to create bootable CD/DVD discs, yet still need a registered copy of CDBOOT.F35 for other purposes (e.g. for use with BINGBURN), you will need to manually "force" your copy of CDBOOT.F35 to be become a registered copy.  To do this, simply run Image for Windows one time after overwriting CDBOOT.F35 during setup.  As soon as Image for Windows has run, CDBOOT.F35 will have been converted to a full registered copy.   You will need to repeat this procedure whenever you update Image for Windows and (assuming you also choose to overwrite CDBOOT.F35 during setup).

Was This Article Helpful?