[Freedos-kernel] Kernel patch policy, branches, and FreeCOM

Hi all, Arkady: PLEASE do make FreeDOS 2035a behave as "wrong" as 2035, because people will want to compare 2035a to 2035, and if things happen like - you cannot format unformatted drives (disk access flag broken) - stable version of FreeCOM (0.82pl3, as opposed to 0.82pl3xyz testing) crashes

[Freedos-kernel] Re: FreeCOM

Hi, even though you now have an (0.82pl3w? Testing, unstable!) FreeCOM, you STILL should "waste" those FEW BYTES in the environment to maintain FreeCOM compatibility! There is TRANSLATED FreeCOM, STABLE FreeCOM, DEBUGGING FreeCOM, NON XMS SWAP FreeCOM, and possibly many other reasons why people c

[Freedos-kernel] Re: Re: FreeCOM

Hi, sorry, I swapped \0\0c:\\freecom.com with \0c:\\freecom.com then... Anyway, if you "waste" 3 bytes to do: A=B\0\0c:\\freecom.com\0 instead of \0\0c:\\freecom.com\0 ... then everybody will be happy! By the way, FDAPM is looking for COMSPEC to know if it is run from INSTALL. This should be work

[Freedos-kernel] Re: patch: dsk.c

> - small bugfix. Which is, for function 0x67: rp->r_ai->AI_Flag = (UBYTE)~(descflags / DF_NOACCESS) & 1; Basically it makes the function work as before, or as, for example: rp->r_ai->Al_Flag = !(descflags & DF_NOACCESS); Original code was: > case 0x47: /* set access flag

[Freedos-kernel] Optimization idea: DIV/MODULO never full 32=32/32bit

Hi, I took the effort to grep through the whole 2035 kernel sources, to find divisions and modulo calculations. Some results: * division/modulo macro should have an "if x/512 then ..." shortcut, especially for older CPUs where division is slow. We often divide by sector size, but without KNOW

[Freedos-kernel] Re: Optimization idea: DIV/MODULO never full 32=32/32bit

Hi! I mean: > + jcxz%%div3216 ; cx=0 -> divisor < 2^16 [ALL this code is NEVER reached in KERNEL now] [So you can add some "panic" here, e.g. deliberately divide by zero...] [...and then you have only he following left:] > +%%div3216: > + cmp dx,bx ; xh < y ? >

[Freedos-kernel] Smaller tour of 32bit stuff in kernel, optimize, bugs

Hi, I reduced the 500 line mail to 140 lines now... enjoy. Eric. --- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com

[Freedos-kernel] Smaller tour of 32bit stuff in kernel, optimize, bugs

Hi, I reduced the 500 line mail to 140 lines now... enjoy. Eric. lfn_inode: l_diroff offset could be an UWORD slot number, smaller dmatch dm_size is LONG but should be ULONG and dm_flags is not currently used. Note that the offsets in the structure are fixed, so dm_flags is to be replaced b

[Freedos-kernel] Re: Smaller tour of 32bit stuff in kernel, optimize, bugs

> > DosGetFree (FatGetDrvData int 21.1c/21.36) can crash, maybe because of > > a NULL navc pointer. > If so, please submit some code to make the kernel crash. > if not, shut up. I did. Read and shut up: http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/format/format-0.91r.txt > > M

[Freedos-kernel] Re: Smaller tour of 32bit stuff in kernel, optimize, bugs

HI ARKADY! No need to shout. Sorry that I did not read all patches well enough. So: f_dmod bug in LFN API to be fixed by Bart, l_diroff already 16 bit but documentation erroneously still lists it as 32 bit, file offsets generally already are unsigned 32 bit. I was wondering what O_LEGACY does...

[Freedos-kernel] Re: patch: cleanups

Arkady, Bart, > BO> -void _seg * KernelAllocPara(size_t nPara, UBYTE type, CStr name, int mode) > BO> +void _seg * KernelAllocPara(size_t nPara, UBYTE type, const char *name, int > BO> mode) > > This is example, how my shortcuts allows to shorter and, thus, more > redable lines. No, Bart i

[Freedos-kernel] timestamp problem on network drives?

Hi, somebody wrote in the FAQ (Using_FreeDOS/274) --> I am using freedos 0.82 pl 3 xms_swap [dec10 2003 06:49:21] and Bart Lagerweij's network tools. When I create a file on a network mapped drive it sets the date to 01- 01-80 and the correct time. If I create a local

[Freedos-kernel] Suggestion: original int 10/13/15/19/1b table implementation

Hi, should we implement this? --> MEM 0070h:0100h - DOS 5+ - ORIGINAL INTERRUPT VECTORS 10h,13h,15h,19h,1Bh Size: 25 BYTEs Note: each value is stored as a BYTE for the interrupt number followed by a DWORD for the vector these values are restored on INT 19 by recent versions

[Freedos-kernel] Re: patch: dosfns.c fcbfns.c inthndlr.c proto.h

Hi Arkady! Your patch is MUCH too long. > This is my (first) try to bugfix wrong INT21/1B, INT21/1C and INT21/36. > Sorry, tom, but there more than 1-2 lines of diff, and I doubt that this > diff may be (noticeably) reduced. > - bugfix: DosGetFree(): *navc was accessed (read and write) without c

[Freedos-kernel] Re: More kernel bugs and incompatibilities

Hi all, could you file the list of problems which are mentioned in this thread as Bugzilla entries? I believe some RTM did work - and Lucho found a very small binary patch to fix 32RTM - so Lucho, please try to remember what you patched and why, thanks. This might also be related to the used XMS d

[Freedos-kernel] Win3.x /3 investigations, /s ones, cool 386SWAT debugger

Hi, as suggested by Michael, I tried 386SWAT and would like to recommend it for those who have no SoftICE at hand... some hints: - 386SWAT loads as a device driver (quite small in DOS RAM) - it debugs "everything", including Win kernels / protected mode / ... - it detects if you have 2 PCI/AGP VGA

[Freedos-kernel] Re: More kernel bugs and incompatibilities

Hi Lucho, Tom, ..., TOM> > and so I won't touch the arkady branch with a 3 meter long stick. L> You already wrote this, but (1) I'd prefer the "innocent presumption", to > the "guilty presumption" towards him, and (2) I think that accusing him > when he's absent to defend himself is not ethical

[Freedos-kernel] 2035 findfirst bug: attr a8 treated as 08 if local

Hi, I am having with the "load saved game" function of a jump and run game... The game modifies the timer speed, hooks int 8, 9, 60, 61, 23 and 24, calls functions (ax) 0..6 of int 60 (int 61 is used quite a lot but does not seem to have "function number in ax" properties), uses functions 0 and 1

[Freedos-kernel] Re: Win3.x /3 investigations, /s ones, cool 386SWAT debugger

Hi Michael, > An unanswered question is are you able to successfully install Windows 3.1 > itself over FreeDOS? Attempting to do so here aborts the install while it > is within the initial stages of running Windows after preliminary DOS file > copies on disk 1 and 2. There is a fatal general

[Freedos-kernel] Win3.1 386Enh patterns (was: More kernel bugs and incompatibilities)

Hi! > the code patterns which Windows 3.1 looks for that Eric > mentions will NEVER be there, nor should they be there, of course. This depends a lot on WHY the patterns are searched / patched by Win3.1 ... For example the "mov ...,dx" might be to make something partially relocateable or to tra

[Freedos-kernel] Re: 32RTM Bug Found, no good fix

Hi, indeed an interesting problem... 32RTM fails to initialize CX (number of words to copy from stack) before a DPMI call, and instead, the CX of int 21.30 (get version) is used. So we need a version other than 1.1.35 (major, minor, seq): > - lr.CH = REVISION_MAJOR; /* JPP */ > - lr.C

