XP Install: Doesn't Recognize 3.5" A:?

[gmgq]

I don't remember this happening before, but recently when I tried to install WINXP, it doesn't recognize my A:. But when I boot with a boot disk, A: is fine.

I need to use A: while installing XP because I need to load the HighPoint controller drivers (or else it won't see my HDs).

The thing is, my A: is actually a LS-120 IDE drive. But I'm sure it was recognized before.

I think the only thing that's changed recently is that I formatted my C: to NTFS. Would that make a difference?

Is there something I need to set in the BIOS? It's currently set to no floppies, but boot order is LS-120, HD0, CDROM. I've tried enabling the floppy A:, but that didn't make a difference.


FYI, my system is:

P3-800
ABIT BE6-II mobo
768MB RAM
IDE1-4: CDROM, CDRW, LS-120
IDE5-8: HD0, HD1, HD2

[NDC]

If I remember correctly, you need to DISABLE the floppy disk controller in the BIOS to make LS-120 drives work in Windows XP... Give it a go and let me know...

[Mntsnow]

I need to load the HighPoint controller drivers (or else it won't see my HDs)

How do you have the BIOS set for the HD's (boot order subsection?) pertaining to "standard IDE or ATA100/raid options"?

I've installed XP many times and XP has native support for the Highpoint controllers built in....

[NDC]

Yeah, that's true. XP does automatically detect HPT370 controllers. As for HPT366, that's not the case though... Strange isn't it? HPT366 was released before HPT370 but you have to load the driver manually! :confused:

[gmgq]

Now you're saying that if I disable the Flopy disk controller, then the WINXP SETUP (the initial setup with the blue background, and gray bar across the bottom in a DOS screen) will recognize my LS-120 as the Floppy A:?

Interesting, I will give that a go when I get home tonight.


BTW, I have installed XP about a week ago. I just got fed up and hooked up a real 3.5" floppy to the system just so that XP could read the HPT366 drivers. I just need to reinstall it now, because something's messed up, and I get these X minute delays when loading some things.

Anyways, inside WINXP, it recognizes the LS-120 drive as FLOPPY B:. But I remember the last time I installed XP (several months ago), it recognize the LS-120 as a Removable Media Drive (after my HD's, so like F: or something). So if I disable the Floppy drive controller in the bios, will XP recognize it as a Removable Media Drive again (which would be more accurate)? But it will still recognize it as Floppy A: during the initial install...?


Originally posted by NDC
If I remember correctly, you need to DISABLE the floppy disk controller in the BIOS to make LS-120 drives work in Windows XP... Give it a go and let me know...

[gmgq]

Yeah, it really Sucks to have to dig out the Old HPT366 floppy disk every time I reinstall the OS. Seems so archaic, heh.

Originally posted by NDC
Yeah, that's true. XP does automatically detect HPT370 controllers. As for HPT366, that's not the case though... Strange isn't it? HPT366 was released before HPT370 but you have to load the driver manually! :confused:

[Mntsnow]

GMGQ Please turn off email notifications as something is wrong with your email address or your email account as the messages are getting bounced back to me as I'm the admin/postmaster.

Delivery failed 20 attempts: gmgq@home.com


Original message follows.

Received: by xtremepccentral.com
id ABA14B0142; Tue, 05 Mar 2002 21:31:29 -0700
Date: Tue, 05 Mar 2002 21:31:29 +0700
Subject: Reply to post 'XP Install: Doesn't Recognize 3.5" A:?'
To: gmgq@home.com

[gmgq]

Sorry Mntsnow, I didn't realize that it was still set to that defunk @home.com address. It's been updated now. Sorry for the inconvenience.

[gmgq]

NDC, disabling the Floppy Controller in the BIOS WORKED. I briefly tried the WINXP setup again, and it was able to recognize the LS-120 as A:. Thanks!!

Guess I can spend the weekend reinstalling it now ;)

[NDC]

Great! Hopefully it's smooth sailing for you from here on! ;)

[Mntsnow]

Thanks for fixing the email addy :)

And glad NDC got you going :)

[gmgq]

Well after I got the floppy drive working, and was able to install the HPT366 drivers, XP appeared to install smoothly. But afterwards, when it tried to start it up for the first time, I end up with a BSOD. Basically:

"The problem seems to be caused by the following file: framebuf"

blah blah blah, "The device driver got stuck in an infinite loop." blah blah blah

"*** STOP: 0x000000EA (0x8228A9F0, 0x822C17C0, 0x823AF790, 0x00000001)"

Rebooting results in the same BSOD. I tried to reinstall XP again, deleting the partition and reformating it, same problem.

