You mean grub to make a cd bootable, or ??? I use grub all the time to boot my frugal hd installs of slax, and all other linux distros I play with. It won't make a usbstick bootable on a bios that can't see your usbstick. I've never heard of using grub to make a usbstick bootable, but it might work.
You can use grub to boot a cd -- el torito standard; at least Suse and Mepis do that, maybe also Ubuntu still. There's lots of google info re how to do that, man pages may explain. Not sure you can write it with k3b, might be necessary to use cdrecord or similar.
I always boot slax fresh, keeping my configuration in a special .lzm file I keep in the modules folder in partition 2. Presumably the changes= cheatcode would work, but I haven't tried it from USB.
Here's what i got. Slax is installed on an SD
memory card located in an internal USB reader,
there's no USB boot BIOS support whatsoever but
the memory card reader is accessible under DOS
with help from 'USBASPI.SYS' & 'ASPIDisk.SYS'.
The batch-file named 'Slax.BAT' which Tomas has
included on his CD is able to launch Slax using
'/BOOT/DOS/LinLd097.COM' but i'm hoping to find
a replacement and i thought 'GRUB4DOS' would be
good enough. If i type "Find" on the 'GRUB4DOS'
command line i only see 'hd0', 'hd1' and 'fd0':
one pair of Hard-Disks and one Floppy drive but
no USB/SD unit. The 'LinLd097.COM' boot-loader
suffers from a severe limitation, either a file
is used for its optional parameters, either the
commands can come from the keyboard but i can't
mix both methods where most of the options are
pre-defined in a file and last-minute commands
can be entered manually. 'GRUB' and 'GRUB4DOS'
seem to be more flexible but i didn't manage to
make 'GRUB.EXE' find the Slax USB setup so far.
One other reason to favour 'GRUB' is because it
exists both as a Linux and a DOS executable, the
later built being suitable for use by 'Slax.BAT',
eventually...
It has been known for some time now that grub won't read a usbstick [to get boot code] running on a bios that pretends the usbstick isn't there.
Linld097 is kinda weird; wants vmlinuz and initrd specified directly, but takes all the rest in a named config file. So the answer to adding parameters is to just have separate config files, and call them from separate bat files -- or from a single bat file using the msdos menu command.
When I'm experimenting with this stuff I use grub> command mode. Tedious to type it all in, but maybe less tedious than continual rebooting. I boot first to msdos, where I also keep a tiny text editor for fooling with bat files and grub config files, etc.
If i'm going to work any further with 'LinLd097.COM'
then i'll need to copy the default configuration file on
a RAMDisk where last-minute parameters can be added.
This defeats the usefulness of '/BOOT/DOS/SLAX.BAT'
completely unless the whole DOS setup is integrated.
Since "GrUB" stands for "GRand-Unified Boot loader",
hence why it's multi-platform, actually, that would be
my prefered option. Maybe if 'PLoP' can be run on top
of DOS it would boot the SD card but i have no idea
if there's even a DOS version at all to begin with.
Anyway, it's not like booting Slax from a USB unit
was impossible: i've done it, it's just that this setup
isn't as convenient as i would have wished it to be...
I do the same thing as you do with a small fat partition on my hard drive. Grub is installed and the menu.1st file is configured to allow me to choose between 3 linux distro's and sadly, XP. Of course, I have many partitions on this drive to keep all this straight. But it does work.
Usually when I want a new USB stick with grub on it. I just dd from an old one and then make mods rather than doing grub-install.
Bicephale wrote:
I'd like to know if there are Slax siblings out here using 'GRUB'.
Almost.
I use Slax with grub4dos, which can do very nice things in a much simpler way than grub. You put it on first sector of any device your bios can see, and you're done.
If you want to boot a device not seen at bootstrap, obviously you need to circumvent the problem by auxiliary boot managers or mini OSs, like wakepup, kexec-loader, or plop (I'd be interested in any other approach known, by the way).
I did some scripting to automate grub4dos frugal install for my Slax-based (though stripped down) "PortableLaTeX" project, which is tuned to LaTeX type setting and mathematical packages. If you're interested you can download new 0.3 version and try it:
marco. wrote: Bicephale wrote:
I did some scripting to automate grub4dos frugal install for my Slax-based (though stripped down) "PortableLaTeX" project, which is tuned to LaTeX type setting and mathematical packages. If you're interested you can download new 0.3 version and try it:
http:/developer.berlios.de/projects/portablelatex
Does it use TeTeX or TeXLive?
Is it based on Slax?
forum wrote: marco. wrote: Bicephale wrote:
I did some scripting to automate grub4dos frugal install for my Slax-based (though stripped down) "PortableLaTeX" project, which is tuned to LaTeX type setting and mathematical packages. If you're interested you can download new 0.3 version and try it:
http:/developer.berlios.de/projects/portablelatex
Does it use TeTeX or TeXLive?
Is it based on Slax?
Thanks!
Version 0.1 used to be based on the defunct TeTeX to save space, and Slax 6.0.7.
Version 0.3 is based on TeXLive 2008 with a fairly complete macro supply, with Slax 6.0.9 and latest Jedit prerelease 16 as default text editor, along with some BeanShell Latex interface macros.
Version 0.3 features a bunch of additional software, you can check out the Changelog.
I use it exclusively and all the time for quite a sparse range of activities, and it fulfils my needs so far.
Major current drawbacks are the lack of a media player and a buggy compilation (missing external fonts, should be no problem for latex generated pdf, however) of xpdf pdf viewer, have to fix them in next release.
You can acceptably typeset LaTeX on a Pentium II/III with 192 MB ram with it on, according to my tests.
I'll have to verify this but i believe 'NimbleX' with
which i toyed before does use 'GRUB' as a boot-loader.
Besides 'LinLd097.COM', which is inflexible but works,
i must look closer at 'GRUB4DOS' and 'SysLinux.COM' in
hope chain-loading will allow to transfer control to
'Slax's original boot-loader so that i can customize
the boot menus directly on the USB drive and transpose
the results to the CD knowing these menus are correct.
I have little hope this is possible judging from what
i've read so far but it's not over yet. I thought of
searching for 'LinLd097.COM' menu related information
to gain some real-time control over the boot options,
mainly to explore language boot-codes in 'PureOS v1.1
2009', in the meantime. Maybe somebody as clever and
focussed as Wengier Wu happens to already have a fix,
i wonder: i don't read Chineese...
Yes, i guess it's the kind of real-life implementation
sample which i was after in order to gather a better
understanding of these things, eventually... I'd wish
there were support similar to this for DOS USB drives:
...
chainloader (fd0)+1
...
My 1st experiment will be to boot from a diskette and
try to start your CD using 'GRUB4DOS'...
My copy of 'Portable Latex v0.3' ('pl-0.3.iso')
displayed this message when i tried to boot it:
Starting cmain() ... No PXE stack
...then nothing happened. The checksums concur.
Too bad, Nimblex has filenames as 'vmlinuz-nx08'
and 'initrd-nx08.gz' which i suspect 'GRUB4DOS'
isn't happy with (expecting 8.3 DOS filenames, i
suppose... I've seen this parameter somewhere:
My copy of 'Portable Latex v0.3' ('pl-0.3.iso')
displayed this message when i tried to boot it:
Starting cmain() ... No PXE stack
...then nothing happened. The checksums concur.
Too bad, Nimblex has filenames as 'vmlinuz-nx08'
and 'initrd-nx08.gz' which i suspect 'GRUB4DOS'
isn't happy with (expecting 8.3 DOS filenames, i
suppose... I've seen this parameter somewhere:
pmedia=usbflash
More reading to come...
Thanks for the report. This sounds like a grub4dos issue, could you be a bit more specific about your hardware (Motherboard, IDE/SATA or SCSI cdrom, bios maker and serial number)? Since you seem to be adventurous, you can try the following, as I understand you have access to grub:
1) Copy GRUB4DOS' grub.exe (you can find it inside pl-0.3.iso/slax/modules/frugal-install.lzm module, or alternatively download the zipped binaries from http://download.gna.org/grub4dos/) to a partition visible from grub
2) Boot using grub and go to command line prompt
3) Issue a "kernel /PATH/grub.exe" command followed by "boot", and see if that works.
Passing to the second part of your message, you seem to be saying that you managed to boot with g4d, but not to launch Nimblex kernel; but you asserted earlier g4d didn't work at all on your machine, so I'm missing a point here!?
Anyway, I think grub4dos should have no problem with long file names, since it supports ntfs and ext2/3, but I can't be more definitive about that at the moment.
Finally, if you track down precisely a problem between grub4dos and your hardware, you could report directly to g4d developer, he is usually glad of receiving (proper) feedback.
Too bad, Nimblex has filenames as 'vmlinuz-nx08'
and 'initrd-nx08.gz' which i suspect 'GRUB4DOS'
isn't happy with (expecting 8.3 DOS filenames, i
suppose...
You can do.
It eats anything (at least no problems with nimblex names or some iso names even longer).
The mother-board is a CA64-TC by DFI, it has
Award's Modular BIOS v6.00PG and USB support
is limited to peripherals such as a keyboard
and/or a mouse... There's a 16 bits ISA slot
(now empty) which fits the "legacy" category
and you can call me legacy too as i just feel
at home using DOS (i see nothing adventurous
about it). I have a pair of hard-disks, one
CD drive and one DVD writer: all IDE as you
can imagine. My mother, sisters, cousins and
relatives are mostly in pretty much the same
situation: we don't spend fortunes over our
HardWare and i sure am the most enthousiastic
of them about technology... In any case, it
may not be necessary to get too involved with
specifics for the time being. I was thrilled
when i read about the idea of booting with a
USB-aware DOS diskette which then should pass
control to 'GrUB4DOS' which in turn might be
able to launch 'PLoP' - the later being USB-
aware when it comes to booting, contrary to
my BIOS. Most unfortunately, i've also read
that 'EMM386' and 'PLoP' are incompatible but
it turns out 'ASPIDisk' requires 'EMM386' so
i'm back to square one until some alternative
is found... 1st attempts with the 'GrUB4DOS'
"find" command were less than conclusive but
maybe i must try to install 'LFNDOS' as well.
Well, I think I should spend a little time and brain on this, 'cause it could be useful for me too.
As first, a simple question:
if you plan to boot a linux distro, why do you need EMM386 to be loaded?
I also use a box like yours booting dos with a multiple config; one of them is a flat, flat, flat config calling grub4dos as a loader for some frugal installations of linux.
when a linux kernel starts, all dos processes die.
I must re-read this thread to understand your goal.
I'm glad to hear that you're curious too
about this topic, there was a bargain on
2 GB micro-SD cards (+adaptor) in a local
store today so i went there and came back
with one in a pocket thinking it might be
handy during the next week-end. The plan
is to attempt to verify if i can boot an
OS installed on that SD memory card using
my USB reader and no BIOS boot support at
all. As i pointed out in another thread,
i found this article somewhat stimulating:
Essentially, i simply explore the concept
imagined by its author; this just didn't
prepare me to find out that 'EMM386' and
'PLoP' are excluding each other, though. I
wonder if he used different drivers or if
he simply didn't really try his method...
Without 'EMM386' i can't get 'ASPIDisk' to
find the SD card so i'm now looking for a
substitute. Once i've got that working, i
will run 'GrUB4DOS' and see if the "find"
command gives me better results. If i'm
lucky, it will make sense to use 'PLoP' if
it's true it's able to boot from USB units.
Should i fail to find how i can boot from a
memory card inserted in my USB reader i'll
need to reduce my expectations to finding
a better boot-loader than 'LinLd097.COM'.
I must go away from the machine for a while but
this is on my menu when i'm back to business...
I always boot slax fresh, keeping my configuration in a special .lzm file I keep in the modules folder in partition 2. Presumably the changes= cheatcode would work, but I haven't tried it from USB.
Hope this is of some use to you.
Where do you put the menu.lst, on which partition and in which folder?
At present I'm using win and slax, but I can boot about ten live or frugal distros.
In all of my win boxes I kept the ability of booting msdos, and I didn't want to make a real install or change MBR. And dos was the easiest way to format and make bootable my pendrives and flash cards.
I began with loadlin but after slax 6.rc6 it didn't work anymore, so I had to discover LINLD (yes, it's me). Soon I migrated to g4d, more flexible.
The next step was to boot (on the cards) g4d itself and, if necessary, load dos (fdos).
I never succeeded in booting dos from hdd or fdd with usb drivers and starting lild or g4d on pendrive or card reader.
My drivers are usbaspi.sys and di1000dd.sys, other drivers don't wake up the reader or the keys.
Well. I think my week-end will be ME and PLoP alone in a room.
There might be a few things here that I do not understand. Let me ask a few questions, but before let me make a summary of my usb slax grub install.
Usb grub slax install:
1) Creation of 2 partitions with gparted on the usb key targetted for the grub install, sdb1 in fat32 and sdb2 in ext3.
2) On sdb1 is created the folder slax6boot which contains intrd.gz and vmlinuz
3) On sdb2 are installed the folders /boot and /slax with all their usual file as in the standard usb install.
4) Instead of the the usual /bootinst.sh procedure to make this new usb installation bootable, I use in a console from my mepis hdd installation the command:
grub-install --root-directory=/mnt/sdb1 /dev/sdb
Questions:
1) Is the grub-install is installing grub on sdb1?
2) As there is no /grub folder with the menu.lst file on my sdb1 partition, how do I install it or get it to be seen on that partition?
Note: this post was corrected for errors reported by @guttaslax
1) Is the grub-install is installing grub on sdb1?
2) As there is no /grub folder with the menu.lst file on my sdb1 partition, how do I get the it to be installed or to be seen on that partition?
As first, let's agree that GRUB and GRUB4DOS are not the same toy.
In my posts I refer to g4d aka grub4dos.
This is what I understood:
grub installation procedure should write grub bootloader to MBR in the disk you specified, nothing else;
in g4d at boot time the MBR code loads GRLDR, the loader;
grldr reads menu.lst and shows the options YOU have programmed.
You must provide your own menu.lst according to your needs, and write down in a text editor.
guttaslax wrote:
As first, let's agree that GRUB and GRUB4DOS are not the same toy.
In my posts I refer to g4d aka grub4dos.
This is what I understood:
grub installation procedure should write grub bootloader to MBR in the disk you specified, nothing else;
in g4d at boot time the MBR code loads GRLDR, the loader;
grldr reads menu.lst and shows the options YOU have programmed.
You must provide your own menu.lst according to your needs, and write down in a text editor.
Why four partitions?
gslax
I do not have four partitions, but two partitions on my usb key: sdb1 and sdb2. The first one being fat32 for data compatible format with window. The second sdb2 in ext3 to install slax. I thought installing slax on ext3 will make its life longer with less corrupted sectors (maybe xfs would be as good or better).
francois.e wrote:
I do not have four partitions, but two partitions on my usb key: sdb1 and sdb2. The first one being fat32 for data compatible format with window. The second sdb2 in ext3 to install slax. I thought installing slax on ext3 will make its life longer with less corrupted sectors (maybe xfs would be as good or better).
Meanwhile I have downloaded g4d: http://sourceforge.net/projects/grub4dos
and I found a tutorial on g4d: http://grub4dos.sourceforge.net/wiki/index.php/Grub4dos_tutorial
I imagine that the best way for me to install g4d would be to install in menu.lst of mepis:
title Load GRUB4DOS
kernel /grub.exe
And then install g4d on the usb key?
You refer in your previous post to sdb1 sdb2 sdc1 sdc2.
You can try your way, it should work.
Or, if you have a win box, try this (we are just discussing in another thread)
Sorry for the sdc1 and sdc2, I had two usb keys on the laptop. I began with the first terminology and then followed with the second. It has been edited to only sdb terms now.
The actual laptop is without windows, but it happens that I also work with win boxes.
Thanks for the advice, I will come back with some feedback.
francois.e -- if you already have a working grub on your machine [mepis?], then you don't have to install anything on the usbstick. Just add an item to your existing menu.lst to load vmlinuz and initrd.gz from the usbstick.
But, I can tell you, if your bios doesn't allow usb booting, then neither native linux grub nor grub4dos is going to make it boot from the stick. There is no special magic in grub4dos that would let it do that trick.
You can copy the vmlinuz and initrd.gz from the stick into a local directory on your Mepis install, and use your mepis grub to load those -- and after slax's vmlinuz is running it will find the rest of itself on the usbstick.
I have a computer that permits usb booting of the laptop.
I just thought that using grub on usb could permit me to boot a usb key with grub and where the os slax would be on a ext3 or xfs file a second partition on the usb,
I just thought that using grub on usb could permit me to boot a usb key with grub and where the os slax would be on a ext3 or xfs file a second partition on the usb, >francois.e
++++++++++++
Not at all sure I understand your problem [or goal] but I have no doubt that syslinux could load vmlinuz and initrd.gz from the first partition, and then find the rest of slax on the 2nd partition. This would just require a proper from= statement in syslinux.cfg
At 1st i used the "sgnfile" boot-time parameter,
i booted from a CD but it could have been another
location then the process continued with my USB
drive and 'Slax' did work but i wanted more: i
was hoping to find for a convenient way to edit
the boot-loader options too... Do you need that
much?
I read that slax install on fat32 seem to be less stable than on xfs. But maybe I am wrong.
I thought that putting slax on a second partition would circumvent the use of lilo and provide some versatility in terms of data reading for win systems (I have xp on another computer).
My few attempts to use lilo as a bootloader on usb has resulted in the inability to get directly in the X environment. I would be happy with a first partition pure linux file type (xfs for example), lilo as boot loader and with a second partition of the fat32 type.
Maybe I make things complex where they could be simple.
francois.e wrote:
I read that slax install on fat32 seem to be less stable than on xfs. But maybe I am wrong.
I thought that putting slax on a second partition would circumvent the use of lilo and provide some versatility in terms of data reading for win systems (I have xp on another computer).
My few attempts to use lilo as a bootloader on usb has resulted in the inability to get directly in the X environment. I would be happy with a first partition pure linux file type (xfs for example), lilo as boot loader and with a second partition of the fat32 type.
Maybe I make things complex where they could be simple.
I've used only fat32 parts until now.
My flash drives contain a linux distro (usually slax) and also win portable apps that can be used on other non re-bootable win boxes or, if I can boot these boxes and again need them, using wine.
I use the slaxsave.dat mode and I never lost a byte.
Did someone boot slax or any other iso "as is" directly from hd and grub. as shown in g4d user manual? >gs
+++++++++++
Ahh ... I dunno what that says, but booting from the iso 'as is' is a feature of slax, not of grub. That is, what grub or isolinux or syslinux or lilo or whatever booter does --their job is to load vmlinuz and initrd to memory and then start executing code from whatever init script. So the answer is, you can boot directly into the 'as is' slax iso with any of them.
If you'll copy vmlinuz and initrd.gz out of the iso -- to some place that grub can see -- then add a proper from=/location/of/slax.iso to the kernel line, then slax will boot fine from the iso. I've done that here with both 607 and 609.
Not exactly a fresh idea; Knoppix and similar have been able to do this for a few years.
bb as guest wrote:
Ahh ... I dunno what that says, but booting from the iso 'as is' is a feature of slax, not of grub. That is, what grub or isolinux or syslinux or lilo or whatever booter does --their job is to load vmlinuz and initrd to memory and then start executing code from whatever init script. So the answer is, you can boot directly into the 'as is' slax iso with any of them.
If you'll copy vmlinuz and initrd.gz out of the iso -- to some place that grub can see -- then add a proper from=/location/of/slax.iso to the kernel line, then slax will boot fine from the iso. I've done that here with both 607 and 609.
Not exactly a fresh idea; Knoppix and similar have been able to do this for a few years.
It says you could boot an iso stored on hdd using the "map" command.
I'm looking for time to test.
It looks like loading slax (or chainloading it) isnt that bad i fyou have two partitions.
However, has anyone used just one partition with slax on it and put grub on it to be the bootloader? It looks like thats what sci_fi did in post #3.
If your using 2 partitions, one for grub one for slax, couldnt you just chainload the bootloader for slax (sda2) from within grub's menu.lst?
I'm not getting your point here.
Isn't any slax+grub4dos liveCD (such as PortableLatex, probably there are others I don't know of) a one-partition (more exactly, non-partitioned) media implementing just that?
You can for sure substitute grub to isolinux as slax boot loader (and get a much better product, but this is just my opinion), the number of partition on which you spread things is irrelevant.
It can indeed be one to four (one for grldr, one for vmlinuz, one for initrd.gz, and the last for lzm modules, but I see no utility in that) or even five (if you dislocate menu.lst, too).
This can be accomplished by using from= slax cheatcode and find --set-root g4d command, which, in a broad sense, do the same thing.
By the way, in PortableLatex (see previous post to get it) there is a frugal install script (accessible from g4d boot menu) which tries to implement such modular flexibility.
guttaslax wrote:
It says you could boot an iso stored on hdd using the "map" command.
I'm looking for time to test.
gslax
There is a serious drawback on that feature: the image (iso or any other format) must be stored on physically contiguous blocks (if that didn't change recently), and I guess this is related to the fact that chainloading is a sequential thing, but have no detailed vision on it.
As an alternative, you can mirror a non-contiguous image file into a ram contiguous replica, and then map the latter (using --mem flag, if I'm right).
this will boot using /slax and /boot on /dev/sdb1 -- to the text mode logon prompt. Any cheatcodes you want to add must be appended to the one 'kernel' line. If you put /slax and /boot into a subdirectory, that subdir name must be added before /boot on the kernel and initrd lines, and then I think you'd also need a specific from=/dev/sdb1/subdir cheatcode.
Correct. I think it's time for some sticky threads about this and other stuff.
But, may I ask why some people use "boot" command in menu.lst (a non interactive sequence)?
Buckiller wrote:
However, has anyone used just one partition with slax on it and put grub on it to be the bootloader? It looks like thats what sci_fi did in post #3.
I didn't read at all this part of the question.
One of my boxes has 2 partitions, system and data.
Well, "data" is for data.
On "system" (fat32) win, slax606, slax609, bt3, puppy, dsl, nimblex, parted magic, fdos, msdos, live
together with grub4dos, which boots them all.
guttaslax wrote: Bicephale wrote:
I thought i could use an .ISO file directly.
you can "chainload" an iso.
I quote myself. :-)
It works.
The iso must be unfragmented, if not, g4d issues an error, but doesn't hang.
Some iso work, other don't, but I can't understand why (not so expert).
Of course, slax doesn't, and stops in --wait a while.
It works.
The iso must be unfragmented, if not, g4d issues an error, but doesn't hang.
Some iso work, other don't, but I can't understand why (not so expert).
++++++++++++++++
What are the grub commands to do that, please? Seems that would be most useful.
Dang, have 7 linux iso files on disks here, and apparently not one is stored as a contiguous file -- and I have no idea how to force that. So far this is not useful.
Bicephale wrote:
'UltraISO' has an "optimize" option, do you think it relates?
I don't know ultraiso, usually I stay away as possible from the words "try" "order" "purchase" ...
I guess it's related to the internal structure of the iso.
Dang, have 7 linux iso files on disks here, and apparently not one is stored as a contiguous file -- and I have no idea how to force that. So far this is not useful.
I'm sure can't bypass this.
My test was on an almost empty fat32 partition, loaded just for the test with some files.
Nevertheless, one of them still was non contiguous, and I hat to apply one passage of defraggler (win) which can defragment a single file.
I have grub as the boot loader on the same partition, but when the machine boots I only get the grub command prompt. From there i can manually enter the lines and it boots fine. But how do I get the menu (grub.conf) to show up?
The /boot/grub folder is a copy from a FC9 install I had. I edited the grub.conf folder and did a grub-install on the appropriate devices.
How do i restore the grub gui menu where I can select the OS to boot?
Hi, MrPloP.
A question on the fly.
How can I space the items in menu.lst?
I mean, insert a blank row between them...
gslax
you can just manually go into grub.conf with a text editor and change it. If you are at the grub boot menu you can hit e to edit the selected OS, then either hit "o" or "O" to insert a line. I THINK d deletes a line. Empty lines are bad. That should help unless I misunderstood your question.
Any thoughts on my newer question? Why that grub gui menu isnt showing up?
DOS era?
That thing between Commodore 64 and VAX?
Hex FF = ASCII decimal 255 = space = ASCII decimal 032 = Hex 20?
Maybe it was
Hex 0A = ASCII decimal 010 = Line feed
or
Hex 1D = ASCII decimal 013 = Carriage return
or both.
They can't work in that environment.
Neither the title -------------, I use it for best reading, and it's ignored.
Oh, when I was young...
Yes, i prefered to use DOS to BBS between 1995 and 2005
because Windows was a waste of resources, too slow and
just incompatible with legacy HardWare in the begining...
I used a "forbidden" character all right, i don't remember
what for exactly but i think DOS can't erase directories
with a space in their filename(s). I'm certain it was none
of the LF/CR characters in any case: those are obvious
in communications... Sorry about the 'GrUB' separator,
it was what i found using Google but maybe it has to be
'GrUB4DOS'. When i was young i could sit in front of a
15 inches amber screen and never complain, not anymore:
my eyes can't take it and the rest of my body neither!!!
----------------------------------------
DI1000 ASPI DISK Driver Ver 2.00
Copyright(C)2001 NOVAC Co.,Ltd.
Available ID = 0
ID 0 = HD .. Generic USB SD Reader
#1 : PRI DOS 1016MB drive = C:
----------------------------------------
Maybe "ID 0 = HD .." should read something
like "ID 0 = HD #" instead, i wonder as i'm
not luckier with 'Gujin's drives list. It sure
doesn't help my confidence when i read some
posts as this one where the reader finally
gets the news that the HP Formatter may not
be so great:
Bicephale
there is a tool install Grub4dos can run on Windows OS which name is grubinst, you can find it in http://download.gna.org/grubutil/
also, you can install grldr with dd to MBR under linux.
I guess my problem is the line saying something like:
root (hdx,y)
I can find the SD card under DOS just fine, it has a
drive letter all right but i'm not sure 'GrUB' sees it
because when i try the "find" command it searches
the DOS floppy forever... 'LinLd' is the only way to
really boot from an SD card USB reader for me so i
wish there were a way to "chainload" to 'SysLinux'
in order for my boot sequence to match the LiveCD.
You are asking how to add a fashion separator in menu.lst ? This is the answer: Every title in menu.lst without at least one command is being ignored.
So to add a line separator with ------------------- simply just add for example:
[code]
title ***********************************************************
pause --wait=0 This title is a delimitor. Nothing to do.
pause --wait=0 You can use non-boot-sensitive commands here
pause --wait=0 of any kind and as many as you would like.
help kernel
help
clear
[/code]
in menu.lst.
Hope you got the point. And here is the source: http://diddy.boot-land.net/grub4dos/files/README_GRUB4DOS.txt
See ya!
