Windows 7 startup logo lost

[Gene E. Bloch]

No, I've criticized your attitude (apparently I was too subtle).

But to be fair[1], I acknowledge (with a smile, of course) your
reference to my name...

[1] It is the least I could do; otherwise I would have done less

OK, I'll go back to my room now...

 

[Char Jackson]

Watch that stuff - there's always the danger that I'll splatter coffee
all over my system...

Sorry. I figured someone would bust my chops for a redundancy
violation, a la ATM machine or NIC card, or in this case Regular
Expression expression.

To be honest, though, I read M$ as "em string", although I no longer
remember which programming language I'm thinking of that uses the
dollar sign to indicate string variables.

 

[Char Jackson]

BTW, right after I stopped laughing at your post (which was *after* I
replied to it!), just for fun I opened a cmd window in my W7
installation and typed help without an argument and got a long list of
help on various commands. When I typed help /? I got help on how to use
help.

The above is 100% consistent and 100% as I expected.

I think I know the reason, though. I am running MS software obtained
from reputable sources, not M$ software.

I don't have any M$ software, either. I don't know anyone else who has
any, so apparently it's not popular.

 

[Char Jackson]

No, I've criticized your attitude (apparently I was too subtle).

Subtlety is underrated. ;-)

 

[Gene E. Bloch]

Subtlety is underrated. ;-)

As is your sense of humor. You've been keeping me amused today...

 

[R. C. White]

Hi, Char.

To be honest, though, I read M$ as "em string", although I no longer
remember which programming language I'm thinking of that uses the dollar
sign to indicate string variables.

Ah, memories! ;<)

Good old Level II BASIC on my first TRS-80 in 1978. Level I (tiny) BASIC
used $ for string variables, too, but it allowed only TWO of them, A$ and
B$, never M$.

The Radio Shack store manager thought I'd be glad that Level II was
Micro-Soft BASIC but, since I had never heard of Micro-Soft, I wasn't
impressed.

RC
--
R. C. White, CPA
San Marcos, TX
(e-mail address removed)
Microsoft Windows MVP (2002-2010)
Windows Live Mail 2011 (Build 15.4.3555.0308) in Win7 Ultimate x64 SP1


"Char Jackson" wrote in message

Watch that stuff - there's always the danger that I'll splatter coffee
all over my system...

Sorry. I figured someone would bust my chops for a redundancy
violation, a la ATM machine or NIC card, or in this case Regular
Expression expression.

To be honest, though, I read M$ as "em string", although I no longer
remember which programming language I'm thinking of that uses the
dollar sign to indicate string variables.

 

[SC Tom]

You're welcome, no problem

After doing it, I was surprised at the number of entries. I don't recall
near that many in XP or earlier Windows.

The one that bugs me is the path. It's huge. (I don't recall how big the
whole set of environment variables was in the older versions.)

Because the method given by MS in the properties box is so bad[1], when
I have to edit the path, I have gotten into the habit of copying the
path variable, pasting it into a text editor, and making the changes
there. After significant amounts of proofreading I finally paste it over
the value in the properties screen's edit box.

[1] You get to do it in a one-line edit box which is 35 characters long.
Maybe there's a way to change it somewhere or somehow else, but I do it
so rarely I haven't bothered to look.

IIRC, the Path through Win98 (and maybe ME) was 256 characters, and XP was
1024. But that got lengthened to 2048 with SP2. I may be thinking of file
path length (directory structure), but the 256 sticks in my mind (and very
little seems to stick any more) for some odd reason.

 

[Char Jackson]

As is your sense of humor. You've been keeping me amused today...

Thanks, but I can't do it every day. It's exhausting.
I enjoy your sense of humor, as well.

 

[Char Jackson]

Hi, Char.


Ah, memories! ;<)

Good old Level II BASIC on my first TRS-80 in 1978. Level I (tiny) BASIC
used $ for string variables, too, but it allowed only TWO of them, A$ and
B$, never M$.

Performing a programming task with only two string variables seems
quite limiting, but perhaps only in hindsight. I remember teaching
myself 6502 Assembly language in 1983 and it only had two registers, X
and Y, and an Accumulator. You had to do an awful lot of loading and
storing to always have the correct values in those three guys.

The Radio Shack store manager thought I'd be glad that Level II was
Micro-Soft BASIC but, since I had never heard of Micro-Soft, I wasn't
impressed.

MS didn't have much of a track record back then, so I'm not sure you
would have been impressed even if you had heard of them.

 

