If there is no ME option in the boot.ini then it does suggest you did actually start an Upgrade - even if it failed - rather than a parallel installation...? If the ME folder (typically it's c:\windows) is still on the drive post back. If XP went into its own folder will have different folder name; what is that in this situation? Incidentally what is the current file format of the Primary partition? For ME it was fat32, but during the attempted XP installation it "might" have gone to ntfs? If the drive is now ntfs then I don't think ME will show up in the boot.ini; but I'm not entirely sure about that... Perhaps have a look to see if the ME folder is still there (intact) anyway? If you are prepared to write off the current XP installation (and possibly the ME version - if any of it is still around...) and the drive is still fat32, then you can either go for the reformat routine and then re-install ME; or, if the drive was converted to ntfs during the failed XP installation then you will have to use Fdisk to remove the Primary partition (this means "everything" goes - data included); afterwhich you reconfigure the drive afresh, format it and re-install ME etc. Also if, by chance, the Primary is still fat32 then you could simply re-install ME to that Primary - alongside XP. If the ME folder is still there (not very likely?) then you could install ME to/over it. If the ME folder has gone... then just change the offered default for ME installation from the usual windows to perhaps win-ME (so as to clearly identify that it is the "new" ME installation). Once ME is re-installed simply delete the failed XP installation from the drive. Then empty the recycle-bin and defrag the drive, afterwhich re-install all appps/utils afresh for the new ME installation. (It is highly unlikely that you will be able to re-install ME over/to the current XP folder...) During this ME re-install (over the previous version, or alongside the XP installation, the mbr will be rewrittn to the dos/'9x version; this will disable all access to XP and thus the boot.ini will not show at boot-time; you will boot only to ME. This latter appproach (where the Primary is still fat32) would mean that you do not reformat the Primary partition - and thus any data etc. would/should be safe and preserved). But if at all possible backup any critical files first, though with no functioning OS it may not be easy, unless you can slave the drive to another system? Need more ideas/help - post back?

0

Yes I did start an upgrade, the windows ME files are in "WINDOWS" and the windows XP files are in "XP". I am pretty sure it did not change to NTFS but stayed FAT32. The WINDOWS file seems to be intact, whether or not Windows XP has altered it in anyway I don't know, I don't think it has. When I try to install Windows ME it says I should run Setup from MS-DOS.

0

When I try to run setup from the Windows ME cd a message comes up saying "An application has attemped to directly access the hard disk, which cannot be supported. This may cause the application to function incorrectly. Choose Close to terminate the application" with the option to close or ignore. If ignore is clicked, another message comes up, saying "Setup cannot run from within Windows 2000. Shut down Windows 2000. Restart your computer using Windows 95 or Windows 98 and then run setup. Otherwise, start MS-DOS, and then run setup from the MS-DOS command prompt"

0

I have just edited the boot.ini file and it now gives me a dual boot, when I try to boot to Windows ME it says that I should reinstall the file below because it is missing or corrupt. The file is <Windows root>\system32\hal.dll

0

