Bad Pool Caller

Go into the System preferences and disable the Auto-restart after a crash.
This will leave the BSOD on the screen so you can catch the useless, cryptic
information and report it back here, so someone who knows about such things
can help.

Start>Control Panel>System>Advanced System Settings (note: may require
Administrator Privileges), then click on the Settings button under "Startup
and Recovery" and uncheck the box marked " Automatically restart."

--
Ted Stevens taught me everything I know about putting internets in tubes...


"Heidi" <Heidi@discussions.microsoft.com> wrote in message
news:2C0E7833-F814-4BBE-B51B-54651691CE10@microsoft.com...

> This is the error on reboot after the installation phase, and before
> Complete
> Installation. Can't read anything else, the BSOD moves to fast.
> ANy thoughts?

That would be fine if we could get to it.
Guess the choice now is to do a clean install, since upgrade failed

"Mark D. VandenBerg" wrote:

> Go into the System preferences and disable the Auto-restart after a crash.
> This will leave the BSOD on the screen so you can catch the useless, cryptic
> information and report it back here, so someone who knows about such things
> can help.
>
> Start>Control Panel>System>Advanced System Settings (note: may require
> Administrator Privileges), then click on the Settings button under "Startup
> and Recovery" and uncheck the box marked " Automatically restart."
>
> --
> Ted Stevens taught me everything I know about putting internets in tubes...
>
>
> "Heidi" <Heidi@discussions.microsoft.com> wrote in message
> news:2C0E7833-F814-4BBE-B51B-54651691CE10@microsoft.com...

> > This is the error on reboot after the installation phase, and before
> > Complete
> > Installation. Can't read anything else, the BSOD moves to fast.
> > ANy thoughts?

>

Yes, the upgrade method has produced decidedly "less-than-ideal" results. I
am sorry I mis-read your post, that you were not able to access the desktop

"Heidi" <Heidi@discussions.microsoft.com> wrote in message
news:2B34614B-6CC7-4786-9502-0B0A4214BA9E@microsoft.com...

> That would be fine if we could get to it.
> Guess the choice now is to do a clean install, since upgrade failed
>
> "Mark D. VandenBerg" wrote:
>

>> Go into the System preferences and disable the Auto-restart after a
>> crash.
>> This will leave the BSOD on the screen so you can catch the useless,
>> cryptic
>> information and report it back here, so someone who knows about such
>> things
>> can help.
>>
>> Start>Control Panel>System>Advanced System Settings (note: may require
>> Administrator Privileges), then click on the Settings button under
>> "Startup
>> and Recovery" and uncheck the box marked " Automatically restart."
>>
>> --
>> Ted Stevens taught me everything I know about putting internets in
>> tubes...
>>
>>
>> "Heidi" <Heidi@discussions.microsoft.com> wrote in message
>> news:2C0E7833-F814-4BBE-B51B-54651691CE10@microsoft.com...

>> > This is the error on reboot after the installation phase, and before
>> > Complete
>> > Installation. Can't read anything else, the BSOD moves to fast.
>> > ANy thoughts?

>>

Heidi--

If I understand this correctly, Heidi this is a "bad pooler call" ***in setu***p--not on a Vista that's already on the box that we can fix via Win RE or some other method.

So your mission here is to get Vista installed. Let me know if I've misunderstood you but your OP was that you said "This is the error on reboot after the installation phase, and before Complete
Installation"

The most common causes of your problem far and away statistically are a
problem with a truncated download at some point corrupting your ISO or a
problem with the burn.

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. Rock on Redmond Rednecks.

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/d...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








"Heidi" <Heidi@discussions.microsoft.com> wrote in message news:2B34614B-6CC7-4786-9502-0B0A4214BA9E@microsoft.com...

> That would be fine if we could get to it.
> Guess the choice now is to do a clean install, since upgrade failed
>
> "Mark D. VandenBerg" wrote:
>

>> Go into the System preferences and disable the Auto-restart after a crash.
>> This will leave the BSOD on the screen so you can catch the useless, cryptic
>> information and report it back here, so someone who knows about such things
>> can help.
>>
>> Start>Control Panel>System>Advanced System Settings (note: may require
>> Administrator Privileges), then click on the Settings button under "Startup
>> and Recovery" and uncheck the box marked " Automatically restart."
>>
>> --
>> Ted Stevens taught me everything I know about putting internets in tubes...
>>
>>
>> "Heidi" <Heidi@discussions.microsoft.com> wrote in message
>> news:2C0E7833-F814-4BBE-B51B-54651691CE10@microsoft.com...

>> > This is the error on reboot after the installation phase, and before
>> > Complete
>> > Installation. Can't read anything else, the BSOD moves to fast.
>> > ANy thoughts?

>>