Actual Tools
Forums list
New topics
Topics list
Search
Help
Login
Register

Messages 1 - 10 of 13
First | Prev. | 1 2 | Next | Last 

Topic: «Command Prompt Windows , V5.0 blue screens W2K3x64 » on forum: Technical Support   Views: 22083
 
Marc Salvatori
Registered user
 
 Posts: 33
Joined: 07/22/2007
Posted: 01/27/2008 13:24:49
 
 
 While this is only a minor issue for me (I would use it if it worked, but I can live without it), I thought I would let you know that W2K3x64 blue screens the moment I enable this feature.  Subsequent logins resulted in blue screens.  I was able to recover by remotely logging in, temporarily renaming ActualWindowManagerCenter.exe and running ActualWindowManagerConfig.exe to reverse this feature.  

On XP this feature works great!
 
Top
Michael Rezvanov
Administrator
-retired-
 
 Posts: 387
Joined: 01/31/2007
Posted: 01/28/2008 00:54:14
 
 
 Please provide us with the exact steps we should perform to reproduce the problem.
 
Top
Marc Salvatori
Registered user
 
 Posts: 33
Joined: 07/22/2007
Posted: 02/12/2008 00:38:01
 
 
 As Administrator of a W2K3 R2 x64 SP1 server, I performed the following steps to get a BSOD:
- Menu.Options
- Command Prompt Windows
- Enabled "Enable support of command prompt windows and console applications" and clicked the Apply button.  
- Between two and five seconds later I got the BSOD (not a great image, but legible).  
 
Top
Michael Rezvanov
Administrator
-retired-
 
 Posts: 387
Joined: 01/31/2007
Posted: 02/12/2008 22:51:08
 
 
 Marc,

Unfortunately we don't have a W2K3 R2 x64 SP1 testing machine. We will try to find access to this configuration.

Meanwhile:

- Do you have any anti-virus program, firewall etc. installed? Please name them.
- It would be great if you could try to reproduce the issue on another machine (of similar configuration): either just on 2003 or clean R2, if you have such an opportunity, of course.  
 
Top
Marc Salvatori
Registered user
 
 Posts: 33
Joined: 07/22/2007
Posted: 02/12/2008 23:42:35
 
 
 Unfortunately I neither have access to another 2003 nor a clean R2, Michael.  These are the malware applications I use:

- Tiny Firewall AMD64
- NOD32
- Ad-Watch 2007

I had disabled Tiny Firewall for AWM, but not the latter two.  Tiny Firewall is very pervasive (as it should be); so I always disable it initially when establishing trustworthy software.  NOD32 and Ad-Aware have never been a problem for me when installing or upgrading software.  Have they been problematic for AWM?  
 
Top
Michael Rezvanov
Administrator
-retired-
 
 Posts: 387
Joined: 01/31/2007
Posted: 02/13/2008 01:22:12
 
 
 Thanks for your prompt reply. We'll try to model the situation.
 
Top
Alexey Fadeyev
Administrator

Moderator
 
 Posts: 1427
Joined: 09/30/2005
Posted: 02/13/2008 01:45:37
 
 
 Marc, please specify the exact versions of mentioned software products.
 
Top
Marc Salvatori
Registered user
 
 Posts: 33
Joined: 07/22/2007
Posted: 02/13/2008 09:35:33
 
 
 Here they are, Alexey:  

Tiny Firewall:  v6.5.126
NOD32:  v2.70.32.00
Ad-Watch:  v7.00.02.05
 
Top
Alexey Fadeyev
Administrator

Moderator
 
 Posts: 1427
Joined: 09/30/2005
Posted: 02/14/2008 03:27:31
 
 
 Thank you, Marc. After a quick check, the bug is confirmed and the culprit seems to be Tiny Personal Firewall. We'll investigate this problem further and try to find a solution/workaround for it.
 
Top
Marc Salvatori
Registered user
 
 Posts: 33
Joined: 07/22/2007
Posted: 02/14/2008 10:03:36
 
 
 I will do some exploring of my own, Alexey, and will let you know if I make any progress . . . .
 
Top

Messages 1 - 10 of 13
First | Prev. | 1 2 | Next | Last 

User(s) reading this topic
Number of guests: 2, registered members: 0, in total hidden: 0
Forums list
New topics
Topics list
Search
Help
Login
Register



 
HomeProductsDownloadOrderContactsPress Map Privacy
Copyright © 2002-2024 Actual Tools. All rights reserved.

Windows and the Windows logo are trademarks of the Microsoft group of companies.