Re: [Freedos-kernel] Codepage and time separator data errors in COUNTRY.SYS

Hi Jeremy, > Hi perditi...@gmail.com, > >> Thank you. I will try to get to this by the weekend. > > Thanks! :-) > > Regarding the "Space between value and currency symbol" bit errors: > I checked my statement about a space between value and the € sign. > Various Internet sources, e.g., >

Re: [Freedos-kernel] Codepage and time separator data errors in COUNTRY.SYS

Hi perditi...@gmail.com, > Thank you. I will try to get to this by the weekend. Thanks! :-) Regarding the "Space between value and currency symbol" bit errors: I checked my statement about a space between value and the € sign. Various Internet sources, e.g.,

Re: [Freedos-kernel] Codepage and time separator data errors in COUNTRY.SYS

Thank you. I will try to get to this by the weekend. Jeremy On Thu, Jan 23, 2020, 3:11 PM Robert Riebisch wrote: > Hi > > for Germany COUNTRY.SYS reports "." (dot) for the time separator, when > it should be ":" (colon). > > I noticed the error in FD 1.3 RC2 and FD 1.2, when using: > >

Re: [Freedos-kernel] FreeDOS disk I/O is much slower then MSDOS

On at 2018-11-05 15:51 +0100, Tom Ehlert wrote: >> the FreeDOS kernel is seriously slower then MSDOS when doing >> larger copy/xcopy operations. > >> the cause: the disk I/O code avoids transfers that cross a 64K >> boundary, and splits these transfers into 3 (smaller) transfers. > >> this was

Re: [Freedos-kernel] FreeDOS disk I/O is much slower then MSDOS

> the FreeDOS kernel is seriously slower then MSDOS when doing > larger copy/xcopy operations. > the cause: the disk I/O code avoids transfers that cross a 64K > boundary, and splits these transfers into 3 (smaller) transfers. > this was needed for floppy controllers in the 1980's, but is

Re: [Freedos-kernel] Checking NUL directory/drive is broken in 2042

Hi, > Was using FreeDOS 1.1 2040 kernel? previously and could check for > drive or directory existence with the NUL device: > If exist c:\nul echo C: exists > If exist c:\mydir\nul echo C:\mydir exists > This behavior is broken with 2042, no longer being able to identify if a > drive/dir

Re: [Freedos-kernel] How do I compile just the bootsector and kernel?

See the FreeDOS Spec [0]. OpenWatcom C/C++ (1.9?) (and by extension WASM/JWASM? for ASM??) and NASM (no version either though many are based on 0.98.x) are the reference compilers/assemblers/linker. I was able to able to compile a recent kernel version with the non-reference compiler Borland

Re: [Freedos-kernel] Can the Kernel start my program instead of command.com?

>>From the point of view of protecting this system from counterfeiting & > unauthorised access, is it possible to interrupt processing config.sys? I > had read about pressing F5 to bypass config.sys and autoexec.bat. Also that > this can be disabled in config.sys. modify kernel.sys by using sys

Re: [Freedos-kernel] Can the Kernel start my program instead of command.com?

Thanks! It looks like the shell directive does exactly what I want. It defines what the kernel loads as the command processor. I'm in a funny situation where I only have just over 6 months total experience with DOS, and yet I'm writing DOS software for machinery which is 200 miles away... Not

Re: [Freedos-kernel] Can the Kernel start my program instead of command.com?

On Fri, 09 Dec 2016 02:07:24 -0700, David Kay wrote: > Is it possible to get the kernel to load my program directly instead of > via autoexec.bat? Then my system would just be composed of the kernel > and my program? Have you tried to declare your program in CONFIG.SYS using the SHELL= directive

Re: [Freedos-kernel] ke2042: nasm fails to assemble files during build time

On 6/12/2016 7:23, Robert Riebisch wrote: > I have used http://www.bttr-software.de/freesoft/menu.htm#linkln for > many years. Yeah, that sounds like the one I was thinking of (and the Free Software list is probably where I came across it). I don't think I ever used it (stopped using DOS around

Re: [Freedos-kernel] ke2042: nasm fails to assemble files during build time

