InTheWayBoy

If you've already copied the files to the HD, then why not call setup from within WinPE? As I understand, it would start the installation, and when it reboots it goes into the next part of the setup.

Yeah, I don't know why they cripple it for servers...most applications like to do that. They used to have a product called ServerMagic, which was basically PartitionMagic for Servers. Of course, they charged a nice premiuim for it As for the topic, your best bet would be to look into making an image of the Server install, back that up to CD/DVD, then erase and repartition as you want. Then you can reload the image to the first partition, and everything should be good to go. I wonder, I've never imaged a Server...will Ghost complain about it being Server? I hope not...

I forgot about that...but even before that, they don't allow an upgrade from Win98 or Win95 I think.

Forget FAT32 and move on...NTFS is much better, and with the right tools it's almost no different than FAT32. First off there are several DOS solutions for NTFS access...either a free read-only plugin or a paid full version...Winternals makes the one I know of. Second, the way of the future is a bootable windows CD. Much like your Linux LiveCD's, a bootable windows CD is the same, but running a modern M$ OS. Rght now you have a few options: 1. WinPE - M$ official "Preinstallation Environment", which you are responsible for customizing to your needs. You need to jump through a few hoops to get this...but it is official. 2. BartPE - A much better alternative, but it's not 100% official. While currently it's running strong, I wouldn't be suprised if M$ but the hammer down and tried to finish them off once and for all. But for now, it's the best **** thing out there...you can customize it to no end. 3. ERD 2005 - A great bootable CD with custom applications that help a system/network admin. You not only get file access, but also there are tools to remotely edit the registry, change any users passwords, and disable problematic drivers or services. Problem is, this ain't cheap...but it's worth every single penny. 4. UBCD4Win - A pre-customized version of BartPE with some pretty standard tools. I find this is a good one to start out with, but I suggest making your own in the end. 5. BART CD - By Avast, I've never used it. If you like geeking out, then take on making your own BatPE disc. It may be frustrating at first, but once you get the hang of it you'll be adding all your programs to it. I used to use it for virus scanning and spyware removal, as well as data backup before a reload. Since all of these run off the WinXP OS, they have fantastic support. NTFS, Domain Support, PnP Hardware (Can be a pain to setup), and native access to USB Drives are just a few of the bonuses. People have customized this to the point where it rivals a standard WinXP install. I do appreciate the concept of staying with FAT32 for file access, but it's really becoming an antiquated technology. I know there are other reasons, but when you think about the benefits NTFS offers it should be a no-brainer.

What are you talking about...he gives very good info in the first post. After a power outage he's got blue screens...tried doing a fresh install and got a pretty common error when copying files..and the error can't read sector message is pretty common on drives that have been physically damaged. While your suggest of "fdisk /mbr" is valid in some cases, it's useless as he states that he's running XP SP2. A HD make/model would be nice, but given the info it's hardly necessary, as these are problems that aren't manfacturer specific.

I think he wants to include WinZip with his UA...so this would be what you're looking for: http://unattended.msfn.org/intermediate/methods/intro.htm At least, that's a start. You will need to collect some info on all the programs you want to install, and then start testing using the guides suggestions. There are countless ways to accomplish what you want, but the guide details what is usually the simpliest method. Doesn't require any extra software, maybe just a little scripting...good luck!

"Thin" is normally used to denote a computer that either runs from a network or some other non-standard way. Usually there is no local HD, it's all done elsewhere. "Embedded" is similar to "Thin", but it usually is more specific...most new DSL routers run an "embedded" version of linux, specific to the processors and NIC's installed in the unit. WinXP Embedded is there way of getting into that market...think home computer automation, car pc, or some other use where a full PC isn't needed. "WinCE" is the old name for the M$ handheld OS...it's mostly used for handhelds or smartphones, but it has other areas. The Sega Dreamcast actually ran a very special version of WinCE. In regards to the topic, I can't say I've ever had to setup or support an embedded version of anything. I did come across WinXP SP1 Embedded, but never got around to trying it. I have a sweat VIA EPIA TC-10000 that might be perfect for it, but right now I just have it running Windows 2003 SP1 just fine.

And from what I've seen, it does that mini setup thing every time a new user opens an Office application for the first time. Probably something to do with the user profiles, but none the less it runs that mini setup thing asking for the name and initials. Problem is, it needs to access the source at some point in that process. The reason it doesn't do it with your Admin account is probably because that's what you installed it with originally, and the mini setup has already been done...probably before the source was deleted.

Or just leave the files on there...with 20GB+ drives a few hundred MB's shouldn't be too much to sacrifice. I know this isn't a fix, but in my opinion it's best to leave a local copy of Office handy for repairs. In fact, if you install it from a CD it already offers the option to copy several files to the machine to accomplish that same goal. If you install it from a HD, it doesn't copy the files, as they are already on the HD. But if you remove it, then you might get caught with your pants down when it want's to repair itself. Sounds like you have the install files on the network. I would think it would be a simple registry setting that points to the location of the source files...one which you could edit to point to a UNC containing the files. However, it sounds like it's not that easy. I find it's best to install from where the files will stay...meaning if they stay on the HD then install from the HD, but if they stay on the server then install over the the network. Of course, this poses issues in regards to network bandwidth usage.

