Date: Tue, 16 Apr 2002 20:46:46 -0400 From: madodelatptdprolog.net Subject: [VOICENWS] Testcase: new 0416 kernels available From: "Scott E. Garfinkle" [All followups to comp.os.os2.bugs] Following is the readme [Moderator Note: I have trimmed the bug fix listing of the readme. These files can be found at ftp://testcase.boulder.ibm.com/ps/fromibm/os2/ Please read the entire readme before doing anything with these files.] . Note the os2dump and the fixes section. -Scott ---------------------------------------------------------------------- This contains fixes since xr_e002/xr_m015/mcp/acp. Important note: If you use the OS/2 SES facility, you need a new sesdd32.sys dated April 2001 or later to use this kernel. Also, a matching dump formatter (df_ret.exe), provided separately, is required, if you want to analyze a dump from this kernel. Finally, note that os2ldr is only required for the >64mb memory detection mentioned below. ***New as of 2002/04/16: I'm including an updated os2dump module, because the one that comes with mcp2/acp2 can possibly OVERWRITE your partition(s)! If you plan to use standalone dump and you have mcp2 or acp2, use this! Caveat: This os2dump will *not* work on non-LVMized systems (i.e. Warp 4+ FP13-16). On the other hand, the bad os2dump wasn't distributed for FP13-16. New function: 1) Support for >64m memory using int15 func e820. Note, this support is enabled ONLY for Intel Pentium Pro or later, or non-Intel Pentium-class machines. This is done in an effort to prevent problems on older PCs. 2) The presence of \os2\boot\os2norev.$$$ suppresses the display of internal revision during boot. 3) Adding "EARLYMEMINIT=TRUE" to config.sys will allow device drivers, etc., access to the memory above 16mb early in boot. Previously, this was only available after DD and IFS init was completed. This has various implications when enabled: a) AHA154X.ADD may do bad things to your system. Don't even ask. b) There may be some settings of HPFS386 cache that are incompatible. 4) Trap messages will now give the module name instead of the device name. For example, "Exception in module: CLOCK01" instead of "Exception in Device Driver: CLOCK$". ***change from 0220/0223: Traps in 32 bit code now show the modname, too 5) Systems with a 486SX chip running FP15 will function correctly. Note, they will NOT work with ACP or (necessarily) on MCP. 6) SESDD32 will now work correctly (I hope) for both uni and smp 7) All process dumps should now be considerably faster. paddr(all) dumps should take about 40% less time and others around 80-90% less time. 8) EXE names will now also be displayed in alt-f2/alt-f3 processing (note that CMD file names, e.g. MPTSTART, will NOT be displayed, only cmd.exe) 9) alt-f4 is like alt-f2 plus it pauses after displaying each names (does not pause after BASEDEV= or PSD=) and, by pressing F1, allows you to skip loading/running the file displayed. Alt-f5 is like alt-f4+alt-f1. 10) The dump formatter (in dfxxx.zip) should be faster and also work on dumps >= 2gb, which was not formerly possible. 04/16/2002: 11) Added "1" as an OK setting for flags in config.sys. Now, things like EARLYMEMINIT=TRUE can also be YES,ON, or 1 (or FALSE,NO,OFF, or 0). I wish I could make stuff like this NLV-independent but that is ABSOLUTELY IMPOSSIBLE without HUGE changes. 2002/01/02: Support for 16bit filesystems with >2gb file support (e.g.the forthcoming >2gb dump support ifs) 9/13/01 11) If you also install the enclosed clock01.sys to \os2\boot, you can add "CLOCKSCALE=x" to config.sys. The choices for x are 1 (the default, which is the old behavior), 2, and 4. The number represents a scale factor for the frequency of clock ticks. The theory is that CLOCKSCALE=4 will speed up some apps (maybe Netscape and/or Java). [Moderator's note: As always these are not officially supported by IBM unless they tell you to use them. Please send any followup to comp.os.os2.bugs on usenet. Also note that files are only on IBM's testcase for 2-3 days, so if you want to try these get them now. Make certain you back up any files replaced and don't try these on a production system. Read any readme file before applying any changes. If your system is working well, and you have no problems addressed by these updates, do yourself a favour and don't mess with this. You have been warned. These testcase kernels contain fixes since xr_e002/xr_m015/mcp2/acp2. The UNI and SMP files are for WSeB/ACP/eCS Pro (SMP kernel) and the W4 files are for post FP15/MCP versions, including eComStation. Only use the SMP kernel on a machine with more then one CPU. Here are the latest changes in this version, as posted in the readme file. (See the Readme for a complete listing):] Bug Fixes: 04/16: Added test fix for trap 000e in _ldrSegFixAddIterRec - *May* have fixed some strange program load behavior with the implementation of the latest JR15038 fix. Fixes to problems that exist in released code: 0416 revision 14.089b PJ28541 sys0008 trying to start up lots of huge DLLs JR15038 new version: rather than slowing executable loads for everyone, I've gone back to using the faster stack-based buffer allocations most of the time. If you have loaded an ISS (security) or if you explicitly add "LDRSTACKOPT=TRUE" (No "SET ,,," please) to config.sys, we will try to minimize ring 0 stack usage by allocating buffers off the heap. This is slower, but prevents ring 0 trap 0008s in some cases. If you use TCPBEUI, particularly with the IBMTRP driver, you should probably add this parameter to config.sys. Following are rough instructions for applying the os2krnl fix: In the directory from which you boot (C:\ or d:\ or whatever), type these commands. Note that os2krnl should have come with this file. 1. attrib -r -s -h os2krnl 2. attrib -r -s -h os2ldr 3. copy os2krnl os2krnl.sav 4. copy os2ldr os2ldr.sav 5. copy \os2\system\trace\*.tdf \save (or wherever) 5. unzip -o xxx.zip If you want, you can turn the os2krnl and os2ldr attributes back on, but it's not necessary to do so. Trace files (*.tdf) have been included. An os2krnl.sym file has been provided with this fix. Just save it somewhere (root directory or anywhere). It is only needed in case OS/2 service requests a standalone dump of your system in the future. -- To unsubscribe yourself from this list, send the following message to majormajoratos2voice.org unsubscribe news end If you have an announcement you would like posted to the VOICE News list, please send it to submitatos2voice.org. Please include a valid reply address and a real contact name. If you wish to comment on this post, please reply to feedbackatos2voice.org