To: Matt Brown who wrote (24185 ) 1/1/2002 1:51:07 AM From: belker Read Replies (1) | Respond to of 110655 i am more confused than you. i went back to the winnt files, which is where i saw the boot.ini and ntdetect files, and they are now not to be found. installed on drive c is w2k. i can access this from the boot menu. this is the install that i made last night, working my way from dos-6.0 thru win3.1 and win 95 until i was able to install w2k. installed on drive d is the original w2k that i have been using for six months or so. this is the drive that i can not access. it is w2k but the boot menu lists it as microsoft windows. (I believe that it is reading as vanilla windows because the install of windows on drive c over wrote its boot and startup files. i think this might be the case due to what i read in w2k help about installing win95 after installing w2k. perhaps this not the reason at all.) i do not have w95 or w98 installed on the machine. i originally had w98 on c. yesterday morning i stupidly formatted drive c, without uninstalling w98, so that i could install w2k on that drive. a thoughtless and unnecessary move that caused all of these problems. right after that i ws unable to boot up at all. c:\=w2k accessible. d:\=w2k not accessible. these are the only operating systems on the computer. there is a folder on c drive containing dos, which was placed there by w2k when it installed over w95. all the partitions on the computer are ntfs except i (which use to be e.) i is the logical partition of c. i converted it, using partition magic, to fat32 so that i could write ghost images of drive d as i am trying to save that data in case of a complete blow up of d. i am puzzled about not being able to locate the boot.ini. it is also in partition magic in the same form, but i know i saw it in winnt. i opened it in notepad to copy it, to post here. when i was done i just closed it out. that would not have affected it existence, would it? i also clicked on the ntdlr(sp) and ntdetect files to see if i could copy them but they didn't open. as you can see, i don't spent a lot of time mucking around inside of these boxes. i have the recovery console available on boot up. if that helps. is this at all clear? belker