[EMAIL PROTECTED] escribió: > Send Freedos-kernel mailing list submissions to > freedos-kernel@lists.sourceforge.net > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/freedos-kernel > or, via email, send a message with subject or body 'help' to > [EMAIL PROTECTED] > > You can reach the person managing the list at > [EMAIL PROTECTED] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Freedos-kernel digest..." > > > Today's Topics: > > 1. bug in kernel build 2037 (Eric Auer) > 2. bug in unstable windows kernel (Eric Auer) > 3. Re: bug in unstable windows kernel (Kenneth J. Davis) > 4. Re: bug in kernel build 2037 (Blair Campbell) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 21 Jul 2006 23:34:59 +0200 (MEST) > From: Eric Auer <[EMAIL PROTECTED]> > Subject: [Freedos-kernel] bug in kernel build 2037 > To: freedos-kernel@lists.sourceforge.net > Message-ID: <[EMAIL PROTECTED]> > > > 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 FreeCOM > FreeCom version 0.84-pre2 XMS_Swap [Jul 17 2006 22:56:22] > from > http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/command/0.84pre/test > ing/command.com > ...) > > My problem is: > > rem somehow this crashes with WINKERN 2037 unless ?= is used??? > 123?INSTALLHIGH=C:\FDOS\bin\lbacache.com 15000 TUNS > > With kernel 2037, lbacache does not load - instead, the usual > illegal opcode thing is shown (emm386 version). However, > 123?INSTALLHIGH?=C:\FDOS\bin\lbacache.com 15000 TUNS > (and then typing Y, of course) does work fine. > > With kernel 2036, INSTALL / INSTALLHIGH work without any problems. > > Speaking of Windows compat, by the way: WIN /S works fine with 2036, > but WIN /3 does not work with 2036 nor with 2037 for me. It just > returns to the prompt. Bug 2037 is supposed to add Win386 support... > I tested only Win 3.1, because I do not own WfW 3.11 :-). > > Bonus Windows problem is that neither XDMA nor the newest QDMA > are compatible: Loading either of the two makes Windows freeze > while it plays the welcome sound. Probably some IRQ/DMA problem. > Happens both with and without EMM386 loaded. > > Eric > > > > > ------------------------------ > > Message: 2 > Date: Sat, 22 Jul 2006 20:05:19 +0200 (MEST) > From: Eric Auer <[EMAIL PROTECTED]> > Subject: [Freedos-kernel] bug in unstable windows kernel > To: freedos-kernel@lists.sourceforge.net > Message-ID: <[EMAIL PROTECTED]> > > > 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 effect is that using INSTALLHIGH > with the "?=" (ask user if this install should be done) > "FIXES" the problem: When I say YES, load LBACACHE, it > works with kernel 2037, but when I work without the "?", > then LBACACHE aborts with an illegal opcode (which has > a more verbose message when EMM386 is loaded, but which > does not really tell me what is going wrong here). > > Maybe you have an idea? > > About Windows compatibility: Win 3.1 "WIN /S" works > fine with kernel 2036 and older already, and "WIN /3" > just returns to the prompt without further messages, > even with the "winkernel". Maybe the patches only help > with Windows for Workgroups 3.11? > > Another Windows issue is that both XDMA and the newest > QDMA somehow spoil the IRQ and/or DMA handling of WIN /S, > which has the effect that Windows freezes while playing > the welcome sound (on ISA SoundBlaster) if XDMA or QDMA > is loaded. > > > Eric > > PS: This is the 2nd attempt to post this message, maybe > there is something wrong with the mailinglist for me...? > > > > > ------------------------------ > > Message: 3 > Date: Sat, 22 Jul 2006 19:05:26 -0400 > From: "Kenneth J. Davis" <[EMAIL PROTECTED]> > Subject: Re: [Freedos-kernel] bug in unstable windows kernel > To: freedos-kernel@lists.sourceforge.net > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=us-ascii; format=flowed > > Eric Auer wrote: > > ... > >> About Windows compatibility: Win 3.1 "WIN /S" works >> fine with kernel 2036 and older already, and "WIN /3" >> just returns to the prompt without further messages, >> even with the "winkernel". Maybe the patches only help >> with Windows for Workgroups 3.11? >> >> > ... > > It works for me, but I load only himem (MS or FD should work), emm386 > from the Windows directory if wanted, very important is share (without > which windows may crash or exit immediately with a variety of error > messages), and cutemouse. Are you trying with a diskcache program? have > you adjusted the win/system ini files to ensure compatibility as > indicated on fd wiki (by the way if in the next week or so it is > unreachable it is because my hosting company is working on migrating to > a new home and I've hit a few snags with their automated transition > tools), and have you tried with 4DOS? I assume you are sure the kernel > was compiled with the windows compat settings (yes I've made this > mistake before :-) > > Jeremy > > > > > > ------------------------------ > > Message: 4 > Date: Sat, 22 Jul 2006 20:25:26 -0700 > From: "Blair Campbell" <[EMAIL PROTECTED]> > Subject: Re: [Freedos-kernel] bug in kernel build 2037 > To: freedos-kernel@lists.sourceforge.net > Message-ID: > <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > >> Speaking of Windows compat, by the way: WIN /S works fine with 2036, >> but WIN /3 does not work with 2036 nor with 2037 for me. It just >> returns to the prompt. Bug 2037 is supposed to add Win386 support... >> > > You're supposed to make a system.ini change as well and load MS's > EMM386/HIMEM. See the wiki for details. > > I suppose that this kernel is not compiled with WIN31SUPPORT option because the debugging messages in the end of execution of a program does not shown on screen. And how i can view if kernel is compiled with WIN31SUPPORT or NOT???
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
