Klaus Mueller
2005-Dec-03 12:18 UTC
[syslinux] Re: SYSLINUX Digest, Vol 33, menu.c32 chaining
Hello, many of our platforms do not have a integrated floppy, some even don''t have a floppy controller. As pxelinux still has a problem with machines without a floppy in combination with some bios versions I need to chainload a different bootstrap loader which works on the floppyless platforms. But I also need to load a BartPE and the other BS loader does not support that. So I tried to use menu.c32 but did not succeed. <snip> ------------------------------ Message: 3 Date: Fri, 02 Dec 2005 13:46:19 +0100 From: Alexander Heinz <mailsanmich@gmx.li> Subject: Re: [syslinux] PxeLinux menu.c32 chaining> multinet.bs is a 3COM bootstrap loader V1.10 which also supports menus, but no chain loading. multinet.bs is configured to directly load a DOS bootfloppy image without showing a menu.> # Dos multinetwork > LABEL DOS > MENU LABEL Boot DOS with multiple LAN support > kernel multinet.bs> Does anybody see a solution?rename multinet.bs to multinet.0, make the according changes to the configuration file and try again. Cheers Alex ------------------------------> Of course I also tried that. See my original text at: "If multinet.bs is loaded (same behaviour if loaded as multinet.0) the 3COM loader reports the error message "ERROR: Proboot API not found!" Thanks and best regards Klaus ------------------------------ Message: 4 Date: Fri, 02 Dec 2005 07:02:17 -0800 From: "H. Peter Anvin" <hpa@zytor.com> Subject: Re: [syslinux] PxeLinux menu.c32 chaining Do you have any details on pxelinux having problems with no floppy? -hpa -----------------------------> Take a look at my request here: SYSLINUX Digest, Vol 31, Issue 22 "I am using pxelinux.0 included in syslinux V3.11. A DOS floppy image is loaded via TFTP and boots fine as long as a physical floppy is in the system and enabled in the CMOS settings. We also use systems running on the same platform that don''t have physical floppy drives. In this case the image is loaded, but I receive the message "Operating system not found" as soon as the image is trying to boot. My "default" in pxelinux.cfg is: default boot prompt 0 say booting... label boot kernel memdisk append initrd=multinet.imz The LSM file of V3.11 said: "MEMDISK: Try work around a bug on some BIOSes when no physical floppy disk is present in the system. " Seems that the problem still exists. The problem occurs on all platforms I use. One is running on a P3 with VIA chipset and Phoenix - Award Bios V6.00PG, the other one is running on a PentiumM with Intel chipset and Phoenix - Award Bios V6.00PG. Both systems behave the same. If the physical floppy is present and enabled there is no problem. As soon as I set the floppy to "None" in the CMOS settings, the image does not boot anymore. I also tried to load the image as a harddiskimage. It did not help. " <------------------------------- I did not receive any suggestions yet. If you need more details please contact me. Best regards Klaus ------------------------------ _______________________________________________ SYSLINUX mailing list Submissions to SYSLINUX@zytor.com Unsubscribe or set options at: http://www.zytor.com/mailman/listinfo/syslinux Please do not send private replies to mailing list traffic. End of SYSLINUX Digest, Vol 33, Issue 2 *************************************** _____________________________________________________________ Show the world your Caribbean soul. FREE email at http://www.caribbeancity.net
hi, alex
i think you are booting dos using pxelinux can u please help me with
one thing how can i solve convential memory probelm in dos after loading
network driver, it gives problem in foxpro based programs insufficient
memory problem..
please help me if you can.
Thanks in advance
Kunal
----- Original Message -----
From: "Klaus Mueller" <Nostromo at caribbeancity.net>
To: <syslinux at zytor.com>
Sent: Saturday, December 03, 2005 5:48 PM
Subject: [syslinux] Re: SYSLINUX Digest, Vol 33, menu.c32 chaining
> Hello,
>
> many of our platforms do not have a integrated floppy, some even don't
> have a floppy controller. As pxelinux still has a problem with machines
> without a floppy in combination with some bios versions I need to
> chainload a different bootstrap loader which works on the floppyless
> platforms. But I also need to load a BartPE and the other BS loader does
> not support that. So I tried to use menu.c32 but did not succeed.
>
> <snip>
>
> ------------------------------
>
> Message: 3
> Date: Fri, 02 Dec 2005 13:46:19 +0100
> From: Alexander Heinz <mailsanmich at gmx.li>
> Subject: Re: [syslinux] PxeLinux menu.c32 chaining
>
>> multinet.bs is a 3COM bootstrap loader V1.10 which also supports menus,
>> but no chain loading. multinet.bs is configured to directly load a DOS
>> bootfloppy image without showing a menu.
>
>> # Dos multinetwork
>> LABEL DOS
>> MENU LABEL Boot DOS with multiple LAN support
>> kernel multinet.bs
>
>> Does anybody see a solution?
>
> rename multinet.bs to multinet.0, make the according changes to the
> configuration file and try again.
>
> Cheers
> Alex
>
> ------------------------------>
> Of course I also tried that. See my original text at:
> "If multinet.bs is loaded (same behaviour if loaded as multinet.0) the
> 3COM loader reports the error message "ERROR: Proboot API not
found!"
>
> Thanks and best regards
> Klaus
>
>
> ------------------------------
>
> Message: 4
> Date: Fri, 02 Dec 2005 07:02:17 -0800
> From: "H. Peter Anvin" <hpa at zytor.com>
> Subject: Re: [syslinux] PxeLinux menu.c32 chaining
>
> Do you have any details on pxelinux having problems with no floppy?
>
> -hpa
> ----------------------------->
> Take a look at my request here: SYSLINUX Digest, Vol 31, Issue 22
>
> "I am using pxelinux.0 included in syslinux V3.11.
> A DOS floppy image is loaded via TFTP and boots fine as long as a
> physical floppy is in the system and enabled in the CMOS settings.
> We also use systems running on the same platform that don't have
> physical floppy drives. In this case the image is loaded, but I receive
> the message "Operating system not found" as soon as the image is
trying
> to boot.
> My "default" in pxelinux.cfg is:
> default boot
> prompt 0
> say booting...
> label boot
> kernel memdisk
> append initrd=multinet.imz
>
> The LSM file of V3.11 said: "MEMDISK: Try work around a bug on some
> BIOSes when no physical floppy disk is present in the system. "
> Seems that the problem still exists.
> The problem occurs on all platforms I use. One is running on a P3 with
> VIA chipset and Phoenix - Award Bios V6.00PG, the other one is running
> on a PentiumM with Intel chipset and Phoenix - Award Bios V6.00PG.
> Both systems behave the same. If the physical floppy is present and
> enabled there is no problem. As soon as I set the floppy to
"None" in
> the CMOS settings, the image does not boot anymore.
> I also tried to load the image as a harddiskimage. It did not help. "
> <-------------------------------
> I did not receive any suggestions yet. If you need more details please
> contact me.
>
> Best regards
>
> Klaus
>
>
>
> ------------------------------
>
> _______________________________________________
> SYSLINUX mailing list
> Submissions to SYSLINUX at zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux
> Please do not send private replies to mailing list traffic.
>
>
> End of SYSLINUX Digest, Vol 33, Issue 2
> ***************************************
>
>
> _____________________________________________________________
> Show the world your Caribbean soul.
> FREE email at http://www.caribbeancity.net
>
> _______________________________________________
> SYSLINUX mailing list
> Submissions to SYSLINUX at zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux
> Please do not send private replies to mailing list traffic.
>
Carl Karsten
2005-Dec-03 18:25 UTC
[syslinux] Re: SYSLINUX Digest, Vol 33, menu.c32 chaining
Somani K. wrote:> hi, alex > i think you are booting dos using pxelinux can u please help me with > one thing how can i solve convential memory probelm in dos after loading > network driver, it gives problem in foxpro based programs insufficient > memory problem..Can you give some deatials of what you need? ^Carl K
Hi, friends,
actually i am booting thinstation + dos boot disk using pxelinux and
menu.c32 everything works fine but there is problem with dos boot disk, when
it loads tcp/ip protocol and packet drivers for netwok in consumps memory
around 540k and dos only supports 640k memory when i access mapped drive
from server using tcp/ip protocol and try to run foxpro based dos program it
gives an error of insufficient memory, but other programs like Wordstar,
lotus123 running fine, i also tryied with memdisk and other things but
nothing woks, so give me a suggestion if you can ?
Regards,
Somani K.
----- Original Message -----
From: "Carl Karsten" <carl at personnelware.com>
To: "Somani K." <globalyogesh at gmail.com>
Cc: <syslinux at zytor.com>
Sent: Saturday, December 03, 2005 11:55 PM
Subject: Re: [syslinux] Re: SYSLINUX Digest, Vol 33, menu.c32 chaining
> Somani K. wrote:
>> hi, alex
>> i think you are booting dos using pxelinux can u please help me
with
>> one thing how can i solve convential memory probelm in dos after
loading
>> network driver, it gives problem in foxpro based programs insufficient
>> memory problem..
>
> Can you give some deatials of what you need?
>
> ^Carl K
So to summarize: (and fill in a few blanks, correct me if I am wrong) You are booting PXE from a floppy PXE is loading dos. Is it using memdisk and an image of a dos bootable floppy? autoexec.bat loads the microsoft TCP stack and SMB drivers map a drive to an SMB (windows) file server. run foxpro, it errors with not enough memory. What is the name of the .exe? guessing foxprox.exe. And this is foxpro v2.6, right? ^C Somani K. wrote:> Hi, friends, > actually i am booting thinstation + dos boot disk using pxelinux > and menu.c32 everything works fine but there is problem with dos boot > disk, when it loads tcp/ip protocol and packet drivers for netwok in > consumps memory around 540k and dos only supports 640k memory when i > access mapped drive from server using tcp/ip protocol and try to run > foxpro based dos program it gives an error of insufficient memory, but > other programs like Wordstar, lotus123 running fine, i also tryied with > memdisk and other things but nothing woks, so give me a suggestion if > you can ? > > Regards, > Somani K. > ----- Original Message ----- From: "Carl Karsten" <carl at personnelware.com> > To: "Somani K." <globalyogesh at gmail.com> > Cc: <syslinux at zytor.com> > Sent: Saturday, December 03, 2005 11:55 PM > Subject: Re: [syslinux] Re: SYSLINUX Digest, Vol 33, menu.c32 chaining > > >> Somani K. wrote: >> >>> hi, alex >>> i think you are booting dos using pxelinux can u please help me >>> with one thing how can i solve convential memory probelm in dos after >>> loading network driver, it gives problem in foxpro based programs >>> insufficient memory problem.. >> >> >> Can you give some deatials of what you need? >> >> ^Carl K > > >
Hi, friends
Carl guessed right, what type of problem i am getting actually it is
not pxelinux problem it is problem related to DOS convential memory, which
is less after loading network drives, and when i run foxpro.exe foxpro loads
but when i give a command in foxpro for running a foxpro based program "DO
programname" it gives error insufficient memory in RED window
Well suggest me if anybody knows about it
Regards,
Somani K.
----- Original Message -----
From: "Carl Karsten" <carl at personnelware.com>
To: "Somani K." <globalyogesh at gmail.com>
Cc: <syslinux at zytor.com>
Sent: Sunday, December 04, 2005 9:24 PM
Subject: FoxPro
> So to summarize: (and fill in a few blanks, correct me if I am wrong)
>
> You are booting PXE from a floppy
>
> PXE is loading dos. Is it using memdisk and an image of a dos bootable
> floppy?
>
> autoexec.bat loads the microsoft TCP stack and SMB drivers
>
> map a drive to an SMB (windows) file server.
>
> run foxpro, it errors with not enough memory.
>
> What is the name of the .exe? guessing foxprox.exe.
>
> And this is foxpro v2.6, right?
>
> ^C
>
> Somani K. wrote:
>> Hi, friends,
>> actually i am booting thinstation + dos boot disk using pxelinux
and
>> menu.c32 everything works fine but there is problem with dos boot disk,
>> when it loads tcp/ip protocol and packet drivers for netwok in consumps
>> memory around 540k and dos only supports 640k memory when i access
mapped
>> drive from server using tcp/ip protocol and try to run foxpro based dos
>> program it gives an error of insufficient memory, but other programs
like
>> Wordstar, lotus123 running fine, i also tryied with memdisk and other
>> things but nothing woks, so give me a suggestion if you can ?
>>
>> Regards,
>> Somani K.
>> ----- Original Message ----- From: "Carl Karsten"
>> <carl at personnelware.com>
>> To: "Somani K." <globalyogesh at gmail.com>
>> Cc: <syslinux at zytor.com>
>> Sent: Saturday, December 03, 2005 11:55 PM
>> Subject: Re: [syslinux] Re: SYSLINUX Digest, Vol 33, menu.c32 chaining
>>
>>
>>> Somani K. wrote:
>>>
>>>> hi, alex
>>>> i think you are booting dos using pxelinux can u please
help me
>>>> with one thing how can i solve convential memory probelm in dos
after
>>>> loading network driver, it gives problem in foxpro based
programs
>>>> insufficient memory problem..
>>>
>>>
>>> Can you give some deatials of what you need?
>>>
>>> ^Carl K
>>
>>