Tripredacus

Has the op specified if this is a local file copy or a network one?

I haven't seen this message before but it might be from Windows Defender. Try to configure it and add your programs to the exceptions if possible. http://technet.microsoft.com/en-us/library/cc722071.aspx I haven't used Windows Defender myself, so hopefully that article will give you some ideas.

We are caught in a situation about putting too much extra effort into XP. Its the same reason we didn't adopt SP3 yet. We weren't supposed to be dealing with it anymore, with exception of approved images, because downgrade rights was supposed to end in January. Now its to July. Should I bother playing around with MDT for XP at this point? And after final preparations, testing and piloting would I only get to use it for 2-3 months if not less? I may look into it for Vista instead. I tried BDD but that never seemed to work properly for me.

Ug you leave the trails on huh. I hate those things. Makes it look horrible.

Also teeming increases the available bandwidth (- overhead) and doesn't actually increase your transfer rate. I've learned that the hard way.

First thing is to do a manual renew. Hopefully you will get another error than a DHCP timeout. If you do get a DHCP timeout, do an ipconfig -all and verify your MAC address (hardware address) is not all Fs. Also verify that the NIC shows up in there, and that you don't have any Network Bridges in Network Connections. Try this out 1. open your command prompt (cmd.exe) 2. type 'ipconfig -release'. Ignore what it says 3. type 'arp -d' and ignore what it says. 4. restart the computer 5. when it comes back up, go into your cmd.exe again 6. type 'ipconfig -all' and post what it says here. 7. type 'ipconfig -renew' and post what error it gives you. Also go into Network Connections and tell us what icons you have in there. Its not important to know if its firewalled, connected, etc. Results 1. If it says DHCP timeout, you may either have a failing NIC (not totally dead) or a corrupted TCP/IP stack 2. If you receive any other error, such as (but not limited to): "operation was attempted on an object that is not a socket" or "access denied" or "cannot find the file specified" these can be researched and resolved fairly quickly. 3. If your NIC is bridged with something, you will not get an IP. 4. If you have a cable or dsl modem, make sure to power it off after you release the ip and power it back on when you restart the computer.

The Wiki page states "two or more disks" for both but I don't see much point for raid1. RAID1 is supposed to be more reliable.

Also, I want to point out that your VEN_1274 = NOT CREATIVE. Creative is 1102. In DrivePacks DP_Sound_B_wnt5_x86-32_805\D\S\CR7\oem14.inf it has this device ID: %ES1371.DeviceDesc%=ES1371,PCI\VEN_1274&DEV_1371&SUBSYS_13711274 ; Concert AC97 PCI board So its actually Ensoniq. I imagine you bought this as an "OEM" product huh? I always buy retail for things like sound cards and video cards. But as you can see here: http://en.wikipedia.org/wiki/Ensoniq_AudioPCI Creative bought Ensoniq and still used some of their cards as budget or OEM items. OK so this explains the different vendor ID. That INF MIGHT install but It isn't designed for x64. Here are some other leads but these are just things I found while searching, no garauntee about them: http://www.download.com/Creative-Sound-Bla...0_4-107830.html You can keep going where I left off if you want. Not looking very promising. http://www.google.com/search?hl=en&q=E...art=20&sa=N

You could say that of a lot of companies, maybe even Microsoft? Nah Seagate (or anyone else) wouldn't do anything like that.

I hate it when OEMs sell machines with nVidia chipsets and then put an ATI card in there...

No, for some reason Vista gets a pass. Probably because of the generalize option for Sysprep. I'm kinda looking forward to when XP goes away because then I'm not going to have to deal with this. Its kinda silly tho, to think that Vista is the magic fix. After working with it for so long, I realise it has some of the same problems. But I hope they don't decide to not use Vista images because it takes even longer than an XP load if doing it by hand. Fortunately my boss is on my side. He says to just keep a lid on it because he realises it is also silly but he can't really do anything about it either.

I have done the following: Changed the background pic. You can see this a couple pages back, I uploaded them. Changed some functions for the buttons at the bottom. Removed Map Network drive, capture image, append image. I changed these to launch my own applications, one that Maps 2 network drives at once, kills mshta and relaunches the HTA again. I couldn't automate the reload button. I also have it launch programs to preinstall applications for Vista and XP. I have other things I'm going to change in the future that I haven't gotten to yet: - change the prompt after imaging complete to restart instead of shut down, and also have option for Restart or install programs instead of cancel. you seemed to have given up. I need another feature which I was going to do myself. When the DISKPART menu comes up (besides the complaint that I can't use the keyboard on that screen) I need another option. I come across some systems (notebooks) that have media drives that the WinPE makes the C drive, so the script doesn't work automatically because it can't assign Disk 0 a drive letter (its already taken). So I have to manually go into diskpart and reassign vol 1 drive letter to another letter before I can format the drive to C and start the image. So.... FEATURE REQUEST: add another radio button to the Diskpart pop-up that says "use custom diskpart.txt" file. You click that, browse to the file, select it and click proceed. So that way I can have a custom text file to do diskpart if I have to do one of those notebooks. I'm in a flux right now (business stuff) with imagex so I'm not sure what my future with it will be.

