If I do:
shsucdx >a.txt ,
it creates the 'a.txt' and redirects the output into a.txt;
but if I do this:
vol h: >a.txt,
it creates the a.txt, but the file is empty; what is more, the output o
f'vol' goes to the screen, so is not being redirected.
I tried this with msdos with the same result. If this is a bug in vol, is
there an easy way around it?
The shsucdx only detects physical drives; I need to also detect all logical
drives present.
------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
endpoint security space. For insight on selecting the right partner to
tackle endpoint security challenges, access the full report.
http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
