DaveWI

Thanks, I figured, but had never done it. Removing from the domain now, and sealing the image for capture

hmm, following guides here making my hardware independent WIM image has worked fine, but so far all I have installed is things like firefox, gimp, and things like that, and it has been working fine. We've deployed numerous times without issue.

I have a proprietary piece of software I need to install in a base image, I don't think it is possible to do a silent install after imaging... Anyway this software can only be installed when the PC is a member of the domain because of login credentials to the database server. What would happen if I join the PC to a domain, install this software, then remove it from the domain, THEN sysprep? you think anything funny will happen to the OS? I'm not worried about the software, just the OS.

Here's the weird thing... The PC was / is in our firewalled network, with up to date anti-virus on it. It had never been on the internet except to download .net 3.5 (I had all other Microsoft hotfixes pre-downloaded). I KNOW it didn't have malicious code on it, it was just formatted a few days ago. Anyway, I borrowed a CD-ROM from an HP and formatted the hard drive, then installed Windows XP fresh... The "broken" DVD-ROM works perfectly now as far as I can test, and I didn't do anything physically to it.

Yeah I've seen that, but it wont boot either, F12 and choose CD-ROM and the BIOS acts like there is no media in the drive. sucks, I think the drive is going. It is an old Dell after all.

Check this out, I have a test machine I have been working on imaging with for a few weeks. I set it up as a baseline machine, captured a WIM image from it and deployed that image a bunch of times now. I even applied the image to the base machine in my testing (Via a DVD image). So anyway now I can't get it to read most CD-ROM's. It will read any DVD I can try just fine. For goofs I tried an old Acer monitor CD-ROM and it read it; I just can't get it to read any other CD's (including the original Dell restore CD). It is a TSST TS-H429C OEM code DE in a Dell Dimension 1100. I saw a firmware update for a different model number, and different OEM code, but nothing specific for this model. Anyone have anything like this, or know what may be the issue?

just an FYI, Norton (Symantec) uses StorageCraft's drivers, and base software to accomplish it's task. The fact they license the rights makes me lean towards StorageCraft, as they update their source code much more often, where Symantec uses the original code they licensed.

No problem, it didn't really seem to fit in any of the forums perfectly

Don't know if this is the best spot, but I figured it would get the most visibility... There's quite a few talented IT professionals here an I was looking for opinions on corporate server backup and disaster recovery solutions. We are a smaller company, with a limited budget. We have 12 servers, and are running Exchange 2003. I'm looking at a few professional solutions: Backup Exec (Symantec), Acronis Advanced Server, StorageCraft ShadowProtect, and Paragon Drive Backup. Does anyone here have experience using any of these? Any recommendations, or thoughts? Thanks in advance.

Hey Iceman, Thanks again for all the help. <EDIT> nevermind the question... HA!, I just happened to stumble on the above thread, it didn't come up in my searches, I was trying too technical of terms I guess lol.

Thank you for the reply... I only posted here because this seems to be the only reference to this Intel SATA driver issue I could find. I'm not using BartPE, I'm using Iceman's Windows PE deployment walk through. I'll check with him I guess.

I'm really sorry but I'd get in trouble at work probably if I read all 44 pages of this thread... Everything I saw so far is for an nlite made installation. What about deployment of WIM images using windows PE? Everything worked fine, but when I booted to XP finally I got the intro screen for a second, then BSOD. I traced the problem to this particular situation. It is a Dell box with this Intel chipset I am deploying too. Does anyone know a solution, or way to get XP to recognize the drive properly? If I just load the drivers into the image and edit the registry to point to the directory of the drivers will it work? Thanks all.

I'm new to this too... so please excuse me if I am giving poor advise. in the default i386 folder if you copied it from an XP cd I know there's a default winnt.si_ or something like that. is that file still there possiblly overwriting yours or being used in place? Also I see nothing regarding InstallFilesPath in the [unattended] section I don't know your source, or what your goal is, corporate, personal, but I can say I followed Ashley's to make my source (except did it on a live box), and Iceman's to make my PE ISO disk, and apart from some things my boss wants I am good to go.