T60 M52 No Execute Technology...Help

[RiverFly]

We discovered a problem with some of the new hardware; hoping someone can shed some light on it. We loaded our standard image onto the new hardware (M52 and T60) and discovered certain Windows applications would not run (e.g. Microsoft Management Console (mmc.exe) Task Manager (taskmgr.exe)). We also found some applications would simply shut down without warning (Outlook or Internet Explorer). In one instance, the M52 would sit at the Desktop for about two (2) minutes and then would simply shut down and restart. The Event Logs gave us no clue as to what was causing this behavior.
<skipping through all the details and getting to the bottom line …>
In the BIOS, there is a settings under Advanced ==> No Execute Technology. Apparently, this is something that integrates with the Data Execution Prevention (DEP) features of the Operating System. The setting is Enabled by default; changing it to "Disabled" makes the machine behave.
Although on the surface, this appears like a great solutions, when it comes time to roll out new hardware, it is highly unlikely we will want to have BIOS changes as part of the process.
I searched around the IBM/Lenovo web site for more information on this "No Execute Technology" feature, but didn't anything pertinent. Again, I'm hoping somone can shed some light on this or point us in the right direction.

[jdhurst]

Are you building your image with the machine you are loading it on? I am not sure what you mean by "loading your standard image on a T60". An image built on a T60 should load on other T60's without problem.

I did have a problem with an image build on a Netvista that would not run on the next batch of the same model/sub-model of Netvista. It was related to the hard drive signature. The vendor corrected the image (which was also backward compatible on the first batch) and the image loaded flawlessly.
... JD Hurst

[christopher_wolf]

We discovered a problem with some of the new hardware; hoping someone can shed some light on it. We loaded our standard image onto the new hardware (M52 and T60) and discovered certain Windows applications would not run (e.g. Microsoft Management Console (mmc.exe) Task Manager (taskmgr.exe)). We also found some applications would simply shut down without warning (Outlook or Internet Explorer). In one instance, the M52 would sit at the Desktop for about two (2) minutes and then would simply shut down and restart. The Event Logs gave us no clue as to what was causing this behavior.
<skipping through all the details and getting to the bottom line …>
In the BIOS, there is a settings under Advanced ==> No Execute Technology. Apparently, this is something that integrates with the Data Execution Prevention (DEP) features of the Operating System. The setting is Enabled by default; changing it to "Disabled" makes the machine behave.
Although on the surface, this appears like a great solutions, when it comes time to roll out new hardware, it is highly unlikely we will want to have BIOS changes as part of the process.
I searched around the IBM/Lenovo web site for more information on this "No Execute Technology" feature, but didn't anything pertinent. Again, I'm hoping somone can shed some light on this or point us in the right direction.

The No-execute bit is implemented by Intel on the boards that ship with certain chipsets. Granted, I have never seen it act up, but this doesn't come as a real shock to me.

Here is the Intel page on it....

http://www.intel.com/business/bss/infra ... /xdbit.htm

What OS are you running on them? If it is old enough and the applications themselves are new enough, it could throw exactly that kind of an error. It does indeed sounds like a controlled shut-down to me, so it can't just be a glaring incompatibility between the two.

[deforest]

I came across this issue as well when I migrated my t40 image to the t60p.

The boot.ini had /NoExecute=OptOut for the t40 and I found that for the t6 it needs to be removed (which would been equivalent to /NoExecute=OptIn )

When I looked at the windows that came preinstalled on the t60p, it is also was missing the /NoExecute flag, which makes me think that the OptOut option isn't compatabile.

I was using the latest version of xp sp2 with whatever the latest patch was, and all the new devices didn't have drivers yet loaded for them since I hadn't at that point installed their drivers.

I would find that the system would run for a while (about an hour) and eventually bsod on me (with, if I remember correctly, a stop 7E error). After removing the noexecute flag I haven't had a bsod since.

[jdhurst]

Doesn't this say one should build an image with the target computer? It takes a bit more time, but it seems to me there are fewer problems. ... JD Hurst

[archer6]

Doesn't this say one should build an image with the target computer? It takes a bit more time, but it seems to me there are fewer problems. ... JD Hurst

I completely agree. I was the first in my group to receive a T60 and I built a customized image for our needs. Then when the other T60s arrived, I simply put that image on their machines no problems whatsoever. Simply, fast, and reliable. Yes, it took some time to initially create the image on mine, however it saved hours in time wasted with problems that would have occured with the others.

[kulivontot]

sounds like a software issue to me. Check your OS settings.