Hi, i'm sorry but i dint actually understand what u asked for, Like do u want to know exactly what error message i'm getting or the configuration of the pc's in which i get these errors ?? Sorry for being so stupid :-)) Bye, Jassi> >Jaspreet oberoi wrote: > > Hi,, > > > > I wud just like to inform that the previous issue of memdisk not booting > > compressed images still persists !! The release 2.05 that was supposed > > to fix this issue dint yet solve the problem !! > > > > Please, let me know if more info on the problem is required !! > > > >Do you have a test case? > > -hpa_________________________________________________________________ Dress up your desktop! Get the best wallpapers. http://server1.msn.co.in/msnchannels/Entertainment/wallpaperhome.asp Just click here!
Jaspreet oberoi wrote:> > Hi, i'm sorry but i dint actually understand what u asked for, Like do u > want to know exactly what error message i'm getting or the configuration > of the pc's in which i get these errors ?? > > Sorry for being so stupid :-)) >You can start with your configuration and *all* the output messages from MEMDISK. However, the best would be if you could *also* send me (privately) the files you're trying to boot, including your configuration file. -hpa
Just a few things which was dicussed in the list: 1. Implement some mechanism by which DOS images can get a look at the command line arguments passed to syslinux 2. COMBOOT images: the append option doesn't seem to work. If these are already in the pipeline, great. If already implemented, ignore the previous lines. Finally, another request: In case an image name entered on the syslinux/isolinux command line does not exist it returns an error. Is it possible to have an additional feature where this would call a user specified image with the "bad command line" as its argument. In my case, I am hoping to write a COMBOOT image, which will then run another image which checks to see if the image can be found on a network location. Thanks, and BTW syslinux rocks! - Murali