similar to: AW: AW: flashing bios & memdisk

I and some other people have problems with running the freedos image included in Ultimate Boot CD (UBCD), when using memdisk for floppy emulation. Memdisk starts booting the image and freedos shows the following menu: 0 Boot Clean 1 Boot UMBPCI (silent) 2 Boot UMBPCI (optimal) 3 Boot UMBPCI (semi-defensive) 4 Boot EMM386 (optimal) 5 Boot EMM386 (semi-defensive) 6 Boot no UMB (defensive) 7 Boot

Hi I'm using memdisk as part of CD Shell' isolinux. I've created custom floppy disk image 8440kB size. I've put FreeDOS kernel and bootsector into the floppy. Boot process goes fine with this command: isolinux /boot/memdisk initrd=/ximg/fdos.img c=60 h=8 s=36 floppy The problems begin when I try to run FreeDOS memory manager emm386 from the floppy image. my config.sys: ...

> It would be possible -- in fact, fairly easy -- to hack the > "raw" mode of MEMDISK to drop the system into big real mode > after finishing instead of real mode; such a "bigraw" mode > might solve the problem with this particular program. > > The PC hardware... gotta love it. ok, i don't understand a lot of this; but sounds nice ;) could you please

(FreeDOS developers, I apologize for the redundant parts of this message. But I want to bring the SYSLINUX folks into the discussion, and the SourceForge mailing list archives are broken.) Background: I have a little Sourceforge project (http://unattended.sourceforge.net/) for which I use SYSLINUX to provide CD-ROM and PXE boot support for my boot disk. And it works great with MS-DOS. However,

When last we saw our hero, er, sysadmin, he'd found that the "noarch" BIOS update was, in fact, a self-extracting .exe file, and he'd extracted it. Finally getting the ok to take the system down, the following hilarity (for small values of hilarity) ensued. First, booting off unetbootin to freedos was fine... except it was try to guess which version - freedos + emm386 + himem,

Hi, Thanks a lot for the great tools at syslinux. I have an interesting problem for which i am trying to use memdisk. I have a cluster of 40 machines (same hardware config) all needing a bios flash. Rather than doing it manually, i am trying to use the PXE mode. So i am using memdisk to boot an image of my bios flash floppy over the network. my platform configuration is supermicro motherboards

This isn't an esp urgent issue, but I'd like to use a certain RAM diagnostic (Doc Mem) which I've already posted a note about a couple of months ago. Simply won't work booting the floppy disk image via MEMDISK. In the interim, I've tried to resolve this by changing things on my side. I'm pretty sure it's a XMS incompatibility, as it fails differently depending on

hi, i've seen that there already have been some messages to bios flash via memdisk image. i also had some problem with that. the programmer of "UNIFLASH" told me, that memdisk is using protected mode and this should be a problem, because uniflash only works with real mode. i've found i amiflash that works with protected mode and with this i can flash the bios. [with memdisk]

Hello! Is it possible to load a virtual DOS Floppy with memdisk to do a few things (e.g. scan for viruses, copy a hard disk image from the network to the local disk) and continue booting from the local hard disk without a reboot? Cheers Alex

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

I'm trying to use this universal DOS TCP/IP boot disk available here: http://members.iinet.net.au/~bdriver/bootdisk/ It requires an MS-DOS formatted disk created by Windows XP. It works great as a floppy but doesn't boot at all with memdisk. The problem can be simplified down to just the XP boot disk. If you make an MS-DOS startup disk with XP on a floppy, dd the floppy to an image

I have added instructions to memdisk.doc for how to disable MEMDISK. However, it's unlikely that this will work if you're running under DOS, since DOS will be very unhappy about drives changing underneath it. Anyway, until the next (pre)release comes out, here are the instructions: --- memdisk.doc 27 Apr 2004 06:49:36 -0000 1.10 +++ memdisk.doc 6 Jul 2004 01:29:03 -0000 @@ -122,5

It appears that the WinME/XP DOS boot disk links code into the INT 15h AH=87h "mover" function which crashes the system DELIBERATELY (it puts the system in a cli/hlt/jmp loop.) I first thought it was specific to MEMDISK, but it's not; calling this function under just about any circumstances from within this version of DOS seems to crash the system hard. It's possible

Hi, I've got the same Problem. Not with WinMe but Win 98SE. But what I figured out is, that it doesn't realy apply to the Command.com rather to the Way the BootImage was created. It took me a long time to get my Hands on a Image with 2.8MB that's working. Since creating one my self, was allways failling. I downloaded the Bootutils 4.3 from 3com and used the Imageedit tools. With these

>that image under B: or X: or whatever. This will allow us to cross the >size limit of 2.88MB floppies. Ofcourse when I say "mount" I dont expect >memdisk to mount it, just that set things up so that DOS mounts it there. I'm using a 5MB image which emulates floppydisk. label test kernel data/memdisk append initrd=data2/test.img c=80 h=8 s=18 floppy problems are

Hello , I trie to use xen 3.0.3 , on my config , and virtual machine with HVM does not work . For testing the hvm virual machine i had used some iso : (1) http://rescuecd.pld-linux.org/download/2006-06-25/x86_64/rescue.iso (2) http://rescuecd.pld-linux.org/download/2006-06-25/x86/rescue.iso (3) http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.0/fdfullws.iso (4)

Hi everyone, Here is the problem: I have a server running Red Hat 5.2 and Samba-2.0.4 as file server for about 20 diskless machines with MSClient boot disks (created with NT server SP3). The server shares a dir with a Clipper/DBF database for those clients and the EXE file is in a NT machine. For weeks I've been trying to put the things together but the clients always break

Hi there, I have a client in a network using a samba-server that has to use MSDOS, because some software running on it needs a clean DOS. I installed the DOS-Client for TCPIP that is available from Microsoft V 1.0 and it works fine; the only thing is, that it takes so much memory below 640 K, that another program also running under DOS does not function correctly anymore. Maybe some of the

H. Peter Anvin, The following problem came to my attention with memdisk. I cannot claim the credit, but wanted to be sure the information made it back into the program for the benefit of all users... In file memdisk.asm, in respect of the operation of the raw and bigraw options, the order of pop instructions does not correspond to the order registers are pushed;

Just for the record, I want to let the list know that I succeeded in booting a modified Universal TCP/IP Network Bootdisk floppy from http://members.iinet.net.au/~bdriver/bootdisk/ I started with a Win98 Bootfloppy from http://www.tobs.uku.co.uk. Then I made a disk image from this, using dd.exe from cygwin. Then I converted this disk image from 1.44MB to 2.88MB with winimage. Then I copied