Result was the same - unable to load DOS file. Maybe something is wrong with paths? Or UNetbootin just doesn't work with this old MS system...
Result of what?
That is not a GRUB/grub4dos message AFAICR.
The path is Linux-like, so does UNetbootin mount C:\ as / ? Furthermore, there is C:\unetbtin but there's no ubnkern and ubninit...
I don't get it:
find --set-root /unetbtin/ubnkern
means find on ANY drive accessible file "ubnkern" inside directory "unetbootin" under the root of that drive AND set as ROOT the drive where that file is found.
There are no such things as "drive letters" or "C:\" at the grub4dos level, devices are identified by:
(fdx) for floppy disks i.e. first floppy is (fd0)
(hdx,y) for hard disk like devices, (hd0,0) is first partition on first hard disk (your USB stick if you boot from it)
means load a Linux kernel named "ubnkern" situated in a directory named "unetbtin" under the root of current ROOT device.
means use as intial ramdisk the file "ubinint" situated in a directory named "unetbtin" under the root of current ROOT device.
this means NOTHING inside a menu.lst, the boot command is implied in menu.lst but needed on command line.
If the files are missing, obviously nothing of the above can work, something must have gone wrong in usung UNETBOOTIN.
I would try re-running from scratch, then use Command Line:http://diddy.boot-la...s/files/cli.htmhttp://diddy.boot-la...iles/basics.htm
entering each command one by one, using autocompletion [TAB] featrures and report the EXACT feedback grub4dos gives after each command has been entered.
Or are you trying to run UNETBOOTIN under win98? http://unetbootin.sourceforge.net/
Microsoft Windows 2000/XP/Vista/7, or Linux