On 30/11/2016 8:54, Mateusz Viste wrote: > Here's the thing: I, as a user, store lots of useful software on my PC. > Many of these programs are so useful that I like to have them available > immediately from anywhere: ZIP, UNZIP, UNRAR, UPX, NASM, TCC, OPTIPNG, > QV, MPXPLAY, UHEX, GOPHERUS,

Re: [Freedos-kernel] ke2042: nasm fails to assemble files during build time

Method 1 is the traditional DOS way of installing software. Maybe some advanced usage of JOIN & SUBST is what you are looking for? Another alternative (though slightly messy) would be to combine Methods 1 & 4. By that, I mean, leave the *.bats in C:\DOS. The *.bats will temporarily create a

Re: [Freedos-kernel] ke2042: nasm fails to assemble files during build time

On Tue, 29 Nov 2016 13:02:59 -0800, H. Peter Anvin wrote: > But why the batch file in the first place? It truly makes no sense: it > pollutes the namespace equally, and can just cause problems (e.g. in the > case of more than 9 arguments.) Not to mention slowing down a make. Here's the thing:

Re: [Freedos-kernel] ke2042: nasm fails to assemble files during build time

On 11/29/16 12:50, Travis Siegel wrote: > > Because, apparently the nasm being called isn't in c:\devel\nasm, so > change the path in the nasm.bat file to point to the proper place, and > the problem should be solved. Either solution will work. > But why the batch file in the first place? It

Re: [Freedos-kernel] ke2042: nasm fails to assemble files during build time

On 11/29/2016 3:32 PM, H. Peter Anvin wrote: > On 11/24/16 00:59, Mateusz Viste wrote: >> Hi, >> >> Your problem is related to the fact that your "nasm" command doesn't call >> nasm.exe directly. Instead, it calls a batch file named nasm.bat which >> has been placed in your %PATH% by the FDNPKG

Re: [Freedos-kernel] ke2042: nasm fails to assemble files during build time

On 11/24/16 00:59, Mateusz Viste wrote: > > Hi, > > Your problem is related to the fact that your "nasm" command doesn't call > nasm.exe directly. Instead, it calls a batch file named nasm.bat which > has been placed in your %PATH% by the FDNPKG installer. This nasm.bat > file is pretty

Re: [Freedos-kernel] EXT3 support

On August 26, 2016 12:26:52 AM PDT, Eric Auer wrote: > >Hi HPA! The boot sector takes a BIOS drive number of the >to-be-booted drive from the MBR, which can take it from >the BIOS. There also are patches to take the MBR item by >pointer from the MBR, but those are not used by

Re: [Freedos-kernel] EXT3 support

Hi HPA! The boot sector takes a BIOS drive number of the to-be-booted drive from the MBR, which can take it from the BIOS. There also are patches to take the MBR item by pointer from the MBR, but those are not used by default. So I guess the kernel could take the drive number from a boot sector,

Re: [Freedos-kernel] EXT3 support

On 01/13/16 08:33, Eric Auer wrote: > > Hi HPA and Joao, > > support for EXT3 in the kernel would indeed be large/complex. > > Only supporting EXT3 READS already would take circa 10 kB of > code, taking the size of the EXT2/3/4 GRUB module as example. > > I like MEMDISK bootable ramdisk style:

Re: [Freedos-kernel] FAT32 CHS boot sector problems since we introduced FAT32 LBA support?

Hi again, I have tried to investigate this problem further by comparing 3 files: > https://sourceforge.net/p/freedos/svn/HEAD/tree/kernel/trunk/boot/boot32lb.asm > https://sourceforge.net/p/freedos/svn/HEAD/tree/kernel/trunk/boot/boot32.asm >

Re: [Freedos-kernel] Kernel 2042 release

