m0u53 Posted August 29, 2009 Share Posted August 29, 2009 so with grub4dos i could map my floppy image(dos6.22.img) and chainload it...however in grub2 this gives an invalid system disk error meaning it chainloads to the floppy but then fails my grub.cfg is : menuentry "Dos 6" { loopback lo (hd0)/Dos6.22.img chainloader (lo)+1 } also set splashimage = /b79t3ud2pf2w9nwt6.xpm.gz set menu_color_normal = green/black set menu_color_highlight = red/black set timeout = 60 this code has no effect at all..am i doing it wrong? or is this not supported yet? any and all help would be awesome note: im editing the grub.cfg file located in /dev/sdb/boot/grub/grub.cfg it was my understanding this was what the new grub config used instead of menu.lst Quote Link to comment Share on other sites More sharing options...
Netshroud Posted August 29, 2009 Share Posted August 29, 2009 Try using memdisk as the kernel (linux /memdisk), and initrd the image (initrd /myimage.img) like in Grub4DOS. I haven't tried it, but logically it should work. Quote Link to comment Share on other sites More sharing options...
m0u53 Posted August 29, 2009 Author Share Posted August 29, 2009 Try using memdisk as the kernel (linux /memdisk), and initrd the image (initrd /myimage.img) like in Grub4DOS. I haven't tried it, but logically it should work. i just did it and yes it works perfectly menuentry "Dos 6" { linux /memdisk initrd /Dos6.22.img } however any tips on getting the menucolors working or maybe the background image? Quote Link to comment Share on other sites More sharing options...
Netshroud Posted August 29, 2009 Share Posted August 29, 2009 not sure about colors, but you can use PNGs, JPEGs and TGAs if you load the correct module. eg: insmod png background_image /myimg.png Quote Link to comment Share on other sites More sharing options...
m0u53 Posted August 30, 2009 Author Share Posted August 30, 2009 not sure about colors, but you can use PNGs, JPEGs and TGAs if you load the correct module. eg: insmod png background_image /myimg.png do you know what the image specifications have to be? like legth and width and color count? Quote Link to comment Share on other sites More sharing options...
Netshroud Posted August 30, 2009 Share Posted August 30, 2009 Well, you can change the resolution of GRUB2, so I would set the image resolution to that. I think full-color (32-bit) is supported. Quote Link to comment Share on other sites More sharing options...
m0u53 Posted August 30, 2009 Author Share Posted August 30, 2009 Well, you can change the resolution of GRUB2, so I would set the image resolution to that. I think full-color (32-bit) is supported. if you have gotten it to actually work could you post your grub.cfg Quote Link to comment Share on other sites More sharing options...
Netshroud Posted August 30, 2009 Share Posted August 30, 2009 I haven't. I'll experiment more with Grub2 and get a working config going when I figure out how to do drive mappings for Kon-Boot. Quote Link to comment Share on other sites More sharing options...
SomethingToChatWith Posted September 7, 2009 Share Posted September 7, 2009 Good point, I wonder how one would do the mapping for kon-boot with grub2 myself. Could you do "loopback (hd0) (hd1)" etc? Quote Link to comment Share on other sites More sharing options...
Netshroud Posted September 7, 2009 Share Posted September 7, 2009 I dont think so. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.