We recently replaced an existing Windows Server 2000 with a Windows Server 2003. The server�s primary function is file/print in our development environment.
One of the directories is shared using NFS. All compiled software is kept in this share (we use C & C++). The generated �.out� and �.ndb� files range from 9.8Mb to 13.8Mb depending on the modifications we have made to the code base.
We connect to the NFS share from a machine running VxWorks (v5.4.2). Using �ld< file.out� or �ld<file.ndb� we load our builds into the VxWorks environment.
Here's our problem: Prior to the server change, we were able to load any �.out� or �.ndb� file regardless of size. Now we are only able to load files that are less than 10Mb. We've got two different machines running VxWorks and have seen the same issue with both. Nothing was changed on the VxWorks machines.
The actual error we are seeing is below:
Ld<file.out
0x1770c20 <tShell>: memPartAlloc: block too big - 9319988 in partition 0x1f62b4.
Could not allocate text and data segments
ld error: error reading file (errno = 0x3d0001).
So my questions:
- Has anyone seen this, and if you did, how did you correct it? (Rolling back to the old server is not an option because it failed catastrophically).
- Are there any settings in W2003 that need to be set/tweaked to correct this?
- Is there a compatibility issue between W2003 and VxWorks?
- Are there any parameters for the "ld" command in VxWorks that will help?