From: vwheeler 

Thanks, That must be the cause the extended partition table now extends
beyond the loaders ability to read it. Ill look at the table tomorrow after
work and I need to locate a binary editor. I always thought it would be
good to learn about about partition tables.


"When you install Windows on a logical drive in an extended partition
OSLOADER needs to "walk the extended partition table" through
BIOS calls in order to get to the partition you have Windows installed in.
Each of these logical drives are addressed in a "daisy chain" of
partition tables. Each sector that contains a partition table entry MUST
end with a 55AA as the last 2 bytes in the sector. "


Rich Gauszka wrote:
> ms has a knowledge base article Q149877 that mentions your error message
>
> http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:8
0/support/kb/articles/Q149/8/77.asp&NoWebContent=1
>
>
> "vwheeler"  wrote in message
> news:40552bb8$1{at}w3.nls.net...
>
>>Booting an W2K Pro I get the message "Boot record signature AA55 Not
>>Found DB02 found windows 2000 could not start"
>>
>>The Hard drive is 200G with the partitions originally copied from an 80G
>>then partitions added to use up to 132G Yesterday I got brave and
>>created a 50G partition the max W2k Disc Manager would allow it sees it
>>as a 160G I had rebooted several times yesterday. Today I used the
>>partition to record some video files with Beyond TV and created a DVD.
>>This evening I shutdown with reboot there was an error about a corrupt
>>file on drive E some file in a directory with a $. The reboot now brings
>>up the NT boot manager menu any selection results in the above message.
>>
>>
>>This hd was originally upgraded from NT4SP6 a long while ago the boot
>>manager has 4 entries DOS, Win NT, a maintenance Win2000, and Win200 I
>>have kept up to date with the service packs and critical updates.
>>
>
>
>

--- BBBS/NT v4.01 Flag-5