IcemanND

see other post. only need to post once.

$oem$ |------$1 |------Drivers |------IntelVGA |------BroadComNIC |------SoundMaxSound OemPnPDriversPath = "\Drivers;\Drivers\IntelVGA;\Drivers\BroadCom;\Drivers\SoundMaxSound"

echo off for %%U in (kb*.exe) do ( echo Applying hotfix %%U start /wait %%U /q /norestart /nobackup ) pause put all of your updates in the same folder as the above CMD script and run. if you don't want to rename your updates change the KB*.exe to *.exe if you want to be able to uninstall them remove the /nobackup switch.

If you are using XP pro, not Home you cna tyr this to delete the files, it won't tell you what was using them if anything but if they were their own app it usually works to get rid of them. Turn off 'Simple File sharing' find file, display properties and click on security tab. Remove all groups and users listed and click ok repeat for all offending files. Reboot system in safe mode. repeat above process except give only the logged in user full control permissions. click ok then delete the file repeat for all of the files.

Some are already made, RyanVM has his update pack there's an app out ther called autopatcher. probably more, otherwise you'd need to extract all of the files and registry settings from each and evey patch you are installing and manually combine them, there is nothing from M$ that will do it.

@ladude626 - Did you bother to read his original post? or any subsequent posts?

Well, I'll state the obviousand most common error. make sure your winnt.sif file is winnt.sif not winnt.sif.txt

Use ghost and deploy it to a hard drive just like you were putting it on one of your production machines. Then rather than booting from the drive boot from a bart pe cd and make your changes. Then recapture. It could also be possible to put it on a secondary drive and make your changes and then recapture it but I've never tried that with a bootable volume.

to my knowledge the only way to edit an NTFS Ghost image is to drop it to a drive, edit it and then recapure it.

try downloading dial-a-fix from djlizard.net and use the WU/WUAU to fix windows update. It will reregister all the associated dll's flush the update software cache and stop and restart the appropriate services.

If it only happens in word, maybe a possible macro virus? If it happens in other apps maybe a stuck key?

I can't quite compare apples to apples as I no longer have a copy of office 200, but in 2003 when I base the report on a query the data is displayed on the repaort just as it is in the query. I can think of no reason why 2000 would have been any diferent, except that this is Microsoft we are talking about.

Can't do it from a cd which has an answer file or anything other than just the SP and integratable hotfixes.

The HAL is what matters, you should not have a problem going from the old system to the new most likely the old one was a ACPI Uniprocessor and the new one is an ACPI Muliprocessor. The issue will more likely be the HDD controller. Lie i said earlier if it's not boot just do the repair as Sonic described. Should be fine it will reinstall the HDD controller drivers for the new motherboard. Then you will need to install the HW drivers for the other hardware not already on the disk.

if you used sysprep on the images before you captured them and added the hdd drivers using sysprep then you can just create a large enough virtual disk and drop your image into the vm. You also need to ave compatiable HAL's though that is not as critical to the VM as it is to a real system. You can also do this in reverse, capture your vm with ghost and deply it to a rela machine. just be sure to have the ide controllers and a compatible HAL installed.

The problem is I have to redo the group names on the shares, preferably put the new group names on the existing server, then disable or delete the existing groups so that we can test. Once the new groups are in place I can use robocopy to copy the current data and security permissions from one server to the other without a problem. The issue is that there are over 400 folders and probably close to 200 different combinations of folder permissions within that. I'd much rather script it than do it by hand.

You would have needed to run sysprep on the drive before you got rid of it. Good news is that if it doesn't boot you should only need to do a repair, you don't normally have to do a full reinstall.

try this: http://support.microsoft.com/kb/156669/en-us

that should work

Or try this and you can keep it updated yourself http://www.msfn.org/board/index.php?act=ST...=70&t=74452

glad to hear it. I have no idea I copied and pasted your post and it wrked when I changed my spreadsheets to match. some single quote must have been wrong or something.

with the exception of your sql statement which may be right depending upon how you formatted the 'control number' and 'quantity' fields in your database it works just fine for me as is. If 'control number' and 'quantity' are number fields in your database and not test fields you need to remove the single quote from around their values in the sql query line. My only thought is if there is something wrong with WMI, or some kind of restriction on WMI calls on the machine you are using. Try it on another system and see if it works. Another thought, what are you using to write the script in? Notepad, wordpad, msword?

watch the leds do they come on and stay on or flash in a pattern or do the leds do nothing at all? watch the caps lock, scroll lock, num lock, power and hdd led. also note the color.

As I recall the 4150 use the LED codes, but I can't find either LED or Beep code list on Dell web site for that model. If it is LED codes the capslock, numlock and scrol lock leds will continously flash. At least that is what happens on other model I have worked on.

it depends upon the manufacturer. Some will have beep codes other will use the caps lock, num lock, power and hdd leds for diagnostics.