win me beast

[tx2Step]

so help me if it's the last thing I do I'm gonna whip this beast! anyone have any ideas about why win me would dial up differently with exact settings as a computer I have with 98 se?

I get false connect, shows I'm connect but am not. Takes me sometimes five to 10 tries to actually get connected. Attach my laptop that has 98 se on it and dial up, bang I'm there first hit.

can't get dsl, or anything fancy where I live, don't even have fibre optic phone lines (smile) but never had such trouble dialing up before, have tweaked every setting, gone back to fresh, made new connections - tried everything and still have trouble only with my ME computer.

Anybody got any ideas? Compaq presario, 1.2 gig athlon thunderbird, 512 mg ram, most bells and whistles, running IE 6 and I still believe it's either ME or the last update I took on for IE 6 for "security". Maybe not. But it's driving me nuts. This is my main computer, sometimes only have a few minutes to check email etc and it doesn't help to get half a dozen false connects before I actually get on.

any suggestions greatly appreciated and I will pray for you to win the lottery.

Texas2Step

[tx2Step]

second note, running mcafee but not constant background scan, thought that might be the conflict - it isn't or doesn't seem to be

any thoughts?

[GaryRouth]

Hi tx2Step

1st thing I'd try is a new driver for the modem. 2nd place I'd look is your Compaq support site. 3rd place is to ask your ISP for suggestions . . .

Try different initialization strings for the modem when it dials?

But I'd suspect the driver most of all.
. . . Gary

[HAL9000]

I'll second the modem driver especially if WinME installed it's own. We had a lot of problems in my area with Lucent modems with our cable company and the driver that WinME installed. Updating the driver was all that was required.

[tx2Step]

The thing is it worked for quite a while. Did upgrade driver, made no difference. Logged on this morning, took two tries at 5 am then logged on again at 7 and went right on first time.

I'd like to blame the service, but hard to do when every other computer I connect to with the same exact settings all hits it first time.

If I hadn't had trouble free connection for several months I'd be concerned about drivers. My other problem as always with this computer is that I bought it from a refurbisher (who should remain nameless and rot in hades) and they stripped a great deal of things from it. Serial numbers and other such things that I try to find for my innards have to be gotten out of the box itself, can't access info via windows control panel.

The really crazy thing is my computer shows me as connected. I mean the animation is even blinking like it's live but I get nothing but dead air.

I can't seem to control what windows settings my dialup is connecting at and it always tries for too fast a connection. My phone lines were put in around the 19th century (at least) so I don't get much speed (usually about 24000 max) but even tho I set it to not connect at any higher it tries anyway.

Am hoping windows xp gets bugs out soon, case me and ME have a personality problem but I hate new OS worse than I hate the mystery of my connection woes.

It still all seems like (tho I have senior disease) that it didn't start happening until I downloaded some MS security patch (which of course there's no way to remove). Maybe I ought to do a clean install of IE explorer.... get rid of the bug... it's a possibility.

Texas2step

[AlwaysUp]

First off I haven't experienced much to write home about using IE6. For this reason I still run IE5.01 and am still a happy camper.

As far as the internal component issue and they stripped a great deal of things from it. Serial numbers and other such things that I try to find for my innards have to be gotten out of the box itself I think you might get all you need and more if you were to go to a site called BelArc.com, there you can download a proggie called BelArc Advisor. Check it out.

[tx2Step]

Thanks for the tip. I downloaded belarc, but to be honest my Scisoft Sandra gave me more info. You ought to try it, they have a free download but I liked the program so much I bought it, it's only about $30.

Same thing with belarc. This computer's serial number has been changed to nothing but a series of symbols. The belarc and sandra both tell me only that it's a compaq pc, no system model.

Here's what I think, the refurb company I got this beast from did something shady with more than one computer and ended up with this one and sold it. I've tried just about every innard checker there is out there and they all give the same lacking info about this machine. It's hard even getting help at compaq because I have no serial number. The sales receipt carried a serial number but when I tried to use it at compaq to otain more info about this machine the site told me it wasn't valid.

Best word of caution never buy anything from Micro Exchange in Dallas. This computer was supposed to have win xp pro and had ME and it's been a headache. ME is more of a gamers OS than a real work horse. I'd love to install 98 se on this thing but don't have the time to spend doing it.

Other than the recently occurring connection problem tho I just about have it worked out. But it seems like it's one issue after another. Get one thing fixed another breaks. But the computer passes all stress tests etc and is otherwise pretty decent.

I may try some cable changing. Even tho it's a new phone line connector cable maybe it's faulty. I mean it's possible the way stuff is made now days that the line is just bad and I get haphazard connections because of that.

Dunno, just about at wits end on figuring it out. Have spent weeks trying to get a connection that works in under 15 minutes on a regular basis.

The belarc is pretty nice, but you really should download Scisoft Sandra and give it a try. Excellent program.

Texas2Step

[AlwaysUp]

