dir/s/A results come out unreadable in win 8, but not in win xp

[Deon]

Hi, when I run:  dir/s/A c:\FileStructurePrev\ >C:\FileStructure\FileStructureSize.txt
in windows 8 result in unreadable re file size, see below:
RESULT!
 Volume in drive C has no label.
 Volume Serial Number is 6EA5-4BCA

 Directory of c:\FileStructurePrev

2017-01-18  09:23 AM    <DIR>          .
2017-01-18  09:23 AM    <DIR>          ..
2016-10-18  09:38 PM            32ÿ032 error messages plus.docx
2002-10-18  02:19 PM               195 filestruc.bat
2002-10-18  02:20 PM         1ÿ588ÿ209 filestruc.txt
2004-03-07  03:26 AM           275ÿ792 FileStrucSize.txt
RESULT THE FILE SIZE IS UNREADABLE. How do it solve this problem? Thank you.

[DaveLembke]

What happens if you run this without passing the output to file. Do you see the ÿ character in the file sizes when its run at command prompt and info passed to display vs to file?

Code: [Select]

dir/s/A c:\FileStructurePrev\
Also where did this Windows 8 come from. Is it a download off the internet which was installed or came with computer? Asking this because I have seen people get Windows off of a torrent and have issues like this.

[Deon]

This is a genuine package with cd's for 32 and 64bit of microsoft windows 8 prof. Screen display is perfect. When I open the file, it is unreadable.  You can test this by running dir>list.txt in any directory and open the file in that directory list.txt. It is unreadable. Thanks.

[patio]

Works fine here...

[BC_Programmer]

I tested this in a VM as well, and the output file looks fine. Is your system set to a language other than english? It seems that in your problematic output, the comma's are unicode characters.

[Deon]

Problem solved, I changed the language from English(South Africa) to English(UK).
Result.
18/10/2016  21:38            32,032 error messages plus.docx
18/10/2002  14:19               195 filestruc.bat
18/10/2002  14:20         1,588,209 filestruc.txt
Thank you.

[patio]

Nice catch BC Programmmer...

[DaveLembke]

Yes nice catch ...  I didnt even think about that. I saw the ÿ character as corruption vs a write to file translation of unicode. Learned something new.