rc5 client detects modem in win98, but not in win2k?

[Cosmic_Horror]

hi i am running dnetc v2.8010-463-ctr-00071214 for win32, in both win98/win2k daul boot. the dnet client is installed in both operating system (but there is only one copy on the computer, that is i installed it on top of itself).

I have a dail up modem, (yeah yeah i know, i know) but in win98 it detects when the modem is connected and updates the buffers, but in win2k it doesn't?

any ideas how to make the client detect my modem when cracking in win2k?

oh yeah, i do crack for anandtech.

thanks

 

[sciencewhiz]

I have seen this problem before on my work computer, but haven't had a chance to try to fix it. What I do is manually flush the client using dnetc.exe -update.

It used to work (I think), so you might try an older version of the client. Also, the new pre-release client supposedly changed some of the network code, so that might work.

 

[Kilowatt]

W2K is crap with modems.
I could never get one I have installed, and didn't bother buyin another one for it.

It's at work, on a cable modem network anyway, but would of been nice to fax in & out of though.

 

[BGod]

Cosmic, I know exactly what you're talking about. My Win2K machine wouldn't even connect via the LAN to the pProxy on my dual boot 98SE/ME machine that's running ICS through gasp! a 56K modem.

My only recomendation is to try v2.8011-464-GTR-00102500 I used to have to run Task Scheduler hourly to get 3 of my machines to flush to the pProxy (dnetc.exe -update). Now that they are all on it, no more problems fetching or flushing. I know people have reported having lower benchmarks with the newer version, but I assure you that none of my cows have slowed down one bit.

 

[Cosmic_Horror]

oh ok... i am having a bit of trouble with my modem and isp (in win2k but haven't had a lot of ftime to investigate it, and am looking into getting adsl as it is just become availabe where i live...

i can flush the blocks manually when in win2k, and when in win98 it does it itself so i will not run out of packets as i have a day approx 30 hours worth and it is very unlikely that i will not be online for that long at any one time.

thanks for all the help guys i do appricate it...

 

[SpaceWalker]

Cosmic...

I'm trying to understand your problem....

you said you installed your Dnet client twice...

<< (but there is only one copy on the computer, that is i installed it on top of itself). >>

Did you over write the .ini when you installed it the second time?...is the client starting in win98 the same as the client starting in win2k...What connection setting do you have the client set to...0,1, or 2?

&szlig;G&oslash;d...

What's the problem you are having on youe LAN... We have kinda the same setup...Maybe I can help....I have my dual system connecting to the internet, running the client and a pProxy, and my other computers connect just fine using ICS. I have them all running the client and flushing to my pProxy.....

MOOOOOOOOOOOOOOOOOOOOooooooooooooooo..............

 

[BGod]

SpaceWalker, I don't have any more trouble now that I've updated all the machines to the lastest beta. In fact the three machines that I had to use Task Scheduler to force them to flush the the pproxy now do it on their own.

Main machine is Win98se/ME dual-boot: running dnet,pproxy, ppstats, ICS
Dually is Win2K A.S.: running only dnet
All other machines run Win98se or Win95 rev C and work fine now.