Installation Vista Beta (5384)

  • Thread starter Thread starter Elimination
  • Start date Start date
E

Elimination

- Installing Vista x86 under XP x86:
After copying and unpacking it makes it's (first) reboot. After displaying
the bootmanager menu it automaticly picks Vista setup. Screen goes black and
"ticks" (as in switching resolution probably) and there is some HDD usage
for a couple of seconds (it doesn't spin the cd drive up). Few seconds later
it reboots.
This results in the same loop.

- Installing Vista X86 via booting from the DVD:
After the bar with loading files has filled up it goes black, ticks, hdd
loads... and reboot. But then it gives an error message in the bootmanager:
File: \$WINDOWS.~BT\Windows\system32\winload.exe
Status: 0xc000000f
Info: The selected entry could not be loaded because the application is
missing or corrupt.

- So what I've tried:
* In both situations all options used in the F8 menu, but they all result in
the same reboot
* In both situations set my CPU and GPU at stock speeds (instead of
overclocked).
* In both situations turned off all onboard stuff (Lan, Audio, Firewire..)
and removed unnecessary USB devices
* Install via XP with and without installing the driver for my s-ata
controller (975X 82801GR)
* Install via XP with and without using the update option during the
install.
* Install via XP selecting different partitions (on the same raid-0 config
though)
Note: Don't know if it's intended or not but the $Windows~BT and ~LS
directories are placed in the XP partition (maybe it's supposed to be placed
in the new (vista)partition?)

- My configuration:
Asus P5W DH Deluxe Bios 0901
Intel C2D E6600
OCZ P2-6400 CL 4-4-4-15
2x WD740ADFD in raid0 using the controller 82801GR(975X)
Asus EN7950GX2
 
You sure have been persistent and thorough. I've been there--at least the
persistent component.

"Note: Don't know if it's intended or not but the $Windows~BT and ~LS
directories are placed in the XP partition (maybe it's supposed to be placed
in the new (vista)partition?)"

It's by default. And if you check C:\Boot you'll see other files installed
there. There are a number of files that are going to your XP drive no
matter where you park Vista.

After reading this I think you need to reburn and use a CRC checker. If you
have SATA most or any RAID you may have to install drivers on a disk for
that but you've tried that both ways. The updates link isn't going to
impact this. I don't know what they have planned for that toward RTM if
anything.

I would delete a volume and do a format again on your target drive, or a
format and a chkdsk. I've noticed starting with 5472 and with 5536 but not
on 5384 that you may not get a setup from XP done, but can get always get it
done if you restart (changes drive letters but they can be reghacked back if
it matters to you).

Reburn Option:

1) Burn slowly. 4X should be fine. Some of this probably varies with the
DVD writer and the media.

2) Make sure to select an ISO tab if there is one on the burning software,
and make sure to close the session on the burn.

3) Try this tweak on your Windows XP drive and burn from there:

Get to Dev Manager by typing devmgmt.msc in run/win key + pause break or
Rt.click My Computer>Prop>hardware tab>Device Manager if you like 5 steps
instead of one cmd. If you're set to PMI here change to DMO and if set to
DMO change to PMI using these 5 steps:

1) Click the + in front of IDE ATA/ATAPI Controllers

2) Double Click the Secondary IDE Controller

3) Click Advanced Settings

4) Under Device 1  Next to Transfer Mode choose DMA (or vise versa)>Click
OK

5) Reboot your System

6) Check your burn with a CRC utility and the links for this are below
including the direct Taco Bell link. It is very classy, sophisticated, and
very Wagner Edstrom/McCann Ericson esque for MSFT to adopt a Taco Bell url
for their public Beta 2 CRC checker.

