NviGate Systems
Well-Known Member
- Reaction score
- 1,164
- Location
- Vancouver
It's been a while, but you can simply echo the entire screen (dos characters) from any cmd commands you run and pipe that into a text file. Store that text file in the temp folder and your batch can simply open that text file after all commands are done.
Now, I might be putting my tinfoil hat on here, but if you are running things like repair scripts as part of a routine check for every PC you work on, you are bound to hit a bug. My first rule these days is if it's not broke don't fix it. Just because a tool exists doesn't mean you can use it daily. I mean, look at horror stories from chkdsk, something many folks would have thought nothing about running.
I always verify the hardware first. That eliminates further errors and degradation. Then once any hardware issues are fixed, I can look at software. I only look into what doesn't work.
There was a time when techs were obsessed (me included) with endless tuneups and tweaks, optimizations. But those days are gone. In fact doing those things can cause more headaches than they solve.
My 2 cents.
Now, I might be putting my tinfoil hat on here, but if you are running things like repair scripts as part of a routine check for every PC you work on, you are bound to hit a bug. My first rule these days is if it's not broke don't fix it. Just because a tool exists doesn't mean you can use it daily. I mean, look at horror stories from chkdsk, something many folks would have thought nothing about running.
I always verify the hardware first. That eliminates further errors and degradation. Then once any hardware issues are fixed, I can look at software. I only look into what doesn't work.
There was a time when techs were obsessed (me included) with endless tuneups and tweaks, optimizations. But those days are gone. In fact doing those things can cause more headaches than they solve.
My 2 cents.