China DOS Union

If it can be done to pack the used third-party files into the BAT file itself, generate temporary files in the temp directory during operation, and then call them, that would be almost okay. If it's just compressed into a compressed package together with the BAT file, it's not very convenient to use.

Voting seems to be of little significance. Release the work and let real users evaluate it.

Originally posted by lianjiang2004 at 2009-4-8 01:31:
The vote doesn't seem to be of much significance.
Release the work and let real users evaluate it.

From the current voting situation, most people support it.

I will consider finishing "Xiao Qiang System Optimization Tool 3.0". Regarding the pop-up window issue, no one has given an answer yet. If I continue to work on it, I will continue with the initial idea I had.

Graduated, just started working today. Maybe I won't have much time in the next few days. Sorry.

I will release it as soon as it's done.
Just like what Brother lianjiang2004 said, let real users evaluate it.

If it's for others, make the interface nice~
Of course, if it's for yourself, as long as you know how to use it, that's enough

Not sure. Practical is enough. Good-looking interface, but it will occupy system resources, which is actually not worth the loss.

If shown to others, it should be a bit better - looking, but it doesn't matter if it's just for personal use

First of all, bat only makes us complete the tasks that should be completed. It is not a very complicated program. Why do we need cmd if we want a beautiful interface? What's the use of flashy and useless things?

3 parties also depend on the situation. If the purpose of the script is dispensable, then naturally...

Some practical 3rd parties can be added without any problem. There's no need to copy them to the system; just call them with relative paths...

choice and MD5 are both very practical. But choice doesn't directly bring set /P

This depends on the trade-off. Using 3rd parties for the interface is not recommended.

But since it's done, posting it for collection or something is not bad, but for application,
at least I wouldn't use it.

Personally, I think that a good batch script, combined with a good GUI, isn't that perfect?

Whether to add a GUI depends on the purpose of this batch file! So I voted for the undecided option!

There is no need to use Windows. I need a menu that can be used with DOS 7.1

Regarding whether the interface should be well - done or not, first of all, I think that being well - done doesn't mean just being good - looking, but rather it should be more in line with reality. A batch processing, which has different requirements according to its function and the different user groups it serves.

It's good that it's easy for people to use, and the interface should be as simple and clear as possible.

A beautiful interface can make people feel comfortable, just like when the gorgeous Windows XP first came out.

It's easy for you to say. You have to see in what environment it's done. Making a graphical interface with batch processing is too resource-consuming. Not to mention making your program bloated, the CPU will definitely be at 100%, and the most important thing is the speed...

Although existing third parties can barely achieve a little effect, the speed of handling the interaction between users and BAT is really too slow.

Unless MS introduces a cmd.exe or something that supports graphical commands.