Re: [Freedos-devel] Joke of the day: lb040501.zip !?
On Sat, 8 May 2004 22:37:50 +0200 (MEST), you wrote: Hi Eric, I got busy because need to remove Netsky and Sassar in customer's PC. Luckily FreeDOS is safe from this. >If you are REALLY downloading my software under DOS, and your browser >is unable to process non-8.3 URLs, let me know. Doh. The browser should be able to handle this. But seems ARACHNE need some "hack"! Rgds, Johnson. --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] Re: LBAcache / TICKLE updated
Hi, IcE reminded me that LBAcache would panic when NDD tried to access funky "CHS with more than 1024 cyl" functions of some BIOS enhancers like EzDrive or OnTrack Drive Manager or SWBIOS. I added code to make those function calls fail and uploaded LBAcache again (still lbacache-09may2004.zip). Hope this solves the problem. I think NDD will just use normal LBA calls if it cannot find the funky stuff. If not, I would have to make LBAcache process those calls properly, but then I wonder how DOS kernel is supposed to be able to use more than 1024 cyl drives... Only hint in RBIL was "Win95b MBR tries to detect..." - but then even Win9x understands normal standard LBA. Let me know if Norton Disk Doctor is still happy with LBAcache. (Especially on drives where EzDrive or OnTrack is installed...) Eric --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] LBAcache / TICKLE updated
Hi, I uploaded a new LBAcache version to http://www.coli.uni-sb.de/~eric/stuff/soft/ lbacache-09may2004.zip >From the history.txt file: 09.05.2004 Included some TICKLE harddisk read-ahead improvements in the LBACACHE package in the TICKLEHD.COM file. Normal TICKLE.COM without harddisk read-ahead abilities still included as well. Fixed detection / support for 1.68 MB floppy geometry! Nicer STAT / INFO drive list display, also suppresses leading 0s now, but not for hex values. So: - INFO / STAT should now show an easier to read list-of-cached-drives in most cases, including LBA information and floppy cache information, but the latter is only shown if the old verbose list-of-drives is not needed. - FLOP mode should finally be able to cache 1.68 MB floppy and other non- standard sizes now! Background: int 13.8 returned ESDI in BIOS rather than returning current int 1e vector... - INFO / STAT now suppresses leading 0s from decimal numbers displayed, but not from hex numbers. Detected by checking whether the explanatory string ends in "0x" :-). - You now have both TICKLE and TICKLEHD available. The latter has harddisk read-ahead support compiled in and takes 0.7k more RAM for that. The hard- disk read-ahead support must be enabled by the command line options (case sensitive!) LB (for LBA) and HD (for CHS) respectively. You can enable both features at the same time with "TICKLEHD LB HD". You cannot disable floppy read-ahead in either TICKLE version, so you must always load it after an LBAcache which you loaded with the FLOP argument. Example: LBACACHE 6144 FLOP TICKLE LB HD Read the files in doc/lbacache for more information. And do not load TICKLE into an UMB if that UMB has problems with DMA - as usual. LBACACHE itself can be loaded into any UMB but will be slow if you load it into an uncached UMB (this affects UMBs created by UMBPCI on certain computers), of course. Happy testing! Eric. --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] new app: scrsave
Diego Iastrubni escribiÃ: ×Sunday 09 May 2004 7:09 pm, ×× ××× Arkady V.Belousov: I suggest, there is only one solution: trap INT 16 and return codes from your own buffer inside your program, if there present something. and what if the app uses int 21? does int 21 call int 16? All file reads produced through a file handle that points to the CON device driver do (or should) perform their activity through BIOS, int 16h. Aitor --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] new app: scrsave
×Sunday 09 May 2004 7:09 pm, ×× ××× Arkady V.Belousov: > I suggest, there is only one solution: trap INT 16 and return codes > from your own buffer inside your program, if there present something. and what if the app uses int 21? does int 21 call int 16? -- diego, kde-il translation team Please avoid sending me Word or PowerPoint attachments. See http://www.fsf.org/philosophy/no-word-attachments.html Free MS-Office replacement for most platforms http://www.openoffice.org/ --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] new app: scrsave
Hi! 9-Май-2004 19:49 [EMAIL PROTECTED] (Diego Iastrubni) wrote to [EMAIL PROTECTED]: >> INT 16/5 is very limited approach - at lewast, it limited by size of >> keyboard buffer (16 scan codes) and not available on old machines. DI> any other aproach? I suggest, there is only one solution: trap INT 16 and return codes from your own buffer inside your program, if there present something. --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] new app: scrsave
×Sunday 09 May 2004 13:53, ×× ××× Arkady V.Belousov: > Hi! > > 8-ÐÐÐ-2004 16:53 [EMAIL PROTECTED] (Diego Iastrubni) wrote to > [EMAIL PROTECTED]: > > DI> I also need to implement "virtual keyboard input" from a text file. I > found DI> function 5 of int 16h which can help me, however some tests I > have run did > > INT 16/5 is very limited approach - at lewast, it limited by size of > keyboard buffer (16 scan codes) and not available on old machines. any other aproach? A google session (a large one which took about all the weeekend) did not give me any pointers. Should I look into dosemu/freedos sources to find the answers? -- diego, kde-il translation team Please avoid sending me Word or PowerPoint attachments. See http://www.fsf.org/philosophy/no-word-attachments.html Free MS-Office replacement for most platforms http://www.openoffice.org/ --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: Splitting patch (was: [Freedos-devel] Re: [Freedos-cvs] kernel/kernel fattab.c,1.30,1.31 fatfs.c,1.66,1.67)
On Sun, 9 May 2004, Arkady V.Belousov wrote: > Hi! > > 9-íÁÊ-2004 15:39 [EMAIL PROTECTED] (Bart Oldeman) wrote to > [EMAIL PROTECTED]: > > BO> See for instance > BO> * From: Arkady V.Belousov > BO> * Subject: [Freedos-kernel] patch: mix > BO> * Date: Sat, 24 Apr 2004 01:56:11 -0700 > BO> Arkady, you should split this patch in 20 easily digestible chunks, and I > BO> will apply about 3 of them. If you don't want to split it, fine, the patch > BO> just goes to NUL. > > How? See: > > - in intr.asm changed allocmem(). > - to allocmem() relate changes in init-mod.h and config.c. So you prepare one logical chunk that touches intr.asm, init-mod.h and config.c. You can do that as follows: apply logical change, diff with previous apply next logical change diff with previous this is fine with me. What you first of all need to do is to isolate the bug fixes from all other changes. Then one patch is one bugfix. Overlapping usually isn't a big problem; "patch" can use a certain amount of fuzziness to deal with that -- I will just see a reject if it fails the fuzzy logic and can then deal with it manually. You should explicitly state it if patch Y really depends on patch X to apply. The main idea is to submit multiple *logical* changes with a short description about what each change does. Bart --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Splitting patch (was: [Freedos-devel] Re: [Freedos-cvs] kernel/kernel fattab.c,1.30,1.31 fatfs.c,1.66,1.67)
Hi! 9-Май-2004 15:39 [EMAIL PROTECTED] (Bart Oldeman) wrote to [EMAIL PROTECTED]: BO> See for instance BO> * From: Arkady V.Belousov BO> * Subject: [Freedos-kernel] patch: mix BO> * Date: Sat, 24 Apr 2004 01:56:11 -0700 BO> Arkady, you should split this patch in 20 easily digestible chunks, and I BO> will apply about 3 of them. If you don't want to split it, fine, the patch BO> just goes to NUL. How? See: - in intr.asm changed allocmem(). - to allocmem() relate changes in init-mod.h and config.c. - but config.c also changes freeAvailableBuf pointer to HMAuserarea offset, and this change spreaded also between init-mod.h, inthndlr.c, globals.h. - in these files are also some other changes: for example, in intr.asm fixed prototypes. How to split these changes (into digestable chunks)? Explain me, if you know this. I _suggest_, that I may do this so: - get my file and copy some changes from it to intermediate file. - make diff-file. - restore original contents of intermediate file and copy next change; goto step 2. But this is error prone process, and it may affect subsequent patching (especially if changes are crossed). Also, patch for batch and makefiles can't be splitted, because these changes related. PS: In next letter in -kernel@ I try to extract some changes. --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Re: new app: scrsave
Hi! 8-Май-2004 18:26 [EMAIL PROTECTED] (Diego Iastrubni) wrote to [EMAIL PROTECTED]: DI> I dont get it... Page N is in B800:[80x*25*N] right? No: __O\_/_\_/O__ volatile const word far &screen_width = *(const word far*) MK_FP (0, 0x44A); volatile const word far &screen_offset = *(const word far*) MK_FP (0, 0x44E); volatile const byte far &screen_height = *(const byte far*) MK_FP (0, 0x484); volatile const word far &char_height = *(const word far*) MK_FP (0, 0x485); volatile const byte far &screen_mode = *(const byte far*) MK_FP (0, 0x449); #define scrwidth(screen_width) #define scrheight (screen_height ? screen_height + 1 : 25) #define charheight (char_height ? char_height : 8) _ O/~\ /~\O Ie. size of screen defined as scrwidth*scrheight. Active video page number you may find as *(const byte far*)MK_FP(0, 0x462), but better to use "Offset from video segment to active video memory page" (screen_offset). --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Re: [Freedos-cvs] kernel/kernel fattab.c,1.30,1.31 fatfs.c,1.66,1.67
On Sun, 9 May 2004, James Tabor wrote: > Hi Bart! > Bart Oldeman wrote: > > On Tue, 4 May 2004, Steve Nickolas - Using Windoze wrote: > > > > don't pay too much notice. This is just standard ritual. Scary thing is > > that it's being going on pretty much the same way for three years now. > > > > Time for me to unsubscribe from the mailing lists and have a break from > > FreeDOS. > > > > > Hang in there! This has gone on for more than 3 years! What I was referring to is this discussion between Tom and me on one side and Arkady on the other. We all know exactly where we stand, yet Arkady seems to ignore all what is said in the last three years and continues to supply me with patches that he should *know* I ignore. With the odd good fix in between but it's quite difficult to find it as a 10 line fix snowed in between 900 lines of layout changes and micro-optimizations (and most of those optimizations are either neutral or make the code size worse for Watcom). This I have told many many times and if you do it too often you get tired of it. See for instance http://www.mail-archive.com/[EMAIL PROTECTED]/msg00752.html I mean: * From: Arkady V.Belousov * Subject: [Freedos-kernel] patch: mix * Date: Sat, 24 Apr 2004 01:56:11 -0700 Arkady, you should split this patch in 20 easily digestible chunks, and I will apply about 3 of them. If you don't want to split it, fine, the patch just goes to NUL. I have to reduce my FreeDOS activities anyway, starting a new job on the other side of the world in six weeks, moving, etc. Another reason is that it works mostly well enough for me now so my motivation to fix the remaining things isn't very high anymore. So at this point I can either just stop completely or spend say an hour per week or so on it. With the amount of pressure from the mailing lists and private emails it just looks easier to stop with it, as a kernel maintainer can't do a good job with such a small amount of time -- people will start to complain that I don't respond (I certainly won't have time and motivation to digest and split Arkady's patches; far more enjoyable to have a beer in the pub or run a half marathon). That's all there is to it really. I'm sure someone will step in and disagree but that's competely pointless as I have nothing to lose. Bart --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] new app: scrsave
Hi! 8-Май-2004 16:53 [EMAIL PROTECTED] (Diego Iastrubni) wrote to [EMAIL PROTECTED]: DI> I also need to implement "virtual keyboard input" from a text file. I found DI> function 5 of int 16h which can help me, however some tests I have run did INT 16/5 is very limited approach - at lewast, it limited by size of keyboard buffer (16 scan codes) and not available on old machines. --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Re: [Freedos-cvs] kernel/kernel fattab.c,1.30,1.31 fatfs.c,1.66,1.67
Hi Bart! Bart Oldeman wrote: On Tue, 4 May 2004, Steve Nickolas - Using Windoze wrote: don't pay too much notice. This is just standard ritual. Scary thing is that it's being going on pretty much the same way for three years now. Time for me to unsubscribe from the mailing lists and have a break from FreeDOS. Bart Hang in there! This has gone on for more than 3 years! I remember one time I suggested making changes to the kernel that was not 100% dos compatible. Than a unholy flame war erupted. The funny thing was, I wasn't trying to start one. Something about, sound blaster driver in ring 0 thing'y. Shit! Thou'z where the days! Don't give in Bart, the Kernel kickz a$$, James --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Joke of the day: lb040501.zip !?
Hello Eric, > Hi, I got an urgent request well - really urgent ;) > The claim is that (paraphrasing) "having to use a web browser > to download non-8.3-filename and save it as 8.3 filename on > disk would be contradictory to GPL". a) the claim is 100% bullshit. b) but is a good reason to switch to a different licens. > echo mmv lbacache-\*\?\?\?20\*.zip lb\#5\#2\#4\#1.zip could you please explain how this shall work on a 8.3 aware OS ? tom --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel