Regedit help?

  • Thread starter Thread starter Kenny
  • Start date Start date
There is documentation on it "out there" that I read a couple years ago
about the "flag" bit. We had found the "fix" previously by observing
that whole boxes of new floppys sent to the field (DOS and Win95 PC's)
in boxes would be unreadable on the Windows 2000 PC's in the office, BUT
floppys formatted at the office(on Win2K) and then sent out ALWAYS came
back readable. And that's what I know of it.

Mark said:
In microsoft.public.win2000.registry Bob I wrote:

In Win2k the problem seems to mainly be that the floppy has what I
will call a "sloppy format" a flag doesn't get set and so Win2K
thinks that it isn't formated. Formating the floppy in the Windows
2000 PC sets the flag and then all is good. After windows 2000
formats it it can be read at all PC's including Windows98
[ ]

Interesting. Bob, do you have any details or references? Not doubting
it, just curious as to the particulars.

And I am guessing you meant that W9x does the "sloppy format".

I seem to recall (perhaps poorly) that there was a problem in W95 and
some different problem in NT4 SP0...but it's been a long time. :-)
 
In said:
There is documentation on it "out there" that I read a couple
years ago about the "flag" bit. We had found the "fix" previously
by observing that whole boxes of new floppys sent to the field
(DOS and Win95 PC's) in boxes would be unreadable on the Windows
2000 PC's in the office, BUT floppys formatted at the office(on
Win2K) and then sent out ALWAYS came back readable. And that's
what I know of it.

Thanks "Bob I", I've not the time to dig it up and no effect here
anyway.

Mark said:
In microsoft.public.win2000.registry Bob I wrote:

In Win2k the problem seems to mainly be that the floppy has what
I will call a "sloppy format" a flag doesn't get set and so Win2K
thinks that it isn't formated. Formating the floppy in the
Windows 2000 PC sets the flag and then all is good. After windows
2000 formats it it can be read at all PC's including Windows98
[ ]

Interesting. Bob, do you have any details or references? Not
doubting it, just curious as to the particulars.

And I am guessing you meant that W9x does the "sloppy format".

I seem to recall (perhaps poorly) that there was a problem in W95
and some different problem in NT4 SP0...but it's been a long
time. :-)
 
In said:
There is documentation on it "out there" that I read a couple
years ago about the "flag" bit. We had found the "fix" previously
by observing that whole boxes of new floppys sent to the field
(DOS and Win95 PC's) in boxes would be unreadable on the Windows
2000 PC's in the office, BUT floppys formatted at the office(on
Win2K) and then sent out ALWAYS came back readable. And that's
what I know of it.

Thanks "Bob I", I've not the time to dig it up and no effect here
anyway.

Mark said:
In microsoft.public.win2000.registry Bob I wrote:

In Win2k the problem seems to mainly be that the floppy has what
I will call a "sloppy format" a flag doesn't get set and so Win2K
thinks that it isn't formated. Formating the floppy in the
Windows 2000 PC sets the flag and then all is good. After windows
2000 formats it it can be read at all PC's including Windows98
[ ]

Interesting. Bob, do you have any details or references? Not
doubting it, just curious as to the particulars.

And I am guessing you meant that W9x does the "sloppy format".

I seem to recall (perhaps poorly) that there was a problem in W95
and some different problem in NT4 SP0...but it's been a long
time. :-)
 
Interestingly enough I just came across a PC that in the BIOS the flopy
could be set as a 3-way or a 1.44 3.5. That would be a possible fix for
those having the 3-way floppy issue in XP.

Mark said:
In microsoft.public.win2000.registry Bob I wrote:

There is documentation on it "out there" that I read a couple
years ago about the "flag" bit. We had found the "fix" previously
by observing that whole boxes of new floppys sent to the field
(DOS and Win95 PC's) in boxes would be unreadable on the Windows
2000 PC's in the office, BUT floppys formatted at the office(on
Win2K) and then sent out ALWAYS came back readable. And that's
what I know of it.

Thanks "Bob I", I've not the time to dig it up and no effect here
anyway.


Mark V wrote:

In microsoft.public.win2000.registry Bob I wrote:



In Win2k the problem seems to mainly be that the floppy has what
I will call a "sloppy format" a flag doesn't get set and so Win2K
thinks that it isn't formated. Formating the floppy in the
Windows 2000 PC sets the flag and then all is good. After windows
2000 formats it it can be read at all PC's including Windows98



[ ]

Interesting. Bob, do you have any details or references? Not
doubting it, just curious as to the particulars.