Okay, so I keep seeing the error in the Event Viewer: Event Type: Error Event Source: DhcpServer Event Category: None Event ID: 1001 Date: 9/25/2005 Time: 9:05:02 PM User: N/A Computer: BLAH Description: The DHCP service failed to register with Service Controller. The following error occurred: The operation completed successfully. . For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 00 00 00 00 .... Is is just me, or if something complete successfully it shouldn't be an error, right? I checked a few websites out, and there is some people who are getting the first part...but none have "The operation completed successfully" part. Any clues? Should I just not worry about this? Everything seems to be fine, no issues with DHCP as far as I can tell. Thanx in advance!

Maybe I need to clarify more: 1. WinXP SP2 does not include any SATA drivers on the CD. It does offer a way to add new drivers...that's the "F6" key. You'll need to have the drivers on a floppy disk, and they must be in the correct format. This usually consists of a few driver files and a TXTSETUP.OEM file, which is the key to all this. The disk that comes with your mobo should be all you need. If you don't have it then look on the mobo's website for a download. 2. If you want to integrate this into the CD, check the Unattended Forum, or possibly the Drivers forum. There are at least ten threads dedicated to this function, you'll have to read them and find which one works for you. As far as I know, nlite doesn't do that... BTW, what mobo are we talking about?

Which is why you post this in there...not here.

Would double qoutes be the problem? You might wanna change this: $MYPATH= "D:\Program Files\CyberLink\PowerDVD" To this: $MYPATH= ""D:\Program Files\CyberLink\PowerDVD"" But I'm probably wrong Give it a shot!

That's what this forum is for: http://www.msfn.org/board/index.php?showforum=80 Good Luck!

Well if you don't create any local users, and disable the local admin account, then there is nothing for them to log into. If you are doing a fresh install then you can add this to your *.sif: DisableAdminAccountOnDomainJoin=1 Now I don't know if that will work unless you join the domain from within the *.sif, but it's a start. I think you can also disable the local admin through a Group Policy.

Well what specifically is the problem? And how are you normally accessing the photos? Are you using the built-in camera program supplied by WinXP...or does the camera require using it's own proprietary application? For shi*ts-n-giggles have you tried plugging it into a different USB port?

To clarify, XP will boot to an SATA drive if you install it correctly. If you are installing the OS yourself, you'll need to add an extra step...when the blue text mode setup begins start mashing "F6" so you can load the SATA driver...otherwise the setup won't find the HD to install to. You'll need to have a floppy drive and the correct disk (Should come with your motherboard). You can accomplish this many other ways, but that's the easiest if you've never had to do it before. Check the unattended forums if you want to permanently integrate the drivers onto a CD...good luck!

There is no newer M$ USB Mass Storage Driver...there is only one. Now if you have a device that isn't getting installed, it might have a special driver from the manufacturer that you need to install. But as far as I know it's been the same driver since Win2000/WinME. There have been tweaked "Universal" USB Mass Storage Drivers, but those were only for Win98SE.

Well here's the guide I used: http://www.msfn.org/board/index.php?showtopic=39048 I took that and further customized it to meet my own needs, but that's the best guide so far.

I seem to recall reading somewhere that you can't modify the text mode portion of the setup...but maybe someone will prove me wrong.

Active Directory is M$ term for their security/networking subsystem...some just call it AD. It's basically a big database that holds all the security and configurations for a whole network...or a domain as they call it. So you have one central 'thing' that controls most aspects of your network...this is good and bad. It good cause it's very effective and actually pretty easy to maintain. But it's bad because it's a whole new thing you'll need to learn, and when it breaks it's a pain to troubleshoot.

Basically what I was gonna suggest...almost all of M$ upgrade CD's still allow you to perform a fresh install, only needing to verify you have a qualifying product. This is by far the best way to approach it, as you could then get ride of that OEM parition that your WinXP Home is sitting on. I personally don't like those, but you may want to keep it there. Only seems to get in the way for me... Just make sure that you have a CD that will allow you to use the upgrade...you could even make your own CD from the I386 files you probably already have on your hard drive. There are a ton of posts about doing that, just do a quick search if you want to try it out.

And that is warezed to hell and back...all the corp and VLK's in that are not only illegal, but usually overwrite the original files with that from another type...so when you are seeing Home Corp, it's really Home OEM or Retail with certain files copied over that turn it into a Corp edition. And that is what we were talking about...there are no official, legal versions of XP Home that don't require activation.

I like Seagates cause they are inexpensive, quite, decent speed, and have that nice five year warranty...mmmm I also used to suggest IBM/Hitachi, but not so much anymore...just can't see any reason to. Western Digital isn't half-bad either, except for their initial reliability...I've had six of their last ten drives die within the first month. Different sizes and models, all turned into clickers...real annoying. Maxtor and Samsung just seem to 'cheap' to me...but I'm sure they are fine.

Interesting...I wonder if he's aware of that issue. WPI runs from RunOnce, but then it makes it own list of applications to install, so they aren't installed from RunOnce.