Hello dear guest!

Boot Land is a community driven pc software site established since 2006 and focused on recovery/backup boot disks, research of Microsoft Windows 2000/XP/2003/Vista/7 install/deployment/lease/antivirus/antispam tools, customizing Microsoft Windows PE administration systems and even learning how to recover computer data from disaster situations!

How about joining our boot disk community? So do it. Life's short!

  - You get free access to our newsletter with all the interesting buzz about boot disks
  - We share publicity revenue with everyone who wishes to participate at the forums
  - Publicity is never, never, never displayed to members (along with many other cool things)
http://boot-land.net/register


 
Reply to this topic
 Boot "any" ISO image or boot "all" ISO images ..., TANSTAAFL
post Sep 4 2009, 11:42 AM
Post #1
was_jaclaz
Finder   ******
Group: Advanced user

  Joined: 14-July 06 From: Gone in the mist

Posts: 7,226
Thank(s): 561


Italy


TANSTAAFL:
http://en.wikipedia.org/wiki/TANSTAAFL

There Ain't No Such Thing As A Free Lunch

Myth: Any .iso is the same as another one, thus you can boot "any" .iso

Fact: Each and every .iso has it's own peculiarities. For each sigle, specific .iso a single, specific solution may be found thumbsup.gif. (or may be NOT sad.gif)

Generally speaking:
QUOTE (jaclaz @ Jan 29 2009, 11:45 AM) *
The problem is the "ANY" .iso.

Very little has changed since this thread:
http://www.boot-land.net/forums/index.php?showtopic=808

In a nutshell:
ALL DOS based .iso usually work or can be made to work easily
SOME Linux based .iso work, ALL of them can be made to work (not so easily)
ONLY RAMDISK (from Server 2003 SP1 or R2, NOT "gold", NOT SPS2 - limited to 512 Mbyte images) NT based images are known to work

This is not "limited" by grub4dos or other bootmanager, but by the actual way the .iso images are built and, in the case of NT based images, by the lack of a suitable driver.

With plenty of RAM there is a Commercial Ramdisk driver capable to go over the 512 Mb limit.

In other words, there is not (yet) a one-size-fits-all solution, each .iso has it's own "story" and needs "particular" attention:
  • some work "as-they-are"
  • some need a few, easy changes
  • some need complex, difficult/undocumented changes (and a solution may even not exist yet)


Of course there are "families" of similar .iso's, thus it is very possible that an existing solution, working for one of the "members of the family" can be used succesfully for another "members of the family", but there is actually no guarantee that it will work, the exception being DOS based .iso images, that usually ALL work when mapped via grub4dos (hd32) or (0xFF) mapping or equivalent Syslinux/memdisk method.

There is a specific thread RESERVED FOR REPORTS OF SUCCESSFUL SETUPS using the (hd32) or (0xFF) mapping approach:
QUOTE
grub4dos, .iso images and (hd32) or (0xFF) mapping
Post here ONLY reports of working setups!

http://www.boot-land.net/forums/index.php?showtopic=5041

If the "whatever" .iso you want to boot is not in that list, do SEARCH on the Forum for your specific .iso/product/OS BEFORE starting a new thread.

Please DO NOT start yet another generic "How do I boot a .iso image?" kind of thread, we already have several of them, in time we became fond of them, and don't want them to be put in the background by "new arrivals" wink.gif

Again, generally speaking:

For Windows 2K/XP/2003 based builds you need a RAMDISK based .iso build (search for keywords BootSDI, RAMDISK.SYS, Firadisk, WinVblock) AND read, before anything else, and attentively this seemingly unrelated thread:
http://www.boot-land.net/forums/index.php?showtopic=4952
AND links given within it to get a general idea of the RAMDISK booting approach.
In any case they are all part of the same "family", thus one of the solutions in the "grub4dos, .iso images and (hd32) or (0xFF) mapping" thread should apply, possibly with some small tweak.

ALL Vista/2008/Windows 7 build are of the same "family" and the solutions in the "grub4dos, .iso images and (hd32) or (0xFF) mapping" thread should apply.

For Linux based builds there is often a partial workaround which consists into extracting from the .iso only the vmlinuz (kernel) and initrd (initial ramdisk file), and as well some of the solutions in the "grub4dos, .iso images and (hd32) or (0xFF) mapping" thread may apply, though it is more probable that some tweaking/changes of the contents of the .iso (on Linux side) will be needed.


In other words:
  1. your mileage may vary
  2. stop asking how many miles per gallon (EU, please read Liters/100Km) "a" car will do, there is simply NOT a valid answer for that.


cheers.gif

jaclaz


--------------------

Light Blue Ribbon Campaign for Freedom of Skin

But ... then, why?

The revenue from clicking on publicity at this post is helping was_jaclaz
Boot Land shares publicity revenue with its members.

.
2 user(s) said "Thank you!" to jaclaz for this fantastic post:
amalux, gnikolic
+Quote Post

Reply to this topic
1 User(s) are reading this topic ()



Collapse

  Topic Replies Topic Starter Views Last Action
No New Posts Boot-loader for INT 0x13 mapping non-contiguous files
6 supaJ 170 Today, 08:02 PM
Last post by: sebus
No New Posts Boot with SYSLINUX
9 mrt_doulaty 493 Today, 07:04 AM
Last post by: mrt_doulaty
No New Posts Boot Grud4dos from SARDU
3 Wile.E.Warrigal 181 Yesterday, 10:40 AM
Last post by: Wile.E.Warrigal
No New Posts Booting iso from 2nd USB partition
2 flok3r 215 14th June 2010 - 05:05 PM
Last post by: flok3r
No new Boot windows from extended partition
41 xpt 2,202 13th June 2010 - 10:58 AM
Last post by: karyonix





    

Display Mode: Switch to: Standard · Linear+ · Switch to: Outline