I extracted the contents of VL5.9-Light-B2.iso to my USB stick.I also extracted the contents of the isolinux folder (from the iso) to the root of the USB stick.I changed the name from isolinux.cfg to syslinux.cfg.Did a syslinux x: (in windows).The thinclient booted right away from the USB stick, and was ready to install VL light!

What does he mean by "extracted"? Is that just a straight copy to the USB stick? I'm never sure how to handle iso s.

I'm know very little about Windows, how do I get to the DOS prompt to run the syslinux command?

After that is done, copy your contents of the ISO over to the newly formatted partition on the USB stick.

____ ONLY ON OLD ISO's (5.9 and older) ______Rename the directory called isolinux to syslinuxgo into the newly ranamed directory (syslinux) and find the file named isolinux.cfgrename this file to syslinux.cfg

I formatted the USB stick with the HP program you recommended Moe and installed the virtual clone drive. Then copied the contents of the CD with the VL 6 iso over to the USB stick.

In linux I ran:root:# syslinux -f /dev/sdbsyslinux: this doesn't look like a valid FAT filesystem

so I tried:root:# syslinux -f /dev/sdb1

No problem this time, so I assumed the USB stick was bootable but the eeePC didn't boot from it despite setting the BIOS to boot from "Removable Dev". So I tried it on my Acer laptop and it wouldn't boot from it (with suitably modified BIOS boot priority).

What am I still doing wrong?Have to do some "real work" now but will get back to it.

Thanks for pointing out the bootinst.sh, MOE-Inx. Good idea. I've eventually worked out how to use it but even though [Removable dev] is the first boot device in the eeePC BIOS, it still doesn't boot into the USB. Probably something to do with my modification of the bootinst.sh.

I have a bootable FAT32 single partition of 3.8Gb on the USB stick. Had to do it under Linux with fdisk and mkfs to get something both XP and linux recognise.

I copied the contents of my VL6 STD CD to the partition. XP and Linux find everything.

To make it bootable continues to be a problem. XP won't let me do it with syslinux. Says it won't allow changes to the hard drive.

So to do it under linux (because it is a FAT32 drive, I can't execute the bootinst.sh actually on the stick) so in my home directory, as root, I made the directory, vl-temp, and copied over /syslinux and bootinst.sh from the CD.

The modified bootinst.sh (so it pointed to the USB stick) is as follows: there is no error checking in the script so the MBR may not have been modified

#!/bin/bash#Modified from bootinst.sh, Borrowed from SLAX

set -e#these values were found with the command: tail -f /var/log/messagesTARGET=/dev/vl-hot/sdb1MBR=/dev/vl-hot/sdb

clearecho "-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-"echo " Welcome to USB boot installer "echo "-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-"echoecho "This installer will setup disk $TARGET to boot only Vector"if [ "$MBR" != "$TARGET" ]; then echo echo "Warning! Master boot record (MBR) of $MBR will be overwritten." echo "If you use $MBR to boot any existing operating system, it will not work" echo "anymore. Only Vector will boot from this device. Be careful!" echo "$NUM is the NUM variable"fiechoecho "Press [ENTER] to continue, or Ctrl+C to abort..."read junkclear

echo "Flushing filesystem buffers, this may take a while..."sync

# setup MBR if the device is not in superfloppy formatif [ "$MBR" != "$TARGET" ]; then echo "Setting up MBR on $MBR..." ./syslinux/lilo -S /dev/null -M $MBR ext # this must be here to support -A for extended partitions echo "Activating partition $TARGET..." ./syslinux/lilo -S /dev/null -A $MBR $NUM echo "Updating MBR on $MBR..." # this must be here because LILO mbr is bad. mbr.bin is from syslinux cat ./syslinux/mbr.bin > $MBRfi

echo "Setting up boot record for $TARGET..."./syslinux/syslinux -d syslinux $TARGET

echo "Disk $TARGET should be bootable now. Installation finished."

echoecho "Read the information above and then press [ENTER] to exit..."read junk

I don't know how to check the MBR. Or what to look for. What simple step have I missed?no2

From experience, I can tell you that this is most likely your partitioning.

From what I've seen, parted, cfdisk, and all the good linux tools can create a fat32 fs/partition, but for some reason syslinux cannot make these bootable... it says it does, but they almost never do for me.

Sometimes, not even formatting the usb pendrive as fat32 with windows is good enough..The only way have been able to do it is using the HP Disk Formatting tool.I dont know what they do differently than a windows formatting, but it works when I do it with their tool.

From experience, I can tell you that this is most likely your partitioning.

The only way have been able to do it is using the HP Disk Formatting tool.I dont know what they do differently than a windows formatting, but it works when I do it with their tool.

Thanks for all the help MOE-Inx, but I had to give up.

After reformatting with the HP tool, copying over the contents of the VL6 iso, and coming back to the Asus (and XP) to run syslinux, I kept getting this error message:

16 bit Windows SubsystemAn application has attempted to directly access the hard disk which cannot be supported. This may cause the application to function incorrectly.Two button choices - "Close" and "Ignore".

I chose "Ignore" but the USB stick was still not booting. (In retrospect, it may have been trying to use syslinux.com rather than syslinux.exe)

But I'm posting this from the Asus eee PC running VL6

I got fed up with all the problems with the USB method and became more aggressive; I took out the hard drive and put it into my Acer notebook (also a SATA HD). I then installed from the CD. Returned the HD and ran vasm from the tui login to redo all the hardware. It works fine.

Haven't checked wireless, webcam or sound yet but will report on that in another thread.

I wonder if we shouldn't look at packaging unetbootin so that other potential netbook users don't have to go through this frustration. Swapping hard drives isn't the most elegant solution.