NIM

I'm sorry that no one replied at your request for the sig, seems that Wolf is preety busy now since he'd probably do it. But I must admit that you made a quality sig, hope that your PS skills improved with this small tut :icon_cool:

Welcome to the forums :a056:

If anyone's interested it can be found HERE :thumbsup_anim:

Event ID 4226 Patcher Download LINK Notice: You should be a Windows Server license holder or this action is considered as illegal!!

I think that every provider in the world except T-Com has higher upload speeds. T-Com suks :nunchaku:

Glad you sorted this out bud :icon_cool:

Introduction to Stopping Processes with WMI If ever you wish to stop or terminate a Windows process, then this is the page for you. Before you begin killing processes, you may wish to list processes running on a the Windows Server 2003 or XP computer. Task Manager is a great utility to match the names of the programs with their processes, you would not want to inadvertently kill the wrong process! Scenario - Why you would want to Terminate a Process? Perhaps you wish to restart a process, if so, then obviously you need to stop the process before you can start it again. Before the WMI script, can stop the program you need to know the precise name of the corresponding program. One way to investigate the names would be to Launch Task Manager, select the Application tab, right click the Task and then choose, Go to Process. Examples of processes that you could terminate include, spoolsv.exe, outlook.exe. Another reason why you may wish to investigate, then kill processes is if a virus manages to launch itself as a process. Once you spot the impostor, then the next step is to create a WMI script, which terminates that virus \ process. Example 1 - WMI Script to Terminate a Process on the Local Machine The purpose of this script is to terminate a process on the local Windows machine. Think of this script as a preliminary script leading the main event in Example 2. Prerequisites for your WMI Script Run this script on Windows Server 2003 or XP. Naturally, if the named process does not exist, there is nothing for the script to terminate. Therefore, you need to start the process referenced on line 9, in my example this process (program) is calc.exe. Consider running my StartProcessScript first. Note the .terminate method does not work with NT 4.0 or Windows 9x machines. Instructions for Terminating a Process Copy and paste the example script below into notepad or a VBScript editor. Save the file with a .vbs extension, for example: ProcessKill.vbs Double click ProcessKill.vbs and check Task Manger, Application Tab. You may actually wish to start both Calc.exe and Task manager before your run the script. Option Explicit Dim objWMIService, objProcess, colProcess Dim strComputer, strProcessKill strComputer = "." strProcessKill = "'calc.exe'" Set objWMIService = GetObject("winmgmts:" _ & "{impersonationLevel=impersonate}!\\" _ & strComputer & "\root\cimv2") Set colProcess = objWMIService.ExecQuery _ ("Select * from Win32_Process Where Name = " & strProcessKill ) For Each objProcess in colProcess objProcess.Terminate() Next WSCript.Echo "Just killed process " & strProcessKill _ & " on " & strComputer WScript.Quit WMI Tutorial - Learning Points From a WMI perspective 1) This script builds on the basic WMI command in Example 1. The heart of the script is the Win32_Process. Once we have selected the strProcessKill, then we call for the .Terminate method to close the program without issuing any warning to the user. From a VBScript perspective 2) Study the VBScript syntax used just before the variable strProcessKill: ("Select * from Win32_Process Where Name = " & strProcessKill). For example, see where the speech marks end in relation to the bracket. 3) Although the script only terminates one process, it still has to loop through all the running processes to select the process = strProcessKill. For Each... In... Next handles this scripting structure. Example 2 - WMI Script to Terminate a Process on a Distant Machine This script builds on Example 1 and adds the ability to terminate a process on a remote machine. Prerequisites for your WMI Script Naturally, if the named process does not exist, there is nothing for the script to terminate. Therefore, you need to start the process referenced on line 9, in my example this process (program) is calc.exe. Note the .terminate method does not work with NT 4.0 or Windows 9x machines. Instructions for Terminating a Process Copy and paste the example script below into notepad or a VBScript editor. Save the file with a .vbs extension, for example: ProcessKill.vbs Double click ProcessKill.vbs and check processes in Task Manger, there should be no calc.exe. Option Explicit Dim objWMIService, objProcess, colProcess Dim strComputer, strProcessKill, strInput strProcessKill = "'calc.exe'" ' Input Box to get name of machine to run the process Do strComputer = (InputBox(" ComputerName to Run Script",_ "Computer Name")) If strComputer <> "" Then strInput = True If IsEmpty (sourcePC) Then WScript.Quit End if Loop until strInput = True Set objWMIService = GetObject("winmgmts:" _ & "{impersonationLevel=impersonate}!\\" _ & strComputer & "\root\cimv2") Set colProcess = objWMIService.ExecQuery _ ("Select * from Win32_Process Where Name = " & strProcessKill ) For Each objProcess in colProcess objProcess.Terminate() Next WSCript.Echo "Just killed process " & strProcessKill _ & " on " & strComputer WScript.Quit WMI Tutorial - Learning Points From a WMI perspective 1) This script builds on the basic WMI command in Example 1. The heart of the script is the Win32_Process. Once we have selected the strProcessKill, then we call for the .Terminate method to close the program without issuing any warning to the user. From a VBScript perspective 2) Study the VBScript syntax used just before the variable strProcessKill: ("Select * from Win32_Process Where Name = " & strProcessKill). For example, see where the speech marks end in relation to the bracket. 3) Although the script only terminates one process, it still has to loop through all the running processes to select the process = strProcessKill. For Each... In... Next handles this scripting structure.

Seems it's messed up preety much now. Can you do a system restore, so you revert to the state prior ACDSee installation?

You have probably choose ACDSee to be the default viewer for all the file types it can handle. Go to ACDSee options and look for file types or file associations. Deselect files you want not to be viewed with ACDSee. Next, choose the file type, double click it and during prompt select the new default viewer for that extension. Or you can right click on the file which you want to be viewed with another application, choose CHANGE for the "opens with" dialog menu and select the desired application. Hope this helps. :tumbleweed:

It also can be posted here, but OK, I'll check your post now :smiley_superman2:

So, will it stay on your words or should I create the forum so you can post your projects? :cool04:

LOL, welcome Yoshi, glad that you decided to join :thumb_yello:

Thanks for reporting this 999. This bug will be fixed in the new version of this skin. :thumb_yello:

Welcome to the forums Radeon.

Here http://www.wincert.net/forum/index.php?showforum=74 If it will be needed I'll create a subforum. :thumb_yello:

You can release your apps here so we can test 'em.. :thumb_yello:

I haven't tested it, you can try though. It should work IMO..

Think not, but it could be made easily by rick or gorki since it's only one .dll file.

LOOL, a sheep with a rocket launcher :thumbsup_anim:

Welcome to the board dopey, hope you'll stick around with us :welcome:

They've probably borrowed the code from Mozilla :whistle:

I would also like to add that MMC console isn't working as it should, at least it's snap-ins. By that I mean that Admin Pack 2003 suck on Vista. You can't use DHCP or SMS console for administration, I have to connect to the server instead. Some network printers won't work with Vista, for instance HP Color 2550. So you get preety frustrated when you constantly run into trouble with Vista. :sad01_anim:

Agreed, it looks very good. They worked on the new smilies also.. :thumb_yello: