|
[x]
Posted via EE Mobile
|
|
| Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again. |
|
|
|
|
|
[x]
The Solution Rating System
|
|
| With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating. - The Grade of the Solution
- The Zone Rank of the Expert Providing the Solution
- The Number of Author and Expert Comments
- The Number of Experts Contributing
- The Feedback of the Community
Your Input Matters Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site. If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support. Thank you! |
|
|
|
|
Asked by For-Soft in Windows 98 Operating System, Windows 2000 Operating System, MS DOS
I'm trying to create an empty (0 length) file with a batch script.
The biggest problem is the fact DOS, Windows 98 and Windows 2000 do handle such situations differently.
Windows 2000 will copy a 0 length file with a copy command. On the other hand the Windows 98 or DOS will display "0 files copied" message in such a case.
Windows 98 is able to create an empty file with such a command:
if>empty.txt
Windows 2000 will just say the > character was unexpected here.
I'm trying to find a solution working in DOS, Windows 95, 98 and 2000.
20090824-EE-VQP-74 / EE_QW_2_20070628