🚀 go-pugleaf

   Here is a message I ran across on a local bulletin board.  Has anyone
else had this problem?

===============================================================================

	I've have a problem with DOS 2.5 in enhanced density mode. When the
disk is very full (exceeding the old single density boundry) and you do a BASIC
SAVE command which replaces a file located in the extended disk area, the file
is actually written starting at sector 1! This has the usual tendancy to make
DOS and DUP and the directory real sad when you write over them. Of course you
cannot reboot from this disk again. The boot sectors are always killed.
Depending on how large the SAVEd BASIC program was determines whether DOS and
DUP are smashed.
	I got the DOS 2.5 kit from CompuSlave. It works just fine in single
density mode. And I haven't noticed a problem in predeleting (or renaming)
the original file and then SAVing the new copy to disk.
	Has anyone else experienced this phenominon? I can reproduce at will
and use one of the DISKDX programs to examine the directory pointers. I suspect
the logic is still checking the old 707 sector size and assuming anything over
that must be a mistake, so resets the sector to the beginning.

===============================================================================

   If anyone else has seen this problem or knows of a solution, please let us
know.

	Bill Endter
	...decvax!decwrl!dec-rhea!dec-wr1for!endterbi