t94xr

thats ok, i've just upgraded to grub2 lol

grub, as in the grub thats installed with ubuntu 9.04 on /dev/sdg1 (hd6) - not grub4dos

we're not - just booting ISOs is apparently much easier in Grub2. This is grub1 - not grub2

ERROR 11: Unrecognized Device String I can't for Ubuntu 9.10 with Grub2! :(

title Hirens 9.9 ISO map --mem (hd6,0)/boot/iso/Hirens.BootCD.9.9.iso (hd32) map --hook chainloader (hd32)+1 like this?

nop nothing thats the top of the screen, then it says Press Any Key to Continue... Also i tried title Hirens 9.9 ISO find --set-root (hd6,0)/boot/iso/Hirens.BootCD.9.9.iso map (hd6,0)/boot/iso/Hirens.BootCD.9.9.iso (0xff) map --hook rootnoverify (0xff) also without the (hd6,0) and that gives me a Error 15: File Not Found...

All of the ones in the list that don't work generate that error. using this title Hirens 9.9 ISO map --mem (hd6,0)/boot/iso/Hirens.BootCD.9.9.iso (hd32) map --hook chainloader (hd32) generates ERROR 11: Unrecognised Device String I can't seem to fix it - I know that hd6 is where my linux drive is, and i want to load these images to memory (4GB RAM ftw!) and it just gives me the same error all the time! ERROR 11: Unrecognised Device String

(fd0) /dev/fd0 (hd0) /dev/sda (hd1) /dev/sdb (hd2) /dev/sdc (hd3) /dev/sdd (hd4) /dev/sde (hd5) /dev/sdf (hd6) /dev/sdg hd6 - /dev/sdg is my linux drive - where grub is installed and contains grub and Ubuntu 9.04 Im having a problem with my config - This stuff works - title Microsoft Windows 7 Release Candidate root (hd1,0) savedefault makeactive map (hd0) (hd1) map (hd1) (hd0) chainloader +1 title Ubuntu Linux 9.04 Desktop uuid 703e182d-9e2d-4e08-b1f8-889fc651c126 kernel /boot/vmlinuz-2.6.28-15-generic root=UUID=703e182d-9e2d-4e08-b1f8-889fc651c126 ro quiet splash initrd /boot/initrd.img-2.6.28-15-generic quiet title Debian GNU/Linux, kernel memtest86+ uuid 703e182d-9e2d-4e08-b1f8-889fc651c126 kernel /boot/vmlinuz-2.6.28-15-generic root=UUID=703e182d-9e2d-4e08-b1f8-889fc651c126 initrd /boot/initrd.img-2.6.28-15-generic #root 703e182d-9e2d-4e08-b1f8-889fc651c126 kernel /boot/memtest86+.bin title GRC SpinRite 6 kernel /boot/utils/memdisk initrd /boot/utils/SpinRite.img This doesn't title Hirens 9.9 ISO map --mem (hd6,0)/boot/iso/Hirens.BootCD.9.9.iso (hd32) map --hook rootnoverify (hd32) boot title Windooh Pro 2007 map --mem (hd6,0)/boot/iso/windoohpro.iso.iso (hd32) map --hook rootnoverify (hd32) boot title gOS Gadgets 3.1 map --mem (hd6,0)/boot/iso/gos-3.1-gadgets-20081205.iso (hd32) map --hook rootnoverify (hd32) boot title Damn Small Linux (dsl-n-01RC4) map --mem (hd6,0)/boot/iso/dsl-n-01RC4.iso (hd32) map --hook chainloader (hd32) rootnoverify (hd32) boot title BackTrack 4 Pre-Final map --mem (hd6,0)/boot/iso/bt4-pre-final.iso (hd32) map --hook chainloader (hd32) #map --rehook #chainloader (hd32)+1 rootnoverify (hd32) boot I've tried everything I can find online! I cant seem to get these to work it just comes up ERROR 11: Unrecognised Device String any ideas?

ok well i was wondering, with people installing WinPE and some forgetting about the usb and booting the system - the usb fat32 file system does have a chance to get infected when its not booted into a livecd or backtrack or something. I did mine using ext3 - wasn't as easy as a fat32 one, but atleast Im happy in the knowledge a windows based OS cant read it or write to it

I have a question, call me stupid for asking this - wouldn't a FAT/FAT32 device have the possibility of getting infected on a compromised/infect system, which would require the use of this device make it fairly insecure and a rather a bad idea for using it as FAT/FAT32? would a linux format like ext3 be more secure when it comes to infect systems and be a bit more secure overall?