I currently have a 40Gb drive split partition:
- 20Gb C: Drive (NTFS - WinXP)
- 20Gb D: Drive (FAT32)

I would like to know how I can install win98 on the FAT32 drive as a dual boot?

I have done the following and receiving an error. Copied win98 CAB files to D: Drive (Windows\Options\Cabs) and booted into MS-DOS using a win98 Bootdisk and tried to run setup. I was unable to even start the installation because of the following error: SU0013

any help?

Win98 wants to be on the C: drive.

To make it simple install Win98 on C: and then install WinXP on D: using it's dual boot manager to boot to your OS of choice for the day.

Bryan

Really more of a question for the XP forum.

Some info on multibooting in a recent post there

SU0013 - not sure how applicable it is to your situation

I'm just looking for clues at the scene of the crime

Report Offensive Follow Up For Removal

Hi Bryan, u can do the same answer 2 lines up in the same chapter...

.. or they could read 2 lines down (asking a lot, I know)

I'm just looking for clues at the scene of the crime

Report Offensive Follow Up For Removal

Prime/critical requirement for a dual-boot '9x(ME)/W2K, and '9x(ME)/W2K is that the active Primary partiton (typically c:) = fat16 (max 2Gig) or fat32.

You have a single hardrive c:= ntfs; d: = fat32.

In that configuration you do not have the required condition, thus you cannot easily create a dual-boot environment. It can be done but requires the use of a partitioning util (e.g. System Commander (SC), Partition Magic (PM) or various others). PM has reported issues with XP; SC has none.

Cost of one these utils is close to that for a second drive; and a second drive is a better option... Creating a dual-boot with two drives would be easier and has distinct advantages...

Need more input/help - post back with which way you want to go; second drive or one of the utils.

Repartition your drive to 15/15/10 & use the 10gb E: partition for data storage. Install Win98 on the C: partition & install WinXP on the D: partition as FAT32.

jam:

That means a total restart - and it may not be a preferred route. It's possible to achieve it all using one of the utils alluded to without going that far...; or using a second drive (which may well be the easier/cheaper/more flexable option).

I realize what it means, but the prferred method is to install the older OS 1st, then XP. And if both are installed as FAT 32, they can "see" each other...plus FAT32 will run faster on the smaller partition

jam:

I agree with you overall. It's just that "our friend" may not want to go that route...

Oldest in first is generally preferable and easier.

Installing Win98 on a second HD is not really an option either, unless the new (Win98) HD is made Primary Master & the old (WinXP) drive is made slave or secondary master. Win98 needs to boot from a partition on the First Primary HD. I'm not sure what would be required to repair XP if it was moved though.

This would be relatively easy if XP was in a FAT32 partition, but being NTFS complicates things.

HTH

Dave

Have you ever noticed that if you rearranged the letters in "mother in law", they come out to "Woman Hitler?"

Simple to achieve if the new drive is Master to current XP installed drive. A minor variation on the XP repair routine will establish the required boot-loader etc. to the new ('98) Master, create the required bootsec.dos for '98 to boot in a dual-boot arangmement - and it's all up and running.

'98 will boot as c:\windows.
XP will, retaining all its current path statements, also boot (as now) as c:\winnt. '98 will not see the XP drive (ntfs areas) but XP will see the '98 drive. XP will assign a drive letter other than c: to the '98 drive when viewed from within XP. This will "not" be an issue or cause any problems for either OS.

It is really a very simple routine to a go thru'. Biggest issue; installing the new drive and resetting jumpers to reflect status of each drive correctly. Once '98 drive installed, Fdisk/format rotuine via '98 boot disk to creat both the Primary and an Extended fat32 partition (for common accessed data). This Extended can be further subdivided if so wished for the usual reasons.