boguing

Don't worry - have ditched and reinstalled XP as it should be. Thanks for advice. John

OK. The raid array has four partitions. Seen as CDEF by win2k. There's an optical seen as G, the pull out ide as H and another optical seen as I. 2k is installed on F, with it's boot files on C. Now, XP sees the IDE pull out as C, and is installed on D (the first partition of the array). It has it's boot files on C (the pull out). So with the bios set to boot from the raid, the xp bootloader doesn't get read, the array one does and so I'm into 2k. If I changed the bios to boot from ide, I'd be in XP. Messy, and the purpose of the pull out is just backup and file transfers to another computer (miles away with no broadband) so sometimes it's not here! EDIT I'm thinking that it'll be easier to ditch the xp and start again. Can you tell me if the XP clean install (not upgrade) will create a dual boot ini?

OK. Machine has 4 drives in a Raid 0/1 array, and (this is the problem) an ide drive in a pull out for backups. What makes you think I'm paranoid about data?! So, it was a 2k box, with 2k in one partition of four, but I've now got XP on another partition. I had hope to find it automatically create a dual boot menu that I could use until XP has everything loaded. And it looked promising. After a few XP instigated reboots I then had to reboot for AVG or Zonealarm, can't remember which. Come back to desk and I've got the 2k logon. Thinks 'goody it's dual booting'. Do a restart expecting to find the menu with 2k as the default. But no. no menu, just 2k. Yep it's gone and put the boot files on the pull out ide. So, can I get around this, or do I ditch the XP install and do it again with the ide pulled out? Thanks folks. John