|
Posted by BillW50 on June 28, 2008, 8:42 pm
Please log in for more thread options
Barry Watzman typed on Sat, 28 Jun 2008 19:12:31 -0400:
> Sometimes.
>
> Not always.
>
> I'm fully aware of 48-bit LBA and all of it's implications.
Oh good! But others may not be.
> In the cases I have seen [ALL of the cases I have seen, and that's a
> lot ... I'm a college instructor in IT],
And I'm an electronic engineer. That doesn't mean I know everything
though. ;-)
> Windows starts to boot and you get the first two screens (the black
> screen and then the almost solid blue screen) and it hangs forever
> there. Fixmbr and Fixboot won't fix that problem ... it's gotten past
> anything that those will fix. It has to do with the system security
> descriptors, I think, and the fact that the drive you are booting from
> is not the same drive that Windows WAS installed on. However I have
> not figured out why it only happens SOMETIMES.
Sad! I have seen this too. But only on OEM Windows copies so far. You
too?
> BillW50 wrote:
>> Barry Watzman typed on Tue, 24 Jun 2008 02:03:06 -0400:
>>> This often happens with Windows. Windows knows what drive it's
>>> installed on and if you "copy" or "clone" it to a new drive (Ghost,
>>> Drive Image, Acronis, etc.) the new drive may not work (won't boot).
>>> But it doesn't always happen, only sometimes. And I don't know why
>>> sometimes but not always.
>>>
>>> Pdigmking wrote:
>>>> Hello,
>>>>
>>>> I have a toshiba A105 with an 80gig HD. I have a new Wester
>>>> Digital HD that I'm trying to swap in there. I used Acronis
>>>> Migrate easy to copy the drive, and I used this USB connection
>>>> kit. The copy appeared to go well although it took 11 hours. When
>>>> I plugged the new drive and fired up the computer I get: "Unable To
>>>> Run Operating System" or something like that. The
>>>> jumper setting is on default (no jumpers) which is master drive. In
>>>> setup the drive is recognized, it just won't boot up. Connections
>>>> are good. Any ideas?
>>
>> Barry, under the Recovery Console command (Windows XP install disc).
>> The following two commands should fix that problem.
>>
>> FIXMBR C:
>> FIXBOOT C:
>>
>> If you have a HD larger than 130GB and you don't have a Windows XP
>> with any Service Packs install CD, don't try the above. As it
>> probably will corrupt the HD. It can be fixed, but what a PIA.
>>
>> BOOTCFG /rebuild
>>
>> I am not sure what the BOOTCFG command all does. but that might help
>> too.
--
Bill
Gateway Celeron M 370 (1.5GHZ)
MX6124 (laptop) w/1GB
Windows XP Home SP2 (60GB HD)
Intel(r) 910GML (64MB shared)
| 
XML Sitemap