On Sun, 03 Feb 2002 15:40:56 -0700, Gregory J. Feig wrote: > no..!!...no..!!...let's not give up, yet...<g g g>...let us at least > discuss it a bit more...because I'm learning things about Arachne that > I never knew (or only half realized)....<g g g g> > ...so...SOME productive thought, here, will be useful...
Ask a specific question, and I'll see if I can (legally) give you the answer. > ......and............."Joerg Dietze" <[EMAIL PROTECTED]> wrote: >> as we all know, the existing 640kB are almost overloaded in most >> computers. Do You rember all the tricks to free up some byte more to get >> Arachne running? And if You look in mime.cfg, most plugins are running >> in 32bit protected mode already. I guess it's time to have a 32bit > -----^^^^^^^^^^^^^^^^^^^^^^^^^^^^--- >> core.exe, too. IMHO, this would help to get rid of the xSwap errors and >> the "Memory Monster", which is still alive in xSwap mem. Old 486 and >> Pentiums can be bought for a few bucks or saved from dump so I guess >> it's worth thinking of breaking support for XT's. > hmmmm...I didn't know THAT...!!!....good thing someone around here > knows what they are talking about...<g g g> No, only TWO plugins accessed thru mime.cfg use 32 bits, and therefore also require CWSDPMI. DJPEG32 and PNG2BMP are the culprits. This is Arachne 1.62. I don't think any others have been added in the standard distribution, but the PDF converter MAY also require CWSDPMI. > ....to be sure, MIME.CFG > has always thrown me for a loop....but I guess I'll have to get in > and DIG... Always willing to help, now that I finally have some idea what mime.cfg is, but I thought I had already spilled my guts on THAT. <G> - Clarence Verge - Back to using Arachne V1.62 ....
