...I only use an old usb stick (Sandisk titanium 512 MB) for the single purpose of trying out alfa and rc releases. I'm using the same media for extensions so there isn't much space left when I have downloaded (or installed with a script) the ones I want to use.
I'm not sure I understand your meaning and may be missing the point you are making.
The reference to the previous post was not to suggest you change your current USB set-up to a multi-boot device, rather it was to provide a working example of how to automatically supply the boot codes when using bootlace+GRUB4DOS to directly boot a TC ISO. Is this not your objective? The principle will work just as well on a single partition bootable USB drive.
All that is required are small amendments to your menu.lst which will not occupy much space.
Current menu.lst
This is my menu.lst:
find --set-root /tinycore.iso
map --mem /tinycore.iso (hd32)
map --hook
root (hd32)
chainloader (hd32)
Where should I put the boot options?
Change it to something like this:
find --set-root /tinycore.iso
map --mem /tinycore.iso (hd32)
map --hook
root (hd32)
kernel /boot/bzImage quiet waitusb=5 noicons tce=sdb1 xvesa=1024x600x32
initrd /boot/tinycore.gz
OR - if it a recent stable version of TC
find --set-root /tinycore.iso
map /tinycore.iso (hd32)
map --hook
root (hd32)
kernel /boot/bzImage quiet waitusb=5 noicons tce=sdb1 xvesa=1024x600x32
initrd /boot/tinycore.gz