| Re: [cooking] booting loram-cdrom on usb ( was: [cooking] various boot modes, successes and failures) |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/slitaz Archives
]
- To: slitaz@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [cooking] booting loram-cdrom on usb ( was: [cooking] various boot modes, successes and failures)
- From: Indigo <pointofavailability@xxxxxxxxx>
- Date: Thu, 30 Dec 2010 07:38:27 -0800
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=WlbagGG5OSq5bb5+tovTrdNmBLTiDcEEoI8BXGG2HXQ=; b=Pxit+Qu8zxyBgOOBQP2PhqaN8qu/hZ46LWiS63fqOfAtXYtxhs/i3RT4CtwfaY6DQQ PmQz63GQDA+ClVUUM3Cvi90k7FRCkGDK9oWCs+m2SSZKLePN9SXHkERnUIN6QAiwzW5g gjvJCL0MWCeY6KI+HsozMkoBJEerbe+6Pe4K8=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=mXQvAt5gvgpvBwzwf0y9MDCLrC8V0GfdVT6D1gtXfaq4bwbmsv9R0SBAJK4toyyGis Zc3+0pE00r0oqVh/X3+A6p2ukosU24A+M9rK8Aw1uVrFd+DjQ+tB7Kmiwj4LPg0nDN7y LBVTJAeJi9OLaHw6+bpjT905iV0FwhVQjeccU=
> Partition table entries are not in disk order
Leave it to Windoze to work better that way... now if only they'd get
native ext support.
2010/12/30 Philippe Lelédy <slitaz@xxxxxxxxx>:
> On 30/12/2010 13:47, Philippe Lelédy wrote:
>>
>> experience shew me that MS Windows only see partition #1. Last try with
>> Seven gave me worst result: with such strange a key, the only this that MS
>> Window propose is formatting it.
>
> I had some success with MS windows, but it's for *experts* only ! (use
> sectors unit to be as precise as possible)
>
> -1- use fdisk from last SliTaz, other tools doesn't work (parted, sfdisk,
> fdisk on ubuntu)
> -2- add 1 partition #2 behind #1 which is the copy of the hybrid
> SliTaz_LoRAM_CDROM, but don't use the space
> -3- delete partition #1 (yes!, the #1 content of which is SliTaz_LoRAM_CDROM
> -4- add 1 partition with number #1 *behind* partition #2
> -5- add 1 partition with #3 add the exact (not easy) place where was
> SliTaz_LoRAM_CDROM
> -6- give it type 17
>
> Here is the result:
>
> fdisk -lu /dev/sdf
>
> Disk /dev/sdf: 4011 MB, 4011491328 bytes
> Units = sectors of 1 * 512 = 512 bytes
>
> Device Boot Start End Blocks Id System
> /dev/sdf1 6338560 7834943 748192 6 FAT16
> /dev/sdf2 280576 477183 98304 6 FAT16
> /dev/sdf3 477184 6338559 2930688 83 Linux
> /dev/sdf4 32 280575 140272 17 Hidden HPFS/NTFS
>
> Partition table entries are not in disk order
>
> Here is the secret.
>
> Now the key boots SliTaz_LoRAM_CDROM, nut when plugged on an MS Windows
> system, the partition #1 is used, it doesn't matter it is at then end of the
> usb key.
>
> Too tricky for wide use.
>
> Ph.L.
>
> ---
> SliTaz GNU/Linux Mailing list - http://www.slitaz.org/
>
>
---
SliTaz GNU/Linux Mailing list - http://www.slitaz.org/