Boot Windows From Syslinux Could Not Find

Boot: select Could not find kernel image: boot/syslinux/whichsys.c32 boot: sys Could not find kernel image: boot/syslinux/archiso_sys_choose.cfg What am I doing wrong? This is not my first rodeo with Syslinux. It's probably worth noting that labelling it 'ARCH_201207' or not doesn't really matter (at this point); I should be getting the install menu since the bootloader is installed fine. Could it have something to do with the APPEND line from syslinux.cfg? Last edited by DSpider (2012-07-24 23:26:49). My system won't boot right now, so I created the usb image from an old CD I had lying around. I have it labelled 'ARCH 2011-08-19'.

I guess it is safe to say that is old enough to run into this problem (I can't boot it right now to find out, as I am cloning a disk). I did get the USB to boot no problem after I made the change. Just now: I looked it up here on archlinux.org, it did have the 4.04 version of syslinux. So, the problem is still solved. For some reason I thought syslinux 4.06 was more ancient than the CD -- I did read that note. Sorry for the confusion.

Last edited by dbourgeo (2013-02-20 22:21:07).

However, whenever I start it up from Syslinux (chain boot from Linux). However, I don't want this because I want multiple Windows OS' on the USB. By the way, for those interested, you can use YUMI multiboot to load OS. I'm trying to install Arch Linux on my 64x Windows 7 laptop via bootable USB and the message 'could not find kernel image: boot/syslinux/whichsys.c32' is what I see.

The urbz sims in the city ps2 ntsc bios download mac. This is starting to drive me nuts, so time to ask for help. I've had an UNRAID server running for years, most recently on 5.0.6. A recent syslog review indicated that the USB stick might be corrupt, so I decided to pull it, reformat, and start fresh. Since that time I have not been able to boot.

I have formatted using Windows XP and Windows 7, Mac OS X and Ubuntu. I've tried FAT 32, exFAT and EXT4. Have also tried versions 5.x and 6.x of UNRAID. Have also changed boot sequence in the BIOS from USB-HDD to USB-FDD.

When I boot I get one of two error messages, either Invalid UI or DEVICE configuration or boot disk not recognized, replace and try again. The original stick was a Sandisk Cruzer 1GB. I bought a Sandisk Cruzer 8GB and am having exactly the same issues. Have also tried booting my regular desktop PC with both sticks and get the same errors. Both my desktop and the UNRAID server will boot to Ubuntu from a USB stick, so I can't figure out why they won't boot to UNRAID. UNRAID motherboard is a Gigabyte GA-G33M-DSR2. Normally the USB stick should be formatted to either FAT or FAT-32 as indicated in the guide at I am sure it will be something silly and you will kick yourself when you spot the error Did you remember to run the make_bootable.bat file?

That seems the most likely step that if missed would leave the USB stick unbootable. Yes, I've primarily been using FAT32. I haven't found a way to format FAT, possibly because the new stick is 8GB and FAT doesn't like that? And yes, have run the.bat file and all files, including the hidden ones, seem to be present and accounted for. Normally the USB stick should be formatted to either FAT or FAT-32 as indicated in the guide at I am sure it will be something silly and you will kick yourself when you spot the error Did you remember to run the make_bootable.bat file? That seems the most likely step that if missed would leave the USB stick unbootable. Yes, I've primarily been using FAT32.

I haven't found a way to format FAT, possibly because the new stick is 8GB and FAT doesn't like that? And yes, have run the.bat file and all files, including the hidden ones, seem to be present and accounted for. Strange then. Although it does not say so explicitly, the error message seems to imply that the syslinux.cfg file (in the syslinux folder) cannot be found. It obviously got far enough to invoke the syslinux loader. Having said that, I seem to remember something about some motherboards having problems with the latest syslinux versions.

In these case an older version of syslinux worked for them. Normally the USB stick should be formatted to either FAT or FAT-32 as indicated in the guide at I am sure it will be something silly and you will kick yourself when you spot the error Did you remember to run the make_bootable.bat file? That seems the most likely step that if missed would leave the USB stick unbootable. Yes, I've primarily been using FAT32. I haven't found a way to format FAT, possibly because the new stick is 8GB and FAT doesn't like that?