Can network software be setup to object to reading from a removable device? My friend was given a system which I think was originally on a network. Can such a system bootup without the Network server?

Last night I tried to copy some data from a 1.44MB diskette to his hard disk. I got a message something like the following.Unable to read from this device.I have seen the Abort, Retry, Fail? message, and this is not it. I have never seen this message.

My friend claimed that he was able to read other diskettes, so I tried to copy some files from one of his diskettes. I got the same message. We gave up and went on to other work he wanted done on his PC.

I am certain that the diskettes are okay, so the problem must be with his system. Does anybody have some thoughts on this?

Today, I started thinking about his system. I think that one file was copied before the message occurred. Then I wondered if network software could be setup to not allow reading executable files from removable media, which is a reasonable restriction to avoid various problems with unreliable and/or stupid users.

sounds like your trying to read a disk that was formated on Example:::
fat32 to ntfs or ntfs to fat32? Which one won't read the other.

Is this the case? or are they both ntfs? or both fat

seems this was on a network were these Encripted disks?

Diskettes created on Win98SE system and tried to read on Win98SE system.

Am certain that diskette format is not the problem. The diskette can be read from my system, so it is okay. I did not check, but assume his system is new enough that his reader can read 1.44MB diskettes. The 720KB diskettes are ancient history now, are they not? I have not seen one for at least ten years.

Since I did not get the Abort, Retry, Fail? message, I assume that the message came from some special driver used by the OS.

Thats an error i'm not real familiar with let alone find anything on it?
so I'm just grabbing at straws here.

I would guess the next thing i would check on it would be the floppydrive it's self(try it on another machine) Known working.

I assume that the message came from some special driver used by the OS.

Thats possable


could try a few of these steps? see if it is a floppy controller?
http://support.microsoft.com/default.aspx?scid=KB;en-us;q131690

Have you looked at floppy drive settings in the CMOS? If you try and can't get into the CMOS, then it is probably an artifact from being on network. I would then reset the CMOS and try again.

Budfred

why not try to clean the disk drive first, can't hurt

On his computer try formatting and writing to a floppy. Then see if you can read it on his computer. You probably will be able to.

Then try to read it on another computer. Probably won't work.

The point is when floppy drives get old, they get out of calibration, so that data can be read by the floppy drive that wrote it, but not by another drive.

The cure is to buy another $10 drive.

What is the OS in the comp, if its 2000/XP on NTFS partitions its likely that foppy access is disabled. Yes, software can do that I mean limit certain types of access, allow and disallow this and that specially on network environment and NTFS partitions.