Godzilla Posted June 1, 2007 Share Posted June 1, 2007 (edited) ThxI will try when I am at home.EDIT: It works so far.I copied the files.I copied and renamed the isolinux-folder to \custom\ubuntuI added the following lines to mymain.cfg:LABEL ubuntu MENU LABEL U^buntu 7.04 LiveCD KERNEL vesamenu.c32 APPEND /custom/ubuntu/isolinux.cfgBut the Ubuntu-menu is now in default-vesamenu. (grey background)Of couse I could addMENU INCLUDE /custom/mydefs.cfgto \custom\ubuntu\isolinux.cfg to customize.But I want the original menu.And I cannot change the language (F2-key) in the "new" Ubuntu-menu. I think \custom\ubuntu\bootlogo is responsable for the ubuntu-menu, but i didn't find out how it works. EDIT2: I forgot to say.. There was no "boot"-folder on the Ubuntu-CD. Edited June 1, 2007 by Godzilla Link to comment Share on other sites More sharing options...
kof94 Posted June 1, 2007 Share Posted June 1, 2007 I think you misunderstood me. The default menu for Ubuntu uses something called gfx which isn't the same as vesamenu.You don't need the original isolinux folder from the Ubuntu disc just the isolinux.cfg file. Open it up with your favorite text editor and copy the relevant commands to your menu. If you require extra options like languages you'll need to add them to your menu as well. You can find the extra options in the F*.txt files (* representing an F key number). Link to comment Share on other sites More sharing options...
Godzilla Posted June 1, 2007 Share Posted June 1, 2007 I understood you.i just copied the isolinux-folder, because I though I need it to get the original menu.There must be a way to start "gfx" from isolinux,but I have no motivation to deal with this. I will use my own Ubuntu-menu. But how can I set the language in the bootcommand?The F*.txt-files don't help.They are just for the help (after pressing F1).And I cannot find a command like "lang=de" or something.Anyway, this is not important.I will concebtrate on other things. Link to comment Share on other sites More sharing options...
kof94 Posted June 2, 2007 Share Posted June 2, 2007 ...But how can I set the language in the bootcommand?The F*.txt-files don't help.They are just for the help (after pressing F1).And I cannot find a command like "lang=de" or something....Sorry about that, I never checked it before posting . You are correct though, there doesn't seem to be any params for language selection. I can only assume it is performed on the fly, might be something to do with gfx or should I say gfxboot. There is very little written (that I can find) about this menu system so I can't really comment. Link to comment Share on other sites More sharing options...
jetman Posted June 3, 2007 Author Share Posted June 3, 2007 I understood you.i just copied the isolinux-folder, because I though I need it to get the original menu.There must be a way to start "gfx" from isolinux,but I have no motivation to deal with this. I will use my own Ubuntu-menu. But how can I set the language in the bootcommand?The F*.txt-files don't help.They are just for the help (after pressing F1).And I cannot find a command like "lang=de" or something.Anyway, this is not important.I will concebtrate on other things. A final word on this:ROOT # mkdir /tmp/initrd; cd /tmp/initrdROOT # gzip -dc /initrd.img | cpio -id; lsWith this little snippet, one can open up the init ramdisk and at least look at the linuxrc script, to better understand the boot initialization process.Ultimately, that's the principal point I've been emphasizing throughout this thread. That is, to open up the underlying components and figure out how they work to realize a custom solution. Not just for the immed issue, but for helping in future efforts....Jet Link to comment Share on other sites More sharing options...
kof94 Posted June 6, 2007 Share Posted June 6, 2007 This topic of gfxboot has got me interested in it again, the only problem is I can't even find a home page for it let-alone any docs.According to one post in the syslinux mailing list "it's uglier than hell to configure" but I still think it looks and performs better than vesamenu.If anyones up for it could we possibly look in to this and try to pool some information for guide?I'm nearly finished with my migration to Ubuntu (I just need a few more apps for specific tasks) so I'm gonna take a look at the UCK - Ubuntu Customization Kit that Jet was talking about, since it is supposed to handle gfxboot customisation.If I learn anything I'll post it here.-kof94 Link to comment Share on other sites More sharing options...
Godzilla Posted June 6, 2007 Share Posted June 6, 2007 Nice to hear.Will wait ... Link to comment Share on other sites More sharing options...
kof94 Posted June 21, 2007 Share Posted June 21, 2007 Sry, abandoned the gfxboot idea again.New syslinux pkg is out with some good updates to vesamenu that negates me switching.If your a Ubuntu (or deb) user I've found a better prog to UCK... Reconstructor.From what I can see this prog was used to create parts of Linux Mint, which is also worth a look.Later. Link to comment Share on other sites More sharing options...
gdhnz Posted June 22, 2007 Share Posted June 22, 2007 I've finally taken the plunge and moved from cdshell to isolinux but the problem I am having now is that I am getting an error when trying to load dsl 3.3 (3.2 no longer available).Can't find KNOPPIX filesystem, sorry.Dropping you to a (very limited) shell.Press reset button to quit.I've followed your instructions exactly in the original post. The original dsl iso boots fine. Link to comment Share on other sites More sharing options...
kof94 Posted June 22, 2007 Share Posted June 22, 2007 (edited) I've finally taken the plunge and moved from cdshell to isolinux but the problem I am having now is that I am getting an error when trying to load dsl 3.3 (3.2 no longer available).Can't find KNOPPIX filesystem, sorry.Dropping you to a (very limited) shell.Press reset button to quit.I've followed your instructions exactly in the original post. The original dsl iso boots fine.Can u post your isolinux.cfg or any other config file thats related, your disc structure (just a representation), and how your creating your iso i.e. cdimage, mkisofs, k3b, nero (god forbid) etc.I'll dl DSL now and see what I can find out.Edit: Tried it out with no probs. * Copy KNOPPIX dir to root of your disc.* Copy linux24 and minirt24.gz from /boot/isolinux/ (on DSL disc) to a dir of your choice (on your disc), I chose /isolinux/dsl/.* Assuming you've used my locations add this to your menu (without **** and word wrap):LABEL dslMENU LABEL **** Small Linux 3.3KERNEL dsl/linux24APPEND ramdisk_size=100000 init=/etc/init lang=us apm=power-off vga=791 initrd=dsl/minirt24.gz nomce noapic quiet BOOT_IMAGE=knoppix* Create image. I used K3B for this but if your in Win then I suggest cdimage or mkisofs.Done Edited June 22, 2007 by kof94 Link to comment Share on other sites More sharing options...
gdhnz Posted June 23, 2007 Share Posted June 23, 2007 (edited) Basic disc structure is/boot/ isolinux/ dsl/ password//images//KNOPPIX//Programs//SETUP/ XP/ Home_OEM/ Pro_OEM/ Professional//Software/ISOLINUX.CFg as followsDEFAULT /boot/isolinux/vesamenu.c32PROMPT 0TIMEOUT 100ALLOWOPTIONS 0MENU WIDTH 63MENU HSHIFT 21MENU VSHIFT 2MENU TIMEOUTROW 18MENU BACKGROUND /boot/isolinux/splash.pngMENU TITLE Recovery DVDMENU COLOR border 0 #ffcccccc #00000000 noneMENU COLOR title 1;36;44 #ffcccccc #00000000 noneMENU COLOR unsel 37;44 #ffcccccc #00000000 noneMENU COLOR sel 7;37;40 #00000000 #ffcccccc noneMENU COLOR hotkey 1;37;44 #ff00ff00 #00000000 noneMENU COLOR hotsel 1;7;37;40 #00000000 #ffcccccc nnoeLABEL winmenu MENU LABEL ^1) Microsoft Windows XP Installations KERNEL /boot/isolinux/vesamenu.c32 APPEND /boot/isolinux/menu_windows.cfgLABEL recoverycd MENU LABEL ^2) Windows ^Recovery Disc KERNEL /BPE1.binLABEL dsl MENU LABEL ^3) **** Small Linux 3.3 KERNEL /boot/dsl/linux24 APPEND ramdisk_size=100000 init=/etc/init lang=us apm=power-off vga=791 initrd=/boot/dsl/minirt24.gz nomce noapic quiet BOOT_IMAGE=knoppixLABEL blank1 MENU LABELLABEL win98 MENU LABEL ^4) Windows ^98 DOS CD Boot KERNEL memdisk APPEND initrd=/images/win98.igzLABEL hdutils MENU LABEL ^5) Hard Drive Diagnostic Utilities KERNEL /boot/isolinux/vesamenu.c32 APPEND /boot/isolinux/menu_hdutils.cfgLABEL password MENU LABEL ^6) Password Reset Utility KERNEL /boot/password/vmlinuz APPEND rw init=/linuxrc initrd=/boot/password/initrd.cgz,/boot/password/scsi.cgzLABEL memtest86 MENU LABEL ^7) MemTest86+ (RAM Diagnostic) KERNEL /boot/isolinux/memtest86LABEL dban MENU LABEL ^8) Erase Hard Drive using dban KERNEL memdisk APPEND initrd=/images/dban.igzlabel blank2 MENU LABELLABEL bootc MENU LABEL ^0) Boot from C: MENU DEFAULT KERNEL /boot/isolinux/chain.c32 APPEND hd0I use the following command to make my ISOmkisofs -N -V RecoveryDVD -b boot/isolinux/isolinux.bin -d -iso-level 4 -no-emul-boot -boot-load-size 4 -boot-info-table -o RecoveryDVD.iso SuperThe disc boots fine and everthing works except for the message about the filesystem not found for dsl. Edited June 23, 2007 by gdhnz Link to comment Share on other sites More sharing options...
kof94 Posted June 23, 2007 Share Posted June 23, 2007 Your locations and commands seem fine. The only thing I think could be causing u a prob is mkisofs. Try adding joliet to your iso.Sorry to be abit vague but I personally never used mkisofs to create images. In Windows I used cdimage and now in linux I use K3B (which uses mkisofs... sort of).The reason I say try adding joliet is I remember reading somewhere that your need it for Knoppix to boot and since DSL is a small ver of Knoppix...Sorry I did say this earlier but it just dawned on me! Link to comment Share on other sites More sharing options...
gdhnz Posted June 23, 2007 Share Posted June 23, 2007 @#$%&@#So **** simple. Just added a --joliet to my command line and it now all works.The reason I'm using mkisofs is that I'm building this iso on a mac.Thanks man Link to comment Share on other sites More sharing options...
kof94 Posted June 24, 2007 Share Posted June 24, 2007 No problem, glad I could help . Link to comment Share on other sites More sharing options...
gdhnz Posted June 24, 2007 Share Posted June 24, 2007 Anyone worked out where the $OEM$ dir now needs to go for this method? Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now