> Freedos-kernel] Kernel 2042 release Thanks :-) (I'll test) -- Attend Shape: An AT Tech Expo July 15-16. Meet us at AT Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their

Re: [Freedos-kernel] BUG: problems with INSTALL=, reported by Bret Johnson

the problem, brought up by Bret: during config.sys processing, INSTALL= \freedos\MEM.EXE /F will report ~24 K used at 99f0:0 however the kernel will crash if memory below this is overwritten. source for the bug: CONFIG.C, DoInstall() sets up a memory arena, and releases memory below the

Re: [Freedos-kernel] Kernel 2042 release

On May 12, 2016 2:05 PM, "Tom Ehlert" wrote: > > > INTERLINK issue has not been resolved, and still requires > > option to load low. > > Why not? > > crashing the kernel when a driver calls DosAlloc() is not so smart an > idea. disabling dosalloc for drivers is possibly

Re: [Freedos-kernel] [Freedos-user] INTERLINK

Hi, https://sourceforge.net/p/freedos/bugs/147/ located the bug in freedos kernel. this the first driver *at all* that uses dos_alloc (int 21 ah=48) INTERLNK.EXE does (pseudocode) is running at 426:2951 if (dos_version < 5)// try load high to UMB goto

Re: [Freedos-kernel] EXT3 support

On 17-11-2015 05:36, H. Peter Anvin wrote: A TSR redirector would be great for assigning an EXT3 drive to a drive >letter for standard I/O operations. However a kernel driver would >allow freeDOS to boot and run from an EXT3 journaling partition, I can >only imagine that the benefits from this

Re: [Freedos-kernel] EXT3 support

Hi HPA and Joao, support for EXT3 in the kernel would indeed be large/complex. Only supporting EXT3 READS already would take circa 10 kB of code, taking the size of the EXT2/3/4 GRUB module as example. I like MEMDISK bootable ramdisk style: MEMDISK can be booted by boot loaders which are able

Re: [Freedos-kernel] FreeDOS and redirectors

> I wanted to ask: to what degree does FreeDOS implement the redirector > interface? Are there any known incompatibilities? it should right work. all known redirectors CD/DVD drivers MS Lan Manager NTFSDOS NTFS4DOS VMSMOUNT (with source) for DOS work without (known) problems >

Re: [Freedos-kernel] FreeDOS and redirectors

2015-11-17 6:35 GMT+01:00 H. Peter Anvin : > I wanted to ask: to what degree does FreeDOS implement the redirector > interface? Are there any known incompatibilities? I didn't find any while implementing my own redirector. > The reason I am asking is that I started a project

Re: [Freedos-kernel] EXT3 support

On 08/14/15 15:00, Till wrote: > > Quoting João Jerónimo : > >> Wouldn't it be better to use a redirector? This can be done with a TSR. >> >> João Jerónimo >> > > > A TSR redirector would be great for assigning an EXT3 drive to a drive > letter for standard I/O

Re: [Freedos-kernel] hmmmm

I don't know if it's still available, but pts dos has source that you're allowed to use in your projects. I haven't looked at it recently, so I don't remember what license it was released under, (if any) but I do recall that as long as you held a license for pts dos, you were free to use the

Re: [Freedos-kernel] hmmmm

Sorry for the link I haven't used thus machine to send emails in a long time. The antivirus tags it with it. I had suspected that I wouldn't be able to kernel merge, but it's nice to have thoughts. The multiuser will have to wait whilst I wait on the response from Caldera, They have an

Re: [Freedos-kernel] EXT3 support

The basic idea is to start with a fresh install of an Ubuntu LTS server. Then a Script could install all the rest. I am already doing this on a project and it works very well, all scripts are posted on github: https://github.com/alainm/nfas (sorry, it's in portuguese due to local colaborators)

Re: [Freedos-kernel] EXT3 support

The only problem with virtual box is that it isn't accessible. Any folks using screen readers are likely to need dosemu instead of virtual box. It may work under orca, but I've not tested that here. Just a point of interest for those who need/want to know.

Re: [Freedos-kernel] EXT3 support

Quoting Alain Mouette ala...@pobox.com: Why not use all that effort to run FreeDOS over Linux? Dosemu works very well... It has already been done in the past, mas it was slackware based and as soon as released had no mantainance, so it went dead. *) you get all the drivers to run on any

Re: [Freedos-kernel] EXT3 support

I am interested in writing a new driver, one that would allow you to boot and run dos on a EXT3 partition. booting from EXT3 would require to make EXT3 part of the kernel. not going to happen. otoh there is virtually no disadvantage to have a loadable TSR to make EXT3 available as a

Re: [Freedos-kernel] EXT3 support

