similar to: DOS access to Samba server

> On Fri, May 23, 2014 at 8:29 AM, Ady <ady-sf at hotmail.com> wrote: > > Testing the DOS-based Syslinux installer, syslinux.com, with the "-m" > > parameter, I found that it works as expected under MS-DOS and its DOS > > variants, but it seems to fail under FreeDOS (please correct me if > > I'm wrong). > > This sounds like either a bug in

On Fri, May 23, 2014 at 8:29 AM, Ady <ady-sf at hotmail.com> wrote: > Testing the DOS-based Syslinux installer, syslinux.com, with the "-m" > parameter, I found that it works as expected under MS-DOS and its DOS > variants, but it seems to fail under FreeDOS (please correct me if > I'm wrong). This sounds like either a bug in FreeDOS or another undesirable negative

On 05/24/2014 01:58 PM, Ady wrote: > > My guess is that if this was a bug in FreeDOS (as in "something" that > has nothing to do with the syslinux.com command) then it would be > somehow triggered by other DOS programs trying to write to the MBR. > Considering that there are several (open source) DOS programs that > are capable of successfully writing to the MBR

On Sat, May 24, 2014 at 11:22 PM, H. Peter Anvin <hpa at zytor.com> wrote: > On 05/24/2014 01:58 PM, Ady wrote: > > > > My guess is that if this was a bug in FreeDOS (as in "something" that > > has nothing to do with the syslinux.com command) then it would be > > somehow triggered by other DOS programs trying to write to the MBR. > > Considering

Sorry for the delay, I should not send email on an holiday week-end. I'll try to answer all the questions by explaining what does work for me right now, and what I'd like to do. I have a script to create the a USB stick or an ISO image. The boot media contains many DOS images, and I use versamenu to select one of them. If my DOS image is smaller than 8megs, everything is working fine as

To make say a BIOS flash tool available over PXE, my impression is that a typical procedure goes like this: modify a generic FreeDOS 1440K disk image to contain the EXE and change the AUTOEXEC.BAT to launch that EXE, then make the 1440K IMG available on the PXE server. But more recent BIOS flash EXE are too large and won't fit on the 1440K, not even 3840K, so now we have to look into

Hi, I did found the problem, a combination of 2 factor. 1- I taught that I did install the latest syslinux, but in fact it was the 3.36 version. 2- Thank to kevin Connelly, he point me to a problem he got with mkdosfs command. The default FAT16 do not work, but the FAT12 do. By adding -F12 to the mkdosfs command fix the problem. The default F16 do seem to work for <8M floppy image. Thank you

Testing the DOS-based Syslinux installer, syslinux.com, with the "-m" parameter, I found that it works as expected under MS-DOS and its DOS variants, but it seems to fail under FreeDOS (please correct me if I'm wrong). Using FreeDOS kernel v.2041 (386f32), Syslinux v.6.03-pre11 and either FAT16 or FAT32 partitions, executing: syslinux.com -m -i c: or: syslinux.com -f -m -i

Hello, I seemed to have encountered a problem with memdisk that I have seen before when I was playing around with USB device booting at one time. Here's the scenario: Take fx a image of a PC DOS bootable diskette. Boot the image via memdisk. This should boot fine if you use the built-in motherboard ide controllers (ide0,ide1). Now install a PCI IDE controller and put one IDE disk on the

Hi, I'm doing a small hobby project writing some tools to put DOS boot images and Linux rescue images on a USB stick. For this I have partitioned my USB stick in 2 partitions, one 192MB partition with a VFAT filesystem (for the normal use) and a second partition with an ext3 filesystem. My aim was to provide a graphical menu (grub) to access the different images using memdisk. Since

Add detection code for "MS-DOS 3.30 through Windows 95 (A)" MBR to disklib. Signed-off-by: Gert Hulselmans <gerth at zytor.com> --- com32/gpllib/disk/mbrs.c | 4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git a/com32/gpllib/disk/mbrs.c b/com32/gpllib/disk/mbrs.c index 77e4180..37309e1 100644 --- a/com32/gpllib/disk/mbrs.c +++ b/com32/gpllib/disk/mbrs.c @@

Hi Maybe HPA or Murali could help me with this one, or anyone who got the following working. I spend numerous hours reading the list and googling without success. I'd like to create a bootable USB stick and CDROM that will do the following. I will have a menu, from which I could pick a specific dos image (not partition). The dos images could have up to 20Megs in size. The goal is to have

Hello Samba users, I use FreeDOS with MS Client to map a network drive. However MS Client is a memory hog and prevents me to run all applications I need. Therefore I would like to ask here is there SAMBA implementation for DOS ? BR, czezz

I've got $SUBJ almost working except for the DOS bit where the CD needs to be read. My pxe config: label Firmware menu label Update IPMI firmware kernel memdisk append keeppxe raw iso initrd=<isofile> The ISO is about 400Mb, and works fine when I boot it from an actual CDROM drive. It also boots fine over PXE, I can see FreeDOS being booted up etc. The problem is - once

Greetings ... > Has anyone ever got command line only Windows 95 DOS to connect to a Samba > machine? I can connect to an NT machine no problem using "net use ...", but > the only machine the DOS machine will see on the network is the NT machine; > all of the others, including my Linux machines and a Win 2k machine, it just > refuses to see. First, any program you

Hi, I live in Brazil and have a question: dosemu works better with foxpro for dos ? Dosemu work with Freedos or msdos ? I'm waiting for answers. Thanks. Luiz Gustavo Brazil.

I'm new to memdisk and I wanted to have multiple floppy boot images on my USB key, I installed GRUB2 as the boot loader and have memdisk in /syslinux and my images in /image, I first tried booting normal images, memtest86+ works, my linux kernel work and they boot perfectly. Now using memdisk, I tried booting Spinrite which uses FreeDOS, it booted fine with no argument them frozen at querying

Version 6.04-pre1; pre-built binaries; the DOS-based installer, "syslinux.com", under Freedos 1.1 always fails, always showing the help / options (in my case, with some garbage characters too). This happens independently of the option being used (e.g. --version, or -i, or -if). Same scenario but with v.6.03 works correctly. TIA, Ady.

> On 08Jul2014--09Jul2014, Ady, Peter Anvin, Gene Cumm, Bernd Blaauw, Shao > Miller, Kenneth Davis, wrote: > > [...] > > Thank you all for your responses. You helped me solve my problem. For > anyone else that runs into similar trouble and finds this thread, here > follow summaries of what I've learned. > > To recap, our PXE server holds Dell BIOS updates in

For the boot floppy at http://superkeen.com/peacecorpsfiles/FUZOMA14.IMG using memdisk from syslinux version 3.72 boots correctly, but for memdisk versions newer than 3.72 (I tested 3.73, 3.75, 3.85, and 3.86) all hang at boot with the following message: Loading boot sector... booting FreeDOS kernel - SVN (build 2039 OEM:0xfd [compiled Oct 2 2009]) Kernel compatibility 6.22 - BORLANDC ... XMGR,