IcemanND

I looking for a way via vbscript, wmi calls, api calls, somehow using M$ own security center, to detect if virus scan software of some kind is already installed on the machine. This is so that if a user runs one of our system security script that installs virusscan it either removes another version or verifies that the user knows what they have and that they keep it updated. Problem is that the virusscan manufacturers constantly change where they install to making it difficult to check for every possible version out there. The M$ Security Center seems to do a good job of this, but I have not been able to find a way to call it myself and get a result that would indicated that one is installed or not and is up to date or not. You can look for the NOTIFY.EXE which is launch if there is something wrong but it could be that the firewall is off, virusscan is missing, virusscan is out of dateor updates are turned off. Only slightly helpfull. Anyone have any great ideas. I've run out of search terms for google that might find me what I'm after, so I thought I would pick the collective brains here. Thanks in advance.

Click Tools -> Options -> View Tab -> Under Show group uncheck Picture Placeholders (bottom of second column) -> click ok

move your install folder out of the OEM tree so it doesn't get copied then in your batch search for the install folder on you cd, check the forums there are numerous ways to do it both batch lines and standalone apps. then create a variable containing your cd drive letter and modify your batch to run the installers from %CDDRIVE%\installs\xxxx\etc.\etc.\etc.

sounds like the permissions may be messed up in the registry for the keys you are trying to import. Right click on the key and select permissions and make sure you have full control rights.

sounds like you need to turn ACPI on in the bios. The either reinstall XP or replace the HAL.

They both still show up when I check the list on a clean xp sp2 machine. And Incroyable Hulk still has both listed in the hotfixes list. You may want to check again. I'd love it if they would replace these two updates.

well that little snippet seems to work as expected if I run it on my machine. Try putting a pause statement inside of the loop and immediatley following for testing purposes as see if that gives a better clue as to what is going on.

Here try this, replace 'ComputerName' and 'UserName' with the appropriate names and 'NewPassword' with the new password, if using a variable for the password then remove the double quotes also. Also don't change the case of the 'WinNT' or it won't work. Set objUser = GetObject("WinNT://ComputerName/UserName") objUser.SetPassword("NewPassword")

I know that MS checks out the forums because they told me to check out one of my own posts to solve a problem I was having with a hotfix that wouldn't integrate.

Windows 3.1 from 6 disks how about a windows 95 upgrade from I beleive it was 16 diskettes.

if you have a copy of the i386 folder on your hard drive then you have everything you need but the boot info on the cd if the entire folder was copied. Otherwise find a cd.

to change key after install: delete DigitalProductID value from registry HKLM\Software\Microsoft\office\xx.x\Registration Where xx.x is the version number of your office install 9.0= 2000 10.0= XP 11.0= 2003 Then launch an office application and it will ask for the product key.

You're talking about those 5 1/4 inch and 8 inch disks right. Seems like everyone I run into anymore calls the 3 1/2 inch floppies hard disks. I still have a 5 1/4 around here somewhere just incase some other old timer comes by and needs to get something off of one of those disks, happens about twice a year. Otherwise I put the 3 1/2 in the machine when I need it.

The power management settings in the Device manager are not controlled by the Dell Quickset utility, at least in my experience with my D810. Uncheck the box for allow computer to turn this device off to save power for both network devices. Also if he is only using the dock NIC turn the one off on the laptop. Sometimes XP is it's infinite stupidity will try using a non connected nic instead of the one with a live connection.

check the power management settings of the network card in the device manager. I've seen this kind of behavior where Windows turns the card off to save power and then is very slow or forgets entierly to turn it bakc on when it is needed.

open two textstreams, one for reading your existing file, one for writeing the modified data. then as you read each line write the line to the other file or modify/add and write it to the second file.

look for the error on the first page of the properties of cd or dvd from the device manager. Error will be listed in the Device Status window. May be something other than the erro 19 problem.

Just wat I needed. Another addictive game. 23372700 - 19 - 24 - 11:00:00

key the LowerFilters value in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E965-E325-11CE-BFC1-08002BE10318} Rename to oldLowerFilters, reboot and try the drive. If it works then either one of the files listed is missing or corrupted or conflicts with another filter.

lost count at 21 and I just got rid of three last night.

cd c:\temp del *.* for /F %%a in ('dir /ad /b') do rd /s /q %%a

use SETX or http://www.msfn.org/board/index.php?showtopic=38913&view=

what error do you get? The script in the post that the second link goes to is how I integrate all of my updates. Which include all but one of the updates you have listed in your first post.

I use integrate for all of those updates. But I believe kb886677 isn't needed anymore. Also there is a conflict between kb885250 and kb885835, see http://www.msfn.org/board/index.php?showtopic=38820 or http://www.msfn.org/board/index.php?showto...15entry279415

the next time you plug in your usb key go to disk management and set it to something other than D:. the next imte you plug it in it will get the assigned drive letter. Unfortunately you have to do this with every usb key you would plug in, since Windows doesn't consider a network drive to be using a drive letter.