All of a sudden my C51 v5.50 is spewing out screen output like this: [Enter loader...In loader] PRIVATE ALLOCATION: LA 1F40000 - 270 Bytes - handle 1721DC0 PRIVATE ALLOCATION: LA 1F50000 - 46960 Bytes - handle 1721DE0 (allocated 289115 bytes for fixup info) PRIVATE ALLOCATION: LA 1FA0000 - 4F000 Bytes - handle 1721E00 PRIVATE ALLOCATION: LA 1FF0000 - FC0 Bytes - handle 1721E20 PRIVATE ALLOCATION: LA 2650000 - 35000 Bytes - handle 1721E40 LINEXE: Using DOS:Extended Startup Conditions... Leave loader...Exit loader Executing C:\C51\BIN\C51.EXE with initial registers: TSF32: prev_tsf32 0 SS 2FF DS 2FF ES 18F FS 0 GS 17F EAX 0 EBX 0 ECX 0 EDX 0 ESI 2F7 EDI 0 EBP 0 ESP 2684490 CS:IP 2F7:01FE2600 ID 00 COD 60A2798 FLG 200 CS= 2F7, USE32, page granular, limit 7FFEFFFF, base 0, acc C7FB DS= 2FF, USE32, page granular, limit 7FFEFFFF, base 0, acc C7F2 ES= 18F, USE16, byte granular, limit 100, base 6580, acc F3 SS= 2FF, USE32, page granular, limit 7FFEFFFF, base 0, acc C7F2 From my point of view, it just started doing it by itself; I didn't do anything that I know about to cause this. I have re-installed and restarted, and no change. Any idea what's up with this?
The number of environment variables or their content does not appear to be a factor. They have all been there for a long time But has their content remained unchanged in all that time? Are you sure your PATH hasn't been tampered with? Would you know if any of your environment variables' contents had been changed? And, BTW: is the environment you listed the DOS one, or the Win32 one? The two can be different. You'll have to explicitly run command.com, not cmd.exe, to get to see the DOS version.