Tripredacus

I'm still waiting for the price to come down. Must still be a good seller since its still about $40 around here. Probably can find it cheaper online tho. I can't play it yet (still) so I haven't bothered looking.

Or another good example is I have a 120GB Maxtor ATA drive that I bought in 2001 that has been partitioned and still works fine! However perhaps the difference is that HDD's partitions are both for data. OS still on another physical drive. Its a "best practice" to have OS on a separate physical disk, and data on (an)other(s). Even better practice is separate physical drives on different controllers. Example, our Domain Controller has 2 drives on RAID1 on onboard controller for OS, and 8 drives on RAID10 on 3Ware card for data.

You may require one of the additional packages for the PE. I do not know which are already included in the Boot.wim. Try creating a WinPE 3.0 from the WAIK and running your program.

No, the OPK is only if you want to make your own install CDs with MCE on it. The package you bought should just be an install CD set. From the sounds of it, you may have bought something that looks like this: http://img.soft4share.com/files/pics/346/345697/img_1_pr.jpg Are both of these CDs have the hologram on them like in the picture?

By hologram, I mean the entire top of the CD is a hologram. Use this as an example: http://www.azcomputertech.com/images/authcd.jpg If not, what wording is on the CD? No company name like Dell, HP, Compaq, etc?

Check for BIOS POST Codes on the website/manual for the motherboard. Which board is it?

That is correct. The item you linked to is a security update to the redistributable package. You cannot redist the update, but you could redist the original package. Is there perhaps a newer version available that already contains that update? Edit: woops, I saw published date July 09.

You haven't mentioned what brand of PC it is. Also, the Windows CD that comes with it, is it a hologram disc?

In addition, computers may turn themselves off if they get too hot. Also, try boot just on battery (no AC hooked up) and also try booting with just AC hooked up and take the battery out.

Oh NOes!

Either reinstall the mouse software, or try a different mouse. If its an optical, try one with a ball, or if its USB, try a PS2 or Serial mouse. If it continues it isn't the mouse.

Rush - Tom Sawyer

Try adding options 6 and 3 as in the WDS guide in my sig.

You may either have a HAL or Mass Storage Driver conflict if you are deploying to different configs. The images made by WDS/Imagex aren't very big and I only have 1 image per motherboard, sans applications. To see why your client is rebooting, after deploy press F8 to get to the Statup Menu. Then choose Disable Automatic Restart on System Failure to see what error you are getting.

This is caused by stuck CTRL or SHIFT keys, or your mouse drivers being corrupted.

There is also the dreaded "Antivirus 2009" clones which do this AND disable Task Manager. The OP didn't mention whether or not Task Manager opened or not, only that it was tried.

When the client is booting up, use F8 to get to the boot menu. Select the "Disable automatic restart on system failure" and see what error you are getting.

67 needs to be "\boot\x86\wdsnbp.com" <-- notice the first slash. What you typed did not have that. I have not tested using relay servers and 2008, only 2003. I am not sure what difference there is between the two. Also I have not dealt with everything being on different subnets.

I only like the Apple Pro USB Keyboards. They last a while but you can't take them apart if you need to clean it.

Just inject the driver into your PE or WIM. You didn't say what PE version you are using, but there is a general rundown: Win PE 1.x = XP driver WinPE 2.x = Vista/2008 WinPE 3.0 = Vista/2008/7

You should pick the one you are most familiar with.

EDIT: I am not having a problem at all. Using your post link hxxp://www.msfn.org/board/index.php?s=&showtopic=137119&view=findpost&p=878576 on paste becomes: http://www.msfn.org/board/broken-links-forum-issue-t137119-pid-878576.html#entry878576 but copy the #10 gives this: http://www.msfn.org/board/broken-links-forum-issue-t137119-pid-878576.html&view=findpost and translates to http://www.msfn.org/board/broken-links-forum-issue-t137119-pid-884506.html#entry884506 Which is my post. OK I see what you are saying.

How are you deploying it? What are the clients, and what OS is the image of? What OS is on your server? Are you running native or mixed mode? We will need more information, such as any errors and a config example of the client.

I'll try to explain this the best I can. Basically, you are using a private network that has your 3 clients and 1 server. This network only has 1 point of entry, your modem. Then it goes to your router. Some modems have firewalls inside, or block certain ports (ISP perogative) but some are straight up pass through devices. We are not really going to get a good answer on what your modem is doing inside, so we will presume that it is a pass-through and doesn't block anything, and we will pretend that it doesn't exist. Now your point of entry into your LAN is your router. All security concerns are directed to that device ONLY. The reason for this is because your clients have a direct connection to the router AND the server, as opposed to your standard enterprise layouts. There are many different things you can do with your router to make it more or less secure. Another factor in the security of the router is, unfortunately, the price. A D-Link may well be fine for home use, but you wouldn't put one in a business. Using Windows ICF (Internet Connection Firewall) is fine for the clients (and the server if possible) on the LAN, but its use is only to protect the clients from each other. In almost all cases (configured properly) the router will block more ports than the ICF does, but it only blocks it on the outside edge, or the port that connects to the internet. Say for example your router is blocking port 21 (FTP), but ICF was set to allow port 21 on your clients. The following would then be true: 1. If you were on the road you could NOT connect to your server (at home) via FTP 2. If you were at home you COULD connect to your server via FTP So your standard setup will allow computers to talk freely on your private LAN, but restrict data coming in, and (sometimes) will restrict data going out.