Tripredacus

This is true of any file-based recovery. It isn't an issue with Imagex, but more with the method. Fortunately, if you wanted to run a restore of this nature, you can either remove the registry files from the WIM or put them into the exception list so they aren't captured in the first place. Of course if you have a corrupt registry you are stuck either way.

They do work with Vista. With the modified drivers everything works. Creative just doesn't want them to as they're trying to force a H/W upgrade to the X-Fi 2. @OP: Search for daniel_k drivers. Ah well sometimes I can't tell who here is trying to do stuff for work or for home. I have to do stuff following the rules so sometimes I forget that other people might not.

There are alternative processes, such as DHCP helpers. This type of function, I don't think, is included with Windows, but network management software (such as Altiris) can manage it. Say computers with "insert-variable-here" will receive IPs in this scope, and computers with "other-variable" will receive IPs from another scope. The variables could be DMI information (from the BIOS), computer name (trimmed) or any other bit of information that the computer can transmit. Or in an extreme case, use one scope for preliminary info and when the server determines what type of interface it is, will reassign an IP from one of the two other scopes. But perhaps a real question is, if both of these types of interfaces are on the same physical network, what is the true purpose of assigning them to different IP ranges?

The first part has been taken care of... now to just handle client machines. We can't take the time to put a CD into every machine. We move between 500-1000 machines a week. Using CDs is not an acceptable solution, as it not only takes time, but also keeps machines sitting in one place too long. Active monitoring is required. Also scanning offline hard-disks are not acceptable either since that doesn't take into account anything running in active-memory or at the start of the OS. But regarding the server itself... another thing we can't just take the drive out and scan it... It runs a 1.7TB RAID6

That's pretty weird. I am guessing that if you had used it, but not while playing games, that it may perhaps have some sleeper processes, or perhaps it has a memory hole/leak (like Firefox used to). That is definately an interesting issue and you should probably report it if possible.

I have heard this about VirtualBox. This isn't going to be something that NEEDS to be reliable... just something I did when bored at work. I haven't even done anything with this machine yet! The other day, after no more work for the day I think of something to do. Should I? a. write a program that reads exported XML from Oracle and copies software from a network share onto the hard drive? b. continue my ages-old project of writing a custom MBR to allow bootable hot-keys? c. install Windows NT on some old computer I found buried under a desk?

This is how I use Ghost: I have a Server (computer) that has the Ghost Server software installed. I make a session to "Dump from client" which will save the GHO (Ghost file) in a folder. It is connected to a LAN where the other computer is. I have a USB Key (UFD) that has the DOS version of the Ghost client, and have the applicable NDIS (Network driver for DOS) driver in the config.sys. I boot to the key and run Ghost. It gets an IP address and I type in the name of my Ghost session. It then sends the volume image up to the server using whatever compression type I choose. Of course you have other options with ghost, like you can clone one hard drive to another without being on a network. Or there are other options that I don't actually use.

Can you confirm that prior to running Sysprep that you can open IE and it is the newer version?

I think this series of cards does not even work with Vista. Does this device appear on the Hardware Certification List?

Is this to say that your Data LAN scope services more than 255 clients? Either way, try setting your DHCP lease time to a lower than default setting. I have always used 3 hours. I think the default is 8 days, but not sure.

The only place I have seen it is when you install the WDS Component. It asks you what mode you want to use it in, and Native is the default option. I don't know how you would switch it after the fact, but I am sure it must be possible.

Try checking out the Unattended XP section to see if there are similar problems there. http://www.msfn.org/board/Unattended-Windo...P-2003-f70.html

There are two reasons for this to occur, and yet both could be affecting you at the same time. The first is that there is a program that is running on your computer that is causing this issue. The second is that Windows is having difficulty ending a process or program (or multiple) on time, causing a delay. And you are likely telling it to restart before it reaches the total time-out allotment before it kills the service(s) altogether. Say if Windows has 50 processes running, and maybe the 3rd one is having a problem. So it has 30 seconds to finish closing before Windows ends it by force. Then maybe because Windows killed that process, the next one it gets to can't close within 30 seconds because a dependent process is not running anymore. For some reason when this happens it seems that Windows gets with the program if you tell it to shut down again and then it does it all real quick. Say also, for example there is a virus on the computer where the special permissions have been altered where the SYSTEM account doesn't have the authority to kill the process, a hang can occur. In Windows NT 4 there was a registry setting that you could change the default timeout for killing a process on a shutdown or restart, but I don't know what it is in XP. I think the second reboot command working thing is a newer feature, because older versions of Windows that had this problem (say NT 4) you could keep telling it to reboot until you were blue in the face if Windows was having a problem with a process or program.

