Please wait......

  • Thread starter Thread starter rmo555
  • Start date Start date
R

rmo555

I wrote: This just started to happen: Quite often when I'm booting, I
get a blue screen and at the top, it says: Please wait.........
the 'periods' keep appearing until the screen goes away and my PC
continues to boot. What could be causing this and how do I correct it?
It can't be the drive because I have a clone and it happens on both
'clones.' Thanks..........

Mark wrote back: Create a new user ID and password. It my be a corrupt
user profile doing an autologon.


If I create a new User ID and password, how do I keep the same Desktop
and QuickLaunch area? You see, I use TrueLaunch Bar so my Desktop is
very specific and complicated - and I would hate to have to reconstruct
it. Also, are there any other possibilities that could be causing this
problem that I could look in to? Thank you........
 
From: <[email protected]>

| I wrote: This just started to happen: Quite often when I'm booting, I
| get a blue screen and at the top, it says: Please wait.........
| the 'periods' keep appearing until the screen goes away and my PC
| continues to boot. What could be causing this and how do I correct it?
| It can't be the drive because I have a clone and it happens on both
| 'clones.' Thanks..........
|
| Mark wrote back: Create a new user ID and password. It my be a corrupt
| user profile doing an autologon.
|
| If I create a new User ID and password, how do I keep the same Desktop
| and QuickLaunch area? You see, I use TrueLaunch Bar so my Desktop is
| very specific and complicated - and I would hate to have to reconstruct
| it. Also, are there any other possibilities that could be causing this
| problem that I could look in to? Thank you........

If this has to do with a previous thread then you have replied to that thread and NO created
a new one.
 
From: <[email protected]>

| I wrote: This just started to happen: Quite often when I'm booting, I
| get a blue screen and at the top, it says: Please wait.........
| the 'periods' keep appearing until the screen goes away and my PC
| continues to boot. What could be causing this and how do I correct it?
| It can't be the drive because I have a clone and it happens on both
| 'clones.' Thanks..........
|
| Mark wrote back: Create a new user ID and password. It my be a corrupt
| user profile doing an autologon.
|
| If I create a new User ID and password, how do I keep the same Desktop
| and QuickLaunch area? You see, I use TrueLaunch Bar so my Desktop is
| very specific and complicated - and I would hate to have to reconstruct
| it. Also, are there any other possibilities that could be causing this
| problem that I could look in to? Thank you........

If this has to do with a previous thread then you have replied to that thread and NO created
a new one.
Click to expand...

I don't understand. This shows as a new thread on my PC. I created a
new thread because the older one was too old and I didn't expect anyone
would go back to see if I wrote anymore about the subject.
 
From: <[email protected]>


|
| I don't understand. This shows as a new thread on my PC. I created a
| new thread because the older one was too old and I didn't expect anyone
| would go back to see if I wrote anymore about the subject.

If anyone was following the older thread it would be marked as being followed and responders
would again chime in.

This was a new thread but belonged in the old thread to keep the subject matter contiguous.
New threads should be created for new subject matter. In fact I just responded to a thread
that wasn't active for ~9 days.

This is my advice based upon NUMEROUS years of accessing News Groups on Usenet and off
Usenet.
 
From: <[email protected]>


|
| I don't understand. This shows as a new thread on my PC. I created a
| new thread because the older one was too old and I didn't expect anyone
| would go back to see if I wrote anymore about the subject.

If anyone was following the older thread it would be marked as being followed and responders
would again chime in.

This was a new thread but belonged in the old thread to keep the subject matter contiguous.
New threads should be created for new subject matter. In fact I just responded to a thread
that wasn't active for ~9 days.

This is my advice based upon NUMEROUS years of accessing News Groups on Usenet and off
Usenet.
Click to expand...
Thanks, I'll keep this in mind. However, I've had the opposite
experience where I've posted a follo- up but not received a reply
(presumably because the original responder(s) were not looking or
following anymore. I wanted to be sure I got a new response.
 
From: <[email protected]>


| Thanks, I'll keep this in mind. However, I've had the opposite
| experience where I've posted a follo- up but not received a reply
| (presumably because the original responder(s) were not looking or
| following anymore. I wanted to be sure I got a new response.

Understandable.

Post a reply in the original thread. If it remains unanswered for 24hrs then create a new
thread and in the replay state that your post was un-answered and point to the old thread.
This way responders of the new thread can research the subject matter of the old thread.
 
From: <[email protected]>


| Thanks, I'll keep this in mind. However, I've had the opposite
| experience where I've posted a follo- up but not received a reply
| (presumably because the original responder(s) were not looking or
| following anymore. I wanted to be sure I got a new response.

Understandable.

Post a reply in the original thread. If it remains unanswered for 24hrs then create a new
thread and in the replay state that your post was un-answered and point to the old thread.
This way responders of the new thread can research the subject matter of the old thread.
Click to expand...

OK, will do. Thanks.......
 
Back
Top