VOGONS

Common searches


First post, by Syntho

User metadata
Rank Member
Rank
Member

I have an image of a Win98 install that doesn't include the boot sector apparently. I used Symantec Ghost to image it, but I think there's an additional flag to copy over the boot information which I left alone. Isn't that how I was supposed to do it?

Anyway this other drive I have had a new partition created, the Ghost image restored, and it wouldn't boot. I spent a while looking up how to fix it, like fdisk /mbr, but it didn't work. Instead of posting here, I decided to just a fresh copy of Win98 on the partition, which would obviously put in a new MBR. It works fine now, including after I put the aforementioned image on it. It was quicker to just install Windows again so that a new MBR would be put on the drive than it was trying to figure out how to fix it somehow else.

So for future reference, if this same situation happens again, how can I more easily create a new MBR/boot sector or whatever it is? Maybe there's a program somewhere that can fix drives easily like that. I'm not sure EasyBCD fools with old drives and operating systems.

Last edited by Syntho on 2024-07-26, 15:18. Edited 1 time in total.

Reply 1 of 5, by jakethompson1

User metadata
Rank Oldbie
Rank
Oldbie

There is both an MBR (first sector of the entire drive) and VBR (first sector of the primary partition).
If fdisk /mbr didn't work, it's possible you needed to sys c:
If neither worked, then I'm not sure, and it could be some MBR geometry issue

Reply 2 of 5, by Syntho

User metadata
Rank Member
Rank
Member

I do remember trying sys c: as well, but now I'm not sure how I had the drive configured at that time. I believe I had the 2nd drive as a slave and it showed up as D:. Maybe next time to be safer I'll have to make sure the 2nd drive takes the C: letter.

Reply 3 of 5, by Disruptor

User metadata
Rank Oldbie
Rank
Oldbie

Perhaps none of your partitions is not activated for startup.
You may run fdisk and use option 2 to set a startup partition.

Basically partitions on drives that are not on the primary/master channel never get activated.
And, please never ever create partitions for legacy operating systems with Windows Vista, 7, 8, 8.1, 10 or 11.

Reply 4 of 5, by Azarien

User metadata
Rank Oldbie
Rank
Oldbie
Disruptor wrote on 2024-07-26, 16:17:

And, please never ever create partitions for legacy operating systems with Windows Vista, 7, 8, 8.1, 10 or 11.

May I ask why? Two things that come to my mind is inadvertently creating a GPT-partitioned disk, and that annoying 32 GB limit for FAT32 partitions, is there anything else?

Reply 5 of 5, by Disruptor

User metadata
Rank Oldbie
Rank
Oldbie
Azarien wrote on 2024-07-28, 08:46:
Disruptor wrote on 2024-07-26, 16:17:

And, please never ever create partitions for legacy operating systems with Windows Vista, 7, 8, 8.1, 10 or 11.

May I ask why? Two things that come to my mind is inadvertently creating a GPT-partitioned disk, and that annoying 32 GB limit for FAT32 partitions, is there anything else?

That's easy. They don't care for CHS alignment which is required for legacy operating systems. Instead they align partitions megabyte-wise...