[J. P. Gilliver (John)]

Performing a programming task with only two string variables seems
quite limiting, but perhaps only in hindsight. I remember teaching
myself 6502 Assembly language in 1983 and it only had two registers, X
and Y, and an Accumulator. You had to do an awful lot of loading and
storing to always have the correct values in those three guys.


MS didn't have much of a track record back then, so I'm not sure you
would have been impressed even if you had heard of them.

No, they were just another producer of BASIC interpreters. However,
theirs did find its way into quite a lot of home computers, and became a
sort of standard - not that there was much compatibility between
machines, but at least if you typed the same listing into another
machine, it was more likely to work if the machine had a Microsoft
BASIC, as long as you stayed off any machine-specific things.

I thought the MS BASIC was quite a good one. (ISTR reading somewhere
that my computer - a Tangerine - had used MS BASIC chips without full
permission, but I could be wrong about that; the Tangerine, and the ORIC
and Atmos it evolved into, are long gone now [I mean the company; I
still have the Atmos somewhere].)

 

[Robin Bignall]

On Mon, 9 Jul 2012 16:34:18 -0700, "Gene E. Bloch"

[..]

No, I've criticized your attitude (apparently I was too subtle).

A guy with a dog went into a bar, the dog saw the barman's hat on a peg,
jumped up and tore the hat to pieces.
The barman asked if the dog owner was going to pay for it and he just
shrugged.
"I don't like your attitude".
"It's not my hat he chewed".

 

[Gene E. Bloch]

On Mon, 9 Jul 2012 16:34:18 -0700, "Gene E. Bloch"

[..]

No, I've criticized your attitude (apparently I was too subtle).

A guy with a dog went into a bar, the dog saw the barman's hat on a peg,
jumped up and tore the hat to pieces.
The barman asked if the dog owner was going to pay for it and he just
shrugged.
"I don't like your attitude".
"It's not my hat he chewed".

That verges on felony

Which means that I laughed out loud...And again I was lucky (no coffee).

Thanks for adding a good perspective to this issue.

 

[Gene E. Bloch]

On Sun, 8 Jul 2012 23:16:43 -0400, SC Tom wrote:

On Sun, 08 Jul 2012 16:37:12 +0100, Robin Bignall wrote:

Does %WinDir% mean \Windows ?
I have forgotten how Dos-like commands work.

I can't contribute to solving your real problem, but I can answer this
one

%Windir% almost certainly means C:\Windows, but you can verify it.

Open a cmd window and run the command echo %windir%.

Or else run the command %set% to see all.

It's just SET and press enter. The % aren't necessary (in fact, they
throw
an error on my Win7 HP 32-bit).

Aagh!

I obviously didn't read what I typed.

Thanks for catching that.

You're welcome, no problem

After doing it, I was surprised at the number of entries. I don't recall
near that many in XP or earlier Windows.

The one that bugs me is the path. It's huge. (I don't recall how big the
whole set of environment variables was in the older versions.)

Because the method given by MS in the properties box is so bad[1], when
I have to edit the path, I have gotten into the habit of copying the
path variable, pasting it into a text editor, and making the changes
there. After significant amounts of proofreading I finally paste it over
the value in the properties screen's edit box.

[1] You get to do it in a one-line edit box which is 35 characters long.
Maybe there's a way to change it somewhere or somehow else, but I do it
so rarely I haven't bothered to look.

IIRC, the Path through Win98 (and maybe ME) was 256 characters, and XP was
1024. But that got lengthened to 2048 with SP2. I may be thinking of file
path length (directory structure), but the 256 sticks in my mind (and very
little seems to stick any more) for some odd reason.

Why did you have to ask?

Here's a developer's perspective:
http://blogs.msdn.com/b/oldnewthing/archive/2010/02/03/9957320.aspx

and from a user's perspective:
http://support.microsoft.com/default.aspx?scid=KB;EN-US;830473&ID=KB;EN-US;830473

