/ Sign-up
Your question

ASUS A7V333 - Trouble installing WIN98 SE

  • Motherboards
  • Asus
Last response: in Motherboards
January 16, 2003 1:08:50 PM


I have the ASUS A7V333 and I think there are variations of this motherboard, so I'm not sure which one I've got.

The problem is when I formatted my WinXP hard drive to install Win98 SE, a dialogue box appeared during installation stating something about a driver needed for "IEE-1394" or "IEE - 1384". I'm not sure which one but it did look like something beginning with "IEE...".

My question is - What is it and where do I find the driver?

I skipped the driver and my computer froze. Everytime it boots up, the monitor doesn't respond.

It's being repaired now, so to not make the same mistake again, I will be very grateful if you could give me some tips on how to install Win98 SE successfully on the following system:

ASUS A7V333 (not sure about which variation it is)
AMD XP2200+
Maxtor DiamondMax 9 60Gb

Installing Win98 SE on my Gigabyte GA-7VTXE always goes smoothly.

Any ideas why it crashed and never booted up right - was it related to the fact I skipped the IEE.. driver installation?


More about : asus a7v333 trouble installing win98

January 16, 2003 1:10:48 PM

shot in the dark: did you format it FAT32 or NTFS? if NTFS it might be causing your problem...

<i>It's always the one thing you never suspected.</i>
January 16, 2003 1:16:16 PM

That was quick!!!

Very good point. Formatted while it was in NTFS mode.
What should I do now..

Tell the repair man - mght invalidate warranty though, or
Install WinXP when I get the computer back - I prefer Win98 SE though

Related resources
January 16, 2003 1:22:33 PM

Win98 doesn't have native drivers for Firewire devices (otherwise known as IEE-1394). If you have onboard Firewire, then you should be able to find the drivers on the CD that came with your motherboard.

:eek:  Call me - 1 900 MAN-MUCK :eek: 
January 16, 2003 2:00:39 PM

Thanks, but have I damaged my hard drive. I formatted it while it had winXP in NTFS mode.

If there is anything else that I should know about installing Win98 on this motherboard - please let me know.

One more thing though - Now that the HD is formatted, is it in FAT32 mode - FDISK recognises it as one FAT32 partition, so I'm not sure why it crashed so badly when I first installed Win98 SE (tried to install).

January 16, 2003 2:17:24 PM

Found a pic of my motherboard <A HREF="" target="_new">;/A>
And here is another version with serial ata ports and a 1394 HEADER
<A HREF="" target="_new">;/A>
The 1394 HEADER, which I haven't got, is located just to the bottom left of the mouse/keyboard ports - that white rectangular socket.

So if I haven't got this 1394 HEADER, why did the computer request drivers for it. And why did the computer come with firewire ports?

I got a feeling that I'll have the same problem when I get my computer back and try to install Win98 SE again.

January 16, 2003 2:21:59 PM

Any chance you could disable the onboard Firewire in BIOS, assuming there are BIOS settings for it? I know that you don't actually have the hardware on board but there's a chance it might still be included as a BIOS setting.

:eek:  Call me - 1 900 MAN-MUCK :eek: 
January 16, 2003 2:29:24 PM

try to delete and recreate the partition, then format FAT32 (if I'm understanding you correctly)

<i>It's always the one thing you never suspected.</i>
January 16, 2003 2:47:10 PM

I have 3 firewire ports at the back and 1 at the front and they were plugged in somewhere on the motherboard, so somehow my motherboard has firewire capability.

I'm looking at screenshots of the BIOS menus in the manual and I can't find anything firewire/IEE 1394 related.

There are many jumpers on the board though, but if there is no IEE 1394 socket, I assume that there won't be a jumper for it.

January 16, 2003 3:01:16 PM

Right now the hard drive has 1 formatted FAT32 partition that FDISK recognises. I should be ready to install Win98 SE then, shouldn't I?

Still not sure why it crashed. Maybe I'm making a big deal about this IEE 1394 device. But that is where the problem started. What usually causes a monitor to not respond at bootup? - I used the troubleshooter at and found out that it was a faulty device on the motherboard but WinXP worked fine when it was installed. Hmmmmmmmm