[Freedos-kernel] Re: Re: Int 2f.122f already supported?

Hi Tom, Lucho, > INT 2F U - DOS 4.x internal - SET DOS VERSION NUMBER TO RETURN > AX = 122Fh > DX = DOS version number (h = return true DOS version) > note the 'internal', 'true version', and '4.x' ( not 4+ ) > I'd recommend to implement setver in a reasonable fashion :(( I t

[Freedos-kernel] int 25/26 LBAcache extension useful for FreeDOS?

Hi, I have been thinking about an extra tool for LBAcache: hook "int" 25/26 (or the FAT32 equivalent int 21.7xxx function, or all), for ONE drive. That drive must not use int 13 BIOS disk access. For all calls, call int 13 LBA functions, using the linear sector number from the call and a fixed im

[Freedos-kernel] Re: Compilers (the eternal topic :)

Hi all, I think it is not okay to move the copyright message from kernel to autoexec. The autoexec is just an example, most distros will not use it. You can keep the message very short... FreeDOS (version), copyleft (years) (mumble about authors) under GNU General Public License (version 2 or, at

[Freedos-kernel] Getting COUNTRY.SYS done right

About country sys: Do NOT copy it from another DOS. Our font (CPI) and keyboard (KL/KEY/KC/whatever) packages show that we can do much better if we collect the information ourselves, for the languages which are used by FreeDOS people. I might even put up an online form like "fill in: your country

[Freedos-kernel] COMDRIVE compatibility problem and analysis

Hi all, please check: http://www.coli.uni-sb.de/~eric/comdrive-analysis.txt.gz ... and tell me how to make (either by fixing FreeDOS or comdrive or both) this potentially very useful tool work with FreeDOS. Thanks! Download URL for the program itself (10k download) is in the txt, too. COMDRIVE 1.

[Freedos-kernel] Re: Boot sector drive incompatibility with other boot sectors

Hi Lucho! > Now our SYS stores 0 if the drive is A: or B: and FF in all other cases. > Then the boot sectors check if this value is FF and if so, use DL from > BIOS, else use the drive number from the boot sector. > ... > someone decides to overwrite our boot sector later with a boot sector fro

[Freedos-kernel] showing off with low RAM?

Hi, after PTS-DOS, the DR-DOS enhancement people have added an option to put more data structures of DOS into UMB (I guess this time we are talking about LoL / SDA). That way they get 626k of 640k low DOS RAM free after loading HIMEM/EMM386. If you want to keep up with the game, we could add such

[Freedos-kernel] Re: Boot sector drive incompatibility with other boot sectors

Hi! > > Only 0 and 80 are used by MS-DOS. ... > I remember a BIOS that had the option to boot from 2'nd drive. > this only makes sense if DOS then boots from 0x81. Therefore I vote for a SYS option which lets you decide whether or not the 0x80 in the boot sector will be used. The DEFAULT should

[Freedos-kernel] Re: boot sector drive incompatibility with other boot sectors

Hi Jeremy, I vote for 2) - use 0 or 80 only in the boot sector (or really any value the user wants, but default to 0 or 80) - the boot sector code has at a fixed location useBIOSorNotFixedLocation: mov [drive], dl - SYS is then responsible for determining if BIOS pro

