Tripredacus

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

We got our first copy of Symantec Norton Antivirus 2009 1-Year OEM CTO SYSTEM BUILDER EDITION in and there are some issues I have with it. Unlike previous versions it requires a CD Key on install. It still has its 15 day warning on the package, but I can't figure out how to install it. The older (2008 and so) did not ask for a key and would install and (I guess) just work for 15 days. Anyone try this one yet? I figure I'd ask here while I am waiting to get our support contact's info.

Are you not using WSIM to make your XP install? I'm guessing that you are doing a network boot to the bootmgr off the server and want the XP image to appear there is that correct? Or does it and it is not installing? There is a thread about using WinPE to install XP unattended, so you may be able to boot into that first. http://www.msfn.org/board/index.php?showtopic=88270

If you hard code this option for 2 CD Drives having the same volume ID, you am going on the presumtion that this will work on every system. There may be times when the Hard Drive is not formatted yet and that is going to throw off your numbering. Also some machines see Memory Slots or Card Readers as being volumes even if there is nothing inserted. The MSI MS-163K does this and it screwed up my scripts as well. You may be able to have a script that detects the number of CD Drives, and runs diskpart_script1 if one drive and diskpart_script2 if two drives. AutoIT has a function called DriveGetDrive. Here is an example: $var = DriveGetDrive( "cdrom" ) If $var[0] = 2 Then Run( @ComSpec & " /c x:\windows\system32\diskpart.exe diskpart_script2.txt" ) ElseIf $var[0] = 1 Then Run( @ComSpec & " /c x:\windows\system32\diskpart.exe diskpart_script1.txt" ) EndIf This is an example, and i wrote this up real quick so I didn't test it. As the help file says, "The zeroth array element contains the number of drives".

I have used HFSLIP before. Maybe it will help you too. http://hfslip.org/ I also was able to put SP3 into a recovery CD with this!

They may require that Windows be activated first. We have some like that, like IE updates will refuse to install if the computer isn't activated.

The speed issue on the 2003 was fixed by manually setting the NIC speed in Device Manager. Even at this point, the 2003 WDS runs slightly faster than the 2008 WDS, but it isn't used enough to bother with it much anymore. Its more of a test bed for me now.

Now that you mention it... IIRC, the serial number was relevant to the date of manufacture, if that helps at all. You could read that date, and the other numbers or letters could be decoded to determine if it was a retail, oem or refurb unit, also which plant it was made in and what country, or what country it was made to be sold in. This knowledge is only of the printed serial number, however. But like I said, repairs/reman/refurb units could have different hardware inside that wouldn't always match the serial number on the casing. Like if it was a bad casing and didn't replace the internals.

Well today I was informed that I will be one of two auditees for my company when ISO recertification comes around again. Has anyone been in this position? Should I be worried about it?

I hate that you can do this. I found out about this ability when researching Conflicker.

I've seen CHKDSK actually destroy hard drives.

I don't think that the serial number is programmed into the firmware. I used to work for Iomega and know that it definately wouldn't be for remanufactured drives. In some cases, if all internal components were busted and they would be replaced but if the casing was still ok, they would just relabel (or sometimes they wouldn't) the serial number. There may be newer software able to read more info off the drives, but when I was there (2000-2001) there was nothing to get that type of info out of it.

Erm do you mean Vista Business? You may be able to use the User State Migration Tool. It is designed for mass migrations but I am sure you can do it for just one account. http://technet.microsoft.com/en-us/library/cc722032.aspx I haven't used it before, just read about it in the Resource Kit, and I remember it being on an MCP test.

I have a standard Samsung T-Mobile cell phone and it has a camera. I think you can play music on it and use a memory card but I don't know. I'm actually an AT&T customer so the phone is pretty limited as well.

Cool. I'll keep that in mind for the future. I've also found a way to search the Indexing Service. Its in Computer Management. I tried it on a machine Audit mode so it didn't work. I'll have to remember to check on a sysprepped XP also.

There was a recently reported issue of Spybot doing this to systems. Did you happen to have installed that at all?

You can also use a WinPE or NTFSDOS to view NTFS volumes. WinPE follows NTFS permissions while NTFSDOS doesn't. So I use NTFSDOS to reattribute, move or delete files otherwise inaccessible.

Both of these DLLs are noted on Prevx site as possibly being associated with malware.

I'm never ashamed to have owned anything really.

This McAfee install, for now I just have it scripted to be pushed and then executed on a reboot for now. Its causing me issues because once it gets installed, it stops the script from working.... so it ends up in a constant reboot loop...

We have the latest drivers. So far we've done NetMon traces on working and non-working boards but have yet to find the issue. However, the issue of losing access to network drives after the image was deployed was fixed. It was a coding issue I had not noticed. Now the issue is only that there are errors initially upon trying to map the drives via startnet.cmd.