search for: himem64

...e SYSLINUX to provide CD-ROM and PXE boot support for my boot disk. And it works great with MS-DOS. However, I want to use FreeDOS for the boot disk. This is very close to working with the latest releases of the FreeDOS kernel and utilities. I just have one blocking problem. I am trying to use himem64.exe, part of FreeDOS EMM386: http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/emm386/ I am comparing it with fdxxms.sys, part of FDXMS: http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/fdxms/ When I use PXELINUX+memdisk (version 2.08) to boot a trivial FreeDOS boot dis...

...(semi-defensive) 4 Boot EMM386 (optimal) 5 Boot EMM386 (semi-defensive) 6 Boot no UMB (defensive) 7 Boot no UMB (ultra-defensive) 0 Boot Clean ____________ Works fine. 1 Boot UMBPCI (silent) ____________________ It prints: ========================================================== FreeDOS HIMEM64 3.26 [Aug 25 2006] (c) 1995, Till Gerken 2001-2005 tom ehlert HIMEM - Fast A20 method used UMBPCI c't 11/95 - Siering/Sch?pers/Stiller V3.77 - support for new chipsets, Inter PPro, AMD K7 - Uwe Sieler 08/2008 AMD K8 CPU found Using CF00-E2FF Using E700-E7FF Program installed LowDMA (haftman# so...

...swer from the freedos XMS driver maintainer. more info will be provided afterwards. errors are these: *case1: device=himem.exe / dos=high,noumb Kernel: allocated 40 Diskbuffers = 21280 Bytes in HMA Invalid Opcode at 35A9 FFFF 0213 AA71 FFDC 0001 0E24 1095 0000 0001 0000 0002 0001 *case2: device=himem64.exe / dos=high,noumb Kernel: allocated 40 Diskbuffers = 21280 Bytes in HMA Invalid Opcode at 360F FFFF 0246 AA71 FFDC 0001 0E24 1095 0000 0001 0000 0002 0001

I am planning to release SYSLINUX 2.08 in the next day or so; basically 2.08-pre9 without any further changes. So, I would appreciate any and all testers for this... -hpa

...e ...which let me boot my 1.44M "test.img" floppy image with FreeDOS. My problem is that config.sys is not being read at all. I am certain it is not being read because: 1) I receive no "press F5/F8" prompt 2) I see no messages from the items in my config.sys (e.g., himem64.exe). 3) When autoexec.bat attempts to start the network, it fails saying that the ifshlp.sys driver has not been loaded. If I downgrade the FreeDOS kernel to 2.0.33 (ke2033_32), keeping everything else identical, the problem vanishes; my config.sys is read properly. If I remove "kee...