DEP - Again (OpenInsight 32-Bit)
At 13 FEB 2006 12:35:34AM Dana Corson wrote:
A while back we had a server that had the hardware DEP and 7.01 did not run. We adjusted and when we tried to move this weekend to 7.2, it did not work. We did removed the old items from the list and re-added the new .exe files after the upgrade.
Any one have any ideas?
Thanks
Dana
At 13 FEB 2006 01:32PM Jeff Warvel wrote:
make sure you point the new entries to the exact location of the .exe (ie. c:\oi\oinsight.exe)
we had to put entries in for each possible location (drive : path) from where we started OI.
At 13 FEB 2006 01:57PM Dana Corson wrote:
Yes, we did that. Removed the old ones, and added the new ones. The DEP is able to sense that they are not the same things.
I am waiting to see if we can just have the DEP turned off in the boot.ini file, and then see what happens.
Interestingly enough, the OENGINE.EXE can start itself up, but oinsight and netdrv etc won't start.
I have tried removing the oinsight.ini file from C:\windows and when I attempt a restart, it has not gotten far enought to create that file.
Thanks
Dana
At 13 FEB 2006 09:00PM Warren Auyong wrote:
Are the "Start-in" properties set properly for the shortcut?
At 14 FEB 2006 11:26AM Dana Corson wrote:
Yes, and it won't start from the DOS prompt either.
They did not alter the boot.ini file to explicitly not use the hardware DEP to see if there is a difference.
Thanks
Dana
At 15 FEB 2006 05:58AM Bill Caisley wrote:
Dana
Have you managed to resolve this problem?
At 16 FEB 2006 02:07PM Dana Corson wrote:
Yes, I had asked that they remove the DEP functionality by changing the boot.ini file for always off / noexecute last Monday.
yesterday they did that after attempting a couple of other options in the .ini file. So after the re-boot this morning that allowed us to launch the application.
So unless something else crops up, I think that it is running.
Thanks
Dana
At 20 FEB 2006 01:51PM Mike Ruane wrote:
I'm leaning to the side that this is a hardware DEP issue, but we are investigating it as it has popped up again.
We'll need to get a new machine or two at the office that have and support hardware DEP; I don't think we have any. The hardware DEP has only been around a short time - http://support.microsoft.com/kb/912923
Thanks
At 14 MAR 2006 01:26PM Ryan Roux wrote:
We have a new Dell PowerEdge 1850 that is running the OI client. It has 2 of the new Xeon's in it with hardware DEP. The server is actually running a shortcut to the OI server. I have tried three of the following options - all with no success.
-Turn on DEP for eseential Windows programs and services only
-Turn on DEP for all programs and services except those I select:
OpenInsight (I added G:\revsoft\OI70\Oinsight.exe)-Edited boot.ini:
boot loader
timeout=30
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
operating systems
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS=Windows Server 2003, Standard" /fastdetect /NoExecute=AlwaysOff
Does anyone have any ideas? I saw that Mike said they were working on it.
At 14 MAR 2006 02:35PM Ray Chan wrote:
We have one client site that we cannot fully upgrade to OI7.2.1. They too have a Dell server running Windows 2003. The are using the Universal Lite.
Based on our experience, we believe that something happened in OI7.11. For example, the client was running fine at OI7.01. When we upgraded them to OI7.1, they were fine. However, after OI7.11, we get this:
I have tried the other two things that you have done without success. I haven't yet figured how to edit the boot.ini based on the Microsoft documentation using bootcfg.exe. How did you edit it?
When you look at the Microsoft documentation, reference is made to contact your software vendor to make its software DEP compatible. Is this like the bird flu where it may be spreading and we really need to start worrying about it.
I would like to see this resolved so I can go back to having fun with OI.
Down with DEP!
Ray Chan
At 14 MAR 2006 02:55PM Ryan Roux wrote:
That is the exact error that I am getting, but we are running 7.2 (which I forgot to mention in my first post). Editing the boot.ini file is the easiest part.
see this MS KB article.
http://support.microsoft.com/default.aspx?scid=kb;en-us;311578&sd=tech
It says it's for Windows 2000, but the same procedure applies to 2003.
At 14 MAR 2006 05:37PM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
We have been able to get around this problem but regretfully at this stage only by site visit. We're hoping to try and document the solutions we have found at some stage but (as is frequently the case with consultancies) we're a little busy at the moment.
World leaders in all things RevSoft
At 15 MAR 2006 01:55PM Warren Auyong wrote:
What happens if you disable DEP in the BIOS setup?
At 15 MAR 2006 06:12PM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
Would you like to drop us a mail - we can make some suggestions.
World leaders in all things RevSoft
At 17 MAR 2006 03:01PM ryan roux wrote:
On these servers, there is not an option to disable DEP in the BIOS.
At 17 MAR 2006 03:18PM ryan roux wrote:
I uninstalled Windows 2003 SP1 and it's working. That was definately the problem. Once I removed SP1, the DEP option is gone in System\Advanced\Performance\Settings.