Garbage Characters in VSS Path Using v4.1

[LotsaCabo]

When looking at the path to the VSS database, there are garbage characters in the path. This worries me a great deal. I have seen people complaining about this with v3.5.x of the product, and with older databases, but neither apply to me.

Here are the facts...

1. Brand new install of v4.1
2. Brand new VSS database created with VSS Admin v6.0d
3. When looking at the status, through a browser, it shows:

250
Protocol-Version:2.0
Message-ID:00000000
Database Aliases:VSSTest01
Content-Length:43
Key Length:16

Í}ɸ~õ,«É(”=ÍüßC:\vsstest01\srcsafe.ini

4. I am running the following configuration...

Dell Latitude C840
1 drive with 3 partitions (system, data, and swap)
1 GB RAM
1 DVD-CDROM, 1 floppy
Drive was partitioned using Patition Magic v8.0
Windows XP SP2

5. I have tried both simple (8.3) and extended paths.

I have used SOS for years and never recall seeing garbage in the database path before. I don't even want to TOUCH the database, nor pull in my existing files, until I can see it working correctly.

Please advise... quick.

Thanx,
Ryan

[LotsaCabo]

Okay, well, it's fixed, but I would like to know why?

To fix it, I basically just ran a thorough defrag and all went back to normal. My only question is...

Why the heck is SOS so sensitive? If I pull anything from the hard drive, using any development environment, I can get clean data; filenames, file contents, volume info, etc. So, how is it that the underlying code for SOS cannot get the same data?

Thanx,
Ryan

[lbauer]

Why the heck is SOS so sensitive?

We've seen garbled characters in the path name when telneting to the secure port.

Other than that, we don't know why the garbled characters would appear in the result of a telnet command.

We've never had any reports of the garbling interfering with any SOS operations.