Re: [Freedos-devel] DeSmet C compiler available under GPL

-- Original message -- From: "Blair Campbell" <[EMAIL PROTECTED]> > > Isn't glibc licensed under the Lesser GPL (LGPL) for this very reason? > > But a commercial app still cannot _statically_ link to it in that > case; only dynamically. > > > > Mark No, that's th

Re: [Freedos-devel] FreeDOS corrupting FAT32 USB Stick partition

-- Original message -- From: [EMAIL PROTECTED] > Good day, all: > > I am trying to get a USB stick to boot FreeDOS using SYSLINUX and MEMDISK. > It boots fine using the odin1440.img file from odin.fdos.org/2005/. FreeDOS > boots fine and copies the odin1440.img f

Re: [Freedos-devel] FreeDOS corrupting FAT32 USB Stick partition

Hi Jeremy: The BIOS setup screen says Phoenix - Award BIOS. Now that the device has been formatted FAT, Linux fdisk has the following to say: [EMAIL PROTECTED]:~# fdisk /dev/ube Command (m for help): p Disk /dev/ube: 65 MB, 65208320 bytes 255 heads, 63 sectors/track, 7 cylinders Units = cylin

[Freedos-devel] FreeDOS corrupting FAT32 USB Stick partition

Good day, all: I am trying to get a USB stick to boot FreeDOS using SYSLINUX and MEMDISK. It boots fine using the odin1440.img file from odin.fdos.org/2005/. FreeDOS boots fine and copies the odin1440.img files to A: (a ram disk). It recognizes the USB stick as C:. However, a DIR C: shows no fi

Re: [Freedos-devel] re: Coding a getdta() function in FreeDOS

Hi Eric: Thanks. That provided enough breadcrumbs to get it going! :-) Mark > > Hi Mark, you are pretty close already... > > > get a getdta() function (to acquire the disk transfer area) that will > > work with Open Watcom... > > The Kernel interrupt handler for Interrupt 21 function 2F >

[Freedos-devel] Coding a getdta() function in FreeDOS

Good day, all: OK, I gotta learn something about DOS programming. I have spent a few hours on what I believe to be a very simple task...trying to get a getdta() function (to acquire the disk transfer area) that will work with Open Watcom. At this point, I'm pursuing it as a learning tool! Also,

[Freedos-devel] re: VOL Command - More Tests

Thanks to Eric, I can now report that the rapidly repeating error message with the stable kernel is: Enter the full shell command line: Bad or missing Command Interpreter: EEE The three capitol E characters actually have an accent over them, but I don't know how to type that. This error appear

Re: [Freedos-devel] Re: FreeCom 0.84pre bugs and stuff

Hi Jeremy: Thanks. Works like a charm with all of the NTFS drives I've tested with...even shows what looks like the correct amount of free space! Wonderful, quick support! Mark Bailey > cvs returned, so the changes below committed and build with them now > available for testing at usual loca

Re: [Freedos-devel] re: Bug in FreeCOM DIR command

No, I think (1024*1024)/(64*32768) would be .5, which is zero in integer division. :-) 2097152 > 1048576 All they appear to be doing is converting bytes to Megabytes, so (FAT32_Free_Space.free_clusters * clustersize )/(1024l*1024) should do it, without yielding 0 all the time (my first suggestio

[Freedos-devel] Bug in FreeCOM DIR command

Good day, all: I believe I have found a bug in FreeCOM's implementation of the DIR command. This causes a Divide by zero error and forces a reboot. Using the DIR command on an NTFS4DOS mounted NTFS partition which should show 0 File(s) 0 bytes 7 Dir(s)