Jump to content

- - - - -

Booting ISO

  • Please log in to reply
3 replies to this topic

#1 A201X

  • Members
  • 2 posts

Posted 07 August 2009 - 09:47 AM


I'm currently having trouble getting my AeroStudio boot menu to work:

1. Bart's PE // Question 1
2. Trinity Rescue Kit // Question 2
3. Partition Magic // No problem here, of course.
4. Damn Small Linux // Question 2
5. Backtrack (Linux) // Question 3

I used bcdw for all 6 ISO images:
bcdw (cd)/images/bartpe.iso,
bcdw (cd)/images/ubcd.iso, ... and so on. Errors received were as follows:

Windows based:

BCDW: Boot \images\bartpe.iso

Bootable CD Wizard v2.0a1 Copyright ©2004 by Alex Kopylov
CDBOOT: Couldn't find NTLDR

Linux based:

BCDW: Boot \images\dsl.iso

Bootable CD Wizard v2.0a1 Copyright ©2004 by Alex Kopylov

ISOLINUX 2.04 (Debian, 2003-06-06) Copyriht © 1994-2003 H. Peter Anvin
Could not find kernel image: linux

I've rummaged through the forums for possible solutions but am still clueless as ever. Perhaps I hadn't put in enough effort, but hey I tried :P

So here goes, my compilation of questions. Hopefully some kind soul could enlighten me? Thanks a million!

Bart PE
Many thanks to Shirin Zaban for the Bart PE tutorial:
Run BartPE ISO from CD by Aero
However I'm still confused as to why 'bcdw (cd)/images/bartpe.iso' wouldn't work. What exactly is the reason and logic behind this?

Q1a: Is this is a limitation of bcdw, or does the problem lie with AeroStudio? Or perhaps Bart PE is at fault?
Q1b: If it isn't too much to ask for, could someone please explain why the command fails to work? Why is it that booting from a real CD works?

Linux based - Damn Small Linux, Trinity Rescue Kit, etc
As quoted from jaclaz's post,
'Most Linux distro's CANNOT be booted from a .iso file. (without changes in the .iso)
And definitely NOT through BCDW command.'

PS: Many thanks to billonious for pointing out that you run Slax using ISO *jumps for joy* :)

Q2a: Are there any tutorials for the ISO changes required?
Q2b: Ouch, so BCDW doesn't work. Are there any other commands or functions on AeroStudio that can bypass this Linux handicap?
Hopefully I get a 'Yes', or that would mean I'd have to turn to grub4dos or CDshell or whatever works. But I really like my AeroStudio menu :P...

As quoted from ERD Commander 2005 ISO by Aero,
'ERDC2005.ISO that i have was "482 MB",i needed to decrease this size to be able to
run that by aero'

From what I understand, this mean that AeroStudio is unable to run large ISO files. I would like to have a copy of Backtrack (Linux) in my menu, and it so happens that Backtrack is humongous...1.36G :P

Q3: So um, is there no way I can squeeze that thing in? Are there any other methods to go around the problem?

Lastly, I am completely new to this multi-boot technology. I've previously heard about CDShell and grub4dos but have yet to try them out.
Out of all the available methods, which is easiest option for a beginner such a I? :idea:

#2 was_jaclaz



  • Advanced user
  • 7100 posts
  • Location:Gone in the mist

Posted 07 August 2009 - 10:08 AM

Lastly, I am completely new to this multi-boot technology. I've previously heard about CDShell and grub4dos but have yet to try them out.
Out of all the available methods, which is easiest option for a beginner such a I? :P

grub4dos. :P
Not because it is "easier", but because:
  • it works (mostly) the same way on any other kind of device (thus you learn one and use on all projects)
  • CD Shell (R.I.P. :P) is long dead
  • BCDW/BCDL (R.I.P. :) :P) is long dead <-one of the single most intelligent pieces of software around has been not developed since several years and the Author, Alex Kopylov, vanished from the net:
    unfortunately without letting available the source code
  • next generation grub2 is/will be very similar to grub4dos in syntax/capabilities
  • it is actively developed/supported on the board, and hopefully we have a rather comprehensive Guide for it:
    as well actively mantained

Aerostudio can use grub4dos as secondary loader, though the syntax/method is possibly going to change in next release of Aerostudio:

In other words you can have the graphical appeal of Aerostudio together with the power of grub4dos. :P



#3 Shirin Zaban

Shirin Zaban

    Frequent Member

  • Tutorial Writer
  • 423 posts
  • Location:Tehran
  • Interests:1_Making Unattended and Customized XP<br /><br />2_Making different types of Bootable and Multiboot CD/DVD<br /><br />3_Like to learn more about grub and grub4DOS

Posted 07 August 2009 - 12:17 PM

hi A201X

I thinks there are some bugs by aero,that can be bypassed by some methodes
i am sure these bugs will be noticed by "useronce" in next versions.any way for
some bugs that i have encontered you can see link below for more information:


About large files i do not know very well but at least aero has problem by i386 folder
of windows and failes when using that .take a look at link below (posts 27 and 28):


for squeeze see link below:

shirin zaban

#4 A201X

  • Members
  • 2 posts

Posted 17 August 2009 - 07:34 AM

Thank you both so much for your help! Finally succeeded in creating a multi-boot CD with 11 different utilities packed into a single 3.1GB ISO file (DVD). Gotta love Aerostudio :unsure:

CD Root directory is in a huge mess though, 27 folders with all sorts of weird names :unsure:
Then again...it works, so who cares.

Here's how to overcome the 'Aerostudio-cannot-create-large-ISO' problem, using an ISO editing software (MagicISO, PowerISO, UltraISO) - paid version. Either pay for it, or...*coughs* :frusty:
Personally I've only tried UltraISO. It's a brilliant piece of software ;)

There are other excellent freeware burners out there like ImgBurn. However they always gave me problems when I include a Windows based PE in the bootcd ;)
The errors seem to be caused by extra-long-folder-names like x86_Microsoft.Windows.Networking.RtcRes_6595b64144ccf1df_5.2.2.3_en_16a24bc0

An Aerostudio bootcd basically consists of:
Boot file (invisible)
Airboot folder
All other files and folders belonging to 'Source'

Step 1: Create an Aerostudio menu.
Step 2: Generate menu.
Step 3: Deploy menu - here's the catch. For 'Source' directory, direct it to an empty folder.
Now you should have an ISO file with only an invisible boot file and the 'Airboot' folder.
Step 4: Work on the contents of your bootcd and compile them in a single folder, which will be the CD's root folder.
Step 5: Open the ISO image using an ISO editor. Now chuck everything from Step 4 into the ISO image and we're done! ;)

Edit: Just in case anyone needs some inspiration, here's a copy of my menu in ISO format :unsure:

Designing tips for those graphic savy people out there:
1. If you want your menu to be interactive, do make full use of AeroStudio's 'Hot-State' function.
Hot-State means 'new image displayed when mouse hovers over an image'.
2. To eliminate 'visual lag' (undesirable lag which is visible), embed all 'Pictures' and 'Buttons' within the background. Next, replace all 'clickable images' with a transparent image (.png format image files). This way your menu will run very, very smoothly. The overall time taken to boot will probably remain the same as before, however all 'visual lags' will be hidden from your users.
This trick works regardless whether or not you wish to have 'Hot-States'.

Recommended software: GIMP (Freeware), Photoshop, Fireworks

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users