On 8/14/2015 12:38 AM, Daniel G. wrote: Greetings, I was reading the FreeDOS development wish-list and adding ext3 support to the FreeDOS kernel is on the list. Is anyone working on this at this time? Doubtful. It's more likely just wishful thinking from someone who doesn't know what all

Re: [Freedos-kernel] EXT3 support

Hiren's BootCD has had something called Paragon Mount Everything 3.0. Or are you interested in writing a new driver? On Fri, Aug 14, 2015 at 1:28 PM, Ralf Quint freedos...@gmail.com wrote: On 8/14/2015 12:38 AM, Daniel G. wrote: Greetings, I was reading the FreeDOS development wish-list and

Re: [Freedos-kernel] EXT3 support

Maybe, but ext3 was designed as a multithreading FS. The multithreading becomes single threading so performance would far worse, and possibly even worse than FAT16/32 or ext3 over redirector. On Fri, Aug 14, 2015 at 3:00 PM, Till oran...@mygrande.net wrote: Quoting João Jerónimo

Re: [Freedos-kernel] Questions about Kernel editions

I am an E.E./Comp. Sci. student, but I want to contribute to the FreeDOS Kernel. Would it be fine if I began setting up a multiuser/multitasking system like Digital Research's DOS 5, and begin the work to get Forth into the kernel? the kernel is definitively not the right place to

Re: [Freedos-kernel] Unable to use drive number 32 with some functions

Thank you. I will try to get a fix implemented this week. Your patch corrects supporting the 32nd drive if provided as value 1 thru 32 (0 is default) but still doesn't handle if passed as ascii value ` (0x60). Jeremy On Apr 26, 2015 3:51 PM, Damien Guibouret

Re: [Freedos-kernel] Unable to use drive number 32 with some functions

Hello, That's right, I was not expecting NDN will use it as it is already out of the spec. You can change the else if (((r-BL = 'A') (r-BL = 'Z')) || ((r-BL = 'a') (r-BL = 'z'))) /* NDN feeds the actual ASCII drive letter to this function */ used_drive = (r-BL 0x1f) - 1;

Re: [Freedos-kernel] removing functions?

In Fri, 30 Jan 2015 17:03:08 +0800, Eric Auer e.a...@jpberlin.de wrote: Hi Roy, Is there any guide that can help on compiling custom kernel with less-used function(for example, NLS functions) removed/stubified? Well FAT32 is a compile time option and I think RayeR made a slightly

Re: [Freedos-kernel] removing functions?

Hi Roy, Is there any guide that can help on compiling custom kernel with less-used function(for example, NLS functions) removed/stubified? Well FAT32 is a compile time option and I think RayeR made a slightly stripped kernel for his DOS in your flash BIOS chip micro... ehh... distro, but

Re: [Freedos-kernel] [Freedos-devel] Regarding Issue with FreeDOS.

Autoexec.bat and config.sys would likely be useful here, especially to understand the value of LASTDRIVE and to know if any other disk drive drivers are installed (CDROM, SATA, USB, Zip, etc.). Ideally, everyone matches MS-DOS, so knowing what functest returns there might help. On Sunday,

Re: [Freedos-kernel] [Freedos-devel] Regarding Issue with FreeDOS.

Louis after testing the application in MSDOS it returned me the value 26. On Mon, Sep 15, 2014 at 7:52 PM, Louis Santillan lpsan...@gmail.com wrote: Autoexec.bat and config.sys would likely be useful here, especially to understand the value of LASTDRIVE and to know if any other disk drive

Re: [Freedos-kernel] Regarding Issue with FreeDOS.

On 9/15/2014 1:42 PM, Tom Ehlert wrote: it would help if you would tell us what PDOS is. I a fairly certain that he is referring to this http://sourceforge.net/projects/pdos/ Ralf --- This email is free from viruses and malware because avast! Antivirus protection is active.

Re: [Freedos-kernel] Free tools for FreeDos

imagefd is useful softprobe too -- -chris Digitalatoll Solutions Group Tawhaki Software http://digitalatoll.com/ http://tawakisoft.com/ On Sun, Mar 23, 2014 at 6:43 PM, Mehdi Sotoodeh mehdisotoo...@gmail.comwrote: I would like to put some of my old tools (still useful) on the public domain.

