Crocodile
- 16 Dec 2002 03:59
Haystack
- 22 Oct 2006 18:33
- 5151 of 11003
Kayak
That was already set. I think it is a spyware problem.
You have to do this
start
run
services.msc
stop (and start "disable") "Remote Access Auto Connection Manager Service
It runs a process called 'rasautou.exe' which is the MS remote access dialler, but it gets highjacked as spyware sometimes.
It seems fine now.
Isaacs
- 24 Oct 2006 10:29
- 5152 of 11003
Here's a weird problem for Office/Outlook experts. I am running Outlook 2003 XP and can't send emails. Basically the send button along with other standard buttons like save and print don't work. Similarly commands off the file menu and some corresponding keyboard shortcuts. Other commands work fine. For a while the send button didn't work but if I saved it as a draft then opened the draft then the send button would work. This was inconvenient but at least I could send messages. Now this doesn't work either. In the past reinstalling the software solved the problem but not this time. Done a quick search of the internet and can't find anyone with this problem so might have to stump and pay for Microsoft support.......please somebody help before I reach those depths....
Isaacs
- 24 Oct 2006 20:54
- 5154 of 11003
Thanks for that klal. I actually found that one this afternoon and still doesn't work. I did at least get send to work in safe mode for a while but now that has packed up as well.
Could be time to switch back to Mozilla. Just got to sort out Pocket Outlook sync.
tvc15
- 24 Oct 2006 21:53
- 5155 of 11003
Isaacs, try a system restore, take it back to a day when it was working properly.
Kayak
- 25 Oct 2006 18:20
- 5157 of 11003
Presumably you're not trying to use OE before your wireless connection is up Alan? It normally takes a few seconds after booting to get going.
DocProc
- 25 Oct 2006 19:48
- 5159 of 11003
Alan
The best web site I know for OE knowledge is:-
http://www.insideoutlookexpress.com/problems/
greekman
- 26 Oct 2006 16:14
- 5160 of 11003
Anyone out there help.
Since downloading/installing IE7 most of the time the last window will not close. Also when it does close and I go to shut down it often will not do so, and although I sometimes get the message showing 'Windows is shutting down' nothing happens even after 5 mins, and I have to manually press the shut down button on the tower.
I am running windows XP, with sp2. This did not occur until the installation of IE7.
DocProc
- 26 Oct 2006 18:53
- 5161 of 11003
greekman
I am getting some of his sh*te with IE7, too.
Things have generally speeded up for me of late after getting rid of a lot of extra Google Too Bar stuff, which I didn't have as much of before I installed IE7 as I did after.
That is, I did have a Google Tool Bar wth IE6 but a lot of extra add-ons mysteriously seemed to have appeared during the IE7 installation. I have now switched them off, particularly one, which was scanning my whole machine so as to allow Google to search it for me as a desk top facility.
greekman
- 27 Oct 2006 10:31
- 5162 of 11003
Thanks DocProc,
I will try same as you over the weekend and let you know the result.
Cheers Greek.
Bolshi
- 27 Oct 2006 12:22
- 5163 of 11003
I'm not getting any problems at all with IE7. Greekman, why don't you try re-installing? It might flush out your problem.
greekman
- 27 Oct 2006 13:26
- 5164 of 11003
Bolshi,
Thanks that will be my plan if DocProc's suggestion does not work.
Mega Bucks
- 27 Oct 2006 13:55
- 5165 of 11003
Problem sorted :-)
Bones
- 29 Oct 2006 19:47
- 5167 of 11003
I have what appears to be a Windows failure on my main computer. Windows XP Pro SP2 running. My daughter tends to be the main user these days as I have my trusty lappie. She is usually on MSN with friends and constantly downloading pics and god knows what else, making websites from Piczo.com etc etc.
Today the thing froze on her and a reboot resulted in the black DOS page saying there was a problem, either start Windows Normally or start using last known working configuration, or use Safe Mode. Usually, last known good config is sufficient, but none of these works. The safe mode comes up with a long list of file names which I have to escape from. The others reboot into the same black DOS screen.
What happens here is there is a millisecond exposure of a blue screen (the sort that shows the technicals of an error - xxxoooooo263784995 etc - you know the thing) but it doesn't stay long enough for me to read it. Instead it just tries to load Windows but goes "click" and presto - black DOS screen.
I assume I have a Windows corruption, and I have no idea what all the BIOS stuff means when I press DEL or TAB to get into those working screens for techies.
Can someone suggest what the problem might be and whether I have any remedies?
The loss of data isn't critical (my daughter might argue otherwise) and I some stuff backed up on a Western Digital hard drive although quite how I recover it I'm not sure. I don't have a boot disk, which may be my fault for not making one?
Thoughts are appreciated before I decide to simply reload Windows from the original Disk and start afresh!
DocProc
- 29 Oct 2006 20:10
- 5168 of 11003
.
Optimist
- 29 Oct 2006 20:29
- 5169 of 11003
Bones
Reloading Windows from the original disk is a last resort, and as the problem may be disc corruption I suggest that in that event, you invest 50 in a new hard disk and install to that. That would leave everything on your old disk for later recovery and is the route you should take if data is important.
As you're not too worried about the data, you should be able to recover the disk by using utillities on the original installation disk. Boot from the installation CD and select the recovery console option (I forget the exact entry path, but it comes up before the main installation, and is the recovery option that does not need a boot disk).
The recovery console will boot into an MSDOS type screen and has a number of recovery commands - including help. Most of them are really good for experts, but mere mortals can use chkdsk. Type chkdsk followed by a space then /? followed by enter to find a list of options.
From memory, you should use chkdsk c: /r but you need to verify the syntax. This will check and attempt to repair any disk errors, when it is finished try rebooting the computer if it still refuses to load windows, boot from the installation disk again, follow the prompts untill it finds your existing installation and you will be given an option to attempt repair of the system. When you select this, the original installation will be recovered but with most of your programs and preferences still installed. You will have to go through multiple Windows updates to bring the system up to date.
Seymour Clearly
- 29 Oct 2006 21:41
- 5170 of 11003
Bones, is this any help - following on from Optimist's post:
http://support.microsoft.com/kb/314058