Text 131, 90 rader
Skriven 2006-06-01 06:34:56 av Mike Luther (1:117/3001.0)
    Kommentar till text 130 av Peter Knapper (3:772/1.10)
Ärende: Some questions
======================
Slight comment Peter ..

 PK> It all comes down to HOW you start things up. I do NOT 
 PK> use the STARTUP Folder, I start everything using 
 PK> STARTUP.CMD and a little utility called SLEEP2, that 
 PK> allows me to set pauses of 1 to nn seconds between 
 PK> items in the file.

You'll have to check the Norman resources and discussion group to really get a
handle on this, but one of the really big buglets that was 'fixed' in the
Norman virus operations involves the above.  If my memory is correct, one of
the major things you cannot do with Norman for OS/2 is to use STARTUP.CMD to
fire off NYMSE.EXE as they originally did with their autoinstall and setup
work.

This last major version change to 5.8 moved the loading sequence for the Norman
virus control product so that a portion of the needed tools is called up in the
CONFIG.SYS file.  Then, instead of using STARTUP.CMD to work with things, they
absolutely have to load the needed tools in the STARTUP folder.  As well,
unless I've got it wrong, and you are using the Norman server for some
debugging work, in addition to this, you cannot use the PROCDUMP operations to
get debugging short form system dumps for SYS errors unless the Norman server
load for that comes in the STARTUP.CMD operation with the NYMSE.EXE in the
STARTUP folder.

As well, because of the required sequencing of the virus tools, I think that
certain other things have to be in the STARTUP folder, and cannot be in the
STARTUP.CMD operation.  There was a pretty large rumble about all this back
late last year during the move from version 5.7 to 5.8. As well, in the IBM
Thinkpad laptops, where the very last uppermost 2K of the DOS operating system
object's code is still wrongly used to let you enable the additional some 100K
of extra DOS memory and even EMS in most all of the later IBM Thinkpads, Viet's
blessed little patch utility PMTPOS2 has to be in the STARTUP folder as well
and not STARTUP.CMD.

With it I can now still use the option in DOS-VDM sessions to get back the 629K
DOS main memory and full use of EMS with DOS CGA lower level or MONO memory
settings in the DOS-VDM session setting options.  This covers every IBM R40,
R51 and T43 ThinkPad I've ever had here for use as far as I can see.

Another tool that at least to me is absolutely needed with the Mozilla or
Seamonkey browsers for OS/2 is the proxy server PRIVOXY.  In order to feather
it 'properly' with Norman and so on, it has to go in the STARTUP folder and not
in STARTUP.CMD, if my research on it is correct, or it has to be started after
the Desktop is up and running.  If you load it in STARTUP.CMD, here it creates
a lot more 100% CPU jamup incidents over days and days of browser fireups and
shutdowns.  I do NOT leave any of the browsers up and running, but fire one up,
do my work, and shut it down due to the long saga about memory leaks, Java
episodes, and whatever.  There are still far too many jamups in the proxy
server world for the OS/2 browser operations here that I see.  And firing
PRIVOXY up in STARTUP.CMD is one sure way I've found to escallate the CPU max
outs.

In my R40 ThinkPad is the Network Messaging, Norman Program Manager,PMTPOS2,
Privoxy and TCP/IP Startup for this MCP2 latest everything laptop.  In the
STARTUP.CMD file is still NET START REQ with the error level vector call to
lserr.exe and that's all.

If you are using Norman's system error dump tools, in STARTUP.CMD will also be
pair of lines like:

   PROCDUMP SET /PROC:NVCSRV2.EXE
   PROCDUMP ON /L:d:\norman

    or oriented toward whatever drive you special dump collection is in.

With the new world of on-access and on-demand inspection of what is now also a
part of OS/2 in relation to Java applications per what I think I understand ..
the idea of STARTUP.CMD has to be thought about differently.  Thus how Norman
needs to fire off and in relation to what per the way they designed the
toolset, as I understand things, has changed the way the sun rises in the world
of OS/2 as well.

Your mileage may vary..  I can't understand all this but I try.  And the worst
part of this is that if the user has already moved everything into the
STARTUP.CMD folder, the Norman setup game doesn't tell you anything about how
you are going to get strangely flushed down the louve, laddie.

 ;(


--> Sleep well; OS/2's still awake! ;)

Mike @ 1:117/3001




--- Maximus/2 3.01
 * Origin: Ziplog Public Port (1:117/3001)