[Freedos-kernel] Re: 2F-122F

Hi Aitor! > I have to agree with Arkady. Two things why I feel it could be inconvenient: > - the extra few bytes it takes > - the fact that, being unique to MS-DOS 4.0... Well... it was my idea to move this functionality from a FreeDOS-only function number to an MS-DOS-4.00-only function number.

[Freedos-kernel] Version setting / Goodbye from Lucho

Hi, CALLVER is http://www.coli.uni-sb.de/~eric/stuff/soft/specials/callver.zip ... and it does not support int 2f.122f nor int 21.33fc YET. If the kernel has it, CALLVER will offer some "set version to ... until the next change" functionality in a later version. FREEVER source code got lost in so

[Freedos-kernel] re: test bootdisk

Hi Bernd and all, > I finally got internet again, so after spending this afternoon reading > about 300 emails I'm back again. I noticed that :-). > DEVLOAD /H /Q ATAPICDD.SYS /D:FDCD0001 > DEVLOAD /H /Q CDRCACHE.SYS FDCD0001 CDRCACH1 5 Oh boy... I still suggest using DEVICE, not DEVLOAD. The

[Freedos-kernel] Broken VERSION= in 2035 etc. - too many kernels

Hi, after a while we found that only the Lucho / Arkady kernel has working VERSION=, which reminds me that we have too many versions: - outdated 2035 - Jeremy has added an unknown amount of patches to CVS HEAD 2035a, but I have no idea if / how well those patches got reviewed and which bugs th

[Freedos-kernel] Re: Broken VERSION= in 2035 etc. - too many kernels

Hi! > If it is broke in stable and fixed in dev, then it should > be fixed in head soon. Please people, the kernels are not > Lucho/Arkady vs Tom/..., they are stable and development (unstable). Well I can only give people the Lucho or the SF homepage URL if they want a kernel BINARY. If I unde

[Freedos-kernel] BUFFERS problem: wasting low memory if HMA too small

Hi, http://fd-doc.sourceforge.net/faq/cgi-bin/viewfaq.cgi?faq=incoming/321 tells: If not ALL buffers fit into HMA, then ALL buffers will be in low DOS memory. How hard would it be to put MOST buffers in HMA and only the REST in low DOS memory, if many BUFFERS are requested? Eric -

[Freedos-kernel] Re: BUFFERS problem: wasting low memory if HMA too small