Re: [Freedos-kernel] A question about the behavior of the NUL device in FreeDOSS 1.1

Thanks for reporting and fixing FreeDOS kernel BUG's :-) -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their

Re: [Freedos-kernel] [Freedos-user] Any interest in 486, 586, 686 kernels?

I'm not sure how you can say the FreeDOS project isn't interested in a BC5 kernel. because I was around when the kernel was ported to MSVC, BC5, OW (in that order) The BC5 makefiles I found in the kernel sources I didn't write. Bart last worked on them 9 years ago. right. an since OW became

Re: [Freedos-kernel] Any interest in 486, 586, 686 kernels?

Hi! Your vision on DOS is somewhat, well, interesting ;-) So there is a lot to chat about, although I am not sure if the KERNEL list is the right place for this topic. DPMI: I would expect performance gain to be minimal. Maybe there could be Low/HMA/UMB memory savings with a different

Re: [Freedos-kernel] [Freedos-user] Any interest in 486, 586, 686 kernels?

I still think having true functions in batch files would be a good thing turn batch files into more capable language On Tuesday, May 21, 2013, Eric Auer wrote: Hi! Your vision on DOS is somewhat, well, interesting ;-) So there is a lot to chat about, although I am not sure if the KERNEL

Re: [Freedos-kernel] [Freedos-user] Any interest in 486, 586, 686 kernels?

On 20/05/2013 02:11, Louis Santillan wrote: I apologize for mis-posting to fd-user previously. On Thu, May 16, 2013 at 10:47 AM, Tom Ehlert t...@drivesnapshot.de mailto:t...@drivesnapshot.de wrote: Dear Louis, a few points a) the FreeDOS project isn't very interested in a BC5

Re: [Freedos-kernel] [Freedos-user] Any interest in 486, 586, 686 kernels?

I apologize for mis-posting to fd-user previously. On Thu, May 16, 2013 at 10:47 AM, Tom Ehlert t...@drivesnapshot.de wrote: Dear Louis, a few points a) the FreeDOS project isn't very interested in a BC5 compiled kernel because BC5 isn't freely available/open source; I also doubt the

Re: [Freedos-kernel] Any interest in 486, 586, 686 kernels?

Hi Louis, sort of a long response - it seems hard to make a short point here: FreeDOS Roadmap, as goals and stretch goals for the project. I read (paraphrasing): built-in networking, built-in USB, integrated DPMI, 32-bit The fd32 project works or worked on the DPMI aspect. As far as I

Re: [Freedos-kernel] Fwd: [Freedos-user] Any interest in 486, 586, 686 kernels?

Louis Santillan schreef op 5-5-2013 18:28: Whoops, didn't realize that I replied to fd-user instead of kernel. One other note, all kernels are slightly bigger withe options I set. I guess it depends on what the compilers do: [1] optimize for certain processor architecture(s) [2] also keep

Re: [Freedos-kernel] Any interest in 486, 586, 686 kernels?

On 03/05/2013 15:55, Tom Ehlert wrote: In the past, we compiled kernels for 8086, 186 and 386 separately afair. I guess we got lazy and have dropped 186 because very few users have 186/286 as their CPU? They either have modern or REALLY old. this is not about 'lazy' it's easier for the user

Re: [Freedos-kernel] Any interest in 486, 586, 686 kernels?

Haha...I'd be interested if you ever developed a 586 core at 1GHz that could utilize DDR-3 upto 4GB. On Sat, May 4, 2013 at 1:43 AM, ht-lab han...@ht-lab.com wrote: On 03/05/2013 15:55, Tom Ehlert wrote: In the past, we compiled kernels for 8086, 186 and 386 separately afair. I guess we

Re: [Freedos-kernel] Any interest in 486, 586, 686 kernels?

On Fri, May 3, 2013 at 4:02 AM, Eric Auer e.a...@jpberlin.de wrote: Hi Louis, if I understand your patch correctly, you only changed the build configuration to check how it affects the size of the compiled kernel before UPX compression, which also is an indicator of RAM size of the kernel?

Re: [Freedos-kernel] Any interest in 486, 586, 686 kernels?

