atupid floppy not being detected under win nt

[fearfox]

okay for some apperant reason i had trouble installing windows nt because it would give me path error so i choose a different driver i get into windows nt screen i go to my computer and cannot find the floppy drive. i tiried two floppys in windows nt and still nothing. how do you make win nt detect your floppy

[FlyingPenguin]

Sounds like you might not have installed the floppy driver.

This can be a tough one since NT is not plug and play.

Go into COntrol Panel-> Devices and see if there's a "Floppy" device listed.

If so, make sure that the Startup for it is set to "System" and that it's currently Started.

Try forcing a manual start if need be.


Hope this helps.

[fearfox]

floopy worked before. i tiried two different floppy drives and cables and still the same thing but when i put in win98 bootdisk it boot fine. when i put a linux mandrake bootdisk it loads up fine and all the files even the windows nt boot disk load up correctly

[fearfox]

thx penguin.
first time windows nt ever acted up on me. i tried what you said it was already set to system and i forced it to start and still nothing this stupid windows nt is retarded. i switched ethernet cards in other to finish install of win nt setup then i installed the ata 66 drivers for motherboard onboard ide. it crashed. i F***n tired of windows nt crashing. it made me realize its time to upgrade win2k server. i will be purchasing win2k server edition next week when i get my paycheck.

[FlyingPenguin]

Well there's no doubt that Win2K is easier to setup, but frankly I prefer NT for a server. It's simpler and cleaner, less code bloat, and while some people have a problem with the lack of PnP, some like me find it a blessing. I never have to worry about the damn computer trying to be "smart" and re-detecting devices.

I don't know if you want to continue to follow this up for the sake of science, but something else I thought of that some people aren't aware of.

The most common reason for something not to work in NT is because you forget to re-install the Service Pack after installing a driver, service or protcol that requires copying files from the NT install CD. Not sure if youe-install the Servicnd it's a common mistake.

Unlike other Windows OSes, any time NT asks for the Install CD you must, immediately afterwards (usually after a required reboot), re-install the last service pack.

Whenever NT copies files from the install CD, it overwrites the newer service pack core files, which usually renders the functions those files are associated with unusable after a reboot until you re-install the service pack.

It's a common gotcha.

[fearfox]

hey penguin i might not be buying win2k cause my win nt finally detected my floopy drive. what happen was the floppy port on motherboard one pin was bent slightly left away from floppy cables input weird???? why did it work under dos mode. hmm weird

yipeee for floppy drive works

[FlyingPenguin]

Ahhh... it's ALWAYS pilot error

Yes, it's possible. There's probably a signal line that Windows checks that DOS apparently doesn't.

I remember once having a 486 system that would access the floppy just fine from DOS, but it would give me a device error in Win95. Turned out to be a bad ribbon.