That error messages reads as though for XP... Re-install ME over itself via the standard ME setup routine (bootdisk and CD or a CD boot) - not from within any installed OS (although you don't appear to have functioning at present on this system). It is often useful (occasionally necessary - and this may be one of those accasions) to run the " sys c: " command from a '98/ME boot disk - prior to re-installing '9x/ME in a working (or otherwise) dual-boot. So boot with '9x/ME boot-disk and type " sys c: " (no " ") at the a:>\ prompt, and press Enter. This rewrites the mbr (currently the XP version) back to the dos/'9x version; this disable any access to XP. Having done this run the standard ME installation routine. Typically(?) one just run ME/'9x setup and points it to (re-)install to the current ME/'9x folder (usually\windows). But if by chance it won't let you then, this link (below) has a reference/link that details things to do to achieve this process successfully; though it should not be necessary this time (all things being equal)? http://www.annoyances.org/exec/forum/winme/t1050614670 Incidentally can/will you post the boot.ini as is at present? Useful to remember that once you start an Upgrade of an OS to another (different) OS many (previous/original OS) core-files etc. often go "bye-bye" (are overwritten/replaced (even deleted). Your present ME folder may be missing all manner of core files - the re-install will (should) restore them all and leave you with a working ME installation. Once you have a working ME, simply locate/delete the abandoned XP folder (and the pagefile.sys - if it exists) from the drive - but be sure you go after the correct folder... The boot.ini will detail what it's called, which is why it might be useful to post that here. There is a remote chance that once you reset the mbr to dos/'9x version (via the " sys c: " routine), you will be able to navigate to the ME folder and boot to ME as is; a remote chance perhaps - but possible.

0

The boot.ini file as it is at the moment is: [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Millenium Edition" multi(0)disk(0)rdisk(0)partition(1)\XP="Microsoft Windows XP Home Edition" /fastdetect Note that I did edit it to that myself.

0

The boot.ini is invalid. Nice try but the entry for ME is incorrect. Typically it resembles c:\"Microsft Windows" - depending on what the '98 folder is called etc. Entries for NT/W2K/XP follow the ARC path covention which looks like the example below: [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINNT [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Professional" /fastdetect The one above is obviously for a W2K system, and W2K is installed in the first (the Primary) partition on the drive; and there is just one hard-drive installd. There is no such syntax for dos/'9x(ME). The ARC path you have set as "default OS to boot" is actually trying to boot to XP (which is an incomplete/failed installation) - hence the error message you're getting. The XP booot-loader is interpreting that line as instruction to go looking for an XP installation which to boot. Since your XP installation is incomplete - it's missing at least one critical/core file - you get the error message relating to it. For a dual-boot '98/XP the boot.ini would resemble (with XP as default OS): Boot Loader] Timeout=30 Default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS [Operating Systems] multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Professional" /fastdetect /noguiboot C:\="Microsoft Windows 98 Second Edition" With '98 as default OS it would resemble: boot loader] timeout=30 default=C:\ [operating systems] C:\ = "WIN98SE" multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows XP" /fastdetect In the '98/XP example, XP is installed into the second partiton on the drive - again only one drive present. The XP partition may be another Primary, or an Extended partition, or a logical-drive in the Extended partition. Which type of partition it is, is not specified within the ARC path statement/syntax (ARC syntax does not allow for that). The various entries multi, disk, rdisk, partition, all have specific meaning and values (dependant on how the system is configured - i.e. number of drives/partitions). Back to your present dilemma: Presuming the Primary (c: ) partition is still fat32, boot with a '98 boot-disk and at the a:>\ prompt change to the c : drive/partition (type c: at the a:>\ prompt, and press Enter) and run the command: dir /w /p You will get a screen listing in two/three columns the contents of the c: drive. If it requires more than one screen to show all the contents then you get a message at the bottom of the screen to "press any key to continue" (and thus see more of the drive's contents). Although you say the ME folder (windows) is there in an earlier post, see if it shows up in the above routine; more of a check that's all. Regardless - to gain access to ME (i.e. boot to it) - presuming it's a complete installation still on the drive, then run the " sys c: " (no " ") command I described earlier; reboot and you should boot to ME (if it's OK), or at least to a c: prompt. If to a c: prompt then change to the ME (windows) folder and type " win " (no " "). All things being equal you my well then boot to ME... Presuming so then all you do is locate/delete the XP folders etc. from the drive; afterwhich empty the recycle-bin and defrag the drive.

0

Bit of a problem - I have tried to boot with a Windows 98/ME boot disk but it doesnt boot up it just does its normal thing. What am i doing wrong?!

0

Could be the boot sequence (in the bios/cmos settings) is set to hard drive first (c: then a: ; where c: = hard-disk, and a: = floppy). You need to reboot and watch the screen for details of which key(s) to press to enter the bios/cmos (setup?) state. Press the key(s) as indicated on the initial boot-screen and access cmos/bios settings. Then you look for the area that allows you change the boot-sequence. Once you have set the boot-sequence to a: first then c: (usually), save changes and exit. Reboot, again with the floppy installed, and away you go. Different bios makers use different key(s) to gain access to bios/cmos settings - Dell call this are 'setup' (don't ask why...). I generally leave the bios boot-sequence settings as a: then c: '; allows a floppy boot at any time without problems. In normal circumstances there is no floppy disk present (the drive is empty). Thus when the boot-sequence checks for the floppy first, finds nothing (no bootable disk) there, then it looks next for the hard-drive (c: ); it finds it and boots up. If it finds a bootable floppy first then it boots from that.

0

Holly: Also - check your message area at the bottom of your "My Computer" area.

0