Edit.com known bugs:

#1

..\splat\..\temp1\t2

where splat does not exist ignores splat.

#2

file entry area:

editing past eol does not display backspace before position 1.

#3

although windows DOS box allows ... and ....
edit.com does not.

(undocumented):

  windows DOS box allows any number of dots up to root.

-end-

Link.exe possible bugs:

#1

linking in similar labels in separate SUBs in a single .BAS module
confuses the linker segmentated fixups, sometimes running the wrong
label.

linking in similar labels in separate .BAS modules does also.

#2

link overlays are object modules added to the main module which are
specified to load in EMS when listed in parenthesis, for example:

Link Hexedit+(hexedit2)+...

this causes XP and other boxes to hang when EMS is not specified in
startup files Config.nt or Autoexec.nt in System32 folder because
overlays swap to disk if no EMS driver is loaded.

-end-

DOS box prompt for Windows 98:

This one IS curious after testing imbedded dots in pathnames:

Goto a directory, Say c:\tmp

Then make a directory with leading dots,
  MD "..temp"

Change to that directory,
  CD "..temp"

Make another one:
  MD "..temp"

Change to it:
  CD "..temp"

Then go one back:
  CD ..

At this point a crash box comes up, and DOS exits!

-end-

Windows XP mouse programming problems:

XP does not seem to report number of mouse clicks since last call
in DOS box.

XP mouse function to Hide/Show should work in pairs with text output
inbetween mouse calls. Hide function is reentrant (it counts number of
calls to hide, then requires same number of calls to show mouse cursor).

However, it seems (undocumented) to call number of mouse show calls also,
crashing at any text output if mouse shows counted is greater than 1
(probably because the mouse focus steps outside the dos box!?).

Best workaround is to run Mouse.com before Hexedit in a full screen
DOS box in XP when using Alt-Enter in Command.com, or use Cmd.exe instead.

-end-

BC7 compiler error:

  Parsing negative double precision does not always work, for example:

    If X#>1d-308

  doesn't compare correctly.

"Out Of Memory" error ocurrs even with systems that have plenty of RAM.
Best workaround is to move subroutines into smaller submodules.

-end-

Windows 95/98 long pathname bug:

  ASCIIZ which is C: (2 bytes) plus pathname (245 chars) plus 8.3 filename
  plus terminating nul (1 bytes) is 260 characters for windows long
  filenames.

  Truncating the drive letter and colon, and prepending any network path is
  260 minus 2 plus length of network path equals filenames longer than 260
  characters and prevents reading some 8.3 filenames in long pathnames.

  Therefore, creating any pathname at 245 characters and writing a file in
  the path, such as filetest.txt then using explorer to open the network
  icon in network neghborhood, and clicking on the subdirectories until a
  'path too long' error ocurrs, then holding Shift while clicking on the
  exit symbol in the upper right corner of the last path crashes with a
  internal error.

-end-

Windows 95/98 sharing bug:

  If drive C: is shared by selecting sharing in properties in right click of
  the C drive icon in My Computer, and a folder in C: named 'c', and right
  clicking properties and selecting sharing for folder 'c' displays a
  message 'C is already shared', then clicking OK to share folder 'c', then
  deleting the 'c' folder removes sharing properties for drive C:

Unknown facts:

  Shared folders are truncated to 12 characters, for example: 'Program files'
  would be accessed as 'program file'.

  Shared folders, such as: 'Program files' will not ambiguate to 'progra~1'
  on remote servers, only on the default server/drive.

-end-
