Many thans.
E.
http://download.webconverger.com/webc-6.1.iso will work in this case
the same as the current instructions use .img
--
You received this message because you are subscribed to the Google Groups "Webconverger Users" group.
To post to this group, send email to webc-...@googlegroups.com.
To unsubscribe from this group, send email to webc-users+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/webc-users?hl=en.
A had actually sucessfully created a bootable image on a USB flash
memory stick. That had been accomplished by
- downloading the (hybrid)webc-6.1.iso;
- changing the file type manually (by replacing ".iso" by ".img" in
the file name)
- writing the image on a FAT32 formatted USB stick, using the win32
disk imager (which only works with ".img" fule type).
Having done this, everything worked fine. HOWEVER: I wanted to edit /
isolinux/lice.cfg to personalize some parameters,
the same way I had done with various previous versions (up to
webc-6.0) but I found this to be impossible since
the USB stick was not automatically recognized as mountable (under
Linux Mint), neither editing of the file was
allowed, even after forcing the mounting of the USB stick.
This lead me to believe that I must have done something wrong in
creating the bootable USB stick, and that is why
I asked for guidance about how to create it. In reality the practical
problem is that the image on the USB - unlike
for previous webc versions - now appear to be "hidden".
I hope this better clarified the nature of the question.
As always, thanks for your help.
E.
On Mar 8, 1:17 am, Kai Hendry <hen...@webconverger.com> wrote:
> Sorry I need to updatehttp://webconverger.org/usb/
>
> http://download.webconverger.com/webc-6.1.isowill work in this case
Besides that, the three fundamental things I would care to understand
are:
1) Manual change of the ".iso" into ".img" in the filename: is that a
correct way of proceeding?
2) Is it right that the bootable USB appears "hidden" and therefore
not automatically mounted?
3) Is it normal that live.cfg on the USB stick remains non-editable
even after mounting the hidden partition hosting it?
I hope my question make some sense, since - as I wrote some other
times, and as it probably shows - I am very far from being a guru in
this field.
Thanks.
E.
You're right. I am not keen to carry on building the USB image tbh, I
prefer the similar single image option.
> 1) Manual change of the ".iso" into ".img" in the filename: is that a
> correct way of proceeding?
Unnecessary. You can dd the 6.1 iso directly.
> 2) Is it right that the bootable USB appears "hidden" and therefore
> not automatically mounted?
I can mount it in Linux, though I can't change live.cfg. I don't know
how it appears in Windows.
> 3) Is it normal that live.cfg on the USB stick remains non-editable
> even after mounting the hidden partition hosting it?
Yes, unfortunately.
Kind regards,
After some tests with different systems (Debian, Ubuntu & Windows) I
did not manage to boot from an usb-stick prepared with the hybrid-iso.
Therefore I changed in my building environment the option to -b usb-
hdd and pushed the *.img onto the usb-stick. This worked fine for me.
> > 1) Manual change of the ".iso" into ".img" in the filename: is that a
> > correct way of proceeding?
>
> Unnecessary. You can dd the 6.1 iso directly.
Didn´t work for me. Booting from a stick after dd the *.6.1.iso onto
an usb-stick does not work when I use the howto (http://
webconverger.org/usb/).
> > 2) Is it right that the bootable USB appears "hidden" and therefore
> > not automatically mounted?
>
> I can mount it in Linux, though I can't change live.cfg. I don't know
> how it appears in Windows.
Under Windows the whole stick is unreadable.
Greez, GMF
dd-ing this iso-hybrid and booting an EEEPC works for me. How exactly
and version of dd etc. are you using to dd the 6.1 image to USB stick?
Hi Kai-Hendry,
I can confirm this Problem. Copy 6.1 with dd leads to an unreadable
USB Stick in Windows and won´t boot at all from any Machine I have
here.
Finally tested some things:
Test #1:
1. Downloaded webc-6.0.img
2. transfered the image with 'dd' (debian) onto the stick
3. plugged the stick in the Test-PC
4. booting webconverger without any problems
Test #2:
1. transfered the image with 'physdiskwrite' (windows) onto the stick
3. plugged the stick in the Test-PC
4. booting webconverger without any problems
Test #3:
1. Downloaded webc-6.1.iso
2. transfered the image with 'dd' (debian) onto the same stick
3. plugged the stick in the Test-PC
4. trying to boot from this stick is followed by this message:
isolinux.bin missing or corrupt.
Test #4:
1. Downloaded webc-6.1.iso
2. transfered the image with 'dd' (windows) onto the same stick
3. plugged the stick in the Test-PC
4. trying to boot from this stick is followed by this message:
isolinux.bin missing or corrupt.
Test #5:
1. Downloaded webc-6.1.iso
2. changed the extension (ISO) to IMG
3. transfered the image with 'Win32 Image Writer' onto the stick
2. plugged the stick in the Test-PC
3. trying to boot from this stick is followed by this message:
isolinux.bin missing or corrupt.
Test #6:
1. building my own webc-6.1 (http://webconverger.org/develop/)
2. changed in auto/config to '-b usb-hdd'
3. transfered the image with 'dd' (debian) onto the stick
4. plugged the stick in the Test-PC
5. booting webconverger without any problems
Version-Infos:
debian: dd (coreutils) 6.10
windows: rawwrite dd for windows version 0.5.
physdiskwrite v0.5.2
dd-commands:
debian: dd if=webc-6.1.iso of=/dev/sdb
windows: dd if=webc-6.1.iso of=\\.f: --progress
physdiskwrite -d 1 webc-6.1.iso
My next step would be to make some changes to live.cfg on the stick
from test #6.
Greez, GMF
from test #5.
Greez, GMF
On 22 March 2010 23:02, GMF <g...@bitchcop.de> wrote:
> 4. trying to boot from this stick is followed by this message:
> isolinux.bin missing or corrupt.
A customer has informed me he edits the ISO-hybrid flashed USB stick
like so to get it working:
# more syslinux/syslinux*
include menu.cfg
default /syslinux/vesamenu.c32
Can you confirm this?
https://fedorahosted.org/releases/l/i/liveusb-creator/liveusb-creator-3.9.1-setup.exe
then change the word isolinux to syslinux in syslinux/syslinux.cfg
directly on the usb-stick
default /syslinux/vesamenu.c32
Michael
My test-PC:
Mainboard: Intel Desktop Board D865GVHZ
CPU: Intel Pentium 4 3GHz
RAM: 1,5 GB DDR400
Bios: BF86510A.86A.0061.P17
Greez, GMF
???
I really don´t know what I have to do with these commands.
When I flash an usb-stick with the original webc-6.1.iso it shows up
like this:
ifos-debian:/media/Webconverger 20100221-13:16# ls -la
insgesamt 30
dr-xr-xr-x 7 gmf root 2048 21. Feb 13:22 .
drwxr-xr-x 5 root root 4096 25. Mär 20:43 ..
-r--r--r-- 1 gmf root 60 21. Feb 13:16 autorun.bat
-r--r--r-- 1 gmf root 29 21. Feb 13:16 autorun.inf
dr-xr-xr-x 2 gmf root 2048 21. Feb 13:22 .disk
dr-xr-xr-x 3 gmf root 4096 21. Feb 13:22 doc
dr-xr-xr-x 3 gmf root 2048 21. Feb 13:22 install
dr-xr-xr-x 2 gmf root 4096 21. Feb 13:22 isolinux
dr-xr-xr-x 2 gmf root 2048 21. Feb 13:22 live
-r--r--r-- 1 gmf root 4277 21. Feb 13:22 md5sum.txt
-r--r--r-- 1 gmf root 814 21. Feb 13:16 README.html
-r--r--r-- 1 gmf root 547 21. Feb 13:16 README.txt
-r--r--r-- 1 gmf root 1903 21. Feb 13:16 style.css
There is no syslinux. So please can you tell me more detailed how I
should use your commands?
Greez, GMF
A report follows when bios is up to date.
Greez, GMF
Flashing the usb-stick with the fedora-tool and changing 'default /
syslinux/vesamenu.c32' worked like a charm.
The only problem I still have is to change the contend of the iso-
file, flash the changed iso-file onto an usb-stick and booting from
it.
But this problem is still discussed in an other thread here.
Sorry for the delay but I`m very busy these days...
Greez GMF
On Mar 23, 12:08 pm, Michael Steinböck <michael.steinbo...@gmail.com>
wrote:
> for me it was easier to use the fedora usb-utility:
>
> https://fedorahosted.org/releases/l/i/liveusb-creator/liveusb-creator...
Greez, GMF
> > webc-users+...@googlegroups.com<webc-users%2Bunsubscribe@googlegroups.com>