Creating USB based boot media for ESX 4 installs
As a follow on to my Automating vSphere ESX4 Host Installations blog I have detailed a howto create USB based boot media using syslinux 3.82 and the ESX 4 installation source files. The process is actually quite simple as we can create the bootable USB from a Windows system. You can also do the same with extlinux but most people will have a Windows based management system so lets only focus on this Windows based method within this blog.
The first step is to ofcourse obtain a copy of the Syslinux 3.82 or higher zip package from http://syslinux.zytor.com/ and extract to a file store of your choice.
Prepare the media:
To prepare a USB memory stick we need to format it with a FAT32 file system. Windows explorer provides that functionallity with a simple right click on your USB device.
Generate a bootable media device:
Once formated we will need to open a cmd prompt and go to our syslinux file store and execute the following example.
In this example the syslinux win32 tool creates a grub based loader and boot sector on the USB memory device mapped to drive G: the tool also defines the syslinux directory using the -d option as the root path and this is where we will copy the ESX 4 initial ramdisk image file and some additional syslinux text menu files. If your planning to use the usb device as a source for the ESX 4 packages then those files e.g. the VMware directory etc. would need to be placed in the root directory of the usb device and not the syslinux directory. In this blog the usb device is only used to launch a remote source file install.
Copy menu and ESX 4 install files:
From the ESX 4 ISO or CD copy the isolinux directory to G: and rename it to syslinux also copy the build_numbler file to G: additionally explore the downloaded syslinux file store and locate ..syslinuxcom32menumenu.c32, copy this file to the G:syslinux location, you may also want to copy vesamenu.c32 if you wish to checkout a GUI based menu. That’s really just eye candy on the requirements side but it can provide some cool background display capabilities.
Create your selectable boot time menu:
Now we are ready to create the syslinux.cfg configuration file in the syslinux directory. Here is an example I created for this blog.
default menu.c32
prompt 0
timeout 9000
menu title ESX 4 Automated Install VC1 HTTP Repo
label Default
kernel vmlinuz
append initrd=initrd.img vmkopts=debugLogToSerial:1 mem=512M quiet ks=http://vc1.laspina.ca:8088/esx/4.0/default.cfg
label vh0
kernel vmlinuz
append initrd=initrd.img vmkopts=debugLogToSerial:1 mem=512M quiet ks=http://vc1.laspina.ca:8088/esx/4.0/vh0.cfg
label vh1
kernel vmlinuz
append initrd=initrd.img vmkopts=debugLogToSerial:1 mem=512M quiet ks=http://vc1.laspina.ca:8088/esx/4.0/vh1.cfg
Once your cfg file is created your ready to boot the USB device either on your server or over RDAC/ILOM interfaces, select a server target from the menu and walk away.
Yes it’s that simple and easy to create USB bootable media for your ESX 4 installs.
Regards,
Mike
Tags: boot, esx, memory stick, menu, syslinux, USB, vSphere
Site Contents: © 2009 Mike La Spina
Subscribe in a reader
Follow me on Twitter
Hello Mike, Great post!!
I followed your steps up until the cfg file and changed only the top line from
default esx to default vesamenu.c32. It all works great, the gui goes through all the usual settings like partions, network, account settings etc. At the end you click next to start the installer and it asks for CDROM. Is there something i’m missing out of the cfg file? I just want it to read from my usb, please can you help?
Thanks for your time..
Hi Tony,
The example was setup to use a central repo. Try adding the key word ks=usb to your append directive.
e.g.
append initrd=initrd.img ks=usb vmkopts=debugLogToSerial:1 mem=512M
Unfortunately you might only be able to use a ks file name of ks.cfg on the usb device with this method based on the docs.
Also what did you spec as a install source in your ks.cfg
e.g.
install = usb
You will need to copy the additional repo VMware ISO files and folders to the root of your usb device shown in the Automating ESX4 install entry.
Hi, I am trying to install ESX from USB.
I have copied the contents of the ESX install CD to the root of the USB drive.
I have tried ks=usb and removed quiet but this doesn’t work, it asks me for media cd at the end of the ESX wizard.
Have you got any ideas?
Thanks in Advance
Dan
Hi Dan,
Have a look at this forum post.
http://communities.vmware.com/message/1295783#1295783
Hi thanks for your quick response and excellent blog!, i have used the askmedia option in the cfg and copied the cd to my flash drive which works fine but the installation gets to 99% and says “no such file or directory ‘/mnt/sysimage/boot/initrd.img” and the machine is unable to boot as the file is missing. Any ideas?
Hi Dan,
The askmedia option should not be required for installing from a boot-able usb stick. Try changing the ks.cfg install token to read install usb
[…] to the ESX Service Console for ESX 4.0 Howto: 101 Scripting ESX server installation on vSphere 4 Creating USB based boot media for ESX 4 installs Automating vSphere ESX4 host installations Cannot log in to an ESX 4 host with vSphere Web Access […]
Hi Mike,
I’ve come so far that it boots from the USB stick and loads all the drivers. However, after coming to having loaded 100 % of the drivers, I get the following error:
Umount: cannot umount /mnt/source: invalid argument
Cannot umount /mnt/media: no such file or directory
Insert the ESX Installation Media
Any help or ideas appreciated.
Thanks & regards,
Sam
Hi,
If you are using the usb drive as the install media source then the kickstart script should have an “install usb” statement. The directory structure should match what you see on the original iso once it’s mounted.
Regards,
Mike
Hi Mike,
Thanks for your response. I have a ks.cfg file in the root of the usb stick, at the moment, it only has one statement in it: install=usb
I am unsure if I have to put more parameters into the ks.cfg file?
The directory structure looks exactly as the DVD (or content of the ISO), only “isolinux” is called “syslinux”.
Thanks, appreciate your swift response!
Regards,
Sam
Sam,
It should not have the = sign, just “install usb”
If your are just replacing the CD with a USB drive then add the “askmedia” statement to your append section of the boot loader.
e.g.
label local
menu label Interactive Local Installation
kernel vmlinuz
append initrd=initrd.img vmkopts=debugLogToSerial:1 mem=512M askmedia
Hi Mike,
Again, thanks a lot for your help. Indeed, I am not planning on using an unattended script to install, I just want to replace the DVD with a USB stick.
So as you advised, I have put this into my ks.cfg:
install usb
askmedia
and then a friend of mine advised to edit my syslinux.cfg as follows:
default esx
prompt 1
#menu title ESX build 164009
timeout 300
LABEL esx
menu default
menu label Install ESX in graphical mode
kernel vmlinuz
append initrd=initrd.img vmkopts=debugLogToSerial:1 mem=512M askmedia
OK, this does not use the menu.c32, however, it works flawlessly and I am now able to install my vSphere Test machine from a USB stick!
Again, thanks a lot for the help and keep up the good work!
Best regards,
Sam
Hi there…
I’m trying to do the installation also on my HP Prolaint 120DL G5 server with a Kingston Datatraveler 8GB USB Disk.
i’ve used the setup in the syslinux.cfg as sam wrote in the last post before mine.
————————-
default esx
prompt 1
#menu title ESX build 164009
timeout 300
LABEL esx
menu default
menu label Install ESX in graphical mode
kernel vmlinuz
append initrd=initrd.img vmkopts=debugLogToSerial:1 mem=512M askmedia
————————-
and in the ks.cfg i have this one line only
————————-
install usb
————————-
I have copied the content from my ISO image of the installation CD to the USB drive. I have also renamed the ‘isolinux’ directory to ‘syslinux’
Also i have copied the ‘menu32’ to the usb disc as described.
I get the same error as Dan. When its 99% done it says that the initrd.img file can not be found.
Any idea of what i am missing?
Hi Lasse,
The message is referring to the location on the original media directory structure. This could be a result of a different relative path or its looking for a item that was in the isolinux dir. The process needs to copy the orignal rd image to the install targets boot volume so try adding the isolinux directory to the usb driver from the original iso file/dvd in addition to the syslinux directory.
Regards,
Mike
Just a quick one. GREAT ARTICLE ! I’ll be trying this tomorrow on new box ! (The ESX install as per the other users). Note if you uses Windows 7 you will need to go and startup an admin CMD or by default it did not allow me to write the mbr. I did that and ran the syslinux -fma in the cmd and it booted correctly.
Otherwise you will get a no bootable partition found in table error.
Wish me luck !
Hi Mike.
I have a USB drive I have created with unetbootin which works for interactive installation.
I have created a CF card the same way and put into my SUN blade. All works until it tries to copy files.
Changed syslinux.cfg and added askmedia – all works until I get the askmedia prompt. There it shows no USB/CDROM.
Opened a console and was able to mount /dev/sda1 as /mnt/source and found there the files on the CF-card.
Obviously the VMware device drivers found the CF-card as a SCSI disk, and not as a USB-drive.
Do you have any idea how I can asscess the CF card (as a SCSI device) as a installation/media source ?
Hi,
The system documentation specifies only the following methods for installation media repo’s.
DVD(CD),FTP,HTTP,HTTPS,NFS,USB.
Thus you should create and external repo in this case since localdisk is not supported.
Regards,
Mike
Hi Again,
This worked a treat (3 servers). I did have to make a change though. The usb device was recognized but did not find any packages so I added the following to the root of the usb drive.
1) Isolinux
2) Misc
3) packages.xml *** I think it looks for this.
Thanks for your help again !!
Regard
Sam
Hi All
I’m really struggling to get this to install from a USB Stick.
I used unetbootin to install the image on a fresh FAT32 formatted USB stick.
I get to 97% complete of the installation and get the following error:
No such file or directory: ‘/mnt/sysimage/boot/initrd.img’
I renamed the syslinux folder to isolinux and the file in the root of the USB stick called syslinux.cfg to isolinux.cfg so it’s a mirror image of the original ESX4 ISO image..
But it still won’t work. Any ideas anyone?!
Thanks
Colin
Colin,
I suggest you simply add the additional folders and not rename the existing ones. I suspect it needs both structures. Sam has implemented it with that method as shown in his comment.
Regards,
Mike
[…] ESXi installikas USB pulgale. Eelinfo on saadud: http://blog.laspina.ca/ubiquitous/creating-usb-based-boot-media-for-esx-4-installs ja […]
[…] ESXi installikas USB pulgale. Eelinfo on saadud: http://blog.laspina.ca/ubiquitous/creating-usb-based-boot-media-for-esx-4-installs ja […]
Great article. I used your config + that described by Sam G. & it all worked a treat……..Who needs a DVDROM hey?
Hi Mike,
I’m having the same issue as listed above. I’ve followed both methodologies listed above (unetbootin & manual)… I’ve replicated the syslinux.cfg shown by you and tried the one provided by Sam. I’ve ensured that at the times I custom-make the usbkey with your process I have not only the syslinux folder but also the isolinux folder. Unetbootin doesn’t create a syslinux folder (it uses isolinux with an absolute path in syslinux.cfg).
Here’s a snippet from my syslinux.cfg:
default vesamenu.c32
prompt 1
menu title UNetbootin
timeout 300
label ubnentry0
menu label Install ESX in graphical mode
kernel /isolinux/vmlinuz
append initrd=/isolinux/initrd.img vmkopts=debugLogToSerial:1 mem=512M askmedia
I have no ks.cfg file as I’m not automating the process (although I’ve tried it with a ks.cfg file with ‘install usb’ in it…
I’m kinda stuck and I have nowhere else to turn. Any thoughts?
Hi,
You have not really indicated what is occurring with your config. However I think I would put the VMware initrd.img file in the syslinux folder and then point the syslinux.cfg append and kernel to it. The idea here is it would keep the init location outside the original VMware install media folder. Also make sure you are not editing the cfg files on a windows system.
Regards,
Mike
OMG!!!This vsphere installation on a generic box is such a pain in the a**. I tried the dvd installation. After sometime it gives me an unmount error and tells me to instert the ESX installation media. I gave up on that and tries the USB. I get all the way to 97% complete and get the /mnt/sysimage/boot/initrd.img error. I even created a directory isolinus directory. placed references to the initrd in the syslinux.cfg with paths and still no go??? Has anyone sucessfully installed on a generic box??? Is there a way I can reduce the size of the ISO and install it from a CDROM?
Thanks and Happy holidays…
-AJ
AJ,
You could try using a remote repository. I know it’s extreme effort just to get it installed but it may work considering it sounds like a local controller issue.
Have a look at this blog entry http://blog.laspina.ca/ubiquitous/automating-vsphere-esx4-host-installations
And yes I have used generic hardware successfully with some of the issues you are hitting.
Regards,
Mike
I’m following the steps and it’s not booting from usb. I’m getting the folllowing error:
could not find kernel image: linux
the windows system I’m prepping from has the usb mapped to drive F:
The server maps the usb key across the ilo as drive C: (BL680 G6)
So I’ve tried using both:
syslinux -d f:syslinux f:
syslinux -d c:syslinux f:
Same results.
Thanks!
J.J.,
The syslinux app simply places a boot sector and loader onto the USB media. The loader looks for a file named syslinux.cfg in the syslinux directory and that file specifies a relative location and file name for the kernel image.
e.g.
…
kernel vmlinuz
append initrd=initrd.img vmkopts=debugLogToSerial:1 mem=512M askmedia
The files vmlinuz and initrg should be in the syslinux directory.
Thus you must examine what the kernel directive points to and ensure that file is present.
Regards,
Mike
Hi Mike.
I did that but I’ll try again. I had both syslinux.cfg and ks.cfg in the root and had copied
over the files from CD as instructed at the top of this URL, renaming isolinux to syslinux,
etc. But if it’s working for everyone else and not me then I must be doing something wrong.
I’ll try it with just the ‘askmedia’ option.
Regards,
J.J.
Hi Mike,
I too am trying an usb install without a central repository. My issue is the boot up does not show anything just a flashing cursor. If I pull the usb out then it boots to seaching for bootable os. I did the syslinux -d f:syslinux f: f: is my usb drive. It is partition for 1gb on fat32. I copied the isolinux and renamed it syslinux on file and folder. I put the ks.cfg in the root of the usb, all the rpms and build number files. I copied menu.c32 and vesamenu.c32 to the syslinux folder.
Here is my syslinux.cfg
default esx
prompt 1
#menu title ESX build 164009
timeout 300
LABEL esx
menu default
menu label Install ESX in graphical mode
kernel vmlinuz
append initrd=initrd.img vmkopts=debugLogToSerial:1 mem=512M askmedia
LABEL esx-text
menu label Install ESX in text mode
kernel vmlinuz
append initrd=initrd.img vmkopts=debugLogToSerial:1 mem=512M text quiet
LABEL usb-ks
menu label ESX Scripted Install using USB ks.cfg
kernel vmlinuz
append initrd=initrd.img vmkopts=debugLogToSerial:1 mem=512M ks=usb quiet
LABEL first-disk-safe
menu label ESX Scripted Install to first disk
kernel vmlinuz
append initrd=initrd.img vmkopts=debugLogToSerial:1 mem=512M ks=file:///usr/lib/vmware/weasel/examples/ks-first-safe.cfg quiet
LABEL first-disk
menu label ESX Scripted Install to first disk (overwrite VMFS)
kernel vmlinuz
append initrd=initrd.img vmkopts=debugLogToSerial:1 mem=512M ks=file:///usr/lib/vmware/weasel/examples/ks-first.cfg quiet
LABEL skip-install
menu label ^Boot from first hard disk
localboot 0x80
here is my ks.cfg
install usb
askmedia
Any help would be very appreciated. I am installed this on an Asus Rampage Gene II mb with an i7-920
TIA
Howard
Hi Howard,
The boot issue you are experiencing is not unusual, I have encountered it many times and it’s not related to the syslinux process. I resolved it by using a different memory stick since it was a hardware compatibility issue. .
Regards,
Mike
Great article! I was having problems installing ESX because I’m using an Asus M2N-MX SE Plus board, which uses the MCP61 chipset and NIC. I came upon this article while looking for a method to edit the simple.map and the appropriate xml files.
Long story short: If I boot using the USB created following your directions, it boots and loads syslinux fine, however the ESX install bombs out because of the NIC driver issue.
I used TUGzip to unpack the initrd.img. Then I edited the simple.map and the forcedeth.xml file to reflect the proper pciid. I loaded Cygwin and used Cygwin to cpio and gzip the files back into a .img file.
This new initrd.img will not boot. It halts and throws: kernel panic – not syncing: No init found. Try pasing init=option to kernel.mapping tables up to 100000000 @ 8000-d000.
If I rename files and switch back to the original initrd.img, it boots fine (but obviously I still can’t complete ESX setup because the drivers aren’t set properly.)
I’ve been working on installing ESX to this motherboard for two days now. I swear I’m not a noob–just not experienced much with linux beyond the cygwin shell.
I guess I have two different questions: 1) What am I doing wrong with the repack of the initrd.img file? 2) Can someone tell me a way to get this working on this MCP61 board? There’s not a single set of instructions that I’ve been able to find that doesn’t skip steps because it assumes intimate familiarity with linux and/or earlier verions ESX.
Much thanks for any info!
Thanks John,
The NIC on that motherboard is not supported, do you have an e1000 intel card you could borrow. I would disable the on-board nic and try an e1000 or any other supported card.
Regards,
Mike
I’m working on getting hold of one or more of them (ultimately this box needs to straddle at least 3 subnets) to give that a shot. Any idea why the repacked initrd won’t work? Is Cygwin doing something different than a genuine linux box would do?
I suspect the tools that created the image are the issue. I normally only create ramdisk images on a Centos VM.
ok need help I am getting unable to find linux kernel:
boot:
after following all the blog
I am using win 7 using cmd as admin to do the syslinux cmd
when I do I don’t get a syslinux folder on the usb drive
Hi Ian,
That’s the correct behavior, the syslinux win32 tool simply creates a boot sector on the USB based drive and an associated loader named ldlinux.sys, the syslinux directory will be the root mount point for the loader. You need to create that directory and define your cfg file to load a kernel and your initrd image. In this blog will are placing the VMware install files into the syslinux directory with a copy and rename action.
Regards,
Mike
right getting somewhere it was my cfg file where called .txt as I edited on windows fixed by ren in cmd now works but I get to 97% and getting /mnt/sysimage/boot/initrd.img
I have both isolinux and syslinux folders on my usb stick any idea
Ian, you will need to ensure you have the following in place.
1. Your ks.cfg is present on the root of the USB drive and has a statement of ‘install usb’
2. Your ESX 4.0 cd was copied to the root of the USB drive.
3. You did not edit or save the ks.cfg using a windows editor e.g. notepad or wordpad
Hello Mike,
Thanks to your blog, I was able to successfully build a USB-based silent installation script wihch prompts for one variable (ESXID=xx, which builds both the hostname and IP address). Thank you *VERY MUCH* for your thorough and well-written procedure!
This time however, I updated ks.cfg to prompt for three variables (ESXHOST=servername, ESXIP=10.10.10.10, and ESXGATE=10.10.10.1). The result is “/tmp/ks-script: line 21: cannot create temp file for here document: permission denied”.
The script does NOT make any reference at all to “/tmp/ks-script”. I’m confounded by the source of the call to this mysterious ”/tmp/ks-script”. I have researched this issue extensively to no avail. Here is my ks.cfg: with certain lines commented out in an effort to facilitate simplification and troubleshooting:
# Regional Settings
keyboard us
timezone –utc ‘US/Pacific’
# Installation settings
install usb
# Unencrypted root password (replace by your own)
rootpw –iscrypted removed_encryption_text
# Licensing
accepteula
# Authentication
auth –enablemd5 –enableshadow
# Partitioning
# This is created in the $PRE section, as it is host-specific
# %include /tmp/diskconfig
# Network configuration
# This is created in the $PRE section, as it is host-specific
# %include /tmp/networkconfig
#+————–+
#| %PRE section |
#+————–+
%pre –interpreter=bash
set — `cat /proc/cmdline`
for x in $*; do
case $x in ESX*)
eval $x
;;
esac;
done
ESXSCHOSTNAME=”$ESXHOST”
ESXSCIP=”$ESXIP”
ESXSCGATE=”$ESXGATE”
mount /dev/sda1 /tmp/
%include /tmp/diskconfig
%include /tmp/networkconfig
# Create the disk config
cat <> /tmp/diskconfig
clearpart –alldrives –overwritevmfs
part ‘/boot’ –fstype=ext3 –size=1100 –onfirstdisk
part ‘none’ –fstype=vmkcore –size=110 –onfirstdisk
part ‘LocalStorage-${ESXSCHOST}’ –fstype=vmfs3 –size=8804 –grow –onfirstdisk
virtualdisk ‘esxconsole’ –size=7804 –onvmfs=’LocalStorage-${ESXSCHOST}’
part ‘swap’ –fstype=swap –size=800 –onvirtualdisk=’esxconsole’
part ‘/var/log’ –fstype=ext3 –size=2000 –onvirtualdisk=’esxconsole’
part ‘/’ –fstype=ext3 –size=5000 –grow –onvirtualdisk=’esxconsole’
EOFdisk
# Create the networking config
# cat <> /tmp/networkconfig
# network –ip=${ESXSCIP} –hostname=${ESXSCHOST} –nameserver=${ESXSCHOST} –netmask=255.255.255.0 –gateway=${ESXSCGATE} –addvmportgroup=true –device=vmnic0 –bootproto=static
# EOFnic
# The ESXID var is lost later, so keep it somewhere
# cat <> /call-script.sh
# /esx-post-script.sh ${ESXHOST} ${ESXIP} ${ESXGATE}
# EOFcs
# chmod a+x /call-script.sh
Hi James,
ks-script is the internal running process name for a kickstart script so that’s not the issue here.
You need to define what is on line 21 since I cannot tell where it is. The issue will be centric to the “permission denied” which is really a write failure message which could be caused by a read only mnt or invalid mount call/mount failure.
What editor did you create the file with?
Regards,
Mike
Hello Mike,
Line 21 of ks.cfg refers to the following comment:
# This is created in the $PRE section, as it is host
The second error occurs on line 30 which is the following:
set — `cat /proc/cmdline
I used WordPad to successfully build a working version of ks.cfg, which is proven and reliable — performing a silent installation of vSphere with the hostname and IP address the same. Now I’m simply taking this working version of ks.cfg and edited it so it will prompt me for three variables (hostname, IP address, and gateway).
If you think WordPad is the culprit, could you point me into an editor to use? Again, thank you very much for your help.
Hi James,
You should not use any windows based editors for the ks scripts. I like Ultraedit32 or you can use a free one like Unix-Edit32.
Your file MUST be saved in unix format.
I suspect the minus after set does not have the correct character code.
Also, on your script you are using a cat console redirect to a file but you are not ending the redirect with an EOF.
This is what it should have, e.g. don’t assume the default behavior will always work.
e.g. cat > /tmp/part.cfg << EOF some type to redirect into part.cfg EOF <- End here as shown don't use EOFdisk Additionally the %pre statement contains some %includes to files e.g. /tmp/diskconfig which may or may not be present on the usb file system. The ordering may be an issue for you depending on the files existence. Regards, Mike
hmm wierd
I am getting error 15 : file not found when my syslinux.cfg is
default menu.c32
prompt 0
timeout 9000
menu title ESX 4 Automated Install VC1 HTTP Repo
label Default
kernel vmlinuz
append initrd=initrd.img vmkopts=debugLogToSerial:1 mem=512M quiet askmedia
label vh0
kernel vmlinuz
append initrd=initrd.img vmkopts=debugLogToSerial:1 mem=512M quiet askmedia
label vh1
kernel vmlinuz
append initrd=initrd.img vmkopts=debugLogToSerial:1 mem=512M quiet askmedia
am I right in saying because I used the manual syslinux -d i:syslinux i: that the default folder will be syslinux, my usb drive looks like
01/05/2009 02:44 isolinux
01/05/2009 02:42 misc
01/05/2009 02:42 upgrade
01/05/2009 02:38 VMware
01/05/2009 02:38 7 build_number
01/05/2009 02:38 17,987 gpl-2.0.txt
01/05/2009 02:42 22,180 packages.xml
01/05/2009 02:37 2,598 README
01/05/2009 02:44 syslinux
14/01/2010 23:22 408 syslinux.cfg
6 File(s) 43,191 bytes
5 Dir(s) 7,131,889,664 bytes free
have tried a ks.cfg as well in the root to no avail
You need to place the syslinux.cfg file in the syslinux directory. Based on the time stamp of the posted list its not in the right location.
ok will try thanks
no still getting file not found error 15
after I put the syslinux.cfg in the syslinux folder
I:syslinux>dir
Volume in drive I is ESX4USB
Volume Serial Number is 7054-01CF
Directory of I:syslinux
14/01/2010 22:57 .
14/01/2010 22:57 ..
01/05/2009 02:42 47,287 16×16.fnt
01/05/2009 02:42 24,603 back.jpg
01/05/2009 02:44 2,048 boot.cat
01/05/2009 02:42 96,768 bootlogo
01/05/2009 02:42 1,111 en.tr
01/05/2009 02:44 80,222,089 initrd.img
01/05/2009 02:42 14,489 isolinux.bin
01/05/2009 02:42 1,055 isolinux.cfg
01/05/2009 02:42 3 langlist
01/05/2009 02:42 1,519,004 vmlinuz
14/01/2010 23:22 408 syslinux.cfg
11 File(s) 81,928,865 bytes
2 Dir(s) 7,131,889,664 bytes free
thats my syslinux folder now
and its still not working
Ian
I don’t see a menu.32 file yet you have it defined in the syslinux.cfg, possibly that is the file it’s looking for.