Re: [Freedos-devel] TDSK report EMS controller fail
At 02:06 PM 4/21/2004 +0800, Johnson Lam wrote: Also another application call BLASTER MASTER (Sound editor) also said EMS Corrupt, I've asked the author, it become free now. I can email or upload to your FTP if you want. I grabbed Blaster Master off the web. Turns out that for it to run under NOEMS, the application needs the EMS ID changed (to EMMQXXX0). EMM386 with NOEMS currently only changes the device driver name. I modified EMM386 to change the ID (at 67h vector seg+offset 10) as well as the device driver name. The result is that Blaster Master now works with NOEMS without the EMS corrupt messages. As a bonus, after the change Turbo Debugger is happy to run under NOEMS. Probably helps a few other EMS-optional applications work with NOEMS parameter. I'm not uploading yet another EMM386 release just now for that bit of obscure support change, but I'll do it later on. Maybe another modification will come up before tomorrow breaks, make it worthwhile. --- 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 01:10 PM 4/21/2004 +0100, Bart Oldeman wrote: On Wed, 21 Apr 2004, Michael Devore wrote: At 02:06 PM 4/21/2004 +0800, Johnson Lam wrote: Also another application call BLASTER MASTER (Sound editor) also said EMS Corrupt, I've asked the author, it become free now. I can email or upload to your FTP if you want. I grabbed Blaster Master off the web. Turns out that for it to run under NOEMS, the application needs the EMS ID changed (to EMMQXXX0) FD MEM checks for EMM0 at this place -- so it will now plainly say that no EMS driver is installed for NOEMS (which kinda makes sense if you take NOEMS literally), before it said (mem 1.5, 1.6): EMS driver installed, 16K free, no frame. Is this documented anywhere? Yeah, if you worked with Clipper, you might still remember the big stink when the new Microsoft EMM386 version made the change for NOEMS. Clipper only checked for the first three letters 'EMM' and failed when it tried to use EMS since it missed the 'Q'. Lots of finger-pointing, confusion, wailing, gnashing of teeth, and tearing of hair over that one. Search for EMMQXXX0 for a representative sample. Google groups has a taste of it, there was a lot more on CompuServe back in the days. Claims to have happened with MS EMM386 version 4.45. Definitely underdocumented, MS site mentions that name only once, but appears to show it as valid in an example. --- 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] 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] 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] 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] 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
