[pvjpkumar]

Hello Everyone,

I have the following configuration :
+ AMD Athlon 2.2 Ghz
+ 1GB RAM
+ HDD:
a) 40 GB (Primary Master) : 2 Partitions ( 1 primary and another extended)
b) 80 GB (Primary Slave) HDD ( 4 partitions)

I have installed Windows XP first on 40 GB in its primary partition. Then used whole of Extended partition for linux. I have installed SUSE Linux Personal Edition 9.1 on this for which I got dual boot.

But when I chose Windows XP, the system just hangs up there.

Investigation Done
============
1. I removed SUSE Linux and did "fdisk /mbr". This has removed the GRUB but even then I am unable to login into Windows.

2. Then, I have erased all the partitions using SUSE and re-created them using FDISK and installed XP, even the same problem.

3. Then, I have erased all the partitions using FDISK and re-created them using FDISK again and installed XP, even the same problem.

4. Then I have erased all the partitions using Mandrake Linux CD, and chose created the partitions with the same with "FAT- Windows 98 LBA Mode" and formatted and tried, the issue still remains.

5. Long before I had taken the Partition Dump of Win XP using Norton Ghost. Removed all the partitions using FDISK and using Norton Ghost, copied the partition back to HDD. Still didnt work.

6. Re-created partitions using Seagate Disk Manager, installed Windows XP using WinXP CD as well as Norton Ghost Dump...... still unable to load the Windows.

7. Played changing the Mode to Large, LBA, Auto in BIOS. Still no use.

-- What exactly happens is, when the windows is about to load, the cursor just blinks as if it is unable to reach the ntdlr. ntdlr is physically existing. Partition Magic Boot Loader also didnt help me in loading the Windows.

Also, I tried to install Windows XP on my 80 GB HDD. But when I change boot sequence to this HDD, and boot from it, I get the following:

L90 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 ..........
and it keeps going.

Linux does install properly on both of these HDDs. And this problem started only after installing Linux.

I do my work using this computer only and all my work has stopped just because of this. Can anyone please please help me in this ???????????

Regards
Pavan

[tsunam]

First off, next time instead of panicing and trying to remove linux, remember to ask. It was no doubt a simple modification of the grub config file to have windows boot. Windows boot up error's unknown. If you want to reinstall windows on whichever drive. put in the windows xp disc and start the installation. You should also be able to get to a text based menu. In there that's where you want to do the fdisk /mbr, partitioning etc, then reinstall after that.

If you want to still run linux play with it. Might i suggest a live cd version of linux so you don't go crazy and can't do work? Something like Knoppix, Suse, Mandrake.

[pvjpkumar]

Hi Tsunama and Other Members,

Thanks for your reply. I think you didnt get my issue. It is not the issue of modifying the grub or lilo confs.

In that case, when I remove all my partitions, and install Win XP that should work. I have already done "fdisk /mbr" couple of times. But that didnt work.

Last operation I have done on my HDD:

Removed all the partitions. Created 5GB FAT32 partition as primary partition. Formatted that partition. Did "fdisk /mbr". Installed WinXP using CD. Windows loaded successfully. System restarted as requested by the installation -> After BIOS settings displayed, it just hangs. Cursor would be blinking and nothing happens.


Any more bright ideas !!!

Regards
Pavan

[saikee]

I think you are doing a lot of things without knowing the consequence.

I am putting my money on you current problem that you simply forget to set your bootable partition "active". You are convince the Linux bootloader is still there.

The partition table is just a letter box system of a high rise apartment block. Fdisk alters only the partition table but does not disturb the tenants inside the aprtment block. The bootloader is the janitor. To evict a residing bootloader you need to boot up the floppy first before issuing fdisk /mbr.

It is a silly statement to suggest a bootloader can corrupt your hdd. None of them ever does such thing. The MBR can be used by Windows NTloader, Linux Grub or Lilo in exactly the same way. Any of them can be restored in identical fashion with a floppy.

Users don't normally bother about how a bootloader work, how to remove it and how to put it back. They just install it and panic when something is not working properly.

[pvjpkumar]

Hi Saikee,

I have done this lots of times before and not for the first time. I know how a bootloader works. Please note that I have set partition to active before installing the any O/s (windows or linux). If you clearly observe, without making the partition active, it throws an error saying that partition is not active (for windows atleast).

Thanks for the reply.

regards
Pavan

[saikee]

OK

Since you are convinced that the Linux is doing harm to the hard drive to the point it cannot be booted, why not just format the partition by DOS, typing

format c:/s

This involves no operating system other than DOS command prompt and surely must work.

I have Windows' NTloader booting a maximum of 9 Linux before. Had stretched Lilo to boot the maximum of 15 operating systems. In my current PC the Linux bootloader Grub is booting 1 DOS, 3 versions of Windows and 32 Linux, thus I think a bootloader derserved to be defended, be it from Windows or Linux.

On the point of partition table - Just last week I tried to copy a Grub bootloader directly onto the MBR and wiped the entire partition table away by mistake. As I kept a record of my 28 partitions, standardised in alternating 5 and 10Gb with exception on XP and swap, I managed to recreate the 28 partitions without losing any of the partitions. That is possibly the closest thing a bootloader corrupting a hard disk but it was my own mistake using a dd command in my own way. When installing it by the normal methods all bootloaders skip the partition table in the last 66 bytes of Sector 0.

[I Fix 4 U]

bout time u messed something up with the dd command saikee. naw man just jokin around.