0x7B means that the mass storage driver in the image is unable to initialize the hard drives that it is booting off of. Make sure that you are deploying onto the same hard drive controller and same settings like RAID or AHCI, etc.

ALT+F4 isn't needed, you could just close the CMD box which will do the same thing. The problem is if you are booted into a PE and close that box you are basically done. You can't open a new one. So you'd have to reboot if you did this. imagex.exe doesn't have a GUI. If this was done (as I have done lol) you gotta reboot and start over. The taskkill (or you can even open taskmgr) is viable but only if you open a second command prompt in order to type that in. Since you execute imagex.exe via the first command prompt, you can't type anything else in until it is finished because it won't be back at the prompt yet.

If you use DISKPART, you can specify volumes, partitions or physical disks by their number. Use the LIST command to view those values before selecting them.

The safest way to run CHKDSK is via the Recovery Console, or boot to a Win PE of some sort and run it there. I believe you use CHKDSK /R for those cases, it will repair the file system if it can. The Full Scans are more known for destroying drives.

Check out this train of thought: http://forum.sysinternals.com/forum_posts.asp?TID=8786

You can do this with the Devcon app. Be warned, however, that (at least I have not determined how) Devcon has problems installing multi-state drivers. In other words, say you have an "unknown device" and then you install the driver and then you have one or two more devices that appear after. I had this problem when trying to use Devcon to install 2 Port Serial cards, where it would install the driver for the first port but fail on the second. You can also look into using Drive Forge as well.

I'm stuck in a situation that I thought got resolved but it really hasn't. I just haven't heard anything about it in a while. What it comes down to is fighting against the ideas and lessons of the past, and that decisions were made at some point, accepted and never revisited. And say it turns out there is a better way, how hard should someone fight to be heard about them? Sometime in the past at my company, they used images for computers. Then things started going wrong and it was decided to not use images anymore. I came into this job during this "no images" period, and also from another company (or so say a much larger and successful company) that did use images and they knew how to use them properly. So when I got hired, the software people are still running around with floppy disks and CDs! They do use Ghost but only for temporary purposes. I see this as an opportunity to make everything more efficient. I write software to eliminate the use of the floppy disks (BIOS updates and Ghost, etc) and start making drive images. Everything goes fine until a customer complains. So it comes back to how we're not supposed to be using images for X reasons. So we stop using images and of course production time increases dramatically. I start to rethink the process and research why we aren't using images. The reasons were HALs and memory timings. I researched many things including Imagex. I could not, however, find ANY issue with using images and memory timings so I threw out that idea. Then my company says "we need to start using Imagex". So I get the server up and running, building our custom Win PE for the network boot and start making images. Except I am taking into account the HAL issue so that won't crop up again. I am also not just making an image and letting it rot up there, which was probably the reason they had problems before. I keep track of everything and if there is an issue that arises during our hardware eval process, or at any other time, I correct the image and replace the bad one. Image maintenance yes? So we had a problem with a driver on a new board, but it got out before we caught it. So the guy who does the evals, and the XP unattended fixes the installer so this won't happen. I find out about it, and fix the image for it and everything is going fine again. Then he finds out we are using images (again) and goes to complain about it. So now we can't use images anymore. It doesn't matter if everything is maintained and checked and updated. And all the work that my company had me go through to implement Imagex, its come down to us not wanting to use it now? What did they think Imagex was? It uses images! So I'm in a situation where we are going backwards again. And I had gotten some systems down to a total deployment time of 10-20 minutes. Now those same systems are up to a 2+ hours to deploy completely. How is it going to look when suddenly I can't handle the work load anymore? I really want to talk to someone about this but I'm up against a guy who's been here for years, and doesn't ever try to work with me on this issue. Its just "this is how it is" and brings no proof or research. It's down to his word against my word + research and proof of my concepts. Its not enough and I'm not sure how to handle the situation.

Forunately the one the other day was just an internal audit. I got everything right except for what was in that binder. You are right about that tho, what it says for my job is pretty basic. It was so basic I couldn't think of it. I figured it would be more in depth.

Its also the architecture detection of the WDSNBP detects most things as 64bit because its seeing the CPU. Very few 32bit CPUs nowadays, so WDS always tries to boot the x64 option. I just hardcoded the 32bit bootpath into the 64bit field to handle that situation.

That's what Microsoft is thinking right now. We're going to send them a demo unit so they can debug the process. I'm not really in the mood to put in a code change like the loop just for these 3 boards.

I'm pretty sure you can Ctrl+C it... You'll lose your partially created WIM tho after you close it.

I'd like to try it out I suppose. I've made so many changes to the current version that it wouldn't be worth it to update to the newer version. Hope you don't mind I've been kinda advertising this thread in my sig. I did it more so I would be able to find it if I needed it.

One old post deserves another. While it is probably in driver packs, Google finds it also. http://www.google.com/#hl=en&q=p35+158...;fp=3WTwdsC3GPc