What's the difference between wcc wcc386? I noticed that wcc386 adds -5s, -5r, -fp5 (-6 equivalents) for stack, register and fpu optimization. Does wcc386 generate code that could be used in the kernel? -L On Fri, May 3, 2013 at 5:57 AM, Louis Santillan lpsan...@gmail.com wrote: On Fri,

Re: [Freedos-kernel] Any interest in 486, 586, 686 kernels?

Kernels with FAT32: 086: 68358 bytes 186: 67180 bytes (286 same) 386: 66044 bytes 486: 65948 bytes (586 and 686 same) It is interesting that even 186 instructions do make a quite big difference and that there is a difference at all between 386 and 486. With 186, you get pusha and

Re: [Freedos-kernel] Any interest in 486, 586, 686 kernels?

What's the difference between wcc wcc386? code generation for 16 bit (DOS) or 32 bit (windows) Does wcc386 generate code that could be used in the kernel? no Big wins could be had on 586 with FPU memcpy 64-bit versus the 16-bit asm in the kernel now and possibly the string functions.

Re: [Freedos-kernel] Kernel 2041 and Singlestepping the FDCONFIG.SYS.

I use the Kernel 2041 and found follow strange: If I press the F8 key for singlestepping and then the ESC key to skip a command, the singlestepping-process of the FDCONFIG.SYS is skipped. I implemented it this way because AFAICT MSDOS 6.2 behaves this way Under MS-DOS the ESC key skips

Re: [Freedos-kernel] [Freedos-user] FreeDOS Boot Disc

Hi Chris, I'll link to the 1.0 boot floppy image, under the FreeDOS 1.0 section. http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.0/fdboot.img That is a bit old so I am still preferring Ruffidea ;-) Also because it is easier to delete than to add stuff, for the latter

Re: [Freedos-kernel] [Freedos-user] FreeDOS Boot Disc

