Re: [Freedos-devel] Recent Bugzilla entries
On Mon, 19 Apr 2004, Bernd Blaauw wrote: Hello Bernd, when you have issues about FreeCOM, please, file them at bugzilla or mail them directly to me ([EMAIL PROTECTED]); I'm likely to miss them in huge mails compiled of many different topics. It is also helpful to mention something eye catching in the Subject line (FreeCOM or FreeDOS for instance) as I get approx. 100 mails of Spam, Virii or Virii notifications per day into each of my publically published mailboxes. Thanks, -- Steffen Kaiser --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] HIMEM64 A20 report (latest)
Hi, I've tested some problematic applications (Quickview, MPXplay) with latest HIMEM64 and DOS32a, seems working fine. For last few version it use KBC-2 A20 but this version changed to always on A20. Sorry for my stupidity, is both them same thing or different? Thanks. Rgds, Johnson. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] TDSK report EMS controller fail
Hi, I just notice the TDSK and some EMS application report neither controller fail or EMS corrupt by using HIMEM64+EMM38664. I've tried to use NOEMS but still EMS exist but it's size was shrink to a very small size, maybe it's the reason of failure? Can I completely disable the EMS handler so application can't see any EMS exist? Thanks. Rgds, Johnson. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] HIMEM64 test release #2
Michael, how does that MAX work in HIMEM64? it keeps complaining about /MAX:4000 ignored I'm trying to reduce memory enough to not let the XMS-version of FreeCOM load in extended memory. DEVICE=A:\DRIVER\HIMEM64.EXE /MAX:4000 ;DEVICE=A:\DRIVER\EMM386.EXE X=A000- SHELL=A:\COMMAND.COM A:\ /E:1024 /D /P set path=a:\freedos also filedate is strange. FTP mentions 19-4, file mentions 19-4, but loading string mentions 18-4 Bernd --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Re: FreeDOS Beta9 RC5 has been released
On Tue, 20 Apr 2004, Eric Auer wrote: This reminds me of the 386 question: How much bigger than the FAT16 kernel is the FAT32 kernel in RAM (low, umb, hma) and how much of this would be saved by optimizing for 386, experiences? Low: the drive data tables take 32 bytes more per drive (depends on the number of partitions you have, independent of LASTDRIVE) The 2 low fnodes take 6 bytes more for FAT32 (12 bytes total) HMA:HEX DEC 8086 80186 80386 8086 80186 80386 FAT16 995c 9694 94c5 39260 38548 38085 FAT32 a7cb a4ed a24a 42955 42221 41546 i.e. FAT32 adds ~3.5-3.7K; 386 optimizes out ~1.2-1.4K The fnodes take 6 bytes more (6 * #FILES) UMB no difference How about speed gain? Perhaps, sometimes 1, 2 or 3 more BUFFERS available can make a difference. Otherwise I can't see any visible speed difference. Bart --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] HIMEM64 test release #2
At 07:14 PM 4/20/2004 +0200, Bernd Blaauw wrote: Michael, how does that MAX work in HIMEM64? it keeps complaining about /MAX:4000 ignored I'm trying to reduce memory enough to not let the XMS-version of FreeCOM load in extended memory. DEVICE=A:\DRIVER\HIMEM64.EXE /MAX:4000 ;DEVICE=A:\DRIVER\EMM386.EXE X=A000- SHELL=A:\COMMAND.COM A:\ /E:1024 /D /P set path=a:\freedos also filedate is strange. FTP mentions 19-4, file mentions 19-4, but loading string mentions 18-4 MAX is an = and not a :, it follows the example of an EMM= memory amount as with EMM386 (or INT15 with Microsoft HIMEM). I think I posted it as a colon, which is incorrect. The file dates are for updated binary and ASM source, but the EMM386C.C source which embeds a date wasn't changed, so the embedded date stayed the same. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] TDSK report EMS controller fail
At 08:42 PM 4/20/2004 +0200, you wrote: Michael Devore schreef: I need to be able to get any application which uses EMS and fails. What is a TDSK and can it be downloaded? http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/ramdisk/ 1)NOEMS 2)NOEMS NOVCPI 3)EMS=1 FRAME=NONE 4)EMM= (or EMM= FRAME=) option 4 is the really different one. option 1 and 2 change name of EMS drive so EMS apps only work in case 4 (because of pageframe), and VCPI apps work in case 1 and 3? 3 is nonexistents, there is no EMS= setting. If you mean EMM, then VCPI works in 1 and 4, and has too little memory to do anything in 3. Classic EMS programs will only work in 4, although there are applications which support EMS and don't use the page frame and therefore will work with the other options. They are pretty rare, though. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] TDSK report EMS controller fail
At 04:41 PM 4/20/2004 +0800, you wrote: Hi, I just notice the TDSK and some EMS application report neither controller fail or EMS corrupt by using HIMEM64+EMM38664. There's definitely a weirdness going on with EMS, but not all EMS, since other applications are using it okay. May have to quick patch EMM386 if I can find it. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] TDSK report EMS controller fail
There's definitely a weirdness going on with EMS, but not all EMS, since other applications are using it okay. May have to quick patch EMM386 if I can find it. note that tdsk up to and including 2.3x series has sourcecode. for problems with tdsk 2.4x series you have to contact Matthias Paul. he's been working on publishing sourcecode for over 3 years now :) (and that driver uses some strange way to patch the environment, a way which is incompatible with FreeCOM). Bernd --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] monitoring screen output
Hi! 20--2004 18:28 [EMAIL PROTECTED] (Diego Iastrubni) wrote to [EMAIL PROTECTED], Arkady V.Belousov Because DOS is not reenterable (you can't call most DOS function from inside TSR, when TSR gets control at time of DOS working), you should check when DOS is in idle state (see INT28 description). Also, there are other issues, related to hardware interrupts: when INT8 calls INT1C, it not acknowledge timer interrupt, so, until you return from INT1C, your system will/can not receive other interupts (timer, keyboard, etc). DI OK nice, still good to learn new DOS stuff :) DI Now, it seems like all I need to do is to trap the 28 interrupt instead of DI 1Ch or 8 (a 1 line patch). I did this and the interrupt is not called. DI I am still missing something. No. Unfortunately, DOS itself calls INT28 too rarely (only when it waits onput to fill input keyboard buffer), so you should use other doors. Ie., for example, you should trap INT21 and, if happen some event (handler from INT1C sets some flag), then your main resident code may call DOS if DOS not called OR you in DOS, but DOS calls INT28. But wait from me too much answers, I'm not write extensive resident code. You should study, for example, libraries like TeSeRact, TSRtoo, AMIS (management library from Ralf Brown) etc. DI Another thing: DI Looking inside the kernel in file chario.c in function: read_char_sft_dev, I DI see this code: DI if (check_break *pdev != syscon) DI check_handle_break(syscon); DI /* the idle int is only safe if we're using the character stack */ DI if (user_r-AH 0xd) DI DosIdle_int(); DI and also: DI http://www.ctyme.com/intr/rb-2739.htm I don't know what contained in this page. Just mention, which interrupt you mean. DI Apparently I have to pass a pointer to a byte to the DOS and set that byte DI to 1? I think I am lost, that manual is not that usefull. :( ? --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] Re: [Freedos-cvs] kernel/kernel blockio.c,1.30,1.31 dosfns.c,1.61,1.62 int2f.asm,1.27,1.28 proto.h,1.61,1.62 task.c,1.41,1.42
Hi! 20--2004 18:43 [EMAIL PROTECTED] (Bart Oldeman) wrote to [EMAIL PROTECTED]: +++ int2f.asm 20 Apr 2004 18:43:03 - 1.28 +global NETWORK_REDIRECTOR +NETWORK_REDIRECTOR: +pushbp +mov bp, sp +mov al, [bp+4] +pop bp +callcall_int2f +ret 2 Isn't better for Watcom declare call_int2f through #pragma aux and do #define network_redirector call_int2f? Like this: %ifndef WATCOM global NETWORK_REDIRECTOR NETWORK_REDIRECTOR: ... ret 2 %endif +++ proto.h 20 Apr 2004 18:43:03 - 1.62 /* network.c */ +COUNT ASMPASCAL network_redirector(unsigned cmd); [...] #pragma aux (cdecl_axdx) remote_printset -#pragma aux (cdecl_axdx) remote_rename +#pragma aux (pascal) network_redirector modify exact [ax dx] #pragma aux (pascal) call_int2f parm [al] modify exact [ax dx] #define network_redirector call_int2f #endif --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] TDSK report EMS controller fail
At 09:42 PM 4/20/2004 +0200, Bernd Blaauw wrote: There's definitely a weirdness going on with EMS, but not all EMS, since other applications are using it okay. May have to quick patch EMM386 if I can find it. note that tdsk up to and including 2.3x series has sourcecode. for problems with tdsk 2.4x series you have to contact Matthias Paul. he's been working on publishing sourcecode for over 3 years now :) (and that driver uses some strange way to patch the environment, a way which is incompatible with FreeCOM). Okay, my problem with EMS seems to have been that it was left in an indeterminate state after interrupted debugger work with TDSK, so that's a big relief. TDSK's problem (or more accurately EMM386's problem with TDSK) is that EMS function 58h is unsupported. TDSK uses that. No big deal to add what it needs. General questions for everybody: Is there any other application using EMS which has a problem for you? Does anyone have problems using TDSK with XMS (seems to work fine here)? --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] monitoring screen output
, 20 2004, 22:09,Arkady V.Belousov: No. Unfortunately, DOS itself calls INT28 too rarely (only when it waits onput to fill input keyboard buffer), so you should use other doors. Ie., for example, you should trap INT21 and, if happen some event (handler from INT1C sets some flag), then your main resident code may call DOS if DOS not called OR you in DOS, but DOS calls INT28. But wait from me too much answers, I'm not write extensive resident code. You should study, for example, libraries like TeSeRact, TSRtoo, AMIS (management library from Ralf Brown) etc. I did a readln in pascal, and was hoping to see my interrupt working :) this is not the case. DI Another thing: DI Looking inside the kernel in file chario.c in function: read_char_sft_dev, I DI see this code: DI if (check_break *pdev != syscon) DI check_handle_break(syscon); DI /* the idle int is only safe if we're using the character stack */ DI if (user_r-AH 0xd) DI DosIdle_int(); DI and also: DI http://www.ctyme.com/intr/rb-2739.htm I don't know what contained in this page. Just mention, which interrupt you mean. DOS 2+ - GET ADDRESS OF INDOS FLAG AH = 34h ignore that... me stupid... did not see GET. anyway, I see an if before. what does is the variable which is checked? DI Apparently I have to pass a pointer to a byte to the DOS and set that byte DI to 1? I think I am lost, that manual is not that usefull. :( ? again, ignore me, I am just half blind. I will look for the libs you mentioned, and I am also looking for demos in C (asm is too long :) Thanks again. -- 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: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] TDSK with EMM386 function 58h fix
At 09:42 PM 4/20/2004 +0200, Bernd Blaauw wrote: note that tdsk up to and including 2.3x series has sourcecode. Alright, I've added support for EMS function 58h in EMM386, and TDSK seems to be happy running under EMS as well as the original XMS. Big question for you, and any other interested parties: Do you want me to hold this version EMM386 and see if any other problems shake out of the tree, or make it available immediately? I do still have one bug report with EMM386, but I can't find it, not sure it's an EMM386 problem, although the user seems to be convinced EMM386 is at fault. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] Mala direta e-mails listas de email http://www.gueb.de/divulgamail
As melhores listas segmentadas de e-mails para mala direta. Todos os tipos: http://www.gueb.de/divulgamail Cadastros de e-mails segmentados por estados, profissões, empresas e pessoas físicas. Tudo que você pracisa para fazer a divulgação e publicidade do seu negócio, programas para spam e e-mail marketing. Listagens atualizadas e garantidas. Visite agora: http://www.gueb.de/divulgamail --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Re: FreeDOS Beta9 RC5 has been released
Bart Oldeman escreveu: How about speed gain? Perhaps, sometimes 1, 2 or 3 more BUFFERS available can make a difference. Otherwise I can't see any visible speed difference. I did som testing some time ago (M$DOS) and my conclusion is that if other buffers are present (in my case smatrdrv and internal cache) it is best _not_ to have too much buffers, no more that something between 10 and 20. In my case I limited to 10, but I remember som Windows problem if buffers were 20, but that could be in wfw3.11... Alain --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] TDSK with EMM386 function 58h fix
At 12:35 AM 4/21/2004 +0400, Arkady V.Belousov wrote: Hi! 20-áÐÒ-2004 15:26 [EMAIL PROTECTED] (Michael Devore) wrote to [EMAIL PROTECTED]: MD Big question for you, and any other interested parties: Do you want me to MD hold this version EMM386 and see if any other problems shake out of the MD tree, or make it available immediately? I think, for bugfixes you should release immediately. :) Not really a bug, we knew that the EMS function wasn't supported but nothing used it to test with and the function was not major. But close enough. I'll get things together and post it in next 12 hours. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Re: [Freedos-cvs] kernel/kernel blockio.c,1.30,1.31 dosfns.c,1.61,1.62 int2f.asm,1.27,1.28 proto.h,1.61,1.62 task.c,1.41,1.42
On Tue, 20 Apr 2004, Arkady V.Belousov wrote: Isn't better for Watcom declare call_int2f through #pragma aux and do #define network_redirector call_int2f? Like this: %ifndef WATCOM global NETWORK_REDIRECTOR NETWORK_REDIRECTOR: ... ret 2 %endif +++ proto.h 20 Apr 2004 18:43:03 - 1.62 /* network.c */ +COUNT ASMPASCAL network_redirector(unsigned cmd); [...] #pragma aux (cdecl_axdx) remote_printset -#pragma aux (cdecl_axdx) remote_rename +#pragma aux (pascal) network_redirector modify exact [ax dx] #pragma aux (pascal) call_int2f parm [al] modify exact [ax dx] #define network_redirector call_int2f Well I am basically looking into converting much of call_int2f into C -- leaving only the bit between int2f_call_push and no_neg_ax, and what goes below lseekeof in assembly language. This way the compiler can use better calling conventions for the callers (without needing funky compiler dependent assembly language) so the code size will decrease a bit too. (yes Tom, you hear that well I'm converting asm to C here!) The present patches are just intermediate stages to get closer -- maybe the remaining bits will be able to benefit from a few pragma's though but I first like to get the portable code up and running. Bart --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] TDSK with EMM386 function 58h fix
Arkady V.Belousov escreveu: Hi! 20--2004 15:26 [EMAIL PROTECTED] (Michael Devore) wrote to [EMAIL PROTECTED]: MD Big question for you, and any other interested parties: Do you want me to MD hold this version EMM386 and see if any other problems shake out of the MD tree, or make it available immediately? I think, for bugfixes you should release immediately. :) I Agree Alain --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] TDSK report EMS controller fail
At 04:41 PM 4/20/2004 +0800, Johnson Lam wrote: Hi, I just notice the TDSK and some EMS application report neither controller fail or EMS corrupt by using HIMEM64+EMM38664. Incidentally,if you get TDSK 2.3 past 32M and/or start playing around with the sector and cluster sizes, TDSK has a strong tendency to crash or misbehave. I went with the defaults and tested up to 32M for EMS and XMS, running Duke3D purely off the RAM disk and it all went okay. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