This is common under situations where Group Policy or some other software limitation is enabled on a machine. If you change the screensaver to say, Marquee or My Pictures Slideshow, does this also happen? This can also happen if you incorrectly attempt to modify the registry regarding the screensaver. I did this to a machine when I tried to write a program that changed screensavers every 4 minutes.

I think this is a feature of Vista. One of these things to look into... I don't use Vista enough to know which it is. This may be caused by Shadow Copy using System Protection/System Protection Points. http://www.microsoft.com/windows/windows-v...hadow-copy.aspx

What changed a few days ago? Install any programs, download anything, update any software? update any drivers? hook up any hardware, stop using something or uninstall a program?

We have a file server that we learned is possible that it may be infected with a virus. This server is on a private LAN that does not have internet access. It is not connected to our domain, but we plan on putting a domain controller on it in the future. It runs Server 2003 Standard 64bit. Because it is not a part of our corporate domain, nor does it have access to it, we are unable (and at this time unwilling) to install our managed Anti-virus client (Trend Micro) on it. So I am in search for a freeware/trialware Anti-virus program that will install on this OS. I know AVGFree will not install. The ability to update it is not a concern right now as we just need something to hold us over until we put the domain controller in. Our future domain controller will run its own Trend Management Console. Also, I am interested in any Anti-virus server software (not an appliance, and can work with the above OS) that is capable of scanning network computers for viruses without installing any client software on them. This software does not require to be free, but should not involve purchasing a crazy amount of software, for example I know that Altiris has/had this capability. Thanks.

Sorry to bump an old topic, but I am also experiencing this problem and there are no other topics about it. In my particular case, I have 4 machines that I cannot install anything that uses an InstallShield installer. All 4 machines use the same image. This problem has likely been in the image since mid-August but we didn't catch it because we typically do not install programs into it. The reason I need to here is because we got a batch that includes a video card. I would like to try to resolve this as the image is provided by our customer and would add a considerable amount of time to our estimated ship date. This is a Windows XP Pro SP2 with all updates possible (critical) without installing Service Pack 3. I am going to leave out the hardware on this one as this does not affect the same hardware using different images. Possible solutions have been tried with no result: - rename/delete c:\program files\common files\installshield\professional\runtime\IsProBE.tlb - delete all files and folders in c:\documents and settings\%USERPROFILE%\Local Settings\Temp - full pass using Memtest x86 v3.3 (PASSED) Error being reported: InstallShield error -6006 Applications attempting to be installed: nVidia GeForce driver package 175.16 and 175.19, also nVidia driver located on CD-ROM that comes with the video card. Sources tried for Applications: Network Share, Desktop, CD-ROM Any other suggestions would be great. RESOLVED This issue was caused by a virus being installed in the image. It fortunately has not propogated to the rest of our network. One of the functions of the virus was to change file permissions and block write access to select folders. At least one of these folders was one in which the InstallShield Engine was attempting to write to, thus generating the error.

Is this a folder you created or part of Windows or from a program? If the folder is marked as a Protected System File, it can retain the hidden status even if you uncheck the Hidden box.

If they are infact .msi files, there should be a log for them under the source MSIInstaller, and it will write an event whether there was an error, or if it completed successfully. Are you able to install other programs on the computer at all? Is it only MSI files that are not installing?

Well I tried some stuff out but it turns out that NT 4 won't install on the computer at all. It complains about the APIC and HAL.DLL upon install... the hardware just might be too new. So I am going the Virtual PC route instead. Thanks for the info on Grub4Dos. It looks interesting. I might even use it on a VHD!

Take a look on their site for a firmware update. They usually add more features.

Check out your exclusions list, first off. Also there are some instances where Windows will hide the entries for the updates from Add/Remove Programs (or Programs and Features) but the actual program should still be there if you open IE, for example, and do the Help->About to see the version.

I am baffled as to why you registered for an account here to ask this question instead of doing so on the Asus forums... http://vip.asus.com/forum/default.aspx?SLanguage=en-us Their download site is here. I don't know what socket your motherboard has so I can't take you further. http://support.asus.com/download/download....SLanguage=en-us

Yes you need to set up your WDS in Mixed-Mode. It will then be able to call the setup.exe with whatever options you select and deploy from your distribution share. However, using a WIM isn't going to work, it isn't meant for unattended installs, only for creating drive images. You may have an option of capturing an XP Pro image, and then scripting sysprep to do the unattended work. I have no experience in this option. You can also use the WinPE to call the setup.exe from within the startnet.cmd, and you can point to an unattend file but you can't use a winbom.ini file.