svchost.exe is memory hog
o contrair Mr Wonderful - maybe you better study a tad more - Jason does
know what he's talking about - notice he said DOS based architecture - maybe
he should've added "pure" 32 bit kernel - yes Win95 operated with a 32bit
kernel however it was by no means the same kernel used today. In fact, the
win32 kernel was rarely used with 32bit .dlls
Remnants of real mode DOS code were still being used.
The shared memory address spaces (below 4MB, above 2GB) are almost
completely unprotected. Both Win16 and Win32 applications can scribble all
over sensitive system data areas.
The Win16Mutex in conjunction with badly behaved 16-bit tasks can affect the
overall system multitasking
KERNEL32 does in fact call KRNL386. Andrew Schulman proved this pretty
conclusively in Unauthorized Windows 95.
The Free System Resources calculation changed to make it look like Windows
95 has dramatically more USER and GDI heap space, even though it doesn't
Additions to 16-bit code were quietly made even though Microsoft publicly
stated that 32-bit code was the way to go
While Microsoft would like you to believe that there's one big happy Win32
API, internally the NT and Windows 95/98/ME teams don't communicate too
well. One result of this lack of coordination is that the number of Win32
functions available on both NT and Windows 95/98/ME suffered needlessly
Although Microsoft was strongly pushing everybody to move to Win32, much of
the underlying support for the Win32 APIs is in 16-bit code. That's no
secret, and not worth bringing up. However, Microsoft wasn't making much
noise about all the new API functions that were added to the 16-bit DLLs. In
many cases, these functions are 16-bit equivalents to documented Win32 APIs.
I'm talking about useful functions like CreateDirectory and
GetPrivateProfileSection. In some cases, these functions were silently added
to the 16- bit WINDOWS.H without fanfare. In other cases, the functions are
exported from the 16-bit DLL, but no prototype is given in the appropriate
You're a dunce if you think you've been running a 32bit OS since Win95 - and
I completely agree with Jason - trying to upgrade between the two different
architectures is a recipe for disaster - so go on giving your
Micro$oft-approved advice while the rest of us deal with the real world.
Paper-MS-MVP - what a joke - go back to your pub and have some some cheese
DOS based architecture to a 32 bit kernel - unless you want to be pulling
your hair out like the rest of the folks here - 90% of which could've
avoided most all of their problems if they would of done a clean install of
I regard that as quite unnecessary advice, and not relevant to the
present problem. There are very many upgraded systems, and you reveal
you r level of knowledge by speaking of DOS based and 32 bit kernel.
The essential kernel has been 32 bit since Win95
Alex Nichol MVP (DTS)
Bournemouth, U.K. Alex.Nic...@mvps.org
Check out:'How to make a good newsgroup post'at