FAT32 file system problem

[Kevin Hatfield]

Any ideas to fix this? Thanks.

The command:
------------

dir
c:\webshare\scripts\pharmacy\data_entry_system\web_to_inven
tory\BA12*.rdr

Returns this:
-------------

Volume in drive C has no label.
Volume Serial Number is 38D8-A4C3

Directory of
C:\webshare\scripts\pharmacy\data_entry_system\web_to_inven
tory

09/11/2003 02:09p 665
BA99_user_05_14050038_09112003.rdr
09/12/2003 10:07a 442
BA12_user_XX_10030033_09122003.rdr
2 File(s) 1,107 bytes
0 Dir(s) 3,679,776,768 bytes free

 

[SunSpot]

What is it your trying to fix?
The command appears to be working as expected.

 

[Kevin hatfield]

BA12*.rdr should only display files starting with "BA12".
Note that below a file starting with "BA99" is displayed.
It isn't just the DIR command. The fso object in scripting
as well as the Search in the Win2K GUI does the same
thing. The files have never been renamed. They were
originally created through a remote FTP session. The
client FTP was a custom Active-X control using the INET
common control, the 6.0 one in VB. This problem has been
happening sporatically over the last two years since
moving from WinNT to Windows 2K Server. All volumes are
hardware serveraid 5 and formatted FAT32. The volume this
is occuring on is the root drive C and is 8GB. A checkdisk
and reboot is done weekly. Thanks for any help you can
think of.

 

[SunSpot]

Are you putting it all on 1 line, like this?
This should work.

dir
c:\webshare\scripts\pharmacy\data_entry_system\web_to_inventory\BA12*.rdr

 

[Marty List]

Any ideas to fix this? Thanks.

The command:
------------

dir
c:\webshare\scripts\pharmacy\data_entry_system\web_to_inven
tory\BA12*.rdr

Returns this:
-------------

Volume in drive C has no label.
Volume Serial Number is 38D8-A4C3

Directory of
C:\webshare\scripts\pharmacy\data_entry_system\web_to_inven
tory

09/11/2003 02:09p 665
BA99_user_05_14050038_09112003.rdr
09/12/2003 10:07a 442
BA12_user_XX_10030033_09122003.rdr
2 File(s) 1,107 bytes
0 Dir(s) 3,679,776,768 bytes free

The other files may be showing up because of their short file name (8.3
SFN). Wildcard matches are done against both the LFN and the SFN.
Sometimes this is a good thing, sometimes it's a bad thing.

Try using the same DIR command with a "/X" switch, this will display the
SFNs and may shed some light on what's going on.

 

[kevin hatfield]

I thought I knew every switch to DIR from my first PC
with DOS 5. Sure enough DIR BA12*.rdr /X showed that both
files in their short names begin with BA12.

'dir BA12_*.rdr' does the trick though, at least for now.
Thanks.

I double-checked and this occurence was just the DIR
command producing these odd results. Last year there was
at least once that this caused the same symptoms with the
Search through the GUI and the filesystem object in
scripting. It was on two files with the same naming scheme
in the same folder, one starting with AA10 and another
AA07. Weird.