Fwd: [CLUG] PXE problems - resolved

[freegazer]

we actually tried that one Bob the errors occoured on all images that it
tried to load. the win boot images were stripped down of the windows install
cd's but we tried using both ready to go RH images and linux bootstrapped
for network install.
we skimmed through the syslinux forums for similar symptoms and all we could
get in earlier replies were "rewrite the comboot keyboard entries in C".

anyway thanks for having a look at this one

On 6/1/06, Robert Edwards <bob at cs.anu.edu.au> wrote:
>
> Cool.
>
> I was going to suggest trying it with a Linux kernel and initial RAM
> disk and see if the same behaviour occurs. That would at least have
> isolated it to a Messy DOS problem or not (why aren't you using
> FreeDOS?)
>
> Cheers,
>
> Bob Edwards.
>
> freegazer wrote:
> > worked this one out thanks anyway guys
> >
> > hint - turn off BIOS numlock status when using USB keyboards :)
> >
> > ---------- Forwarded message ----------
> > From: freegazer <freegazer at gmail.com>
> > Date: Jun 1, 2006 11:45 AM
> > Subject: [CLUG] PXE problems
> > To: linux at lists.samba.org
> >
> >
> > hi there listers.
> >
> > After Bobs presentation on PXE booting and Diskless systems I have
> > attempted
> > to make an O/S installer boot over PXE. currently all is good with the
> > system running fine 3/4 of the time. the problem on every 4th boot is
> that
> > PXE, TFTP, and syslinux seem to run fine but once the ramdisk image of
> the
> > MS-DOS install disk (please no flames I know its wrong but its what I
> have
> > to do) starts there is an error and the system drops back into a prompt.
> > when this is run with a prompt instead of the menu system entering the
> > image
> > name at the prompt runs perfectly.
> > If the script however is run with the prompt option set to 1 no prompt
> is
> > given and the same 3/4 rule applies.
> > Also as a side note this is occouring on multiple images from in the
> system
> > can someone please advise on at least a ballpark area that may be
> causing
> > this type of error at the moment I have run out of ideas.
> > the current menu file in use has the following options:
> > DEFAULT menu.c32
> > PROMPT 0
> > NOESCAPE 0
> > IMPLICIT 1
> > ALLOWOPTIONS 0
> > TIMEOUT 600
> >
>
>


-- 
by ipxodi (156633) on Tuesday August 23, @07:47AM (#13378220) (
http://slashdot.org/)
Duct tape is one of the sacred triumvirate of the Most Important Tools in
the World. Use the Tool Triumvirate thusly:
1) If it moves and it shouldn't -- use Duct Tape.
2) If it doesn't move and it should -- use WD-40.
3) If it should sometimes move -- use Velcro.