OK. I'll b(y)te. This is some kind of joke, right? Must have stepped on
someone's
dongle (or worse). 'Rhino' rhymes with 'whiner' (almost) and probably, as
usual,
also, I was a bit to longwinded again. Actually, I try to elaborate as much
as
possible at one go in a post, to avoid to much back and forth, as that takes
up
even more of your time.
So if this is some kind of coincidence, let me be the first to apologize;
but it
does look kind of suspicious in that it appears that someone, possibly the
first
respondent or maybe some MS moderator (the kinder term), thought the question
was poignant but decided to teach me a lesson in manners and brevity by re-
submitting it here in a much shorter and more complementary form via Mssr
(alias) 'Rhino'. Am I right or am I right?
In any case, fact is, as we probably all know (unless I'm really far off base
here), I clicked on my email notification to come here, which I did but,
alas,
there was no response to my post, "System Restore lies...?", anywhere in
sight.
It took a few minutes to browse and open the copasetic responses here, which
look
like exactly what I need - except for the answers to the even more pertinant
for
me supplemental queries.
(The query from 'Rhino' just seemed such a succinct, curt, well put and
wholly to the point version of my own - and with just the right touch of
grammar deviation -that it made me suspect a ghost writer. Sorry if I'm
wrong. No offense meant).
In any case, I must thank all for your time and effort. It looks like your
input
hit the nail right on the head (hopefully for 'Rhino' as well).
No need to peruse the following if time is limited or MVP's here are not into
batchfiles and such, which might be beneath some; but, to illustrate my
point, I feel obliged, for the record, to include the following toned-down
extract from my original post, thank you.
-----------------------------------------------------------------
28-Apr-06
Win XP PRO SP2 / INTEL CELERON 2.66 GHz / 224MB RAM
System Restore (expletive deleted) - just like ERUNT says.
- - - - - - - - - - - - - - - - - - - -- - - - - - - - - - - - - - - - - -
This popular refrain came true for yours truly recently as well. Fortunately
System Restore does still have its good points.
All I wanted was to fix my batchfile problem. Somewhere in there I tried to
check my so-called 'file associations' to get the default 'Edit'or (Notepad)
altered to the much more sensible and presentable 'EDIT.COM' editor on the
right-click menu.
But the process there was so contorted, (muck deleted...) that I must have
accidentally changed the default 'Open' to EDIT.COM, instead of the default
'Edit'
to 'EDIT.COM'.
For the record, I couldn't find the "BAT" extension anywhere in the list,
neither before nor after I clicked 'new' (superfluous stuff deleted), etc.
(Regardless of the reasons, that extension should be there anyway).
(Frustrations deleted...)
Since then it's been an unending battle trying to get ANY of my batchfiles
to RUN (much less, run properly) - which is a heck of a hassle in any case,
in XP (here I was hoping for some helpful advice on use of batchfile in XP
from someone experienced in this ancient endeavor - not from any KB).
(excess deleted...)
(historical info deleted...)
Finally I decided to risk the dreaded System Restore and found, to my dismay,
that all the assurances given by the dialog boxes about "not affecting any
of your data" and so on and so forth, were ALL complete (expletive
abbreviation
deleted...). I'm wondering now, what "other" files of mine it "restored"...
(some
known issues would be helpful here).
I spent the last 10 days working on that batchfile which was to simplify
and largely automate the running of the MS OFFRHD tool from the command line,
(plus a few extra neat little features) so that multiple folders and multiple
Office files could be cleaned at once, in one session, by a single click on
the batchfile (with Menu).
Came to find out that 'Restore' did exactly that. Not only did it 'restore'
the batchfile AND it's support (... .txt) files in root to earlier mucked up
versions, but it did so also for several backups of them (derogatories
deleted) in
3 different folders - including 2 sub-folders! Fortunately I also had them on
diskette - but not quite the latest.
I had to finally un-do Restore, copy my final versions there to diskette
and then Restore again to the day before and replace the old files there
with my latest ones, manually.
(painful-to-certain-people remarks deleted...)
The saving grace was that Restore did restore the default 'file association'
settings to what they were before the fiasco. So at least all my batches can
run
now. (I won't go so far as to say 'run OK' because I'm still trying to
decipher
the Help language for the 'SET' cmnd, which looks totally beyond me and I'm
still
wondering whether it's Greek or old Latin).
There's supposed to be a way, also, to simulate "command/y/c" - which is gone
now from the lexicon - via 'SET', but Im still totally unclear on the
concept and
would greatly appreciate some clarification on this.
But I'm still as confused as ever over the process of selecting the correct
program to 'Open' (there's another one for you) / run / execute files w/ the
'BAT' extension. I could use a bit of enlightenment there from anyone who's
clearer on the concept than yours truly.
Babylon, here I come (if you think the latter word is any better).
Ted the Frustrated ...
------------------------------------------