And I am guessing you meant that W9x does the "sloppy format".

I seem to recall (perhaps poorly) that there was a problem in W95
and some different problem in NT4 SP0...but it's been a long
time. :-)
 
Interestingly enough I just came across a PC that in the BIOS the flopy
could be set as a 3-way or a 1.44 3.5. That would be a possible fix for
those having the 3-way floppy issue in XP.

Mark said:
In microsoft.public.win2000.registry Bob I wrote:

There is documentation on it "out there" that I read a couple
years ago about the "flag" bit. We had found the "fix" previously
by observing that whole boxes of new floppys sent to the field
(DOS and Win95 PC's) in boxes would be unreadable on the Windows
2000 PC's in the office, BUT floppys formatted at the office(on
Win2K) and then sent out ALWAYS came back readable. And that's
what I know of it.

Thanks "Bob I", I've not the time to dig it up and no effect here
anyway.


Mark V wrote:

In microsoft.public.win2000.registry Bob I wrote:



In Win2k the problem seems to mainly be that the floppy has what
I will call a "sloppy format" a flag doesn't get set and so Win2K
thinks that it isn't formated. Formating the floppy in the
Windows 2000 PC sets the flag and then all is good. After windows
2000 formats it it can be read at all PC's including Windows98



[ ]

Interesting. Bob, do you have any details or references? Not
doubting it, just curious as to the particulars.

And I am guessing you meant that W9x does the "sloppy format".

I seem to recall (perhaps poorly) that there was a problem in W95
and some different problem in NT4 SP0...but it's been a long
time. :-)
 
Still watching this. Whilst I appear to have solved it on my own PC others
I know are still having the same problem.

--

Kenny


Bob I said:
Interestingly enough I just came across a PC that in the BIOS the flopy
could be set as a 3-way or a 1.44 3.5. That would be a possible fix for
those having the 3-way floppy issue in XP.

Mark said:
In microsoft.public.win2000.registry Bob I wrote:

There is documentation on it "out there" that I read a couple
years ago about the "flag" bit. We had found the "fix" previously
by observing that whole boxes of new floppys sent to the field
(DOS and Win95 PC's) in boxes would be unreadable on the Windows
2000 PC's in the office, BUT floppys formatted at the office(on
Win2K) and then sent out ALWAYS came back readable. And that's
what I know of it.

Thanks "Bob I", I've not the time to dig it up and no effect here
anyway.


Mark V wrote:


In microsoft.public.win2000.registry Bob I wrote:



In Win2k the problem seems to mainly be that the floppy has what
I will call a "sloppy format" a flag doesn't get set and so Win2K
thinks that it isn't formated. Formating the floppy in the
Windows 2000 PC sets the flag and then all is good. After windows
2000 formats it it can be read at all PC's including Windows98



[ ]

Interesting. Bob, do you have any details or references? Not
doubting it, just curious as to the particulars.

And I am guessing you meant that W9x does the "sloppy format".

I seem to recall (perhaps poorly) that there was a problem in W95
and some different problem in NT4 SP0...but it's been a long
time. :-)
 
Still watching this. Whilst I appear to have solved it on my own PC others
I know are still having the same problem.

--

Kenny


Bob I said:
Interestingly enough I just came across a PC that in the BIOS the flopy
could be set as a 3-way or a 1.44 3.5. That would be a possible fix for
those having the 3-way floppy issue in XP.

Mark said:
In microsoft.public.win2000.registry Bob I wrote:

There is documentation on it "out there" that I read a couple
years ago about the "flag" bit. We had found the "fix" previously
by observing that whole boxes of new floppys sent to the field
(DOS and Win95 PC's) in boxes would be unreadable on the Windows
2000 PC's in the office, BUT floppys formatted at the office(on
Win2K) and then sent out ALWAYS came back readable. And that's
what I know of it.

Thanks "Bob I", I've not the time to dig it up and no effect here
anyway.


Mark V wrote:


In microsoft.public.win2000.registry Bob I wrote:



In Win2k the problem seems to mainly be that the floppy has what
I will call a "sloppy format" a flag doesn't get set and so Win2K
thinks that it isn't formated. Formating the floppy in the
Windows 2000 PC sets the flag and then all is good. After windows
2000 formats it it can be read at all PC's including Windows98



[ ]

Interesting. Bob, do you have any details or references? Not
doubting it, just curious as to the particulars.

And I am guessing you meant that W9x does the "sloppy format".

I seem to recall (perhaps poorly) that there was a problem in W95
and some different problem in NT4 SP0...but it's been a long
time. :-)
 
Back
Top