Lock Pages in Memory X64 server

Hi, I have two x64 clusters, both have 8 GB of memory. Both the servers have lock pages in memory for sql server service account.This KB article
http://support.microsoft.com/kb/907877 says in the output of DBCC memorystatus
AWE allocated :value shows the overall amount of memory that locked pages consume on the 64-bit version of the product.
But when i run the DBCC Memorystatus , on one of the box i am getting some value for AWE allocated. the other Box i am getting AWE Allocated = 0 all the time. I was wondering is there any reason why its not using the AWE memory even though the Lock Pages in Memory is set for both the boxes?
It will be great if someone help me understand the reason for this behaviour:
Thanks
Jay
Results BOX 1:Memory Manager KB
------------------------------ --------------------
VM Reserved 6373368
VM Committed 62232
AWE Allocated 434176
Reserved Memory 1024
Reserved Memory In Use 0
(5 row(s) affected)
Memory node Id = 0 KB
------------------------------ --------------------
VM Reserved 6367608
VM Committed 56560
AWE Allocated 434176
MultiPage Allocator 30456
SinglePage Allocator 243672
BOX 2:Memory Manager KB
------------------------------ --------------------
VM Reserved 8472184
VM Committed 6455504
AWE Allocated 0
Reserved Memory 1024
Reserved Memory In Use 0
(5 row(s) affected)
Memory node Id = 0 KB
------------------------------ --------------------
VM Reserved 8466424
VM Committed 6449832
AWE Allocated 0
MultiPage Allocator 29632
SinglePage Allocator 99976

i dont get any error messages

Its running windows 2003 sp1, and sql 2005 Standard Edition 9.00.3152 (x64)
Thanks
Jay

So does the Lock Pages in Memory just ignored in SQL Server Standard Edition? coz one of my boxes is Enterprise Edition and other is Standard Edition. The DBCC MEMORYSTATUS returns 0 for AWE Allocated in the Standard Edition Box and not in the EE box.
Thanks
Jay

Yes you cant sat Lock Page in Memory for SE