SliTaz Forum
You are not logged in.
Hi, Fatmac.
I appreciate your help very much, but your posts re confusing me so much that I can't sleep.
-- What is the difference between copying and dd-ing? What is the purpose of dd-ing?
-- You wrote: "Once you have an installation on your hard drive, you should be able to upgrade it to version 4". I have no intention of putting Slitaz on my hard drive. I explained this in my first post, and again many times. I want to run it from a pendrive.
-- It does not help when you say that rawrite.exe is an "image writing program that run under MS Windows". I need to know what it does, and why and how I should use it.
-- You wrote:
"On SliTaz 4.0 there is a program called isohybrid & it is part of syslinux, I believe.All that you have to do, at a command line/in a terminal, is this :-
isohybrid name_of_your.iso then you can 'dd' (image write) it to a pendrive & it will boot up."
How can I use isohybrid - a syslinux file in Slitaz - in a commandline if I have not yet installed Slitaz? This makes no sense to me at all. Or do you mean I should use this procedure after I have installed Slitaz 3?
-- You wrote: "Some iso images are already hybrid isos, those can be written to pendrives & they will boot." I have extracted many Linux distro iso files to pendrives, and none of them would boot. I suppose that's why there are so many
programs for creating bootable pendrives (most of which don't work either, like tazusb). If it were as simple as you say, then why is everyone having so much trouble and why are so many people writing special programs to make bootable pendrives?
-- Is dd a standard Linux command? What about using dd.exe in Windows, if I can make an isohybrid in Windows?
Cheers!
Mike
Offline
For Linux users dd is a standard program, it copies blocks of a drive, not files, from one drive to another drive or to a file, that file is then an image of the drive just copied.
You said you had a bootable pendrive with Puppeee on it that had the isohybrid program, it will also have dd.
Put your SliTaz.iso on your Windows disk in its root (C:\), put your Puppeee pendrive into a usb slot & reboot into Puppeee.
In a terminal in Puppeee, as the root user, mount your Windows partition, (mount /dev/sda1 /mnt).
Change directory into your Windows computer, (cd /mnt). Type ls, you should see your SliTaz.iso file.
Type isohybrid SliTaz.iso, you now have a hybrid SliTaz.iso.
Put a clean pendrive into another slot. You now need to be certain of its /dev designation, type dmesg | tail, this will show you. (Likely to be /dev/sdc1)
Once you are absolutely sure of its /dev designation, type dd if=SliTaz.iso of=/dev/sdc bs=1M.
this will now write the SliTaz.iso image onto your second pendrive.
You now have a live SliTaz pendrive.
Hi, Ceel.
I had an emergency in my house: a leaky roof. So I have been too busy to reply until now.
However, I have tried again all the methods suggested here so far except your manual install: iso2exe, tazusb, isohybrid.exe, dd.exe. None of them has worked, and I have lost many frustrating hours.
But I am not giving up. I want Slitaz on a pendrive.
If all else fails, maybe I can borrow a usb cd-rom from someone, put slitaz-3.0.iso on a cd, and install to pendrive from that. Yes?
But I will try your manual install first.
So just a few questions for now about that:
-- Is the latest version of Syslinux the best one to use for your manual install? You know, it does not have the .bat file any more.
-- You said: "download slitaz-4.0.iso on the stick". But you also said "don't work with SliTaz4.0". Bellard said that Slitaz 3.0 is hybris, but 4.0 is not. Should I use version 3?
-- You said: "copy \syslinux-9.20\win32\syslinux.exe in boot\syslinux". Do you mean I should copy the whole directory structure (\syslinux-9.20\win32\syslinux.exe), or just syslinux.exe?
-- You said: "type
e:\boot\syslinux>syslinux -ma -d \boot\syslinux e:
Are you sure the right command is "syslinux -ma -d" and not "syslinux -maf -d"? (The reason I ask is that the Puppeee4.4 batch file used the same syslinux command but with -maf operators.)
If you will please answer these few questions, I will try your manual install method this week.
Merci pour tout ton appui.
Mike
Offline
Hi, Fatmac.
I have been too busy with a leaky roof to reply until now.
I tried all installation methods again, with no success. I even found on the Internet versions for Windows of isohybrid and dd programs (isohybrid.exe and dd.exe), installed them in Windows\system32, and ran them in a commandline on all my Slitaz versions (2, 3, and 4). Did not work. Will not boot.
I also tried the Linux commands on my Slitaz iso's while in Puppeee 4.4. That also did not work.
The problem (aside from anything being wrong with the iso files themselves) is that when I dd onto the pendrive, it is no longer a recognizable file system to Windows. I don't know if this should matter, so long as it boots. But it doesn't.
I tried everything I could think of. I tried formatting the pendrive FAT32, FAT16, and ext3, before dd-ing the iso to it, but it made no difference. It still would not boot.
I had a lot of trouble in Puppeee 4.4, too. I did some research on the isohybrid and dd programs, and it seems that they work best on FAT16. But Gparted doesn't like FAT16, at least on Puppeee 4.4. FAT16 is on the drop-down menu of available formats, but it won't do it. After I try to re-format FAT16, Gparted returns FAT32.
So I am really stuck. No method of installing Slitaz has worked.
What am I doing wrong?
Cheers!
Mike
Offline
Did you try http://mirror.slitaz.org/boot/isohybrid.exe to convert http://mirror.slitaz.org/iso/4.0/slitaz-4.0.iso and http://mirror.slitaz.org/boot/dd.exe to create a boot stick ?
> dd.exe --help
> dd.exe --list
Edit: isohybrid.exe is a DOS and a WINDOWS executable, dd.exe is a WINDOWS executable only.
Offline
Mike7 said "What am I doing Wrong?"
I honestly don't know, it worked for me.
(Sorry, I don't have any other suggestions.)
If all else fails, maybe I can borrow a usb cd-rom from someone, put slitaz-3.0.iso on a cd, and install to pendrive from that. Yes?
Yes but if you create a LiveCD, use slitaz-4.0.iso :-)
You can also use a RW cd-rom if you have one.
Is the latest version of Syslinux the best one to use for your manual install? You know, it does not have the .bat file any more.
Reading the french page to install SliTaz from windows, I saw the link, in "Version rapide", for syslinux.zip pointed to http://files.openomy.com/public/Erjo/syslinux.zip. This link is not active anymore and I suppose Erjo had placed in his zip file the bootusb.bat. You won't find it in any syslinux.zip you'll download, you have to type all the commands yourself...
You said: "download slitaz-4.0.iso on the stick". But you also said "don't work with SliTaz4.0". Bellard said that Slitaz 3.0 is hybris, but 4.0 is not. Should I use version 3?
Yes you're right, use a 3.0 iso! My mistake; I never succeded to install SliTaz4.0 correctly on a FAT 16/32 stick.
You said: "copy \syslinux-9.20\win32\syslinux.exe in boot\syslinux". Do you mean I should copy the whole directory structure (\syslinux-9.20\win32\syslinux.exe), or just syslinux.exe?
Just copy the syslinux.exe but take care, here is an other error in my post: copy \syslinux-5.01\win32\syslinux.exe (and not 9.20).
You said: "type
e:\boot\syslinux>syslinux -ma -d \boot\syslinux e:
Are you sure the right command is "syslinux -ma -d" and not "syslinux -maf -d"?
Yes, but you can use -ma or -maf
-m = Mbr; install a bootable MBR sector to the beginning of the drive
-a = Active; marks the partition used active (=bootable)
-f = Force installing
I never needed the - f option
I saw in 3.0 that the \boot\syslinux\syslinux.cfg is a little different of this of 2.0. Edit it using notepad as this:
display syslinux.msg
label slitaz
kernel /boot/bzImage
append initrd=/boot/rootfs.gz rw root=/dev/null vga=normal autologin
include common.cfg
Offline
Hey Mike7,
Good news! I spent my evening to test different iso and where UNetBootIn, LiLiCreator or others fail, the old method written by fantomas at http://doc.slitaz.org/fr:handbook:liveusb#installer-slitaz-sur-usb-depuis-windows (strangely never translated in english ?) works like a charm, even the 4-in-1 slitaz-4.0.iso, as well as FAT16 than FAT32 (somebody knows why the LiveUSB is faster with FAT16?)
Follow the steps I gave you in previous posts, just change the version of syslinux: syslinux-4.05 for SliTaz 4.0, syslinux-3.82 for SliTaz 3.0 (syslinux-3.73 for SliTaz 2.0 and syslinux-3.61 for SliTaz 1.0) if you want that options work at boot.
If you use slitaz-4.0.iso, you'll just have to
[*]rename \boot\isolinux in \boot\syslinux
[*]copy the \syslinux-4.05\syslinux.exe file in the \boot\syslinux repertory of your stick
[*]rename \boot\syslinux\isolinux.cfg in \boot\syslinux\syslinux.cfg
[*]modify line #32 of \boot\syslinux\syslinux.cfg from [c]kernel /boot/isolinux/ifmem.c32[/c] to [c]kernel /boot/syslinux/ifmem.c32[/c]
[*]and make your stick bootable and, as says totoetsasoeur,
Happy SliTaz!
Promissed; as soon as I'll find time, I'll improve the documentation.
Now windows users, you have no excuse to not try SliTaz!
J'espère que tu es à nouveau au sec :-)
Tu n'aurais pas des bouleaux à proximité de ta maison ?
Offline
Hi, Bellard.
I can no longer remember where I downloaded the isohybrid.exe and dd.exe files from, but they seemed to work:
> isohybrid Slitaz-4.0.iso
There was a pause before the prompt returned; and the iso file was larger after running the command than before.
> dd if=Slitaz-4.0.iso of=\\.\e:
xxxxxx bytes in
xxxxxx bytes out
Not sure what you mean, that dd.exe is a WINDOWS executable only. The version I have runs from the command interpreter. I put it, together with isohybrid.exe, in C:\Windows\system32, and it runs at any level just like all the other commands. Or so it seems, anyway.
But the stick won’t boot.
Cheers!
Mike
Offline
Hi, Ceel.
Je te donne beaucoup de travail, je crains. J’ai des remords.
I have noted all your changes and instructions. I will collate them and try out your procedure as soon as I have time (and the courage <grin>).
You wrote:
> . . . if you create a LiveCD, use slitaz-4.0.iso.
I think I will stick to slitaz-3.0.iso for all attempts to create a bootable usb stick. After reading that version 4 iso is not hybrid I don’t trust it any more.
> You can also use a RW cd-rom if you have one.
I have no external CD for my netbook. Also, I live in Buenos Aires, where they are very expensive. (I am from New York City originally).
> I suppose Erjo had placed in his zip file the bootusb.bat. You won't find it in any
> syslinux.zip you'll download, you have to type all the commands yourself...
I think it is best to have a batch file in the root of the usb stick for creating the MBR. The BIOS in many computers such as my EeePC does not seem to understand the MBR made by syslinux.exe. But I will try it anyway.
> I never succeded to install SliTaz4.0 correctly on a FAT 16/32 stick.
Please do not mention FAT16 <grin>. Even Windows XP does not know what to do with FAT16, even though the drive manager allows you to create a FAT16 file system. And Gparted hates FAT16.
> copy \syslinux-5.01\win32\syslinux.exe (and not 9.20).
J’ai compris.
> you can use -ma or -maf. . . I never needed the - f option
I force everything. Merde, alors, avec ces commandes!
> the old method written by fantomas at
> http://doc.slitaz.orgfr:handbook:liveusb#installer-slitaz-sur-usb-depuis
> -windows works like a charm
I wish I could understand it.
> as says totoetsasoeur,
> Happy SliTaz!
C’est Toto où sa soeur qui l’a dit?
> J'espère que tu es à nouveau au sec :-)
Je suis au sec dans ma chambre où j’écris ceci, mais le toit de ma salle à manger est au point de s’enfoncer à cause de la pluie. J’habite une maison très vielle.
> Tu n'aurais pas des bouleaux à proximité de ta maison?
Des bouleaux dans le centre-ville, à Buenos Aires? Tu rêves, mon amie.
Offline
Hello, Fatmac.
Don't worry. Thank you for all your help. I think the fault is with my computer or the pendrives I am using, not with your method. The isohybrid and dd commands seem to work just as they should. But there appears to be something peculiar about the BIOS in my computer. I was able to create two bootable usb sticks a month ago, but since then I can do none and I have tried everything.
However, I learned a lot from trying. All this is completely new to me. So just learning for example what the dd command does, is useful to me. Before, I knew nothing about formats and raw data. Now I know a little.
So, thank you again for your kind help.
Cheers!
Mike
Offline
@Mike7
I translated old fantomas method into English: http://doc.slitaz.org/en:handbook:liveusb
It is a straight translation. I mean I did not test the method itself.
Would you please try it and post comments here?
Happy slitaz.
Offline
@mike
> There was a pause before the prompt returned; and the iso file was larger after running the command than before.
Are you sure that you run http://mirror.slitaz.org/boot/isohybrid.exe ?
It does not change the iso size (update the first 32Kb only).
Tested with Windows 98, Windows XP, wine, dosbox. Take less than 1s with a pentium 133 / windows 98.
Which Windows are you running ?
dd.exe is 32bits (windows) only. isohydrid.exe from mirror is 32bits (windows) and 16bits (dos before windows 95)
Offline
Hi, totoetsasoeur.
That was a good thing to do, for English-speakers having trouble with a USB install. I have made a copy of it and will try it as soon as I have a chance.
In the meantime, however, I have finally succeeded in booting Slitaz-3.0 from my pendrive! For what I did, see my post to Ceel, below.
Thanks for your help.
Cheers!
Mike
Offline
Hi, Bellard.
I have two isohybrid.exe files. One of them, which is 2,431,994 bytes, I got from http://www.com-magazin.de/fileadmin/download/ergaenzungen/com0609/isohybrid.exe. This is the one I put in c:\windows\system32 to use in a commandline.
The other isohybrid.exe file is 27,136 bytes, and I no longer recall where I got it.
I just downloaded yours, the one from the Slitaz mirror, and compared its size with the with the other two. It is also a small file, 34,436 bytes, but somewhat larger than my other small one.
So, there seem to be many versions of isohybrid.exe. I will give the Slitaz version a try, but I do not know any way of testing the result. For that matter, I do not know any way to test an iso file to see if it is hybrid. Do you know of a way to do this?
To answer your question, my version of Windows is XP Service Pack 3. It has been modified somewhat by Asus for my netbook (Asus EeePC 1000HA).
I believe that an installation method using isohybrid.exe and dd.exe could work. But there are unresolved questions about the results of applying isohybrid.exe to an iso, and there are unresolved questions about the use of dd.exe on a pendrive. There is also the question of whether raw data from an iso, hybrid or not, can be used by the BIOS of my computer (or another).
This is an interesting subject and worthy of further study. I spent many hours trying to use this method and failed, But I believe it can be made to work.
Cheers!
Mike
Offline
Hi, Ceel.
Success! I now have a bootable pendrive with Slitaz-3.0 on it.
Here's what I did:
I compared the instructions you gave me with the procedure used by Universal-USB-Installer (from pendrivelinux.com). That installer is the most reputable one. It is recommended by Ubuntu. It is also the only installer that is transparent: It prints out a flow of operations.
It seemed to me that your instructions and the procedure of Universal-USB-Installer were essentially the same. I was not able, previously, to boot from a pendrive made by Universal-USB-Installer, but I thought it was worth another try, with a modification to the MBR. (I have always thought that the MBR was the problem for me, because the only installation that has worked until now was Puppeee, which, as you will remember, uses a bootinst.bat file to create an MBR specific for Puppeee.)
First I used Gparted in Puppeee to partition my pendrive with a 1Gb FAT32 boot partition, leaving the rest (3Gb) unallocated. Then I removed the newly formatted and partitioned pendrive from my computer and shutdown Puppeee.
I booted into Windows, plugged in the pendrive, and, with the new information that Slitaz-3.0.iso is hybrid, I installed Slitaz-3.0.iso using Universal-USB-Installer. I removed the pendrive and shut down.
I booted back into Puppeee Linux, plugged in the pendrive, and used the testdisk tool. First, it recorded a problem in the boot sectors, and I let it fix the problem. Then it offered the choice of having testdisk write a new MBR to the pendrive, and I let it do this.
I unplugged the pendrive, shut down windows, plugged the pendrive back in, and, while powering on, pressed the "Escape" key to get the pre-BIOS boot choice: Boot From HDD or Boot From Removable Media. I chose Removable Media, and it booted into Slitaz. Voilà!
I need your help now with four initial problems:
-- How can I boot without having to run through the language and keyboard selection every time?
-- How do I set up persistence?
-- How do I get administrator privileges? (I tried every way I could to do this, and also to change the password, but failed.) And how do I set it up so that I do not have to enter a password every time I click on a reserved (admin) application?
-- How do I set up wireless? (Slitaz 3.0 has the Atheros5xxx driver, yes?)
These are priorities. Can you help me with them? Then I will be off and running with my new Slitaz operating system.
Happy Slitaz!
Cheers!
Mike
Offline
@ Mike7,
I would just add a word to your post above: Yyyyeessss !!!!!
Welcome to SliTaz!
How can I boot without having to run through the language and keyboard selection every time?
Just modify your /boot/syslinux/syslinux.cfg (ie for french) like this:
[c]append initrd=/boot/rootfs.gz rw root=/dev/null[/c] lang=fr kmap=fr [c]vga=normal[/c]
How do I set up persistence?
Unfortunately, you can't... with a FAT16 or 32 LiveUSB but you can now make a new Live that will have persistence:
[*]Download the SliTaz iso of your choice in /home/tux
[*]Format a stick ext3
[*]Then >>> Applications > System tools > Create a liveUSB; password is root of course
[*]image iso >>> select your iso
[*]USB Media >>> choose the good stick!
[*] click OK and wait... it'ready!
Minor differences with your FAT stick:
[*]the /boot/syslinux is replace by /boot/extlinux folder
[*]the config file is now /boot/extlinux/extlinux.conf
Don't forget to modify extlinux.conf as indicate above to have language, keyboard
How do I get administrator privileges? (I tried every way I could to do this, and also to change the password, but failed.) And how do I set it up so that I do not have to enter a password every time I click on a reserved (admin) application?
Well, not sure you can do it simply with a Live.
You have to wait that a professsional takes the hand for this, I'm just a sorcerer apprentice (and far to be Harry Potter :-))
If you don't have any answer, I'll try it this week end. I don't have my livebook tonight, just use a very old P4 with SliTaz 4.0 installed.
How do I set up wireless? (Slitaz 3.0 has the Atheros5xxx driver, yes?)
This shouldn't be very difficult if the driver exists for SliTaz 3.0.
You can find posts about Atheros on the forum but may be the best is to wait for Mojo, the Master for wifi.
(Hi mojo!)
EDIT: see this http://forum.slitaz.org/topic/setting-up-wifi-on-eeepc701#post-8569
Hope it'll help.
Offline
@ Mike7,
I suggest you to open new topics for your other problems and to mark this one as solved.
I came back home later today. I didn't see time passing. It is time to go to bed.
Offline
Hi, Ceel.
I will make a new live stick, following your directions, as soon as I can get another pendrive. Is it okay to put slitaz-4.0 (or slitaz-4.0-firefox) on it, even though they are not hybrid iso's? Should I run isohybrid on the iso before installing it with Create A Live USB?
I finally figured out that the word "root" was the password. This is not very clear from the instructions page. I am going to make a suggestion about this in a separate post.
Since I was able to open the network applications with "root", I have formed more specific questions about getting wireless to work, and I will make a separate post about that, too (probably a new thread would be best, as you say). Post 8569 was not much help, as the version of Slitaz was different and so, too, was the computer.
I want to thank you again for all your kind support and help, Ceel. It is a pleasure to join you in this nice Slitaz community.
À très bientôt, j'espère.
Mike
Offline
Hi, all. Allô, tout le monde.
I have a suggestion about the introductory English documentation that accompanies Slitaz (at least Slitaz 3.0).
On that document page there is a brief explanation about the password protection used by Slitaz. In it, there is the expression "(default root)". That is not very clear and can lead to misunderstanding, as was the case when I first booted up Slitaz and was unable to access any of the administrative applications. It should be changed to "(default "root")" to make it clear that the default password is the word "root". Without the quotation marks around the word "root", the expression "default root" appears to be an explanation of what preceeds it, which it is not. Making the change will solve what can be, and was for me, a very vexing problem: how to access applications.
I hope you will take this suggestion in the spirit of collaboration that it is intended.
Cheers!
Mike
Offline
Hi Mike7,
Yes you can use slitaz-4.0 or slitaz-4.0-firefox or all other flavors or releases you want. No need to run isohybrid before installing. This method has worked with all the SliTaz's iso I've downloaded, without any problems.
By the way, I've updated the french section "Installer SliTaz sur USB depuis Windows". If you do a new Live, could you test it please and tell me if all is clear? Then I'll update the english page.
Thanks to totoetsasoeur to have translated the original text; this will save me time.
Concerning root privileges, I've read your post too quickly and understood you wanted to boot automatically with admin rights...
It has been a pleasure to help you too. Few people are so persistent, most would have abandoned.
Hope we can work together again.
Offline
Hi, Ceel.
You wrote:
> Yes you can use slitaz-4.0 or slitaz-4.0-firefox or all other flavors or
> releases you want. No need to run isohybrid before installing. This method
> has worked with all the SliTaz's iso I've downloaded, without any problems.
Were you booting them from a USB stick?
> If you do a new Live, could you test it please and tell me if all is clear?
> Then I'll update the english page.
What would you like me to test (besides whether or not it boots {grin})?
> I've read your post too quickly and understood you wanted to boot
> automatically with admin rights...
That would be nice. Having to click on the password sub-routine every time you want to access an admin app is a real pain in the derrière.
I am not going to close this thread yet because I have some new information for Bellard (and other interested members) about dd.exe.
Cheers!
Mike
Offline
Hi, Bellard (and others interested in the use of dd.exe, the Windows version of the Linux dd command, for creating bootable USB sticks from hybrid Slitaz iso files).
I emailed some questions to John Newbigin, the author of the version of dd.exe that I have been using.
---------------------------------------------------------------
[John Newbigin | ITS Senior Analyst / Programmer
Faculty of Information and Communication Technologies
ITS | Swinburne University of Technology | Melbourne, Australia
O: EN306 | T: +61 3 9214 8185 | M: +61 410 569 362
E: jnewbigin@swin.edu.au]
---------------------------------------------------------------
Here are my questions and his replies:
> Hi, John.
>
> I am trying to use dd.exe to put hybrid iso files of various linux
> distros onto pendrives from an Asus EeePC 1000HA netbook whose BIOS
> will boot from USB removable media. No luck so far, but I am studying
> your documentation at http://www.chrysocome.net/dd and have a few
> questions:
>
> Am I correct that the of= address for a removable usb device can
> be in the form \\.\x: ? Or must it be in the long form as \hardrive1\ ?
There are 2 syntaxes you can use. UNC or John's invention.
\\. is a UNC standard (you know about \\servername, well \\. says the
local computer). From there, Microsoft allows you to specify driver
letters, but drive letters are normally attached to filesystems which
are attached to partitions, not disks.
If you want to talk to a disk (other than a floppy disk or CD) then you
can't use \\.
But you can use my way which is based on the NT Native IO path.
In your case, I am pretty sure you will have to use the format
\\?\Device\Harddisk<X>\Partition0
You just have to work out the value for X. dd can try and do this for
you if you specify
od=x: (This means, find the disk for the partition mounted on x:)
> When if= an iso file on the hard drive, must the --size operator
> necessarily be used to keep dd from reading beyond the end of the
> file?
No. --size is only needed for block devices on older windows OS (before
Microsoft realised that knowing the size of a disk was important).
> What about controlling the size of the read out? In some
> instances, dd has filled a 4Gb pendrive with the command: dd
> if=xxxx.iso of=\\.\e: when the iso file was 125Mb.
I don't know, but it is possible because you are talking to the
filesystem driver and not the disk. \\.\e: is not where you want to
write to (at least, not before you unmount the filesystem).
> When of= FAT32-formatted usb removable media like a pendrive, will
> dd overwrite the boot sector, specifically the bytes reserved for the
> MBR?
Yes, if you tell it to (the MBR is the first sector of the disk (not the
partition).
> In your documentation you wrote:
>
> "... --size will tell dd to figure out the size of the device and
> make sure it does not read past that point. This is important for USB
> sticks which stop working if you read past the end of them."
>
> Query: Does this apply to the output file as well as the input
> file?
The process will stop when the end of the input is detected or there is
an error so it should not matter the size of the output.
> Query: If it does apply to the output file, and this has happened to
> my USB stick, will re-formatting the stick correct the problem?
All you need to do is unplug the USB stick and plug it back in.
========================================================================
I Hope this is of interest.
Cheers!
Mike
Offline
@ Mike7,
I didn't test yet the slitaz-4.0-firefox iso but yes I've booted LiveUSB created with this method from slitaz-4.0 and slitaz-4.0-core iso's (and other iso's of 3.0 and 2.0 releases). So, as I never arrived to boot a 4.0 LiveUSB made with a third party tool, I'm pretty sure the firefox flavor will work.
What I want you to test?
Just tell me if the instructions are clear enough and if following them you can create a Live that boots. But there is no hurry, try to solve your wifi problem first.
Offline
Hi, Ceel.
Thank you for hanging in here with me. I feel that if I lose you I will never get Slitaz running right and all my hard work will be lost.
Regarding the Slitaz-to-Slitaz installation, I still would like to understand the isohybrid issue. How can a non-hybrid iso like Slitaz-4.0 work on a USB stick? I thought that only hybrid iso's worked on sticks. Can you help to explain? Is it because the Create A Live USB program runs isohybrid on the iso?
I haven't had a chance to look at this Create A Live USB program yet. It's not the same as tazusb, is it? (Pas ça! Non! <grin>.)
I started a new thread named "Oh, no, not another wirless problem!" with a long post including all the data I could get from lspci and network.conf, as well as some bugs I found along the way. Check it out if you have a minute, c'est amusant je crois. (I hope it doesn't put off anyone like Mojo. It was intended in the best spirit.)
As soon as I can get wirless working I'll download a Slitaz 4 iso, try it out with the Slitaz 3 USB creator, and report back.
J'espère que tu as goûté d'un joli weekend.
Mike
P.S. I have been making tests and discovered that there is no coordination on my computer between the Escape key boot choice routine and the F2 full BIOS config routine. This is no doubt the cause of some of these boot problems I've been having. I am writing a summary of this BIOS "bug", in the form of a personal anecdote, and plan to send it to the forum when it's done. It could help others having my same problems.
Offline
[ Generated in 0.023 seconds, 8 queries executed - Memory usage: 1.63 MiB (Peak: 1.77 MiB) ]