Yeah, I have Sisoft Sandra Pro, just not installed. I used to on this machine, but there was a few of the benchmarking tools that would seem to lock up my PC. I became less concerned about wringing out little increases to performance and focused upon solid, consistant, headache-free operation. I have now concluded, as much as a Microsoft cheerleader as I am; that with Windows there is no such thing as headache-free! I will steer clear of that Dallas store, though as I am just 60 miles North of Dallas and go there allot for this and that.

[tx2Step]

Did the same myself, not into speed demon or overclock or specialty tricks for faster performance just better handling of the large files and artwork etc that I have to handle every day.

Used to be a MS cheerleader (and still am for win 98se) just not for ME which appears to be an absolute pain in the buttocks and never headache free. Each day is a new experience with ME.

I like the sandra for other info tidbits, there's a lot of good tips in the bios readings and other things that have helped me greatly with getting rid of some ME headaches

Texas2Step

[GaryRouth]

Hi again

Sorry the updated driver didn't do the trick. If your trouble started more-or-less since the last MS Security update, how about trying a System Restore to a restore point prior to the Security patch? If might get at least some of the files back to versions that your modem/ISP like to tango with. Of course, the trick is having a restore point old enough. And...if you've disabled System Restore (usually for performance reasons)...then this tactic won't go.

Whenever modems have trouble with ISPs, I like to let them have the phone line all to themselves. Less than 15ft long a line, and straight from the wall jack to the modem's Line plug. No phones or other modems or fax machines "come before me ..for [modem] am a Jealous [Modem]" (tech version of Exodus) ...If you've got this one covered already, then it's Strike Two for me. (I suggest the line thing, because I've seen Lucent modems slow down to 33.6 when relaying phone line to another computer, but when on their own line alone -even the same line, just without another pc- they can download at 52k+ ...very nice...)

If these two don't do it, I'll look around for Strike Three
. . . Gary

[hmm...just thought of a couple other things...if you have Call Waiting, disable it with your phone's code (usually *70) in the dialup to your ISP. ....and sometimes you get a better connection by dialing 1 then your area code number and your ISPs number... This trick used to help X2 based modems the most, but can't hurt to try... it has to do with how calls get routed through switches at the phone company (the original tip was on a site like modem.com or 56k.com or something like that)]

[highrisemech]

tx2Step, try a different modem in that Compac. It's not the OS nor the ISP especially if your other computers have matched settings and are connecting first shot out. Results can vary a lot when trying different modems in the same computer.

[tx2Step]

I have just about figured it will be the new modem route. tried all the things you listed Gary, but thanks for the info anyway. Don't have call waiting or any other interferences. It probably does boil down to the modem. My laptop signs me on instantly and so does any other computer I connect to the end of my connection cable. All cables are new, phone line is dedicated only to my internet use and is a good clean line (well best I can get considering the older phone lines we have). But since I can't replicate the problem on other computers and they all dial right in modem is the last ditch but probably the main problem.

I do get connected sometimes immediately, but seldom - usually it's two to five tries and even a restart of computer in between.

Thanks everyone. I'll check into a new modem for this beast and maybe stop blaming win ME <smile>

Texas2Step

[GaryRouth]

The interesting thing is: that the Compaq itself used to connect with no problem, like your other pcs & notebooks ...until recently?

It's a $40 question. That's what the going rate is for a USR 2977 internal PCI "controller-based" or "hardware" modem. Also available at that price is an external based on Intel/Ambit/Cirrus logic chips (also "controller based") OEM boxes...the lastest at Fry's is some importer named "Modular". Since your box is modern, I'd go for the USR 2977 hardware PCI internal. The external USR cost about twice as much.

You'll need to thoroughly uninstall the previous modem if you decide to add a new one, of course.

Good luck ...24k connects are no fun
. . . Gary

[tx2Step]

Of course the crazy thing is my SciSoftSandra tells me my modem is fine and this afternoon I connected first time no problem. It's so intermittent I can't figure out what step to make next, feels like I've made them all...

I have an external moden that I know is good, may uninstall modem and install it and see what happens. I don't mind spending $40 or $50 for internet happiness but sure hate to do it if don't need to.

Yes it's crazy just had a client bring his laptop by today. He has a young student employee who has been playing with his computer while he was out of the office and of course the kid has fouled up some stuff. He wanted me to get him straightened out so I worked on his computer for a couple of hours then got online with it to make sure his connections and everything were good, they were and I got connected at about twice the normal speed I get so maybe modem is the key.

Slow sometimes and not connecting sometimes it could be. But why does my computer show me I'm connected (like a false connection even the icon is blinking). Haven't a clue on that.

May try the external this evening. Thanks Gary

Texas2Step

[GaryRouth]

Hmmm been re-reading your posts.... when you say the other machines are using the same settings: are you referring to the same ISP dialup numbers, port speeds, receiving modem type, etc? Are the modems similiar enough to use the exact same settings? That's why I mentioned the initialization string earlier, since the different chips have fairly different needs as far as those strings go.

