How to fix the bootup screen logo after running setup

"PCR" wrote in
:

SNIP

You seem to have something extra. If I were willing to
trust my memory this soon after it lied, I'd probably say I
doubt I ever saw my BIOS post a message. For a while a
while ago, it was beeping at me quickly thrice-- but that's
gone away! Before that, it was beeping once or twice-- but
I'm fairly sure that's gone too now!

Beeps MAY indicate memory and other problems. Look on the HP
site and find out what the beeps mean for your machine.

[BTW, I tried the BIOS logo flash utility... it has a
variety of weird restrictions AFA the "image", and it took
about twenty times and the furthest I got was "image
palette error" or something, but I did it just like it's
supposed to be, RLE compressed BMP and everything, 64KB or
less... Who cares...

You mean just to alter the Compaq logo screen? I can only
guess on that. Looks like Zabkar is the one for that.
Somewhere in the course of this thread, I came to believe
you already had changed your Compaq logo to be Natashia. I
see I was wrong, & you actually said it was the Win98Lite
Logo.sys that was changed.

Right, and BECAUSE OF YOU AND YOUR NAGGING ;-) I ended up trying
to flash the stupid BIOS Logo, and the only thing left to try is
to alter the original (the ONLY thing the damn program WOULD do
was to save the original logo so I have it as a BMP file now and
can try editing it instead of making a /new/ BMP RLE file to
their /STUPID SPECS/.

OK. But THAT should block out Config.sys & Autoexec.bat!

(2) MS Startup Menu.
Mine is set for 10 seconds in MSDOS.sys...
BootMenu=1
BootMenuDelay=10
But hit ENTER, & it goes away immediately.

This I knew, and in spite of getting old, 3 or 5 secs is
enough for me.

I didn't like it that short.

Size doesn't matter.

SNIP

Right. But you see it with Logo=1?

Yes. How many more times do I have to tell you?

It pops into Natasha for 30 seconds. And what the hell gave you
ANY idea she is dancing? I know these days it appears mandatory
for all dancers and backup singers to wear bikinis (for lack of
a better term), and I did say she is wearing a white bikini, but
please do not confuse a startup screen with the "virtual girl"
annoyance.

(4) The Windows desktop & its wallpaper.
R-Clk Desktop, Properties.

Sure... but what is the point of mentioning it here?

I became mixed up somehow. I thought you were seeing
Natashia twice with (what might be) DOS in between.

YES.

I /DO/, but only when the Windows 98 (DOS shell) is starting...
way past BIOS!

I thought wallpaper might be the 2nd Natashia after your

Natasha. Are you just trying to drive me crazy? Is that what
this thread is about now?

Compaq logo (which I know now isn't one-- IF there are
two).

No offense, but either you ARE trying to drive me crazy or we
seem to have a slight cognitive mismatch... This is really
beginning to remind me of some group therapy arguments I was
part of in the good old days...

Anyway, I won't repeat what I already said 3 or 4 times...

If "@ECHO OFF" controls what you see, what you see is the
DOS of Config.sys & Autoexec.bat. But those shouldn't show
when Logo=1 in MSDOS.sys. The MS logo hid that for me.

Also shows the autoexec.bat file, which I can ECHO out
but then it shows the c:\ECHO OFF

That shouldn't be! It should be obscured behind the MS
logo.

Many things SHOULD BE in MS products. I just look3d at my
MS-DOS 5 book... At the time of its printing, the MS
slogan used to be "Making it all make sense[TM]".

Right.

Uh-huh. I'm certainly about to give up. I see System
Commander may be involved too. I must leave that between
you & MEB.

I dumped System Manager. I thought I'd play around with Damn
Small Linux (I ran it from a virtual drive and it works great)
but what's the point.

That's what happened here. Are you sure you are set
Logo=1 in MSDOS.sys? Can it be the 2nd Frenchwoman you
see is the wallpaer?

I already /told you/ she's Canadian! And it's the same
Windows logo.sys but for SOME reason the damn startup menu
interrupts it every time!

I thought for sure it was a dancing Frenchwoman. My Startup
Menu shows up BEFORE my Logo.sys. MSDOS.sys is before the
menu. IO.sys is before MSDOS.sys. MBR boot code is before
IO.sys. BIOS is before MBR boot code.

Could be System Commander has changed one of the 10
commandments for you-- as MEB seems to be saying. I can't
say for sure!

It ALWAYS happened this way with 98SE. For about 4 or so years
I've had this computer.

I got really fed up with wallpapers a long time ago, after
collecting about a zillion of them... made some of my own
too... Way too much free time... Now I don't even have a
custom color scheme - I'm on plum now IIRC... I went to a
lot of trouble to set up an all greyshade scheme and I
have it saved,

I can see all that. Now/then I switch Desktop Themes, but I
hardly look much at the Desktop, really.

Themes? No thanks.

but for some
reason on my "new" "monitor", (LG 17", last new CRT I
could find around here) it shows up in very faint shades
of colors. I MAY have had the graphics set to High Color
not 32bit, like I do now, but for now I don't see much
point in checking if the greyscale scheme look OK now or
not... Do I sound a little jaded?

I don't know. And I don't really want to talk about
monitors. This is the 3rd one about to go! An Envision
EN5400e! I was so happy with it at first! Now, its buttons
won't work-- even the on/off button must be pressed
multiple times to work. And a week/so ago-- it was going
on/off by itself while I was trying to post! I often find
it has gone on by itself overnight! But my colors are fine.

Sigh. Maybe I should use the F8 (IIRC) method for the
startup menu...

Tried it, the stupid Compaq boot mechanism gives me about 1/100
of a second to hit the F8 key (if I hit it too early it gets me
into the BIOS, why i don't know...) so I had to go back to the
bootmenu=1...

SNIP

(a) "START, Run, MSConfig, Advanced button"
(b) Uncheck "Enable Startup Menu"
(c) Reboot -- I guess -- to enable MSConfig to complete,
or check inside MSDOS.sys to see whether it's done.
(d) Open MSDOS.sys & manually enter...
BootMenu=0
BootMenuDelay=5

When set through MSConfig, you get 30 seconds. Can it be
doing it each boot? I am unchecked in MSConfig & still get
my menu (for 10 seconds).

Sigh...

I never even SAW MS Config until a few years ago when someone
mentioned it. I can't find it in the Windows directory but when
I typed the run command you gave above, it did show up. I think
I prefer just editing ini files. Anyway, I saw it today for the
2nd time in my life, and I only remember that I DID see it one
before but I don't /actually remember/ seeing it, I just /know/
I did. It's late.

I did set memory to 500 and we'll see what happens. I have a 3.1
program that won't run because there's not enough and too much
memory at once. (It USED to of course, before all world's
computers started plotting against me...

So I installed Tiny XP, same thing. Maybe I'll just have to
install win 3.11 on ANOTHER partition.

Am I having fun yet?


--
Lots of theoretical butchers are alleged and other bloody eyes
are suitable, but will Pam secure that?

thanatoid wrote:
"PCR" wrote in
:

SNIP

You seem to have something extra. If I were willing to
trust my memory this soon after it lied, I'd probably say I
doubt I ever saw my BIOS post a message. For a while a
while ago, it was beeping at me quickly thrice-- but that's
gone away! Before that, it was beeping once or twice-- but
I'm fairly sure that's gone too now!

Beeps MAY indicate memory and other problems. Look on the HP
site and find out what the beeps mean for your machine.

I never found a description of beeps at that site, but found various
ones elsewhere. But I haven't heard any beeps in a while. So, it didn't
matter I never could quite figure which beep list applied to me. And it
didn't come in the Compaq manuals, either, not that I've spotted.

[BTW, I tried the BIOS logo flash utility... it has a
variety of weird restrictions AFA the "image", and it took
about twenty times and the furthest I got was "image
palette error" or something, but I did it just like it's
supposed to be, RLE compressed BMP and everything, 64KB or
less... Who cares...

You mean just to alter the Compaq logo screen? I can only
guess on that. Looks like Zabkar is the one for that.
Somewhere in the course of this thread, I came to believe
you already had changed your Compaq logo to be Natashia. I
see I was wrong, & you actually said it was the Win98Lite
Logo.sys that was changed.

Right, and BECAUSE OF YOU AND YOUR NAGGING ;-) I ended up trying
to flash the stupid BIOS Logo, and the only thing left to try is
to alter the original (the ONLY thing the damn program WOULD do
was to save the original logo so I have it as a BMP file now and
can try editing it instead of making a /new/ BMP RLE file to
their /STUPID SPECS/.

Sounds like I'm lucky I didn't get that capability with my 7470! I
hesitate to offer any advice. I'd rather Zabkar be blamed for the worse
outcomes! :-).

OK. But THAT should block out Config.sys & Autoexec.bat!

(2) MS Startup Menu.
Mine is set for 10 seconds in MSDOS.sys...
BootMenu=1
BootMenuDelay=10
But hit ENTER, & it goes away immediately.

This I knew, and in spite of getting old, 3 or 5 secs is
enough for me.

I didn't like it that short.

Size doesn't matter.

SNIP

Right. But you see it with Logo=1?

Yes. How many more times do I have to tell you?

It pops into Natasha for 30 seconds. And what the hell gave you
ANY idea she is dancing? I know these days it appears mandatory
for all dancers and backup singers to wear bikinis (for lack of
a better term), and I did say she is wearing a white bikini, but
please do not confuse a startup screen with the "virtual girl"
annoyance.

(4) The Windows desktop & its wallpaper.
R-Clk Desktop, Properties.

Sure... but what is the point of mentioning it here?

I became mixed up somehow. I thought you were seeing
Natashia twice with (what might be) DOS in between.

YES.

I /DO/, but only when the Windows 98 (DOS shell) is starting...
way past BIOS!

I thought wallpaper might be the 2nd Natashia after your

Natasha. Are you just trying to drive me crazy? Is that what
this thread is about now?

Compaq logo (which I know now isn't one-- IF there are
two).

No offense, but either you ARE trying to drive me crazy or we
seem to have a slight cognitive mismatch... This is really
beginning to remind me of some group therapy arguments I was
part of in the good old days...

Anyway, I won't repeat what I already said 3 or 4 times...

If "@ECHO OFF" controls what you see, what you see is the
DOS of Config.sys & Autoexec.bat. But those shouldn't show
when Logo=1 in MSDOS.sys. The MS logo hid that for me.

Also shows the autoexec.bat file, which I can ECHO out
but then it shows the c:\ECHO OFF

That shouldn't be! It should be obscured behind the MS
logo.

Many things SHOULD BE in MS products. I just look3d at my
MS-DOS 5 book... At the time of its printing, the MS
slogan used to be "Making it all make sense[TM]".

Right.

Uh-huh. I'm certainly about to give up. I see System
Commander may be involved too. I must leave that between
you & MEB.

I dumped System Manager. I thought I'd play around with Damn
Small Linux (I ran it from a virtual drive and it works great)
but what's the point.

That's what happened here. Are you sure you are set
Logo=1 in MSDOS.sys? Can it be the 2nd Frenchwoman you
see is the wallpaer?

I already /told you/ she's Canadian! And it's the same
Windows logo.sys but for SOME reason the damn startup menu
interrupts it every time!

I thought for sure it was a dancing Frenchwoman. My Startup
Menu shows up BEFORE my Logo.sys. MSDOS.sys is before the
menu. IO.sys is before MSDOS.sys. MBR boot code is before
IO.sys. BIOS is before MBR boot code.

Could be System Commander has changed one of the 10
commandments for you-- as MEB seems to be saying. I can't
say for sure!

It ALWAYS happened this way with 98SE. For about 4 or so years
I've had this computer.

I got really fed up with wallpapers a long time ago, after
collecting about a zillion of them... made some of my own
too... Way too much free time... Now I don't even have a
custom color scheme - I'm on plum now IIRC... I went to a
lot of trouble to set up an all greyshade scheme and I
have it saved,

I can see all that. Now/then I switch Desktop Themes, but I
hardly look much at the Desktop, really.

Themes? No thanks.

but for some
reason on my "new" "monitor", (LG 17", last new CRT I
could find around here) it shows up in very faint shades
of colors. I MAY have had the graphics set to High Color
not 32bit, like I do now, but for now I don't see much
point in checking if the greyscale scheme look OK now or
not... Do I sound a little jaded?

I don't know. And I don't really want to talk about
monitors. This is the 3rd one about to go! An Envision
EN5400e! I was so happy with it at first! Now, its buttons
won't work-- even the on/off button must be pressed
multiple times to work. And a week/so ago-- it was going
on/off by itself while I was trying to post! I often find
it has gone on by itself overnight! But my colors are fine.

Sigh. Maybe I should use the F8 (IIRC) method for the
startup menu...

Tried it, the stupid Compaq boot mechanism gives me about 1/100
of a second to hit the F8 key (if I hit it too early it gets me
into the BIOS, why i don't know...) so I had to go back to the
bootmenu=1...

SNIP

(a) "START, Run, MSConfig, Advanced button"
(b) Uncheck "Enable Startup Menu"
(c) Reboot -- I guess -- to enable MSConfig to complete,
or check inside MSDOS.sys to see whether it's done.
(d) Open MSDOS.sys & manually enter...
BootMenu=0
BootMenuDelay=5

When set through MSConfig, you get 30 seconds. Can it be
doing it each boot? I am unchecked in MSConfig & still get
my menu (for 10 seconds).

Sigh...

I never even SAW MS Config until a few years ago when someone
mentioned it. I can't find it in the Windows directory but when
I typed the run command you gave above, it did show up. I think
I prefer just editing ini files. Anyway, I saw it today for the
2nd time in my life, and I only remember that I DID see it one
before but I don't /actually remember/ seeing it, I just /know/
I did. It's late.

I did set memory to 500 and we'll see what happens. I have a 3.1
program that won't run because there's not enough and too much
memory at once. (It USED to of course, before all world's
computers started plotting against me...

So I installed Tiny XP, same thing. Maybe I'll just have to
install win 3.11 on ANOTHER partition.

Am I having fun yet?

--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR

Clicked SEND too soon. Here's the rest.

thanatoid wrote:
"PCR" wrote in
:

SNIP

You seem to have something extra. If I were willing to
trust my memory this soon after it lied, I'd probably say I
doubt I ever saw my BIOS post a message. For a while a
while ago, it was beeping at me quickly thrice-- but that's
gone away! Before that, it was beeping once or twice-- but
I'm fairly sure that's gone too now!

Beeps MAY indicate memory and other problems. Look on the HP
site and find out what the beeps mean for your machine.

I never found a description of beeps at that site, but found various
ones elsewhere. But I haven't heard any beeps in a while. So, it didn't
matter I never could quite figure which beep list applied to me. And it
didn't come in the Compaq manuals, either, not that I've spotted.

[BTW, I tried the BIOS logo flash utility... it has a
variety of weird restrictions AFA the "image", and it took
about twenty times and the furthest I got was "image
palette error" or something, but I did it just like it's
supposed to be, RLE compressed BMP and everything, 64KB or
less... Who cares...

You mean just to alter the Compaq logo screen? I can only
guess on that. Looks like Zabkar is the one for that.
Somewhere in the course of this thread, I came to believe
you already had changed your Compaq logo to be Natashia. I
see I was wrong, & you actually said it was the Win98Lite
Logo.sys that was changed.

Right, and BECAUSE OF YOU AND YOUR NAGGING I ended up trying
to flash the stupid BIOS Logo, and the only thing left to try is
to alter the original (the ONLY thing the damn program WOULD do
was to save the original logo so I have it as a BMP file now and
can try editing it instead of making a new BMP RLE file to
their STUPID SPECS.

Sounds like I'm lucky I didn't get that capability with my 7470! I
hesitate to offer any advice. I'd rather Zabkar be blamed for the worse
outcomes! :-).

OK. But THAT should block out Config.sys & Autoexec.bat!

(2) MS Startup Menu.
Mine is set for 10 seconds in MSDOS.sys...
BootMenu=1
BootMenuDelay=10
But hit ENTER, & it goes away immediately.

This I knew, and in spite of getting old, 3 or 5 secs is
enough for me.

I didn't like it that short.

Size doesn't matter.

LOL!

SNIP

Right. But you see it with Logo=1?

Yes. How many more times do I have to tell you?

It's unbelievable!

It pops into Natasha for 30 seconds.

I've really given up on that. But ... maybe ... itemize the order in
which you see the following-- both with the MS logo activated & with it
de-activated. Perhaps also toggle whether the Startup Menu is activated.
Is it possible to toggle System Commander?

(1) BIOS logo Screen
(2) System Commander screen
(3) MS Startup Menu
(4a) MS logo screen (Natasha)
(4b) DOS lines of Config.sys/Autoexec.bat
(5) Whatever else you see

When you deactivate the MS logo-- do you see Natasha at all?

And what the hell gave you
ANY idea she is dancing? I know these days it appears mandatory
for all dancers and backup singers to wear bikinis (for lack of
a better term), and I did say she is wearing a white bikini, but
please do not confuse a startup screen with the "virtual girl"
annoyance.

All Frenchwomen dance!

(4) The Windows desktop & its wallpaper.
R-Clk Desktop, Properties.

Sure... but what is the point of mentioning it here?

I became mixed up somehow. I thought you were seeing
Natashia twice with (what might be) DOS in between.

YES.

I DO, but only when the Windows 98 (DOS shell) is starting...
way past BIOS!

Foof! I really don't see how Logo.sys would show twice. I still want to
believe there is a second source of the image.

I thought wallpaper might be the 2nd Natashia after your

Natasha. Are you just trying to drive me crazy? Is that what
this thread is about now?

Compaq logo (which I know now isn't one-- IF there are
two).

No offense, but either you ARE trying to drive me crazy or we
seem to have a slight cognitive mismatch... This is really
beginning to remind me of some group therapy arguments I was
part of in the good old days...

I guess one of us could have a cognitive mishmash. I certainly amn't
trying anything!

Anyway, I won't repeat what I already said 3 or 4 times...

Any further repetitions are iterations.

If "@ECHO OFF" controls what you see, what you see is the
DOS of Config.sys & Autoexec.bat. But those shouldn't show
when Logo=1 in MSDOS.sys. The MS logo hid that for me.

Also shows the autoexec.bat file, which I can ECHO out
but then it shows the c:\ECHO OFF

That shouldn't be! It should be obscured behind the MS
logo.

Many things SHOULD BE in MS products. I just look3d at my
MS-DOS 5 book... At the time of its printing, the MS
slogan used to be "Making it all make sense[TM]".

Right.

Uh-huh. I'm certainly about to give up. I see System
Commander may be involved too. I must leave that between
you & MEB.

I dumped System Manager. I thought I'd play around with Damn
Small Linux (I ran it from a virtual drive and it works great)
but what's the point.

Sounded like it might alter the startup axis, which maybe we both need
to review...
http://cquirke.mvps.org/9x/startup.htm
The startup axis. I'll bet the answer is here!

That's what happened here. Are you sure you are set
Logo=1 in MSDOS.sys? Can it be the 2nd Frenchwoman you
see is the wallpaer?

I already told you she's Canadian! And it's the same
Windows logo.sys but for SOME reason the damn startup menu
interrupts it every time!

I thought for sure it was a dancing Frenchwoman. My Startup
Menu shows up BEFORE my Logo.sys. MSDOS.sys is before the
menu. IO.sys is before MSDOS.sys. MBR boot code is before
IO.sys. BIOS is before MBR boot code.

Could be System Commander has changed one of the 10
commandments for you-- as MEB seems to be saying. I can't
say for sure!

It ALWAYS happened this way with 98SE. For about 4 or so years
I've had this computer.

Could be the answer is on cquirke's site. The boot process has many
variations & complexities. Let's look for something that could interrupt
Logo.sys or display it a 2nd time.

I got really fed up with wallpapers a long time ago, after
collecting about a zillion of them... made some of my own
too... Way too much free time... Now I don't even have a
custom color scheme - I'm on plum now IIRC... I went to a
lot of trouble to set up an all greyshade scheme and I
have it saved,

I can see all that. Now/then I switch Desktop Themes, but I
hardly look much at the Desktop, really.

Themes? No thanks.

All right. As I said, I just was guessing the wallpaper could have been
the 2nd image.

but for some
reason on my "new" "monitor", (LG 17", last new CRT I
could find around here) it shows up in very faint shades
of colors. I MAY have had the graphics set to High Color
not 32bit, like I do now, but for now I don't see much
point in checking if the greyscale scheme look OK now or
not... Do I sound a little jaded?

I don't know. And I don't really want to talk about
monitors. This is the 3rd one about to go! An Envision
EN5400e! I was so happy with it at first! Now, its buttons
won't work-- even the on/off button must be pressed
multiple times to work. And a week/so ago-- it was going
on/off by itself while I was trying to post! I often find
it has gone on by itself overnight! But my colors are fine.

Sigh. Maybe I should use the F8 (IIRC) method for the
startup menu...

Tried it, the stupid Compaq boot mechanism gives me about 1/100
of a second to hit the F8 key (if I hit it too early it gets me
into the BIOS, why i don't know...) so I had to go back to the
bootmenu=1...

Holding in the CTRL key during boot is superior to F8. The time limit is
not a consideration that way.

SNIP

(a) "START, Run, MSConfig, Advanced button"
(b) Uncheck "Enable Startup Menu"
(c) Reboot -- I guess -- to enable MSConfig to complete,
or check inside MSDOS.sys to see whether it's done.
(d) Open MSDOS.sys & manually enter...
BootMenu=0
BootMenuDelay=5

When set through MSConfig, you get 30 seconds. Can it be
doing it each boot? I am unchecked in MSConfig & still get
my menu (for 10 seconds).

Sigh...

I never even SAW MS Config until a few years ago when someone
mentioned it. I can't find it in the Windows directory but when
I typed the run command you gave above, it did show up. I think
I prefer just editing ini files. Anyway, I saw it today for the
2nd time in my life, and I only remember that I DID see it one
before but I don't actually remember seeing it, I just know
I did. It's late.

OK. But what about the Advanced button & that checkbox?

Another thing-- don't forget to look below the comment lines in
MSDOS.sys. A second BootMenuDelay may be hiding under there.

I did set memory to 500 and we'll see what happens. I have a 3.1
program that won't run because there's not enough and too much
memory at once. (It USED to of course, before all world's
computers started plotting against me...

So I installed Tiny XP, same thing. Maybe I'll just have to
install win 3.11 on ANOTHER partition.

Am I having fun yet?

You're starting to stray to other matters. But keep at it. We probably
both will learn from this. And MEB too!


--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR

"PCR" wrote in
:

thanatoid wrote:

SNIP

Beeps MAY indicate memory and other problems. Look on the
HP site and find out what the beeps mean for your machine.

I never found a description of beeps at that site, but
found various ones elsewhere. But I haven't heard any beeps
in a while. So, it didn't matter I never could quite figure
which beep list applied to me. And it didn't come in the
Compaq manuals, either, not that I've spotted.

I never got manuals with mine, but you can DL everything from
HP. When my first 1GB stick died, I got beeps to tell me what
was wrong, but had to use my OTHER computer to find out what
they meant.

SNIP

Sounds like I'm lucky I didn't get that capability with my
7470! I hesitate to offer any advice. I'd rather Zabkar be
blamed for the worse outcomes! :-).

I have seen and admired his posts for years, I do not believe he
has EVER advised anything which could/would result in a
disaster.

OK. But THAT should block out Config.sys & Autoexec.bat!

Like I said, Windows *should* run OK out of the box, too, etc.
etc. etc. etc.

SNIP

Natasha. Are you just trying to drive me crazy? Is that
what this thread is about now?

Compaq logo (which I know now isn't one-- IF there are
two).

There are two - well, 4 - logos: the BIOS logo and 3 Windows
logos - apparently more in XP but that's another subject and
LET'S LEAVE IT THAT WAY.

No offense, but either you ARE trying to drive me crazy or
we seem to have a slight cognitive mismatch... This is
really beginning to remind me of some group therapy
arguments I was part of in the good old days...

Anyway, I won't repeat what I already said 3 or 4 times...

If "@ECHO OFF" controls what you see, what you see is the
DOS of Config.sys & Autoexec.bat. But those shouldn't
show when Logo=1 in MSDOS.sys. The MS logo hid that for
me.

Well, as I have said x times, the startup menu pops in between
the SAME *1* logo.sys Natasha - you can NOT have 2 logo.sys's.

Also shows the autoexec.bat file, which I can ECHO out
but then it shows the c:\ECHO OFF

Yes, isn't that just wonderful?

That shouldn't be! It should be obscured behind the MS
logo.

Again, /many/ things SHOULD be.

Many things SHOULD BE in MS products. I just look3d at
my MS-DOS 5 book... At the time of its printing, the MS
slogan used to be "Making it all make sense[TM]".

Right.

Uh-huh. I'm certainly about to give up. I see System
Commander may be involved too. I must leave that between
you & MEB.

I dumped System Manager. I thought I'd play around with
Damn Small Linux (I ran it from a virtual drive and it
works great) but what's the point.

That's what happened here. Are you sure you are set
Logo=1 in MSDOS.sys? Can it be the 2nd Frenchwoman you
see is the wallpaer?

THERE ARE NO 2 FRENCHWOMEN, in fact there is not a SINGLE
Frenchwoman, Natasha is Canadian.

You should work in a mental hospital, you know... You could be
on permanent call alert and when a patient is borderline, and
they have just HAD it, they call you in, and after ten minutes
with you s/he is WAY over the edge and ready to be "dealt with"
properly.

SNIP

When set through MSConfig, you get 30 seconds. Can it be
doing it each boot? I am unchecked in MSConfig & still
get my menu (for 10 seconds).

MSconfig sucks. That's what Edxor and ini files are for.


--
Lots of theoretical butchers are alleged and other bloody eyes
are suitable, but will Pam secure that?

"PCR" wrote in
:

Clicked SEND too soon. Here's the rest.

I can't wait.

SNIP

Right. But you see it with Logo=1?

Yes. How many more times do I have to tell you?

It's unbelievable!

It pops into Natasha for 30 seconds.

I've really given up on that.

Popping into Natasha? She let you?

But ... maybe ... itemize the
order in which you see the following-- both with the MS
logo activated & with it de-activated. Perhaps also toggle
whether the Startup Menu is activated. Is it possible to
toggle System Commander?

Now I KNOW you're screwing with my head.

(1) BIOS logo Screen
(2) System Commander screen
(3) MS Startup Menu
(4a) MS logo screen (Natasha)
(4b) DOS lines of Config.sys/Autoexec.bat
(5) Whatever else you see

I'm pretty sure it can't be done.

When you deactivate the MS logo-- do you see Natasha at
all?

This question does not merit a reply.

SNIP

Foof! I really don't see how Logo.sys would show twice.

That's what I've been complaining about throughout this thread!

I still want to believe there is a second source of the
image.

HOW COULD THERE BE? Show me a system with two identically-named
files in the same directory!

I thought wallpaper might be the 2nd Natashia after your

Natasha. Are you just trying to drive me crazy? Is that
what this thread is about now?

Compaq logo (which I know now isn't one-- IF there are
two).

NO Natasha in Compaq, just Compaq.

No offense, but either you ARE trying to drive me crazy or
we seem to have a slight cognitive mismatch... This is
really beginning to remind me of some group therapy
arguments I was part of in the good old days...

I guess one of us could have a cognitive mishmash. I
certainly amn't trying anything!

Right.

Sounded like it might alter the startup axis, which maybe
we both need to review...
http://cquirke.mvps.org/9x/startup.htm
The startup axis. I'll bet the answer is here!

Now there is what MIGHT be of some use. Will check it out.

Could be the answer is on cquirke's site. The boot process
has many variations & complexities. Let's look for
something that could interrupt Logo.sys or display it a 2nd
time.

Why don't we then.

SNIP

All right. As I said, I just was guessing the wallpaper
could have been the 2nd image.

HOW? The taskbar and the icons would be all over it after a few
seconds! Plus, having the same image for startup logo AND
wallpaper would be a little boring, /and/ confusing. Things are
confusing /enough/!

Holding in the CTRL key during boot is superior to F8. The
time limit is not a consideration that way.

Thank you for the tip.

OK. But what about the Advanced button & that checkbox?

Pure evil. See other reply about what it did, in hex to boot (so
to speak).

Another thing-- don't forget to look below the comment
lines in MSDOS.sys. A second BootMenuDelay may be hiding
under there.

That is WHERE IT IS, not above. That's OTHER STUFF.

Is there a mental hospital nearby where you apply for a well-
paying on-call "consultant" job?

You're starting to stray to other matters. But keep at it.
We probably both will learn from this. And MEB too!

See, again, you are doing what they used to call "crazymaking"
in my group therapy group.


--
Lots of theoretical butchers are alleged and other bloody eyes
are suitable, but will Pam secure that?

thanatoid wrote:
"PCR" wrote in
:

thanatoid wrote:

SNIP

Beeps MAY indicate memory and other problems. Look on the
HP site and find out what the beeps mean for your machine.

I never found a description of beeps at that site, but
found various ones elsewhere. But I haven't heard any beeps
in a while. So, it didn't matter I never could quite figure
which beep list applied to me. And it didn't come in the
Compaq manuals, either, not that I've spotted.

I never got manuals with mine, but you can DL everything from
HP. When my first 1GB stick died, I got beeps to tell me what
was wrong, but had to use my OTHER computer to find out what
they meant.

Aye, there's the rub, if you haven't got an audiographic memory. OK,
I'll go look again at the site. OK, thanks.

SNIP

Sounds like I'm lucky I didn't get that capability with my
7470! I hesitate to offer any advice. I'd rather Zabkar be
blamed for the worse outcomes! :-).

I have seen and admired his posts for years, I do not believe he
has EVER advised anything which could/would result in a
disaster.

I doubt it too-- at least, not intentionally. My smiley face meant I was
at least half joking. :-). Also, my signature mentions the possibility.

OK. But THAT should block out Config.sys & Autoexec.bat!

Like I said, Windows *should* run OK out of the box, too, etc.
etc. etc. etc.

OK.

SNIP

Natasha. Are you just trying to drive me crazy? Is that
what this thread is about now?

Compaq logo (which I know now isn't one-- IF there are
two).

There are two - well, 4 - logos: the BIOS logo and 3 Windows
logos - apparently more in XP but that's another subject and
LET'S LEAVE IT THAT WAY.

All right. I meant something else unimportant now, if ever.

No offense, but either you ARE trying to drive me crazy or
we seem to have a slight cognitive mismatch... This is
really beginning to remind me of some group therapy
arguments I was part of in the good old days...

Anyway, I won't repeat what I already said 3 or 4 times...

If "@ECHO OFF" controls what you see, what you see is the
DOS of Config.sys & Autoexec.bat. But those shouldn't
show when Logo=1 in MSDOS.sys. The MS logo hid that for
me.

Well, as I have said x times, the startup menu pops in between
the SAME *1* logo.sys Natasha - you can NOT have 2 logo.sys's.

That's why I was searching for another Natasha besides the one that is
Logo.sys for you. I'd think it impossible Logo.sys would return once
it's gone.

Also shows the autoexec.bat file, which I can ECHO out
but then it shows the c:\ECHO OFF

Yes, isn't that just wonderful?

Yea. But didn't MEB say how to thwart that?-- @ECHO OFF.

That shouldn't be! It should be obscured behind the MS
logo.

Again, /many/ things SHOULD be.

Uh-huh. No doubt.

Many things SHOULD BE in MS products. I just look3d at
my MS-DOS 5 book... At the time of its printing, the MS
slogan used to be "Making it all make sense[TM]".

Right.

Uh-huh. I'm certainly about to give up. I see System
Commander may be involved too. I must leave that between
you & MEB.

I dumped System Manager. I thought I'd play around with
Damn Small Linux (I ran it from a virtual drive and it
works great) but what's the point.

That's what happened here. Are you sure you are set
Logo=1 in MSDOS.sys? Can it be the 2nd Frenchwoman you
see is the wallpaer?

THERE ARE NO 2 FRENCHWOMEN, in fact there is not a SINGLE
Frenchwoman, Natasha is Canadian.

You should work in a mental hospital, you know... You could be
on permanent call alert and when a patient is borderline, and
they have just HAD it, they call you in, and after ten minutes
with you s/he is WAY over the edge and ready to be "dealt with"
properly.

How much does it pay?

SNIP

When set through MSConfig, you get 30 seconds. Can it be
doing it each boot? I am unchecked in MSConfig & still
get my menu (for 10 seconds).

MSconfig sucks. That's what Edxor and ini files are for.

Check the setting I mentioned, & check under the comment lines within
MSDOS.sys.


--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR

"PCR" wrote in
:

thanatoid wrote:

SNIP

I never got manuals with mine, but you can DL everything
from HP. When my first 1GB stick died, I got beeps to tell
me what was wrong, but had to use my OTHER computer to
find out what they meant.

Aye, there's the rub, if you haven't got an audiographic
memory. OK, I'll go look again at the site. OK, thanks.

SNIP

That's why I was searching for another Natasha besides the
one that is Logo.sys for you. I'd think it impossible
Logo.sys would return once it's gone.

One would think that, but one would be wrong. It is entirely
possible I am the only person on the planet that this happens
to, but believe me, it DOES happen. We both know that because of
the infinite combination of factors in even a 286 with nothing
BUT Win3 installed, ANYTHING can happen and anything can be
impossible to reproduce or verify or fix.

Everyone has their stories. I don't even like to remember mine,
I try to forget them. I have lost MONTHS on inexplicable
problems which apparently NO ONE else on Earth ever encountered.
(Once I figured it out, I checked with the author, with the guy
whose site I first saw the program on, and various Usenet groups
- nothing.)

Yet I was able to replicate the problem on TWO different
machines via several completely clean installs until "all the
possibles were eliminated, so the impossible HAD to be the case"
and it was - of course, it wasn't /impossible/ but like I said,
the number it did on my machine was such that unless everyone
else it happened to just gave up on computers altogether (I was
pretty damn close), then I /am/ the only person it happened to.
And don't ask me what it was, I don't want to think about it any
more than I just did. In fact I - with a LOT of work - have
pretty much managed to forget about it except once in a while
something reminds me...

You should work in a mental hospital, you know... You
could be on permanent call alert and when a patient is
borderline, and they have just HAD it, they call you in,
and after ten minutes with you s/he is WAY over the edge
and ready to be "dealt with" properly.

How much does it pay?

On-retainer extra special "consultants" often make more than
people working at the place full-time.

SNIP

When set through MSConfig, you get 30 seconds. Can it
be doing it each boot? I am unchecked in MSConfig &
still get my menu (for 10 seconds).

MSconfig sucks. That's what Edxor and ini files are for.

Check the setting I mentioned, & check under the comment
lines within MSDOS.sys.

I did all that and changed all the variables involved probably
about 30 times in the last few days, and I'm done. There are
worse things than the startup logo showing up for 30 seconds.


--
Lots of theoretical butchers are alleged and other bloody eyes
are suitable, but will Pam secure that?

thanatoid wrote:
"PCR" wrote in
:

Clicked SEND too soon. Here's the rest.

I can't wait.

SNIP

Right. But you see it with Logo=1?

Yes. How many more times do I have to tell you?

It's unbelievable!

It pops into Natasha for 30 seconds.

I've really given up on that.

Popping into Natasha? She let you?

Ah, ha, ha! Naturally, I meant I was giving up on a solution to the two
Natasha's.

But ... maybe ... itemize the
order in which you see the following-- both with the MS
logo activated & with it de-activated. Perhaps also toggle
whether the Startup Menu is activated. Is it possible to
toggle System Commander?

Now I KNOW you're screwing with my head.

No. It's hard for me to believe Logo.sys would show up twice or that the
DOS of Config.sys & Autoexec.bat would show when Logo=1 is enabled. I
wanted more detail as to what is showing & when it shows. The order of
the image(s) & the messages in the course of a boot is normally a big
clue as to what they are.

(1) BIOS logo Screen
(2) System Commander screen
(3) MS Startup Menu
(4a) MS logo screen (Natasha)
(4b) DOS lines of Config.sys/Autoexec.bat
(5) Whatever else you see

I'm pretty sure it can't be done.

What can't be done? I'm not trying to screw with your head! Any attempt
is inadvertent!

When you deactivate the MS logo-- do you see Natasha at
all?

This question does not merit a reply.

OK. Chris Quirke's site probably has the answer, without any further
questions or experiments.

SNIP

Foof! I really don't see how Logo.sys would show twice.

That's what I've been complaining about throughout this thread!

OK. And it's what my questions (probably repetitious through disbelief)
meant to examine.

I still want to believe there is a second source of the
image.

HOW COULD THERE BE? Show me a system with two identically-named
files in the same directory!

I was thinking the BIOS screen or the wallpaper might be the second one.
A weird possibility is that Logo.sys is getting called twice. But I
don't know how that could be.

I thought wallpaper might be the 2nd Natashia after your

Natasha. Are you just trying to drive me crazy? Is that
what this thread is about now?

Compaq logo (which I know now isn't one-- IF there are
two).

NO Natasha in Compaq, just Compaq.

All right. Forgive my repetition & confusion over that BIOS logo.

No offense, but either you ARE trying to drive me crazy or
we seem to have a slight cognitive mismatch... This is
really beginning to remind me of some group therapy
arguments I was part of in the good old days...

I guess one of us could have a cognitive mishmash. I
certainly amn't trying anything!

Right.

:-).

Sounded like it might alter the startup axis, which maybe
we both need to review...
http://cquirke.mvps.org/9x/startup.htm
The startup axis. I'll bet the answer is here!

Now there is what MIGHT be of some use. Will check it out.

Yep. (Alas, we lost cquirke to XP.)

Could be the answer is on cquirke's site. The boot process
has many variations & complexities. Let's look for
something that could interrupt Logo.sys or display it a 2nd
time.

Why don't we then.

I'll go right after I post this. Hopefully you've found it by then.

SNIP

All right. As I said, I just was guessing the wallpaper
could have been the 2nd image.

HOW? The taskbar and the icons would be all over it after a few
seconds! Plus, having the same image for startup logo AND
wallpaper would be a little boring, /and/ confusing. Things are
confusing /enough/!

OK. That's right. It was a silly grasping at straws for me.

Holding in the CTRL key during boot is superior to F8. The
time limit is not a consideration that way.

Thank you for the tip.

You are welcome.

OK. But what about the Advanced button & that checkbox?

Pure evil. See other reply about what it did, in hex to boot (so
to speak).

I'm not sure I do see that reply. Other than the stuff you've cut from
this thread segment, all you said was: "MSconfig sucks". Is it -- or
isn't it -- checked to enable the Startup Menu at its Advanced
requestor? Uncheck it -- if so --, possibly reboot; then, set MSDOS
manually for your 5 seconds...

BootMenu=1
BootMenuDelay=5

Another thing-- don't forget to look below the comment
lines in MSDOS.sys. A second BootMenuDelay may be hiding
under there.

That is WHERE IT IS, not above. That's OTHER STUFF.

That's where MSConfig would put it, IIRC, & with a delay of 30 seconds.

Is there a mental hospital nearby where you apply for a well-
paying on-call "consultant" job?

You want my job?

You're starting to stray to other matters. But keep at it.
We probably both will learn from this. And MEB too!

See, again, you are doing what they used to call "crazymaking"
in my group therapy group.

Well, what is this stuff you've cut...?...

I did set memory to 500 and we'll see what happens. I have a 3.1
program that won't run because there's not enough and too much
memory at once. (It USED to of course, before all world's
computers started plotting against me...

So I installed Tiny XP, same thing. Maybe I'll just have to
install win 3.11 on ANOTHER partition.


--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR

thanatoid wrote:
"PCR" wrote in
:

thanatoid wrote:

SNIP

I never got manuals with mine, but you can DL everything
from HP. When my first 1GB stick died, I got beeps to tell
me what was wrong, but had to use my OTHER computer to
find out what they meant.

Aye, there's the rub, if you haven't got an audiographic
memory. OK, I'll go look again at the site. OK, thanks.

SNIP

That's why I was searching for another Natasha besides the
one that is Logo.sys for you. I'd think it impossible
Logo.sys would return once it's gone.

One would think that, but one would be wrong. It is entirely
possible I am the only person on the planet that this happens
to, but believe me, it DOES happen. We both know that because of
the infinite combination of factors in even a 286 with nothing
BUT Win3 installed, ANYTHING can happen and anything can be
impossible to reproduce or verify or fix.

Everyone has their stories. I don't even like to remember mine,
I try to forget them. I have lost MONTHS on inexplicable
problems which apparently NO ONE else on Earth ever encountered.
(Once I figured it out, I checked with the author, with the guy
whose site I first saw the program on, and various Usenet groups
- nothing.)

Yet I was able to replicate the problem on TWO different
machines via several completely clean installs until "all the
possibles were eliminated, so the impossible HAD to be the case"
and it was - of course, it wasn't /impossible/ but like I said,
the number it did on my machine was such that unless everyone
else it happened to just gave up on computers altogether (I was
pretty damn close), then I /am/ the only person it happened to.
And don't ask me what it was, I don't want to think about it any
more than I just did. In fact I - with a LOT of work - have
pretty much managed to forget about it except once in a while
something reminds me...

Very intriguing! You seriously could make a living writing mysteries or
science fiction, thanatoid. There's some Conan Doyle up there, but
you've put it well.

You should work in a mental hospital, you know... You
could be on permanent call alert and when a patient is
borderline, and they have just HAD it, they call you in,
and after ten minutes with you s/he is WAY over the edge
and ready to be "dealt with" properly.

How much does it pay?

On-retainer extra special "consultants" often make more than
people working at the place full-time.

I'll check into it.

SNIP

When set through MSConfig, you get 30 seconds. Can it
be doing it each boot? I am unchecked in MSConfig &
still get my menu (for 10 seconds).

MSconfig sucks. That's what Edxor and ini files are for.

I see Edxor is a Notepad repacement. But I guess some .ini file could
possibly be responsible for establishing your 30 second BootMenuDelay.


Check the setting I mentioned, & check under the comment
lines within MSDOS.sys.

I did all that and changed all the variables involved probably
about 30 times in the last few days, and I'm done. There are
worse things than the startup logo showing up for 30 seconds.

Something must be set to reenable the Startup Menu with a standard 30
second delay each boot. MSConfig can do that, but I'm not sure it redoes
its work inside MSDOS.sys each boot; I would hope, once done, its done.

It's OK to quit on this & Natasha. You're right, neither is a critical
problem. But what was that other thing-- the horrible one you won't talk
about?


--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR

"PCR" wrote in
:


SNIP

then I
/am/ the only person it happened to. And don't ask me what
it was, I don't want to think about it any more than I
just did. In fact I - with a LOT of work - have pretty
much managed to forget about it except once in a while
something reminds me...

Very intriguing! You seriously could make a living writing
mysteries or science fiction, thanatoid. There's some Conan
Doyle up there, but you've put it well.

Thank you. The idea of writing has been popping into my head all
my life, and many people - although most of them, unlike you,
simply barely able to string together any coherent sentences at
all, and therefore impressed by someone who /sort of/ can - have
suggested I should be one, but what is the point of writing
stuff no one will read? Also, I really have nothing to say, in
spite of managing to post as much as I do.

SNIP

On-retainer extra special "consultants" often make more
than people working at the place full-time.

I'll check into it.

:-)

SNIP

When set through MSConfig, you get 30 seconds. Can it
be doing it each boot? I am unchecked in MSConfig &
still get my menu (for 10 seconds).

MSconfig sucks. That's what Edxor and ini files are for.

I see Edxor is a Notepad repacement.

And a VERY good one, especially since it's free.

But I guess some .ini
file could possibly be responsible for establishing your 30
second BootMenuDelay.

I thought you got us confused. YOU said it reset to 30 - that's
why I never use sysconfig - it's one of those "make it easy but
crash your machine while doing it" (that's EXACTLY what it did
for me) apps MS is so good at.

Mid-typing the first few words I realized you meant the 30-
second "reappearance" of the startup menu I have lived with
forever. No big deal. I've (sort of) learned to live with worse
things, like my personality.

SNIP

It's OK to quit on this & Natasha. You're right, neither is
a critical problem. But what was that other thing-- the
horrible one you won't talk about?

It's a long story and after writing that big paragraph about it,
I have been trying /real hard/ to forget about it again. It was
a REAL nightmare. An app. made my system act like it was virus
possessed - but only after a certain date, and that was after
/years/ of using it. The author denied all culpability. And,
like I said, while I was able to replicate it on different
systems, with several full formats and clean installs, /and/
DISABLE the problem by resetting the computer date, apparently
NO ONE else on Earth had it happen.

I can't remember what gave me the idea of changing the clock,
but had I NOT done it, I probably would not be using a computer
now. It was THAT bad.

In the interest of protecting the guilty /and/ the victim, I
won't name the app - sorry.


--
Lots of theoretical butchers are alleged and other bloody eyes
are suitable, but will Pam secure that?