Hi Eric, Kernel on that image uses 386+ instructions... and it seems as if it does that without (properly) checking for the presence of a 386. That is correct, as a kernel cannot be both optimized for 386 and compatible with 8086 at the same time. Well, yes it could (look at FreeDOS

Re: [Freedos-kernel] [Freedos-user] Virtual floppy change problem and slow VirtualBox UIDE2 init problem

When DOS detects an unreliable floppy change line hardware, it should use the floppy label / serial / similar to detect changes in software ... How does DOS ever detect that any hardware is unreliable?? I do not know, but earlier in this thread, somebody said that the numbering of FAT

Re: [Freedos-kernel] [Freedos-user] Virtual floppy change problem and slow VirtualBox UIDE2 init problem

Jack, kernel people (now CCed), When DOS detects an unreliable floppy change line hardware, it should use the floppy label / serial / similar to detect changes in software ... How does DOS ever detect that any hardware is unreliable?? I do not know, but earlier in this thread, somebody

Re: [Freedos-kernel] Commit 1705

Kernel 2041 seems to be out: http://sourceforge.net/projects/freedos/files/Kernel/2041/ (untested, just history.txt __IS__ updated this time) but nobody annouced it :-D -- Virtualization Cloud Management Using

Re: [Freedos-kernel] Commit 1705

Op 19-2-2012 10:57, dos386 schreef: (untested, just history.txt __IS__ updated this time) but nobody annouced it :-D It's a secret to everybody! (hm, too much Zelda) The pre-386/memdisk detection is a good thing, finally a unified kernel. Right until someone does a append FD={INSTALL=FORMAT

Re: [Freedos-kernel] Commit 1705

Hi Bernd, (untested, just history.txt __IS__ updated this time) but nobody annouced it :-D Yes, why?? I forward a message from RayeR in the forum below. It's a secret to everybody! (hm, too much Zelda) The pre-386/memdisk detection is a good thing, finally a unified kernel. For the

Re: [Freedos-kernel] Regarding commit 1702 (large sector sizes)

Note that the 1702 changes were effectively reversed by 1704. The 1705 changes are unrelated. Wrong From -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but

Re: [Freedos-kernel] Regarding commit 1702 (large sector sizes)

Dear PerditionC,    UBYTE DiskTransferBuffer[MAX_SEC_SIZE]; wastes 3,5 KB low memory for *everybody*, not only when it's needed. regarding how much time we have spend until we had 64 byte free I think this is a bad idea please see my previous messages, I know exactly how much space

Re: [Freedos-kernel] Re : Support for 4k byte

Hi Czerno / Bertho, Hi Eric! On the freedos-kernel list, you voiced such opinion about the future of big sector disks: that has low priority imho, as drives with large sectors are a temporary thing, will be gone with GPT partitions. This refers to the following quote from an earlier 4

Re: [Freedos-kernel] Regarding commit 1702 (large sector sizes)

Dear PerditionC, UBYTE DiskTransferBuffer[MAX_SEC_SIZE]; wastes 3,5 KB low memory for *everybody*, not only when it's needed. regarding how much time we have spend until we had 64 byte free I think this is a bad idea I also think that these experiments should NOT be in the stable

Re: [Freedos-kernel] Commit 1705

Hi Chris, Jeremy, Commit 1705 renames a particular LoL field CPULevel and adds a comment correctly claiming that MS-DOS sets this field to 1 on 386+ CPUs and to 0 otherwise. The commit however makes the boot loader store the detected CPU level (0, 1, 2, or 3) there instead. I don't

Re: [Freedos-kernel] Regarding commit 1702 (large sector sizes)

On Tue, Feb 7, 2012 at 9:51 AM, Tom Ehlert t...@drivesnapshot.de wrote: Dear PerditionC,    UBYTE DiskTransferBuffer[MAX_SEC_SIZE]; wastes 3,5 KB low memory for *everybody*, not only when it's needed. regarding how much time we have spend until we had 64 byte free I think this is a bad

Re: [Freedos-kernel] Regarding commit 1702 (large sector sizes)

Hi Jeremy, Chris, others, I am aware they are different... That is risky - even for a demonstration implementation, consistency seems important to keep code maintainable... dynamically adjusted same as MSDOS. That currently is not done. that has low priority imho, as drives with large

Re: [Freedos-kernel] Regarding commit 1702 (large sector sizes)

- First, dsk.h defines the maximum sector size (MAX_SEC_SIZE) as 2048 (as the commit comment says) while the relevant LoL entry (maxsecsize) in kernel.asm is initialised to 4096. Yes - this is simply for testing purposes; I plan to default both to 512. I would prefer both set from the

Re: [Freedos-kernel] [Freedos-user] Re : Support for 4k byte sectors

On Jan 14, 2012, at 5:26 PM, Eric Auer wrote: are simply too small to be bootable anyway. I wonder if you should be able to boot from nonstandard sector sizes at all - for example a CD- ROM does not even have a FAT filesystem, so why would you boot from a (raw!) CD-ROM then? Booting from cds

Re: [Freedos-kernel] [Freedos-user] Re : Support for 4k byte sectors

Op 14-1-2012 19:48, Bertho Grandpied schreef: It's been a few days and I'm surprised my first mail hasn't been acknowledged in any way, let alone answered; strange, I've been part of various lists before, usually 'newbies' are greeted rather than ignored altogether. So I'll reiterate and

Re: [Freedos-kernel] [Freedos-user] Re : Support for 4k byte sectors

Replaying a 12 May 2005 mail :-) [Freedos-kernel] Analysis: Support for sector sizes != 512 bytes Hi, I have browsed the CVS kernel a bit, and got the impression that it would not be too hard to support sector sizes below 512 bytes (32, 64, 128 and 256 bytes should be possible). For sector

Re: [Freedos-kernel] [Freedos-user] Re : Support for 4k byte sectors

On Sat, Jan 14, 2012 at 5:26 PM, Eric Auer e.a...@jpberlin.de wrote: Replaying a 12 May 2005 mail :-) [Freedos-kernel] Analysis: Support for sector sizes != 512 bytes Hi, I have browsed the CVS kernel a bit, and got the impression that it would not be too hard to support sector sizes below

Re: [Freedos-kernel] [Freedos-user] Re : Support for 4k byte sectors

Hi Jeremy :-) Replaying a 12 May 2005 mail :-) [Freedos-kernel] Analysis: Support for sector sizes != 512 bytes Thank you for reviewing and providing a suggested road map. Well, that old mail is nice for reference, but I would still say: So I suggest to support nonstandard sector sizes