Hi! Undocumented limitations like "buffers are in one segment" can be countered in two ways: Document them (show a warning, like "only N buffers possible in HMA, have to keep all buffers in low RAM") or (possibly configurable) ignore them (put 38 buffers in HMA and 2 in low RAM, but offer a SWITCH

[Freedos-kernel] FreeDOS, DR DOS and Win386 compatibility (shorter)

Hi, I exchanged some mails with Udo from DR DOS improvement project, and the conclusion might be that FreeDOS is not missing much for 386Enh compatibility - it only has one thing too much: fnodes. - DR DOS does not support int 2f.1603, so there is no ADDITIONAL instance data - DR DOS supports int

[Freedos-kernel] Re: question about the kernel with

Hi Jeffrey, I think I can explain your symptoms... Your bootable CD probably contains a boot floppy image. The BIOS uses this image to simulate an extra floppy drive. You can check the contents of the A: and B: drives to verify this. To avoid the effect, create a bootable CD with help of ISOLINUX

[Freedos-kernel] The magic of SAVEDS / SAVEBX

Hi, I tried to understand what SAVEDS and SAVEBX mean for MS DOS... it is used in the main int 21 handler, functions 0..32, 34..4f, 52..61, 63 and 64..??. First, ES DS BP DI SI DX CX BX AX are pushed. Then DOSDS is loaded, caller DS and caller BX are saved in SAVEDS and SAVEBX. A far pointer at do

[Freedos-kernel] Win386 compatibility: useful SDA quotes

Hi, I should have known that it was all in SDA... In MS DOS, SDA is at dosds:320, so I have an instant explanation for "saveds", "savebx", "user id", "computer id", "psp vs user id" and several other questions. Format of DOS 4.0-6.0 swappable data area: Offset SizeDescription (Table 0169

[Freedos-kernel] User ID stuff pinpointed: int 21.5d0x

Hi, I finally found out what the background of that (patched by Win if it finds it, by adding a breakpoint) "cmp al,7 / jb check / cmp al,9 / jbe skipcheck / check: ..." code sequence means! It is in int 21 functions 5d0x, and the check is for "computer ID" (dosds:33c, 0 for "local computer") and

[Freedos-kernel] Floppy boot config read broken in 2034/32+

Hi, Steve reports that while things were fine in kernels 2030 ... 2033 (both with and without FAT32 support), kernel 2034 WITH FAT32 support and all 2035 kernels fail to read the (fd) config sys file when booting from floppy. Probably something wrong with BPB initialization, but even then, shouldn

[Freedos-kernel] unused SFT fields <-> f_nodes not needed???

Hi, I tried to check SFT compatibility of FreeDOS, quick conclusion: sft_dcb is never accessed sft_stclust is never accessed sft_relclust is never accessed sft_cuclust is never accessed sft_dirdlust (sic!) is never accessed sft_diridx is never accessed sft_bshare is never accessed sft_ifsptr is ne

[Freedos-kernel] Re: unused SFT fields <-> f_nodes not needed???

Hi, not sure about that yet, but I think Bart pointed out the way to go here: As I described, most f_node fields have corresponding SFT fields. And we recently had this new abstraction level which copied between NEAR and FAR f_nodes. Barts suggestion is to replace those copy functions by functions

[Freedos-kernel] Re: Fwd: FreeDOS kernel disk routines

Hi! > te> My computer BIOS INT 13 is able to access up to 4096 cylinders > te> in a hard disk. > te> by using bits 6 -7 of DH in INT 13 requests as bits 10-11 of cylinder > te> number. I remember having a 386 (NeAT mainboard) which had this kind of BIOS feature. It means you can have 4k cylinde

[Freedos-kernel] Re: CF and HOT SWAP

Hi, you do NOT have to write code to handle FAT filesystem. You only have to EITHER convince the BIOS to access your CF disk OR write some (relatively simple) code which can read and write single sectors on the CF disk by accessing the IDE controller directly. The REST will be done by the FreeDOS

[Freedos-kernel] Re: feasibility question about embedded FreeDOS in my hobby project

Hi, you are not the first one who is planning FreeDOS ports for embedded x86: http://fd-doc.sourceforge.net/faq/cgi-bin/viewfaq.cgi?faq=incoming/277 This FAQ entry contains a detailled description of the needed BIOS services for the kernel. You can remove some of them by modifying the kernel a b

[Freedos-kernel] Suggestion: CPU detection and preparation

Hi, as we already (should) have 386 detection in 386+-only-kernels, some new suggestion: FPU detection! The Memtest86+ (memtest.org) maintainer tells: Some BIOSes fail to clear the FPU stack after POST, but mask exceptions. In other words: You will not be able to store variables in the FPU, but y

[Freedos-kernel] Re: Re: [Freedos-cvs] kernel/kernel inthndlr.c,1.87.2.12,1.87.2.13

Hi guys, interesting anecdote from Pat, but: > But in given case (`break' after `return_user()') there are _no_ > untested code, and return_user() doesn't returns back to switch in > inthndlr.c unconditionally. So, `break' there is _really_ not need... The whole point is that if you remove

[Freedos-kernel] Ways to improve the kernel (was: inthndlr...) f_nodes...

Hi, Tom is completely right: > in this case, removing 'break;' may have saved 5 bytes in the early > 90ties, but is irrelevant (or even contraproductive) with optimizing > compilers, and leads only to such irrelevant 'why was this changed' > threads. I have accepted that it is a passion of Arkad

[Freedos-kernel] Add GENIOCTL helper to KERNEL for USB?

Hi, I found that FORMAT and SYS need support for function int 21.440d.0860 (for FAT32: int 21.440d.4860) to find out the BPB contents. This function is not supported by ASPIDISK when you use USBASPI4, and it is not supported by some RAMDISK drivers. Other drives can be affected as well, maybe ZIP?

[Freedos-kernel] DosDevIoctl r_unit kernel bug (was: Add GENIOCTL helper to KERNEL for USB?)

Hi, I found out that SYS does not need the "get default BPB" call, it just uses it as optional data source to adjust the BPB of the already existing boot sector. However, FORMAT does need the default BPB when formatting a not-yet-formatted disk. The FORMAT problem with my USB flash memory stick,

[Freedos-kernel] DELTREE gets error 5 for directories since 2035a

Hi, Mohammed Sayed found out that kernel 2035a has a bug with DELTREE - it does not allow it to delete directories. However, RMDIR does work. With kernel 2035, everything works, so this is a 2035a-specific bug. Confirmed by own testing in DOSEMU... > http://www.freedos.org/bugs/bugzilla/show_bug.

[Freedos-kernel] Re: DELTREE gets error 5 for directories since 2035a

Hi, Lucho pointed out that DELTREE got error 5 because it had code which does "if OEM ID is 0FDh and CX is 0 or -1, then explicitly exclude the DIR attribute when resetting file attribs in preparation of deletion". This code is triggered by 2035a as it sets CX to 0, which is needed by 32RTM DOS ex

[Freedos-kernel] Trying to figure out 386 kernel EMM386 crashes

Hi, I found that http://fdos.org/kernel/ 386-optimized kernels, at least the CVS stable FAT32 one, crash iff you load EMM386, after the EMM386 "frame at" display and before the next "load Y/N" display of the kernel in F8 mode. Maybe you can have a look at kernel.HEAD sources from the same homepage

[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 sizes above 512 bytes (e.g. 1024 and 2048), each element in BUFFERS and the DiskTransferBuffer would have

[Freedos-kernel] Re: Analysis: Support for sector sizes != 512 bytes

Hi Arkady, > AFAIK, CD-ROM sector is 2352 bytes. That would be the raw (cdda) sector size. For data (iso9660...) CD-ROM, the useable sector size is 2048 bytes, rest is CRC/ECC overhead. > Eric, I suggest, non-standard sector size is not the hottest issue > (and, probably, will never b

[Freedos-kernel] re: DEVLOAD / ramdisk troubles - or kernel problems?

Hi, as the KERNEL.dbgdev from fdos.org/kernel works for me in DOSEmu, I could do some DEVLOAD CD .. problem debugging: Unfortunately the debug output is very verbose and multi-line, so I replaced "media_check: no change" by "MC:ok" and replaced "get_near_f_node" and "got near fnode" by "getfnode"

[Freedos-kernel] re: DEVLOAD / ramdisk troubles - or kernel problems?

Hi Jeremy, that was quick... > > quite straightforward: 1. . .. \ are all no device names and > > 2. dhp->dh_attr should be tested for ATTR_CHAR before comparing > > the IsDevice input to dhp->dh_name. > Eric, I have uploaded a test kernel [stable branch] for you to try. > http://www.fdos.org/ke

[Freedos-kernel] Shorter partition error messages please...

Hi, just saw on devel that a single wrong partition type already gives: WARNING: partition Pri:4 FS 06 has CHS=3584-0-1, not 1023-254-63 WARNING: partition Pri:4 FS 06 has CHS=3646-254-63, not 1023-354-63 WARNING: partition Pri:4 FS 06 is not LBA Please run FDISK to correct this - using LBA to ac

[Freedos-kernel] re: Kernel debugging

Hi, I think you can indeed introduce a compile time option like the DOSEMU one (which makes put_console send output to int e6 function 13) to get output to Bochs / QEmu specific interfaces. On the other hand, you can just use DOSEMU :-). I really recommend to use Bochs and the built-in debugger o

[Freedos-kernel] re: reload partition table and reassign drive letters

Hi, Jeremy is right, FreeDOS boots in seconds, so it is best to just reboot. Dynamic drive letter assignment is not what DOS programs are used to cope with. HOWEVER, useful aspects of "re-read partitions" would be: - you can scan a PCMCIA disk after initializing the disk controller - you can resc

[Freedos-kernel] re: Re: reload partition table and reassign drive letters

Hi, yes, FreeCOM can handle changing drive letters. The PROBLEM is that harddisk letters are handled by a kernel driver which can only do one hole-free range of drive letters. So if you could enable a new partition on the fly, all subsequent drive letters would move. HOWEVER, you are free to write

[Freedos-kernel] re: reload partition table and reassign drive letters

Hi Bernd, I did not invent quickboot, fdapm hotboot just calls int 19 (load boot sector and run it). To make that work in real life, you would have to have all interrupt vectors "DOS free" at the moment, or at least some int 19 handler would have to be hooked by everything which hooks boot-relavan

[Freedos-kernel] loading disk drivers before the kernel (was: request for comments/ideas etc)

Hi Jeremy, kind of generic subject line but a nice question :-). > For some projects I would like to work on I need to modify the kernel to > not overwrite certain sections of memory at startup... In general, you can modify the load segment (using the SYS option, editing the EXEFLAT options in

[Freedos-kernel] Diskette access question

Hi, question about the kernel used in beta9sr2: When you boot from beta9sr2 CD, a MEMDISK will simulate the A: drive, so your normal drive would become B:. However, on computers without actual diskette drive, FreeDOS seems to get stuck in some error condition. Did the "is DJ mechanism needed?" log

[Freedos-kernel] re: Can FreeDOS be installed on embedded system based on 80186/80188?

Hi, the short answer is: YES. You can run FreeDOS on 8086. > is it possible that freeDOS work on an embedded system without BIOS? The answer for that is longer. Searching for "embed" on http://fd-doc.sourceforge.net/faq/cgi-bin/search.cgi will point you to: http://fd-doc.sourceforge.net/faq/cgi-

[Freedos-kernel] New version numbers please!

Hi, please assign version numbers 2036 and 2037 to the last daily build CVS kernel stable and unstable versions... That will make it a lot easier to refer to versions e.g. in bugzilla. And people will be able to use VER to get a hint of what version they are using :-). We have been sitting with da

[Freedos-kernel] please change the default freecom and increase the kernel version

Hi, http://fdos.org/kernel/ makes people use 8086 FreeCOM if I understand the text right. This means they will likely have no XMS swap and no LOADHIGH. In short, they will think FreeCOM is really a BAD command.com Please make the XMS SWAP 186+ FreeCOM the one which is linked at the "Stable Kernel

[Freedos-kernel] re: please change the default freecom and increase the kernel version

Hi Bernd, > kernel 2034, 2035 released by Bart > kernel 2035A released by Jeremy > kernel 2035B by Jeremy (2035A + "stable features backported from 2035W) > kernel 2035W by Jeremy, experimental/development line The core problem is that 2035w is not a version. It is the label for the daily compil

[Freedos-kernel] solution for problem with diskette-less systems

Hi, I looked at the issue "kernel acts weird if there is no diskette drive"... In short: ddt *getddt(int dev) { return (ddt*)Dyn.Buffer + dev; } #define getddt0() ((ddt*)Dyn.Buffer) This assumes that the DDTs are at the start of the dynalloc area and that the first DDT is for A:, second for B:,

[Freedos-kernel] fdos.org editing needed, who can do it?

Hi, as Jeremy seems to be missing in action, could you tell me who else can modify the fdos.org/kernel page? I just downloaded the daily builds of several FreeCOM and FreeDOS kernel packages and found several problems with the web page, you could say. 1. kernel HEAD is featuring daily builds, bu

[Freedos-kernel] correction: fdos.org editing needed, who can do it?

Hi, I was wrong about item 2 of my mail: The link http://fdos.org/kernel/command.com leads to a classic FreeCOM 0.82pl3, build date 12/2003, file date 1/2005, which uses XMS SWAP, supports LOADHIGH but does not support LOADFIX... So: The file is older than I thought but at least it does support LO

[Freedos-kernel] FreeDOS kernel 2036 released

Hi all, what has been known as the "daily 2035 cvs stable build" kernel for over a year now has a new name and a new home: http://sourceforge.net/project/showfiles.php?group_id=5109 now has a file release "FreeDOS kernel 2036test". The "test" in the name simply means that I could add some last m

Re: [Freedos-kernel] FreeDOS kernel 2036 released

Hi Bart, you have to give cvs the command line option "-r UNSTABLE". interesting! Turbo C insists that the source files have CRLF line endings. You ran into the old problem that UNIX CVS clients check out source files using LF line endings and Windows (not sure if anyone uses a DOS CVS

Re: [Freedos-kernel] FreeDOS kernel 2036 released

Hi all, I have now uploaded an updated kernel2036-source and kernel2036-binary zip with CRLF source files and with both OpenWatcom AND TurboC kernel binaries to http://www.coli.uni-saarland.de/~eric/stuff/soft/by-others/ It would be nice if somebody could help by reverting the batch file versio

[Freedos-kernel] bug in kernel build 2037

Hi all, I have a problem with FreeDOS "unstable" / "Win386/WfW311" kernel, the kernel which calls itself 2037 by now: FreeDOS kernel version 1.1.37w (Build 2037w-UNSTABLE, Jun 29 2006) (by the way, the 1.0 pre ISO of FreeDOS has a buggy FreeCOM LFN thing, so either set LFN=N or update to the FreeC

[Freedos-kernel] bug in unstable windows kernel

Hi all, I found that the INSTALL(HIGH) of the winkernel (2037 unstable with Win386 patches) is broken. It works with kernel 2036. The test case is loading LBACACHE, size 15000, with TUNS option (which allocates an extra memory block in low memory when the cache itself is in UMB). An interesting ef

[Freedos-kernel] Kernel 2037 bugs (was: FreeDOS and FPC 2.0.4)

Hi all, Laaca writes that FreePascal works fine in FreeDOS 2036, our stable kernel version. So far so good. 2036 rocks. But FreePascal shows abnormal behaviour in FreeDOS unstable / testing kernel version 2037. So if any of you wants to figure out what is going wrong... would be really nice. Bec

[Freedos-kernel] FreeDOS MS DOS 3 last missing APIs, was: INT 21h, AX=43FFh

Hi all, I would like to draw attention to the fact that FreeDOS is even still missing a few MS DOS 3.3x functions. So function 43ff (create directory / rename file, allowing path/file names up to 128 rather than 67 bytes, allowing deeper nested directories) should IMHO wait until the other stuff

Re: [Freedos-kernel] DMA boundary error re bugs 698, 1952

Hi Jackie, basically other DOSes include a workaround to protect programs from themselves when they try to do disk access with buffers which cross multiples of 64k address-wise, while FreeDOS does not, yet, have such a workaround in the kernel. As far as I know, that part would be written in Asse

Re: [Freedos-kernel] Questions on news:alt.os.free-dos

Hi, have some answers :-). Maybe you can push them into alt.os.free-dos somehow, in a spam-safe way... > Google Groups is a nice web<>USENET interface. Have a look at > http://groups.google.com/group/alt.os.free-dos > Look for "Kernel Bug" (the first message right now) and > "FreeDOS Install Lang

[Freedos-kernel] Comparison of FreeDOS 2036 to the Tom kernel

Hi all ... and happy new year :-) I took some time to compare the current CVS stable / HEAD kernel FreeDOS 2036 to the "extra stable 2035c" kernel which is used by Tom. The latter is generally a bit older, but also features some patches which have not yet found their way into 2036. There are also

Re: [Freedos-kernel] Comparison of FreeDOS 2036 to the Tom kernel

Welcome in 2007 :-) Here part 2 of my mail from last year ;-), comparing Toms extra stable 2035c kernel to the CVS stable HEAD 2036 kernel. inthndlr.c: Toms version modifies DL on return from int 21.3301 (set ctrl c flag), while the CVS does not - CVS is better. The CVS version uses the ne

[Freedos-kernel] possible freedos kernel bug for char devices

Hi all, when looking into a bug report about a funny character device driver which is "writeonly", I found something problematic in our FreeDOS kernel sources. For more details, check the snippets of FreeDOS 2036 below, or: http://freedos.cvs.sourceforge.net/freedos/kernel/kernel/chario.c?revisi

[Freedos-kernel] FcbParseName bugfix, dos_rename (was: re: Online Bible and Freedos?)

Hi Frank, you wrote that the "Online Bible for DOS", which one can download at http://www.onlinebible.net/dosolb.html does not work in FreeDOS. After some messing with dosemu and the built-in debugger and interrupt trace functions of it, I figured out that your problem is in DOS INT 21 function

Re: [Freedos-kernel] Tom's kernel changes vs. CVS

Hi Bart, Tom, some extra comment for > 2. initoem.c: > + if (ramsize == peek(0, RAMSIZE)) > if (ramsize * 64 == ebdaseg && ramsize < 640 && peek(0, RAMSIZE) == ramsize) >the extra double check looks strange to me, why check twice? > Something strange with short-circuit boolean evaluation? .

Re: [Freedos-kernel] Comparison of FreeDOS 2036 to the Tom kernel

Hi Bart, here my reply to your reply to my list :-) Few "part 2" reactions first: - what was the reason for 21.3301 modifying DL again? - why is 2f.1228 "seek" disabled? - do you want to explain the "something else" in nls.c? Reactions to this first part: Any volunteers for SYS.TXT / CONFIG.T

Re: [Freedos-kernel] regarding COFF parser

Hi Reddy, http://www.delorie.com/djgpp/doc/coff/ provides lots of COFF info, but I think there are several file formats which are all called COFF. As DJGPP is open source, you can also read COFF file format aware source code in the sources of the compiler, linker / binutils, C library... For the

Re: [Freedos-kernel] New FreeDOSers Monthly Reminder

Hi Nick and everybody else who wants to unsubscribe: > [furious scream of frustration] > How do I get off of this mailing list?! I've > been trying to get off of it for months. Help me! That is ridiculously easy :-). Each mail explains it in the headers: > List-Unsubscribe: >

Re: [Freedos-kernel] Use of DJGPP under FreeDOS

Hi Andris, I think Bart Oldeman recently fixed the GNU SED problem... > Some time ago I submitted am error report for DOSEMU about > problems running DJGPP port of GNU SED from configure scripts > http://sourceforge.net/tracker/index.php?func=detail&aid=1429741&group_id=49784&atid=457447 > and

[Freedos-kernel] freedos tabstop handling problem?

Hi Bart, Arkady, other kernel people, what do you think about the following problem: We only have ONE scr_pos variable in the SDA but several functions use it for several char devices as far as I can tell. So tabstop calculation will probably go wrong when you "mix" accesses to, say, CON and AUX

[Freedos-kernel] fresh freedos svn kernel updates

Hi Rugxulo, Robert, kernel people, I finally figured out svn at home, so I updated three areas of the stable "branch" of the FreeDOS kernel in svn. Actually only UNSTABLE is a branch, stable is the default. Anyway. The three changes vary a lot in complexity. Fixing language glitches was easy. Th

Re: [Freedos-kernel] fresh freedos svn kernel updates

Hi Bernd, > Only KERNEL2.SYS works for me, better than the Fastboot supporting > kernel I downloaded (I think) a while ago. > KERNEL.SYS in your zip hangs my machine at the HMA/BUFFERS message. Yes, I have the same problem :-(. What I did to create kernel2 is to undo the changes of SVN revision

Re: [Freedos-kernel] fresh freedos svn kernel updates

Hi again, after checking > http://freedos.svn.sourceforge.net/viewvc/freedos?view=rev&revision=1325 again, I think that only IRQTEXT is what broke Bochs compatibility. So I applied a patch (revision 1341) which leaves the other 1325 changes intact. Jemm FASTBOOT should work with version 1341.

[Freedos-kernel] fix truename and report version 6.22?

Hi Bernd, I have tested the new kernel a bit in Bochs already. > >> Sample kernel binary: www.coli.uni-saarland.de/~eric/ke2007jul21.zip > same filename yet updated release? Yes, it was still 21jul :-). Updated kernel, kept kernel2. Something else: Rugxulo tested the executable-unpacker IUP

Re: [Freedos-kernel] fresh freedos svn kernel updates

Hi Bart, > I was looking into merging parts of UNSTABLE a few months ago but > it's a lot of work since I don't like about half of the changes. Actually I think it might take man-months or more to review all the MANY changes between unstable and stable, plus merge all the fixes of stable into un

Re: [Freedos-kernel] fix truename and report version 6.22?

Hi all, please check the current kernel updates with Bart's FASTBOOT versus STACKS fix and some DOS 6 compatibility updates from me: Binaries: www.coli.uni-saarland.de/~eric/svn-binaries-freedos.zip > Something else: Rugxulo tested the executable-unpacker IUP > (ftp.sac.sk/pub/sac/pack/iup067.z

[Freedos-kernel] Kernel, Sys and Freecom TODO items

Hi all, For the next file release of FreeCOM 0.84xyz and kernel 2038 / sys, I would be happy if somebody could figure out and fix the following problems: - SUBST somehow breaks getcwd / chdir in the kernel?? - when you write a char dev, the kernel tries to read it to detect ctrl-break, which

  1   2   3   >