I disconnected the LS-120 and plugged in a regular 3.5" floppy for the install (what I did a few weeks ago, which worked), but I still end up with the same BSOD!

Also, it seemed kind of slow when copying files from the CD... The installation took at least 2 hrs (didn't actually time it). The progress bar was going Very slowly... I don't recall it being so slow before...? Or am I just imagining things?

The only thing different I did a few weeks ago, was reformat each of my 3 HD's. But I only have minimal data on them right now, and I don't see how it can make a difference...?

Any ideas what this "framebuf" BSOD is about? TIA.

[Mntsnow]

Have you checked to make sure you have the most up to date drivers for the controller?

[gmgq]

Originally posted by Mntsnow
Have you checked to make sure you have the most up to date drivers for the controller?

Actually I tried the latest HPT366 drivers before, and they didn't work with my ABITBE6-II mobo for some reason.

But OMG, I just figured out what the problem was. For some reason, the CPU L1 CACHE was DISABLED in the BIOS! That's why the installation took so long. I'm thinking the system was so slow, that it probably 'thought' that the framebuf was stuck in an infinite loop.

When I enabled it and rebooted, everything was SO much faster. And as I type, the other computer has resumed it's installation of WINXP.

Thanks anyways! Better jot this down somewhere for future reference ;)

[Mntsnow]

LOL Glad your on your way again! :)

[unisol]

can you tell me how do you enable on CPU cache in bios?

I am having similar issue with DELL Optiplax Gxa 300 system.
I am trying to upgrade my harddrive to 40G Maxtor
with bios A10. I have also installed PNY 128/100 SDRAM memory.
and when it trys to setup winxp, after copying all the files I get framebuf error.

Appreciate any suggestions

- Thanks
Unisol

Originally posted by gmgq
Actually I tried the latest HPT366 drivers before, and they didn't work with my ABITBE6-II mobo for some reason.

But OMG, I just figured out what the problem was. For some reason, the CPU L1 CACHE was DISABLED in the BIOS! That's why the installation took so long. I'm thinking the system was so slow, that it probably 'thought' that the framebuf was stuck in an infinite loop.

When I enabled it and rebooted, everything was SO much faster. And as I type, the other computer has resumed it's installation of WINXP.

Thanks anyways! Better jot this down somewhere for future reference ;) how do you turn on CPU cache in bios enable

[Mntsnow]

Welcome to XPC Unisol.

I'm not sure if the Dell Bios will allow you to change the cache but it should be on by default. Enter into the bios at bootup and under the advanced properties you should be able to see if it is or not.

[unisol]

Thanks Mntsnow, i will check this tonight.
But do you think that this setting is cause of framebug error or do you suggest other things besides checking cpu cache settings?
Also I recall seeing bios memory exclusion settings in the setup.
Previosly I had 16m sdram and that setting was set to 15-16 M.
When I upgraded to 128M SDRAM I changed this setting to none.
Should I change it back to 15-16M?
Also I get warning one or more of your DIMM is out of REV when machine boots up. what does this mean?

- Unisol

[ardora]

I'm having the same problem that this thread was originally about..

I just have one question.. How do you disable the floppy controller in the BIOS? ^^;

[NDC]

Welcome to XPC, ardora! :)


Go into the BIOS and go to the Standard CMOS Setup page and you will see DRIVE A: and DRIVE B:. Simply select none...

[diablo243]

Originally posted by gmgq
But OMG, I just figured out what the problem was. For some reason, the CPU L1 CACHE was DISABLED in the BIOS! That's why the installation took so long. I'm thinking the system was so slow, that it probably 'thought' that the framebuf was stuck in an infinite loop.

I had the same infinate loop problem and it was driving me nuts!!!!!! I tried for days to firgure it out. I researched every manufacturor of every peice of hardware untill I found this post. and low and behold... it was the cache turned off in the bios! Your are the only person on the internet that has had and resolved this issue. Thanks for the help you have saved my insanity and I'll be sure to check this forum first from here on in!

-Cheers!

[Anya20]

Much THANKS!!! to gmgq and diablo243!!! I had the same WinXP install error framebuf / infinite loop crap, and sure enough after weeks of frustration I found your posts and changed the CPU L1 and L2 cache to Enabled instead of Disabled in the BIOS, and BINGO! Success...Finally...What a pain in the butt...Thanks again guys...

[jarvis_the_1]

GMGG......many many thanks for sorting this problem. I have been having this problem for ages now and i've never been able to find an answer for it....until now!!! I agree that you're the only person who has found a solution for this so well done. This forum has just gained a member.

Thanks again guys
Nick

[Cowboybooter]

Good to hear,

Welcome to XPC, jarvis the 1 ! :)

:)

Bob