>> License evilness. Better to have the EDR DOS style
>> hack for files above 4 GB file size than "that".
>
> Than what "that" ??? Isn't it the same thing ???
I thought there was some discussion about exfat or whatever the
MS thing for big files on embedded devices is, as that is not FAT
in the DO
> License evilness. Better to have the EDR DOS style
> hack for files above 4 GB file size than "that".
Than what "that" ??? Isn't it the same thing ???
> How about 64 kB?
Heh ??? DOS can read or write full 64 KiB (DX=0 ??? or is it only
64'000 Byte's ???).
> I think some hacks even support 128
Hi!
>>> My silly FATPLUS.EXE maybe ???
>> Was that the hack to go above 4 GB file size?
> NO: http://www.fdos.org/kernel/#fatplus
License evilness. Better to have the EDR DOS style
hack for files above 4 GB file size than "that".
Or of course turn LTOOLS into a drive letter driver
to support EX
SORRY for the repost:
Anyone can please upload the __correct__ "HISTORY.TXT" file for the
2040 kernel release on some place where it is easily discoverable ?
Both SF and fdos.org ?
http://sourceforge.net/projects/freedos/files/Kernel/2040/
http://www.fdos.org/kernel/
http://sourceforge.net/apps
> > My silly FATPLUS.EXE maybe ???
> Was that the hack to go above 4 GB file size?
NO: http://www.fdos.org/kernel/#fatplus
> Evil...
Anything is good in this word ?
> > Almost documented: ATA-33 and XDMA
> UDMA, probably.
NO, XDMA 3.1.
> Better use a multiple of cluster size and a power of 2.
And Bart is too quick, he already adjusted the watcom.mak so it just works. :-)
Thank you,
Jeremy
--
5 Ways to Improve & Secure Unified Communications
Unified Communications promises greater efficiencies for business. UC
On Jul 20, 2011 1:37 PM, "Bernd Blaauw" wrote:
>
> Op 20-7-2011 3:50, Bart Oldeman schreef:
> > It's probably best to make things explicit (unless the goal is a true
> > Win32->DOS cross-compile), using DOS16 utilities, by changing the last
> > part of mkfiles\watcom.mak to:
> >
> > CFLAGS1 = -os-
On 20 July 2011 13:36, Bernd Blaauw wrote:
> And now the fun part: compiling on Windows x64. No support for running
> 16bit programs at all.
Sure, for that you *need* a true cross-compilation. Just like on Linux.
The FreeDOS-kernel build's utility programs (patchobj.exe) are also
16-bit DOS if y
Op 20-7-2011 3:50, Bart Oldeman schreef:
> It's probably best to make things explicit (unless the goal is a true
> Win32->DOS cross-compile), using DOS16 utilities, by changing the last
> part of mkfiles\watcom.mak to:
>
> CFLAGS1 = -os-s-wx-bt=dos
>
> # *Implicit Rules*
> .obj.exe:
>
On 19 July 2011 13:27, Kenneth J. Davis wrote:
> On Sat, Jun 25, 2011 at 4:40 PM, Bernd Blaauw wrote:
>> Op 25-6-2011 16:06, Kenneth J. Davis schreef:
>>> Hello all.
>>>
> ...
>> Are there any verified/stable working compiled versions available of the
>> following?
>> * COMMAND (there's an openwa
On Sat, Jun 25, 2011 at 4:40 PM, Bernd Blaauw wrote:
> Op 25-6-2011 16:06, Kenneth J. Davis schreef:
>> Hello all.
>>
...
> Are there any verified/stable working compiled versions available of the
> following?
> * COMMAND (there's an openwatcom CVS/SVN version somewhere?)
I finally managed to buil
Op 10-7-2011 13:11, Eric Auer schreef:
>
> Hi dos386,
>
Ninja-ing thread here slightly:
Can kernel 2040 please be mirrored to Ibilio? Can't be found yet at
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/kernel/
---
Hi dos386,
>> PS: You could also compare EDRDOS+UIDE with FreeDOS+UIDE.
>
> IIRC I tested some caches in the past. Result: NO SPEEDUP at all for a
> single big file.
Maybe only helps with the sparse hack ;-)
>> unless dos386 describes what program(s) he used
>
> My silly FATPLUS.EXE maybe ???
> It's history.txt inside the doc directory, inside the zip archive.
No, it's outdated: 2011-04-09 ...
http://freedos.svn.sourceforge.net/viewvc/freedos/kernel/trunk/docs/history.txt?revision=1640&view=markup&sortby=date&pathrev=1640
--
~~~ wow ~~~
Op 10-7-2011 3:10, dos386 schreef:
> Anyone can please upload the __correct__ "HISTORY.TXT" file for
> the 2040 kernel release on some place where it is easily discoverable ?
> Both SF and fdos.org ?
>
> http://sourceforge.net/projects/freedos/files/Kernel/2040/
It's history.txt inside the doc dir
> I am working on updating my site as I move files to my new host.
> www.fdos.org/kernel is updated.
Anyone can please upload the __correct__ "HISTORY.TXT" file for
the 2040 kernel release on some place where it is easily discoverable ?
Both SF and fdos.org ?
http://sourceforge.net/projects/freed
> PS: You could also compare EDRDOS+UIDE with FreeDOS+UIDE.
IIRC I tested some caches in the past. Result: NO SPEEDUP at all for a
single big file.
> the data are useless :(
NOT that bad ...
> unless dos386 describes what program(s) he used
My silly FATPLUS.EXE maybe ???
> on what hardware to
More tests: http://jafile.com/uploads/dos386/perftest.txt
>> unless dos386 describes what program(s) he used on what hardware
>> to produce these results, the data are useless :(
>>
>>> ...you can try first writing some dummy data at where the file
>>> will end, then close it and re-open (wit
Hi Christian,
>> - write 1 byte of data at this place
>
> Shouldn't it be sufficient to seek to the desired size (as offset), then
> do a write with length zero there? (Writing with length zero extends or
> truncates the file to the current seek offset.)
Possibly, but I wanted to keep things si
> - write 1 byte of data at this place
Shouldn't it be sufficient to seek to the desired size (as offset), then
do a write with length zero there? (Writing with length zero extends or
truncates the file to the current seek offset.)
> - close the file
> - open file for writing (no truncate)
I wou
Hi Tom,
>>> More tests: http://jafile.com/uploads/dos386/perftest.txt
> unless dos386 describes what program(s) he used on what hardware
> to produce these results, the data are useless :(
>
>> ...you can try first writing some dummy data at where the file
>> will end, then close it and re-open (
>> More tests: http://jafile.com/uploads/dos386/perftest.txt
unless dos386 describes what program(s) he used on what hardware
to produce these results, the data are useless :(
> ...you can try first writing some dummy data at where the file
> will end, then close it and re-open (without truncate
Hi!
You tested copying a 2.2 GB file...
> More tests: http://jafile.com/uploads/dos386/perftest.txt
...you can try first writing some dummy data at where the file
will end, then close it and re-open (without truncate of course)
and do the actual copy. That should bundle the FAT updates and
incr
I am working on updating my site as I move files to my new host.
www.fdos.org/kernel is updated. But I only have a little bit of time that I
split among development & website updates.
--
All of the data generated in your I
> Also available for download at fdos.org
http://www.fdos.org/
> Content has not yet been moved to this host - please visit
> http://www.fdos.info (mirror) in the meantime
http://www.fdos.info/
> This page last updated - July 17, 2006
http://www.fdos.info/obten.html.en
> FreeDOS Beta8 (Nikita
More tests: http://jafile.com/uploads/dos386/perftest.txt
--
~~~ wow ~~~
--
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, sec
> Kernel 2040 has been tagged and should be made available on
> Sourceforge file releases within next few days
It is now: http://sourceforge.net/projects/freedos/
+ it does boot (no further tests yet)
- "history.txt" is lowercase and not updated:
> 2011 Apr xx - Build 2040
> Jeremy Dav
Op 25-6-2011 16:06, Kenneth J. Davis schreef:
> Hello all.
>
> Kernel 2040 has been tagged and should be made available on
> Sourceforge file releases within next few days.
Nice to have an official updated kernel.
> Also available for download at fdos.org:
> installer compatible form - http://www.f
Hello all.
Kernel 2040 has been tagged and should be made available on
Sourceforge file releases within next few days.
Also available for download at fdos.org:
installer compatible form - http://www.fdos.org/kernel/package/
same as sf releases - http://www.fdos.org/kernel/release/LATEST/
Note: t
29 matches
Mail list logo
