Tripredacus

The only thing I can think of is that you'd have to install Windows 7 to Audit Mode. Then get your unattend.xml to use with sysprep /generalize and then capture the image. Then you'd have to deploy the image with Imagex. After that part is done, you'd need to write a program that asks for a computer name, changes the computer name node in the XML on the deployed OS and reboot. It is already known that you can change the XML for an OS that is deployed but before it boots the first time.

Such an amazing tool would just take the fun out of it!

I couldn't even say. Last time I had dial-up was using a defective 14.4 modem I found in the garbage that connected as ISDN speed somehow.

That is to be expected. Windows XP was installed on your computer using the ACPI HAL, and that setting in the BIOS effectively changes your HAL. XP doesn't like when you change the HAL, as you have seen.

Windows 8 is a beta! But that is interesting. I never tried to look at WEI on the dev preview.

Flaw - Payback

BCDEdit can only show you the options of the OS you are currently booted into.

MDT isn't wholly dependent on WDS. You can use MDT to build USB key installation too. Anyways, you can build a Task Sequence specific to what you want the deployment to do.

I wonder if hitting the hard disk in the freezer could be a valid troubleshooting step someday...

See my screenshots here: Has recovery partition = enabled Doesn't have recovery = disabled

How are you deploying this image? There shouldn't be a reason to extend the disk... since you'd run diskpart prior to imaging to set up the partition.

It sounds like you are building installations for a company right? You can use MDT to give a computer name and then join a domain. This works because it asks these questions BEFORE the installation actually takes place, so it has the computer name already when it goes to join the domain. Alternatively, another user mentions the use of a Powershell script to join the domain.

Have you already talked to your network Administrator about this problem?

Ah screensavers isn't something I normally think of. Nowadays I don't bother with them and just use ribbons or whatever. But my 98 does have the Marilyn Manson screen saver that came on a single. It spells out DRUGS, which prompted many friends to call it "The drugs computer" rather than Shiva. // I've tried IrfanView, I remember needing it during college for some reason. My favorite is always the version of ACDSee that is on my 98, but it is impossible to find that version. But that's fine since in XP and up the Office Image Viewer is good enough.

Well at least it does give you the breakdown of each component. But it is the old addage with computers, it is only as fast as the slowest component, so it does make sense.

Diary of Dreams - Butterfly:Dance

IDK that seems a little complicated. If you install the WMI package, you can do a WMI script that would grab the volume size. That's my only idea.

That happening happened today.... New scores after replacing bad video card: Base Score: 5.1 CPU: 7.2 RAM: 7.2 Graphics: 5.1 Gaming Graphics: 6.4 Primary Hard Disk: 5.7 Ooops new video card is XFX Radeon HD 4670

MSI's website is connect, iaStor is a SATA driver. The "IDE" Mode option you see in the BIOS is a legacy compatibility mode. So your main mode of SATA operation are: - IDE - AHCI - RAID However, in some BIOS there is another setting to further dictate SATA behaviour that includes options for "legacy" or "native" however I do not know the proper use for that setting. Well the lack of drivers in XP wasn't so much of an "issue" when it came out! It is a fairly old OS, I'd hardly expect that Windows 7 will be able to properly install without some additional driver files 10 years from now! As far as the driver packs go, if you want to make an XP disc that is to be used on a bunch of different kinds of boards, they only one you'd really need would be the mass storage drivers. If you want to make your XP disc install everything for you, I couldn't really say. As far as the files needed, It doesn't hurt to put the entire f6flpy-x86 folder onto the floppy disk, but having the AHCI files in there when you are using IDE may be confusing because Text Mode might list multiple drivers with the same name. As far as the EXE, the driver package I downloaded did not have one. I see from MSI's website (you didn't post if you had the first or B3 board) neither of them have a floppy connector on the board. Your best bet would be to get a USB Floppy drive for systems like this. As time goes on, you'll see less and less systems that have floppy ports.

Driver for XP32 is here: http://www.msi.com/service/download/driver-17380.html The files needed are: - iaStor.cat - iaStor.inf - iaStor.sys - TXTSETUP.OEM Those files are for using the IDE option in the BIOS.

In this case, you are safe to delete the winre.wim. Windows won't have a need for it unless you have programmed the recovery options in the BCD.

Did you rename the volume or something else? Is this one of those drives that has built-in software?

I suppose in 15 years from now, users will come here for our old Windows 7 files!

Most people will refer to the System Builder kit as OEM version because it does indeed state the term "OEM" on the packaging, but this is due to how it is allowed to be sold. Its something that sales people need to realise that the general customer base will refer to the incorrect terms for the products and need to be able to decode what exactly a customer is talking about... You cannot create a pre-activated install using the System Builder kit.

Are you making some new website or something? The one you put in your first post is already coded to center the page content. I'm wondering what you're trying to accomplish here.