It seems like the answer is "it depends" :-(

But anyway, 2047 characters (or slightly fewer) should always work, if I
interpret the above correctly.

I could probably find mare definitive write-ups, but somehow, I'm ready
to stop looking now...

 

[SC Tom]

On Mon, 9 Jul 2012 19:46:11 -0400, SC Tom wrote:

On Sun, 8 Jul 2012 23:16:43 -0400, SC Tom wrote:

On Sun, 08 Jul 2012 16:37:12 +0100, Robin Bignall wrote:

Does %WinDir% mean \Windows ?
I have forgotten how Dos-like commands work.

I can't contribute to solving your real problem, but I can answer
this
one

%Windir% almost certainly means C:\Windows, but you can verify it.

Open a cmd window and run the command echo %windir%.

Or else run the command %set% to see all.

It's just SET and press enter. The % aren't necessary (in fact, they
throw
an error on my Win7 HP 32-bit).

Aagh!

I obviously didn't read what I typed.

Thanks for catching that.

You're welcome, no problem

After doing it, I was surprised at the number of entries. I don't
recall
near that many in XP or earlier Windows.

The one that bugs me is the path. It's huge. (I don't recall how big the
whole set of environment variables was in the older versions.)

Because the method given by MS in the properties box is so bad[1], when
I have to edit the path, I have gotten into the habit of copying the
path variable, pasting it into a text editor, and making the changes
there. After significant amounts of proofreading I finally paste it over
the value in the properties screen's edit box.

[1] You get to do it in a one-line edit box which is 35 characters long.
Maybe there's a way to change it somewhere or somehow else, but I do it
so rarely I haven't bothered to look.

IIRC, the Path through Win98 (and maybe ME) was 256 characters, and XP
was
1024. But that got lengthened to 2048 with SP2. I may be thinking of file
path length (directory structure), but the 256 sticks in my mind (and
very
little seems to stick any more) for some odd reason.

Why did you have to ask?

Here's a developer's perspective:
http://blogs.msdn.com/b/oldnewthing/archive/2010/02/03/9957320.aspx

and from a user's perspective:
http://support.microsoft.com/default.aspx?scid=KB;EN-US;830473&ID=KB;EN-US;830473

It seems like the answer is "it depends" :-(

But anyway, 2047 characters (or slightly fewer) should always work, if I
interpret the above correctly.

I could probably find mare definitive write-ups, but somehow, I'm ready
to stop looking now...

 

[SC Tom]

On Mon, 9 Jul 2012 19:46:11 -0400, SC Tom wrote:

On Sun, 8 Jul 2012 23:16:43 -0400, SC Tom wrote:

On Sun, 08 Jul 2012 16:37:12 +0100, Robin Bignall wrote:

Does %WinDir% mean \Windows ?
I have forgotten how Dos-like commands work.

I can't contribute to solving your real problem, but I can answer
this
one

%Windir% almost certainly means C:\Windows, but you can verify it.

Open a cmd window and run the command echo %windir%.

Or else run the command %set% to see all.

It's just SET and press enter. The % aren't necessary (in fact, they
throw
an error on my Win7 HP 32-bit).

Aagh!

I obviously didn't read what I typed.

Thanks for catching that.

You're welcome, no problem

After doing it, I was surprised at the number of entries. I don't
recall
near that many in XP or earlier Windows.

The one that bugs me is the path. It's huge. (I don't recall how big the
whole set of environment variables was in the older versions.)

Because the method given by MS in the properties box is so bad[1], when
I have to edit the path, I have gotten into the habit of copying the
path variable, pasting it into a text editor, and making the changes
there. After significant amounts of proofreading I finally paste it over
the value in the properties screen's edit box.

[1] You get to do it in a one-line edit box which is 35 characters long.
Maybe there's a way to change it somewhere or somehow else, but I do it
so rarely I haven't bothered to look.

IIRC, the Path through Win98 (and maybe ME) was 256 characters, and XP
was
1024. But that got lengthened to 2048 with SP2. I may be thinking of file
path length (directory structure), but the 256 sticks in my mind (and
very
little seems to stick any more) for some odd reason.

Why did you have to ask?

Here's a developer's perspective:
http://blogs.msdn.com/b/oldnewthing/archive/2010/02/03/9957320.aspx

and from a user's perspective:
http://support.microsoft.com/default.aspx?scid=KB;EN-US;830473&ID=KB;EN-US;830473

It seems like the answer is "it depends" :-(

But anyway, 2047 characters (or slightly fewer) should always work, if I
interpret the above correctly.

I could probably find mare definitive write-ups, but somehow, I'm ready
to stop looking now...

Whoops, wrong button :-(

Well, thanks for looking that up, since I wasn't going to bother <wink,
wink, nudge, nudge>.

As the one responder wrote "Why isn't there one answer to this question?"
But then, that seems to be the way of most OS related questions.

Thanks!