Re: [Freedos-kernel] [Freedos-devel] [PATCH] kernel - only print suspect partition warnings if FORCELBA is not in use

Op 18-12-2011 23:31, Pete Batard schreef: 1. I am the developer of Rufus [1], which is a DOS-bootable USB flash drive creation utility for Windows. One of the versions of Rufus embeds FreeDOS (kernel + freecom) for installation as the default DOS, in lieu of the WinMe DOS that can be

Re: [Freedos-kernel] [Freedos-devel] [PATCH] kernel - only print suspect partition warnings if FORCELBA is not in use

... 3. All the machines I have tried so far report the CHS vs LBA computed mismatch warnings. Considering that first time FreeDOS users might be put off because of these benign warnings, I would very much like to avoid them. There's a list of warnings indeed. A big one at that,

Re: [Freedos-kernel] ..

.. http://koag.tym.cz/christmas.html?uCID=y9i1 -- Cloud Services Checklist: Pricing and Packaging Optimization This white paper is intended to serve as a reference, checklist and point of discussion for anyone

Re: [Freedos-kernel] (no subject)

hello! http://islamy.unidar.ac.id/winterpharm.html?jrtopicid=o5o5 -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats,

Re: [Freedos-kernel] possible to disable initdisk?

Hoi Bernd, I'm in a situation where I got Syslinux bootloader on an USB flash drive. It loads the MEMDISK ramdisk module with a floppy image as contents which is then executed (as drive A:). I'd like to get into a situation where the USB flash disks doesn't get a driveletter assigned by

Re: [Freedos-kernel] possible to disable initdisk?

Op 22-8-2011 0:47, Eric Auer schreef: You can hook int 13 function 8 (get drive parameters) and make sure that for dl = 80 or higher, it always returns carry set and dl = 0 to pretend having no harddisks. Of course DOS does a lot of work for you to parse partitions, so it is a bit odd to

Re: [Freedos-kernel] possible to disable initdisk?

Op 22-8-2011 0:58, Bernd Blaauw schreef: Then, again, Syslinux/memdisk documentation lists a nopassany parameter to disable showing harddisk. Gotta test that next I guess :) This works like a charm, however FreeDOS kernel happily lists about 50 lines with 'illegal partition table, drive nn,

Re: [Freedos-kernel] FreeDOS kernel UPX'ing and versionning chaos

Most FreeDOS kernels released so far were UPX'ed and not un-UPX'able. The kernel almost-2040 included on 1.1test3 CD distro is NOT UPX'ed. Problem: with UPX'ed kernel, you can't check the version without booting the kernel. Suggestion: at the beginning or end of the file, add a string

Re: [Freedos-kernel] FreeDOS kernel UPX'ing and versionning chaos

Hi Bernd, general question: How much do we want to know about a kernel without booting it? Because a lot of the information below is available AFTER booting the kernel, be it by human reading of the version description string (21.33xx) or by querying some int 21 functions to check FAT32 support

Re: [Freedos-kernel] Kernel 2040 released

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 DOS sense

Re: [Freedos-kernel] Kernel 2040 released

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 kB I

Re: [Freedos-kernel] Kernel 2040 released

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:

Re: [Freedos-kernel] Kernel 2040 released

On 20 July 2011 13:36, Bernd Blaauw bbla...@home.nl 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

Re: [Freedos-kernel] Kernel 2040 released

On Jul 20, 2011 1:37 PM, Bernd Blaauw bbla...@home.nl 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 =

Re: [Freedos-kernel] Kernel 2040 released

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

Re: [Freedos-kernel] Kernel 2040 released

On Sat, Jun 25, 2011 at 4:40 PM, Bernd Blaauw bbla...@home.nl 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

Re: [Freedos-kernel] [Freedos-user] Kernel 2040 16-bit

Op 14-7-2011 5:09, Marcos Favero Florence de Barros schreef: I'm now using the 32-bit 2040 kernel, because none of these errors has ever appeared under the previous 32-bit kernels, and I'm hoping they will not appear under the new one either [fingers crossed]. Any advice is

  1   2   3   4   5   6   7   8   9   10   >