Filename conventions in uV2 v2.36

This is not a bug, but it bugs me!

In my M51 map file, some files are shown on the included command line as residing in ".\filename.obj" and others as just "filename.obj", even though they are all in the same place and uV2 shows them as being in the same place.

The linker seems to be just echoing what the uV2 project builder is telling it, but what does it mean?

Also, I type in all my .c and .h filenames in lower case, but uV2 will sometimes show the name.ext in all caps, just the extensions in caps, or just the name in all caps. I wonder why.

I am using Windows NT 4.0, svc pak 6a, and am using networked file shares.

Thanks in advance for any clues.

George

Parents
  • You ask,
    "uV2 will sometimes show the name.ext in all caps, just the extensions in caps, or just the name in all caps. I wonder why?"

    You say,
    "I am using Windows NT 4.0..."

    You should be used to it then!
    It's a feature of the PC/MS-DOS/Windows;
    Microsoft operating systems are not case sensitive, but may preserve case when storing/displaying filenames.

    Haven't you noticed how NT sometimes insists on using lowercase with a capital initial, irrespective of how you try to force it otherwise?!

Reply
  • You ask,
    "uV2 will sometimes show the name.ext in all caps, just the extensions in caps, or just the name in all caps. I wonder why?"

    You say,
    "I am using Windows NT 4.0..."

    You should be used to it then!
    It's a feature of the PC/MS-DOS/Windows;
    Microsoft operating systems are not case sensitive, but may preserve case when storing/displaying filenames.

    Haven't you noticed how NT sometimes insists on using lowercase with a capital initial, irrespective of how you try to force it otherwise?!

Children
More questions in this forum