Obtain CRC Utility for Vista Beta 2 Here: (The CRC utility is a way to check
the integrity of the ISO Burn which is probably where your problem
lies--it's #1 on the list):

Here's a link:

The CRC utility for Beta 2 is contained here (Scroll down to the bottom
under "Additional Information"

Microsoft® Windows® Software Development Kit (SDK) for Beta 2 of Windows
Vista and WinFX Runtime Components
http://www.microsoft.com/downloads/...73-F5EA-4B7B-B022-97755838DB94&displaylang=en

Additional Information:

To verify that your download of an ISO file for the Windows SDK Beta 2 build
is not corrupt, download the CRC Utility. (Note: this is not a Microsoft
application. Use at your own risk.)

To run the CRC test, open a command prompt and run the utility. providing it
the name of the file (i.e. crc
c:\6.0.5383.1.1.WindowsSDK_Vista_idw.DVD.Rel.img) The CRC utility will run
two tests on the ISO: it will verify if the ISO is valid, and it will give
the AutoCRC signature for the file. The AutoCRC signature for the Windows
SDK Beta 2 ISO is 0x28434EEF. You should also confirm the size of the ISO is
correct: 1.14 GB (1,229,355,008 bytes).

If it fails any of these three tests, re-download the ISO.

I really like the direct link to it though if you right click CRC here>left
click Properties:
http://tacobell.iexbeta.com/longhorn/crc.exe

Good luck,

CH
 
Chad Harris wrote:

The CRC utility for Beta 2 is contained here (Scroll down to the bottom
under "Additional Information"

Microsoft® Windows® Software Development Kit (SDK) for Beta 2 of Windows
Vista and WinFX Runtime Components
http://www.microsoft.com/downloads/...73-F5EA-4B7B-B022-97755838DB94&displaylang=en


Additional Information:

To verify that your download of an ISO file for the Windows SDK Beta 2
build
is not corrupt, download the CRC Utility. (Note: this is not a Microsoft
application. Use at your own risk.)
Click to expand...

Chad:

This CRC check is for the ISO download, not for the burned DVD.

The burner I use (the free BurnCdcc) has a ReadVerify setting, which (I
think) extracts the files from the ISO again and checks that they are
identical to the ones on the burned disk. It seems to double the time
taken. I have yet to see this test fail, and my burned CD's and DVD's
have always worked correctly.

David Wilkinson
 
David--

You are correct. The directions state that explicitly in the link. I didn't
say it was for the burned DVD. I know right now he doesn't have a legit
source of a download. But he can check the ISO he has, and depending on
what he uses, as you point out many have a read verify setting and a lot of
people find it very useful. There are also MD5 and CRC checkers for the
"burned ISO on a DVD" on the web.

Always glad to hear of other burners people use successfully so I can pass
on the recommentdations like the free BurnCcc. Currently I'm using Nero 6.6
and have used it with every build of Vista, having to reburn rarely.

I have noticed with the last two builds, 5472 and 5536 that if you try to
install from XP it will give you a message on my box saying that I need
drivers for an IDE controller. It will say this no matter what I update and
no amount of appropriate drivers copied to disc and inserted satisfies this.
I'd like to know what's going on there.

If I ignore that mesage and restart I get a perfect setup every time. Your
drive letters will change but they can be reghacked any way you want them.

Also the Vista Upgrade Advisor that you can run on your system is
notoriously inaccurate. I attribute this to MSFT wanting to scare people
into buying hardware they don't actually need to up the OEM preinstall box
sales where they aren't required to provide Genuine MSFT Media and the
people can't do repair installs or reach Win RE in Vista. OEM sales
increased 20% last quarter and retail sales fell with respect to Windows XP.

The Advisor told me I couldn't use my sound card (Turtle Beach excellent
quality and I have in every board--there's a trick but it's findable on the
web and I've posted it in every possible MSFT Vista group appropriate). It
also said. It also said that my VIA bus controller was not Vista
compatible nor was my IDE/ATA controller.

Rubbish MSFT.

CH
 
Sorry for my late response but I have been trying all the things you said :)
So to be safe I just burned at 1x in the burn application someone noticed
above my post. Before burning i checked with CRC utility and everything was
correct.

Still.... Installing freezed when I tried to install after restart. This
time i noticed
a very vague loading bar (i must've overseen that the first couple of times)
but
still the same reboot.

I tried everything, bios update to 1305 (beta) and disabling everything.
I even disconnected my hard disks just for the sake of testing! :) Though
when I did
that it didn't want to copy the files ;-) Then i tried to remove the Videocard
from the PCI-e slot. As it's fairly new I thought to give it a shot.
Surprisingly I followed
the boot from sounds and LEDs and saw the DVD spinning up and copying the
files... and
it didn't reboot! What exactly happened after that I don't know...

Soo should I get a very old PCI card then? I hope this isn't the only
solution...
 
Sorry for my late response but I have been trying all the things you said :)
So to be safe I just burned at 1x in the burn application someone noticed
above my post. Before burning i checked with CRC utility and everything was
correct.

Still.... Installing freezed when I tried to install after restart. This
time i noticed
a very vague loading bar (i must've overseen that the first couple of times)
but
still the same reboot.

I tried everything, bios update to 1305 (beta) and disabling everything.
I even disconnected my hard disks just for the sake of testing! :) Though
when I did
that it didn't want to copy the files ;-) Then i tried to remove the Videocard
from the PCI-e slot. As it's fairly new I thought to give it a shot.
Surprisingly I followed
the boot from sounds and LEDs and saw the DVD spinning up and copying the
files... and
it didn't reboot! What exactly happened after that I don't know...

Soo should I get a very old PCI card then? I hope this isn't the only
solution...
 
Back
Top