similar to: Using memdisk to remotely flash BIOS

Displaying 20 results from an estimated 1000 matches similar to: "Using memdisk to remotely flash BIOS"

2006 Aug 18
2
Universal Packet Driver
I often boot DOS using MEMDISK and 33MB HD images for remote flashing. After my flash I need to activate the NIC and send a signal. Currently I use different packet drivers for different NICs, but this link below looks like a universal solution: http://www.emboot.com/products_UniversalPacketDriver.htm Does any thing else like this exist that is open source or freely available and freely
2003 Jun 20
4
PXELINUX keeppxe mem footprint
Hi, I want to use PXELINUX to load a DOS disk image which I currently use for Win2K/XP unattended installs. I want to move away from reliance on specific NDIS2 drivers and use the 3Com UNDIS3C driver instead. I have used this successfully to start the MSClient, but the problem is that the UNDI and PXE layer take about 90K of base memory, which means that WINNT.EXE has insufficent memory to run
2007 Sep 15
2
keeppxe+memdisk+FreeDOS example?
Hi, I'm trying to get the above working, without success so far: UNDIS.DOS refuses to load with an invalid NDIS stack message (from memory). keeppxe has some effect: it reduces the available conventional memory by 140 kbytes or so... still, the packet driver doesn't seem to find the interface. Does anybody have a working setup I could look at? -- Thanks, Feri.
2005 Jan 09
1
UNDI packet driver?
Hi all, I'm still trying to figure out a good way of booting a DOS disk image via PXE and accessing files over a network share. Having some success with the Microsoft network DOS client, it seems that many programs have issues with its IPX support - so, now I'm trying to use Novell's IPX driver instead. Unfortunately it seems I need an ODI driver to do this, and there are no
2004 Nov 07
1
Network booting DOS with IPX support
Hi all, I'm trying to work out how to boot DOS on a diskless PC, and I've come to a bit of a stumbling block with loading IPX support (which is extremely important, since most DOS games use IPX for network play ;-)) So far thanks to PXELinux and Memdisk I've gotten a DOS floppy image booting successfully, but I'm stuck trying to get IPX support. Admittedly I don't have much
2004 Dec 18
2
UNDI NDIS DOS Driver
I found the 3Com one, but I'm looking for the intel one. The PXE PDK doesn't have it anymore, and the intel site points me to the proboot.exe archive, which has no *.dos files in it. Does anyone know of other generic drivers for dos that work with memdisk's keeppxe option?
2007 Dec 14
8
KEEPPXE/DOS
First off I love syslinux and it has worked flawless for us on the unix side of the realm. We're trying to use our ghost images within a dos netboot using syslinux. Unfortunatly we can only pass DHCP ip's to hosts that exhibit a vendor code 'like windows/pxe/and other os's do". Unfortunatly DOS does not, so we cannot request a second IP after the pxe process to map samba
2008 Nov 11
3
Syslinux 3.70 - BSS DOS boot says: "Could not find kernel Image: linux".
Hello, I'm trying to create and boot a Win98SE-DOS OS through Hard Disk emulation. My src files are from a Win98SE 1440K floppy image file, with a x86 boot sector (dl'd from the net - I have no floppy drive and a slow net link 3.2KB). I don't know what to put into the partition boot record of my image and how to load dos.bss properly (the docs explain for floppy images not for HD
2005 Apr 07
2
blame-transfer protocol on PXE boot
hpa, etal, pxelinux works great from a push of the reset button. machine boots normally. However, after i issue 'reboot' command, my box fails to find the tftp server during reboot. This looks to be happening before pxelinux has any chance to participate, so it cannot be to blame. Im seeking corroboration here before I go badgering the bios-provider here's the relevant
2006 Nov 27
8
Chaining from PXELinux to some other boot loader
Hi I am using PXELinux to boot BartPE and some other application and it works fine. There are some other Boot application which I am using 3COM MBAUTIL PXE.mnu and floppy images. I have problem chaining from pxelinux.0 to 3com pxe.0 (pxe.mnu). Consider: BIOS->(DHCP-TFTP)->pxelinux.0 works fine. BIOS->(DHCP-TFTP)->3COM pxe.mnu works fine, the menu appears and I can choose a floppy
2018 Feb 06
2
syslinux PXE boot version upgrade, network no longer working
Hi David, On Mon, 5 Feb 2018 18:09:51 -0500 David McDowell via Syslinux <syslinux at zytor.com> wrote: > Thanks for the suggestion Lukas. Is lpxelinux.0 [1] a fork of this > distro or a completely different open source option? The file is part of syslinux (pxelinux) and exists since version 5.10. So neither a fork nor a different project ;) . According to the link I had provided:
2005 Sep 03
3
MSCDEX over NDIS ethernet
I would like to implement a replacement MSCDEX driver (based on the replacement in FreeDOS SHSUCDX http://johnson.tmfc.net/freedos/shsucdx.html and SYSLINUX) however instead of talking to disk BIOS calls or PATA chipset I would like it to talk to the NDIS driver and act as a TFTP client simply forfulling application get block requests through TFTP. Its not clear where the ISO9660 CD
2015 Apr 27
2
Real sh? Or other efficient shell for non-interactive scripts
On Mon, Apr 27, 2015 at 2:13 PM, Joerg Schilling <Joerg.Schilling at fokus.fraunhofer.de> wrote: > Les Mikesell <lesmikesell at gmail.com> wrote: > > There was no court case, but VERITAS published a modifed version of gtar where > additional code was added by binary only libraries from VERITAS. The FSF did > never try to discuss this is public even though everybody did
2003 Jul 29
2
Rebooting to hard drive from DOS floppy
Hi all, Do any of you have any ideas for getting a DOS floppy to reboot to the hard drive (which may contain Windows 98 or XP or Linux or Novell etc etc)? I want to use syslinux, but it does not support the localboot option like pxelinux and isolinux do. Basically, I want to boot DOS from a floppy, run some DOS stuff, then reboot to the hard drive while leaving the floppy disk in the drive.
2016 Nov 20
3
Current pxelinux always unloads undi driver
Good day, I have the problem to pass the ?loaded? undi driver to the next bootloader. In current pxelinux ?lernel memdisk keeppxe harddisk raw initrd::parh_to_img? always unloads undi before memdisk (or other kernel) takes control. After many tries I found that the keeppxe feature is broken starting from version 6.03 pre 9. I tried to find the reason by comparing sources 6.03 pre 8 / 6.03
1999 Jun 14
1
msclient and Case
Hello Everyone, I recently installed a MSCLIENT machine each time it writes to my samba 2.04b share it produces all uppercase filenames. Is the best way to handle this with "preserve case = yes/no" controls if new files are created with the case that the client passes, or if they are forced to be the "default" case. Default Yes. "short preserve case = yes/no"
2014 Sep 06
19
[Bug 83550] New: [NVA5] Monitor not restored after resume [regression]
https://bugs.freedesktop.org/show_bug.cgi?id=83550 Priority: medium Bug ID: 83550 Assignee: nouveau at lists.freedesktop.org Summary: [NVA5] Monitor not restored after resume [regression] QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter:
2010 Mar 12
4
PXELINUX menu is not displayed at start-up
Hello, I have the following problem. I am trying to pxeboot a virtual machine using Sun's Virtualbox. I am trying to experiment with the menu options of pxelinux and this is my pxelinux.cfg/default file. # generated by fai-chboot for host cdbexample with IP 172.16.31.200 default menu.c32 prompt 0 default fai-generated timeout 300 #ONTIMEOUT local MENU TITLE PXE Menu LABEL fai-generated
2006 Mar 02
2
keeppxe - documentation recommendation
Summary ======= I have a recommendation for a minor documentation change regarding 'keeppxe'. I lost some time on this and think that a clarification could save other people time in the future. pxelinux.doc should be tweaked to explicitly say that the "keeppxe" option should be given on the kernel command line through the APPEND statemen Detail ====== pxelinux.doc line 356
2009 Jan 21
1
Problem with Symantec's UNDI driver and PXELINUX
Hello, We use undi_drv.exe that is provided with Symantec Ghost Enterprise. This driver loads a UNDI PXE stack into memory. It, along with a UNDI packet driver are bundled into a 1.44MB disk image that we use for netbooting computer lab machines into the ghost client. This is done with pxelinux. This driver has been working fine for a couple years now. Recently, I upgraded the pxelinux.0 to