<div>
That was a quiet question! &nbsp;Thanks for the points..
</div>


That was a quiet question!  Thanks for the points..

<div>
<div class="content wysiwyg-content">
I am looking at device manager, network card propery, resource tab.<br />
<br />
1)I assume that memory range is the physical memory that the driver is loaded up in (Network Card property, Resource Tab)? &nbsp; (yes or no). &nbsp;<br />
2) It says FFDFFF80 - FFDFFFFF as the memory range of my network card. &nbsp;Does each address represent 32 bits on a 32 bit machine (yes or no), and 64 bits on a 64 bit machine? <br />
3) So if a software is written as a 32 bit software, you would actually be WASTING memory when running on a 64 bit machine (yes or no)?<br />

</div>
</div>


I am looking at device manager, network card propery, resource tab.

1)I assume that memory range is the physical memory that the driver is loaded up in (Network Card property, Resource Tab)?   (yes or no).  
2) It says FFDFFF80 - FFDFFFFF as the memory range of my network card.  Does each address represent 32 bits on a 32 bit machine (yes or no), and 64 bits on a 64 bit machine? 
3) So if a software is written as a 32 bit software, you would actually be WASTING memory when running on a 64 bit machine (yes or no)?


Memory, Machines, and software....

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).