Jito463

Lucky for you I help out on the support forums for Alcohol. Try doing a manual uninstall of Alcohol in case there are some remnants in the registry.

I just used the same commands I used for Spybot 1.3 and it installed without any problems:

Another possibility that I didn't think of before is that a multi-boot DVD as we currently know them just will not work with x64. Think about it. When it boots initially it's running in 16-bit mode if I'm not mistaken. It then launches whatever setup files are needed to run the other setup disc on the DVD. However, x64 is not compatible with 16-bit mode. We may have to resort to a WinPE/BartPE method for preinstalls from here on out. Frankly, it's probably a better idea anyway. What do you think?

I got Nero 6 just shortly after it came out retail (my CD has version 6.0.0.3 iirc) and my key still works for the 6.6.x.x version.

That's just my signature. It's there on every post I make.

Where did you download this from?

winnt.sif

Hmm, that's odd indeed. What's your hardware specs? RAM? CPU? MoBo? etc.

ISO of what? x64? Is this an RC version or final? If RC, try downloading the trial version from MS instead. If final...tsk, tsk.

I've always just used the following: [DiskConfig] Disk1=Disk1.config [Disk1.config] Size1=* PartitionType1=primary FileSystem1=ntfs Quickformat1=Yes Works everytime for me and quickformats

Open My Computer, go to Tools -> Folder Options then click the View tab and uncheck Hide extensions for known file types.

Under [DATA] add AutoPartition=1. Under [unattended] add Repartition=Yes. I think the following sections only work for WinPE, but I've always added them anyway and it always works so why mess with it [DiskConfig] Disk1=Disk1.config [Disk1.config] Size1=* PartitionType1=primary FileSystem1=ntfs Quickformat1=Yes Note that this will not only format the drive but also repartition the drive.

When you save the file, choose save as all types. Then name it winnt.sif.

I just don't know what to say to that. You are *that* dependent on AOL? What exactly is it you're trying to do that can't be done without a resource hog internet software like AOL?

The sheer ignorance in some of these posts astounds me. There is nothing "unstable" about the AMD64's. In fact, they run so much cooler than P4's. And even proved their stability in the THG dual-core competition (if you can read between THG's biased lines). I've been running a dual-boot XP/x64 system since RC1. Been running x64 almost exclusively (though still dual-boot) since RC2 and now running dual-boot but still almost exclusively x64 with the final OEM release. My games run better. My system performs better. True there are a lot of driver issues to work out still. Chipset drivers are pretty much set (Nvidia and Via at least anyway). Video card drivers are good for Nvidia, not so good for Ati though admittedly. Printer drivers are lacking as well as some mass-storage drivers. But even in spite of all that, x64 is worth it for those who don't mind spending a little time tweaking their computer. Sure, x64 may just be a stepping stone to 64-bit Longhorn, but it's still here and ready.

A game question under Unattended Windows forum...?

Well, I did figure something out. I copied ntldr from the actual i386 directory to the boot directory (1OPX on my disc). It got past the ntldr is corrupt message, but stopped with a NTDETECT failed error. That's a start anyway.

Hmm, this is interesting. I was planning on implementing x64 onto my preinstall today, but I see my work is cut out for me. I'll play around with it at work later and see what I can figure out.

I think he's down for the count. Been MIA for quite some time now...too bad.

Some SATA drives are detected while others are not because some SATA controllers are integrated into the BIOS and some use an external BIOS. Those integrated will be detected like any IDE HDD. Those with an external BIOS must have the drivers loaded to find them. Though I do agree that MS should have included drivers for the more common SATA chipsets.

Does your netword adapter show up in Device Manager?

According to that article, the /PAE switch does not work for 64-bit Windows.

In your Windows\system32 directory is a file named wpa.dbl. Just back that up in case you have to reinstall Windows. If you do, and the hardware hasn't changed, just copy that file back over the one in your System32 directory and your system is reactivated.

I think they mean you need to change the configuration of the SATA controller to RAID in the BIOS. You don't actually have to create a RAID array, but the SATA controllers have to be set to RAID, if I'm not mistaken. Give that a try.

I don't know how that worked, then. Because the old bootloader looks like this: The new bootloader looks like this: Odd