[syslinux] Problem with SysLinux but not with LILO

[JJ]

Hi guys,

I'm really stuck with this and am not sure how to fix it. I tried creating
my own bootdisk with no -s and with -s  option but it did not help. This may
sound stupid but is there no debugging options I could turn on to try and
trace the problem? Any help would be appreciated.

Thanks,

jj

----- Original Message ----- 
From: "JJ" <jungle_jim at icon.co.za>
To: <syslinux at zytor.com>
Sent: Monday, July 19, 2004 11:52 PM
Subject: [syslinux] Problem with SysLinux but not with LILO


> More of an update:
>
> The problem I'm having is with SysLinux. It just will not boot on my PC.
> IPCop 1.3 uses LILO and this boots fine but in the beta release 1.4, they
> are using  SysLinux. It is an older PC (486 with Pentium overdrive and
16MB
> of memory with 1.2 Gig hard drive) and the BIOS reads as follows
> "PhoenixBIOS(TM) A486 Version 1.00.09.AC0"
>
> Is there something I can do to debug this?
>
> -jj
>
>
>
>
> ----- Original Message ----- 
> From: "JJ" <jungle_jim at icon.co.za>
> To: <syslinux at zytor.com>
> Sent: Saturday, July 17, 2004 12:21 AM
> Subject: [syslinux] Problem with SysLinux but not with LILO
>
>
> > Hi,
> >
> > I am trying to use two products that use SysLinux and finally realised
the
> > SysLinux is the cause of my woes. I'm trying to use Freesco and IPCop.
> IPCop
> > version 1.3 used a different boot loader to 1.4 which uses SysLinux. I
> have
> > been through numerous trials and tribulations in trying to get Freesco
to
> > work but eventually gave up and went with IPCop. I kept getting the
"Boot
> > Failed" error message. I went of to use IPCop instead. ICOP ver 1.3 uses
> > LILO. Now the new version of IPcop (1.4b5) use SysLinux, so I am almost
> > right back where I started - with the "Boot Failed error message. I then
> > traced the problem to the common denominator - Syslinux. I used the same
> > floppy disk and was able to boot with LILO but not with SysLinux.
> >
> > Have any of you heard of this problem before?
> > What can I do?
> >
> > Thanks
> >
> > JJ
> >