Sometimes if a modem is an older USR-type, it will do better dialing into a line identified by the ISP as "X2/v.90", even though it should Theoretically be fine with any v.90 modem pool. Same idea for the older "Kflex" models (I think they were Rockwell based), they do better dialing into modem pools identified as "Kflex/v.90".

Of course, you probably know all of this already, but I thought I'd mention it just in case.

I like to use the initialization string that I find in the ".inf" file for my modem in the \Windows\Inf\Other folder. (It would also be on any installation disk that came with the modem). Those strings often work better than what the ISPs software guesses at. I find that the strings are particularly important for the WinModems.
_____
False Connect --- seems like the only way you'd get a false connect is if your software thinks it's sensing an active connection from a previous connection attempt . . . that didn't disconnect itself properly. I've seen this happen in the CompuServe software. If a connection to the local modem pool is good, but "the network doesn't respond" (the relay from local subcontractor to CompuServe doesn't happen) - then that first connection isn't properly ended, and the software still thinks there's a good connection. ---Does that match your case at all?
After five or six more tries, the modem usually gets reset, and a good connection happens. If you find another reason, I'd be glad to hear it, because it might be helpful if we run across it again in the future . . .

I'll bet the external has you connecting around 48000 already, and this is idle reading!

. . . Gary

[tx2Step]

Arggghhh... after unistalling, installing and reinstalling the plot thickens. Get same thing with external modem. Back to square one. I think what I'm going to do is download and reinstall IE6 and maybe whatever glitch I got with the patch won't be in it.

Also think I'm going to send a nasty email to support at my internet service company. Long time ago had a problem getting disconnected about every hour, complained and it stopped happening (even though they said they weren't causing the problem).

Am now totally confused. I can't think of anything I haven't checked, rechecked, installed uninstalled, adjusted readjusted tested and retested. Whew guess by now I should just be glad I can get online at all.

Don't think I will ever understand how something that ain't broke and wasn't messed with all of a sudden went crazy.

But thanks to everyone here for all the suggestions. Maybe dynamite in the floppy drive will help me..... smile

Texas2Step

[ConLog]

I still have IE5.5 running on my WindowsME OS because everytime I install IE6.0 I get all kinds of problems. Also, since I stopped WindowsME from doing automatic updates it has run oh so smoothly.

[tx2Step]

Well all one has to do is use the old thinker. What's on my Win ME that's not on the other computers I'm using for dialing in? Took me however long since this post began and a couple of months back to figure this one out, but for anyone else that uses a little program called PGP - it can be the source of similar problems.
I changed the settings within PGP (turned off the adapter settings basically) and dialed up first shot no problem. Was so stunned I disconnected and connected again - same thing. Figured it must be a freak accident so disconnected and dialed up again. Bingo.

Went to PGP site to FAQ and here's what I found:

PGP Desktop Security Win32 - FAQs



Question:
Why has PGP Disabled my NIC's bindings to the TCP/IP & WINS Protocols?

Answer:

We will use 3com as an example in this explanation.

PGP has removed the 3com’s bindings to TCP/IP & WINS, PGP then bound the 3com to the PGPNet VPN Driver.

Now the PGPNet VPN Driver is Linked to the PGPNet VPN Lan Adaptor, Which is then bound to the TCP/IP & WINS Protocols.

In summary PGP has placed its driver between the Network Interface Card (3com) and TCP/IP & WINS Protocols.


Somewhere within this mass lies my problem. Of course I'll have to reconnect the adapter setting when I use PGP, but it has to be it. I dialed up several times first shot as long as their re-routing was disconnected.

They must have a glitch somewhere in the new version.

I may be fixed! Yeah! Everything is working right again.

Texas2Step

[GaryRouth]

Odd all around: do you actually use that program for "tunnelling" for virtual private networking? Even some versions of AOL and IE will install VPN adaptors, but they don't usually kill the dial-up much. Sure sounds like PGP may have a patch for you someday.

Did it also help the connect speeds? I wonder if that program assumes you're on a LAN and sets the MTU and such to 1500k, which can cause POTS dialup to suffer.

Thanks for posting your solution, anyone with PGP and strange dialup problems will see your post if they search the forum using those two keywords . . .

. . . Gary

(I haven't heard of that program before. Other than killing your dialup, did it do it's other jobs well?)

[tx2Step]

PGP is a security program for encryption of credit card numbers or other sensitive data traveling over the Net. I only use it when obtaining the orders from my ecommerce site. Surely they will offer a patch, but I think it's ME and PGP related because I don't have this problem on my Win 98SE computer.

I am connecting faster, getting 33333 instead of 24000 and even sometimes getting into the 40000's without the PGP interference. I think the recent patch PGP did have might have been a problem. Am going to reinstall the PGP and not the patch and see what happens.

PGP is widely used I think anyone who wants encryption of email etc probably uses it at some point. The program works well and does it's job other than it doesn't seem to like Win ME or vice versa.

Thanks to everyone for the suggestions and info. This one was like trying to pin down a ghost.

Texas2Step