Draining resources after an hour

I give up on this one as well - we are not talking about conventional
memory that can be magically restored by RAM savers.
Are you saying you have a Win98 16 bit memory manager ?
Now that would be something !

 

Let me clarify that for you. When you have an OS like Win98 operating on Pentium chip, you're really talking about a 16-bit OS running on a 32-bit cpu. This 16-bit architecture goes back to the original Win3.x and there is a reason for that: it's called backward compatibility (in terms of software and also w/ the fact that the original Win OS could only access 16-bit registers in the BIOS). Without going into too much of a technical explanation (which I doubt you would bother to read anyway), I'll tell you that WinNT was created from the ground up. In essence it was not created w/ the limitation of this 16-bit legacy compatibility.

Now, Merlin, I don't appreciate you twisting my words to your liking. With ignorant-style questions like this, it really shows the utter lack of knowledge you have with computers. (and it also helps to quote people accurately).

 

OK Professer fill me in. Or lets clear something up.

I believe ( thought ) that all Windows starting with 95B ( OSR2 ) were capable of 32bit. Depending on how the USER set them up. ( I believe )

Plus I was just looking at System Info on a 98 SE machine.

It shows several items such as

Avgemc.exe--32bit app and also shows

Windows32------Win32sys
Windows16------Win16sys

Now unless I am wrong that machine with 98 SE IS RUNNING 32BIT.

This is on a machine with a AMD Duron Processor 1.2GHz.

So is it Windows or the CPU that determins whether it is in 16 or 32 bit.

BillyBob

 

With sarcastic comments like that, I neither have the inclination or time for your pathetics/debates which prove nothing to me other than that you lack a basic understanding of the Enlgish language.

According to Merlin's title he is a "Supergeek" so he might have the knowledge to fill you in.

 

If your looking for some reading to sleep by this should do it. The following is an excerpt ....

An important distinction between DOS and Windows applications is the size of a machine word. Intel designed the original 8086 opcodes with 16-bit computing in mind. As a result, they use a single bit to distinguish between 16-bit operands and 8-bit operands. Because one bit has two possible values, this forces the newer 32-bit processor mode to have only two operand sizes as well. 32-bit mode changes the meaning of the size bit to distinguish between 32-bit operands and 8-bit operands. As a result, the size of a "small" operand is 8 bits in both modes, but the size of a "large" operand depends on the mode. Under DOS, the CPU runs in legacy 16-bit mode. This means that the default size of a "large" operand is 16 bits. Windows, however, runs in 32-bit mode, making the default size of a "large" operand 32 bits. To keep things simple, this article uses the term "word" to mean the size of a large operand. If your application runs under DOS, a "word" is 16 bits, but if your application runs under Windows, a "word" is 32 bits.

 

Thank you Dennis L

BillyBob