moray

Has anyone tried reallocating hardware to different IRQs under win2K to avoid sharing on IRQ9? I have been having problems with CFS2 and the only thing left to me that I haven't done from the list of suggestions is to manually move my graphics and sound cards to different interrupts. This is a major hassle as it seems to involve reinstalling windows due to the (ultra-smart) Microsoft ACPI and HAL automatic assigning of P&P hardware to interrupts. Anyone got any smarter ideas? Cheers Mozzer

Has anyone successfully installed this drive under win2k and if so has anyone encountered any problems? I am still wrestling with the installation and will post my experiences soon, but wanted to hear about everyone else's thoughts first. Cheers Moray

Has anyone else encoutered problems using Netmeeting under Win2kPro? I am Ok when it starts up and conncecting to another user is also fine. It is when I disconnect, the program hangs and I can't shift it even with Ctr Alt Del and task manager. It sits there completely lifeless for about 5 minutes then crashes me out of windows altogether. I don't think it is conflicting with anythin g else as I can open the program and close it normally as long as I have not connected to another user. AS soon as the connection is established it is inevitable that it will crash at some point. Also video performance on NM is pretty poor. I am using Creative Webcam Go Plus Thanks in advance Moray

Anyone know anything about upgrading the processor on a Dell Desktop machine? The Dell website says "don't do it" and come up with some lame excuse about their moBos being carefully balanced to support the components supplied. I have a Dell Dimension PII 350MHz and have upgraded or replaced about every other compnent except for the board and processor. Does anyone have any experience of ripping bits of Dell circuitry out and replacing it with something more up to date? Thanks Moray

Hi again I thought you might be interested to look at this page. It shows good pictures of a P2 to P3 upgrade in progress. http://mav.net/phil/dell.shtml

Thanks for all the comments on this thread however I must disagree with Igor about the possibility of upgrading a P2 machine with a P3 chip. This site, lays it all out complete with testimonies from user who have successfully done it. http://roberthancock.netfirms.com/dell/index.htm The key point is that there is the newer P3 chips run on LOWER voltages than the old P2 chips (until you get towards 1GHz) so there is no problem with the power supply. The P3 has its own heatsink and fan and the motherboard (a variant of the Intel SE440BX) has a socket to plug the fan straight in so there shouldn't be a cooling problem. The bios will not recognise the chip as a P3 because the board and Bios were both created before the advent of P3 chips, however although wrongly labelling the chip it still runs and everything zips along a hell of a lot faster than it did before. Or so I am told....I'll be trying it out soon and will let you know if I run into problems - i am prepared to eat my words if it all goes pear-shaped!! Moray

This is turning into an interesting thread. I have since discovered that the mobo was based on the Intel SE440BX Slot 1 board. BIOS is flashed as far as it will go. There is an excellent online resource for any other Dell owners wanting to upgrade here http://roberthancock.netfirms.com/dell/index.htm There are a few issues regarding processor voltage and potential thermal overloading, but all things considered, it looks like I can just swap processors and not worry about new power supply or mobo. Different processor architecture is a consideration (SECC or SECC2 vs PCA or FC-PCA) and may necessitate a slocket (socket adaptor). See also the Delltalk upgrade forum for info http://webtalk.us.dell.com

Thanks for the suggestion Kingtrey What does everyone else think about this? Will the motherboard be happy if I just replace the PII 350MHz chip with a PIII x00 chip? Do I need a new power supply or fan or anything else? Regarding the case issue - I have replaced the graphics card, hard drive and internal modem and added RAM. None of this has any implication for the space within the case. Moray

OK - here's the story. I was running NT4 and upgraded to win2k with no problems. Half life ran under NT and ran under 2000. Fine. Then I had to reformat my disk and reinstall Win2k. Since then I have taken the opportunity to load the most recent video drivers for my Matrox G400 Max(5.51) and reinstall HL with the most recent patch (1.1.0.4). The result? Menu screen opens up but the game doesn't run. Under OpenGL it says something like unable to run current version of OpenGL and under D3D it almost runs but the screen has lots of glitches and runs at about 1fps.... I have also installed DX8.0a. Any idea whether it is my video driver, HL patch or DX8 that is causing the screw up??

Unreal Tournament runs with no problems in NT4 Did you think of using the extensive listings on this site to check for game compatibility? It is called "NTCompatible" after all.... To that list you can add Diablo, Starcraft, Age of Empires 2, Links LS and many more.....

Sorry to bore you good folks with a dull post like this but..... I have a MS Intellimouse which I have always just used as a non-wheel mouse. Now that I'm happily running Win2K I thought I'd resurrect its wheel capabilities, but I've had no joy so far. Windows detects it and loads PS/2 drivers. I installed the Intellipoint software but that didn't seem to affect the device manager listing as basic PS/2 mouse. Also I now notice that the keyboard and mouse are listed as conflicting hardware although both are functioning fine. msi8042 is listed as loaded on IRQ1 and 12 and the mouse also shares IRQ12. Any suggestiobns for getting the correct mouse driver loaded? After uninstalling the PS/2 driver should I also unplug the mouse so that windows doesn't detect it and reload basic PS/2 driver on startup???? Thanks

Thanks Wolf This sounds like the sort of thing that I want. When I uninstalled the Intellipoint software, the msi8042 port seems to stay activated and conflicts with other hardware resources but to no obvious ill efect. I just hate having yellow exclamation points!! To clarify, it is a PS/2 mouse - not USB. I just wasn't sure when the correct driver wsa being loaded as it always reports a basic PS/2 device and the wheel didn't seem to work. Moray

This is driving me nuts - I hope you guys can come up with something...! I have installed the USR/3com 56k voice internal PCI modem into my Windows 2000 system. The modem was successfully recognised and the drivers which were supplied were loaded. The modem is able to dial out. However the first 2 times I tried to dial my ISP it connected with reported rates of 28.8bps and 50.6bps. On both occasions the modem was unable to send or receive any data, it just sat there doing nothing. Subsequent attempts to connect stalled at the "verifying username and password" stage of connection. My details have not been changed as I was previously able to connect with an ISA sportster x2 flash upgraded to v.90 under NT4 and I have simply upgraded to Win 2000. Using hyperterminal I was able to dial out using the PCI modem again, however about 5 seconds after connecting to a remote number it would autiomatically disconnect. Hyperterminal would display the message "busy". The "disconnect if idle" option is not selected in modem properties. The modem seemed to install on COM3 and IRQ9 (which is shared with several other devices according to ACPI principles) but there is no conflict report. I manually changed the modem properties to COM2 but this made no difference. COM2 was not displayed as installed under Device Manager / Ports. I am using the supplied cable and adapter to connect to my analogue phone line. The line is obviouly good enough to support a 3com modem as it was connecting every time without problems using my old sportster under NT4. Do you have any advice?

Yeah - except my "method" wasn't exactly sophisticated - I just reformatted my disk and reinstalled everything....!

test

I had already thought of that and tried to change the IRQ before without any success. It was on IRQ9 before (when it didn't work) and it is again installed on IRQ9 so there doesn't seem to be an issue there.

After that monster post (sorry) you will be glad to know that I have finally sorted out my mystery problem. I still have no idea what was wrong. I tweaked everything I possibly could 9steady...) and in the end took the last resort - reformated and reinstalled Win2000. Modem now dials up and transmits data without problems except it seems to occasionally connect at 28.8k which it never did before. Anyway, I am happy so smile for me!!

I have installed the 56k voice internal PCI modem into my Windows 2000 system. The modem was successfully recognised and the drivers which were supplied were loaded. The modem is able to dial out. However the first 2 times I tried to dial my ISP it connected with reported rates of 28.8bps and 50.6bps. On both occasions the modem was unable to send or receive any data, it just sat doing nothing. Subsequent attempts to connect stalled at the "verifying username and password" stage of connection. My details have not been changed as I was previously able to connect with a sportster x2 flash upgraded to v.90 under NT4 and I have simply upgraded to Win 2000. Using hyperterminal I was able to dial out using the PCI modem again, however about 5 seconds after connecting to a remote number it would autiomatically disconnect. Hyperterminal would display the message "busy". The "disconnect if idle" option is not selected in modem properties. The modem seemed to install on COM3 and IRQ9 (which is shared with several other devices thanks to ACPI) but there is no conflict report. I manually changed the modem properties to COM2 but this made no difference. COM2 was not displayed as installed under Device Manager / Ports. I am using the supplied cable and adapter to connect to my analogue phone line. The line is obviouly good enough to support a 3com modem as it was connecting every time without problems using my old sportster under NT4. Do you have any advice?

After that monster post (sorry) you will be glad to know that I have finally sorted out my mystery problem. I still have no idea what was wrong. I tweaked everything I possibly could 9steady...) and in the end took the last resort - reformated and reinstalled Win2000. Modem now dials up and transmits data without problems except it seems to occasionally connect at 28.8k which it never did before. Anyway, I am happy so smile for me!!

Unfortunately, disabling multi-link and LCP didn't make any difference Here's an extract from the modem log showing what happened. The first time I try to connect it seems to work, but only connect at 28.8k - nothing happens after that. When I disconnect and then try to reconnect, it will stall at the "authenticating password" stage. 02-20-2001 23:55:30.850 - Modem type: U.S. Robotics 56K Voice Win Int 02-20-2001 23:55:30.850 - Modem inf path: mdm00c4.inf 02-20-2001 23:55:30.850 - Modem inf section: Modem1807_2K 02-20-2001 23:55:30.881 - Opening Modem 02-20-2001 23:55:30.881 - 115200,8,N,1, ctsfl=1, rtsctl=2 02-20-2001 23:55:30.881 - Initializing modem. 02-20-2001 23:55:30.891 - Send: AT<cr> 02-20-2001 23:55:30.901 - Recv: AT<cr> 02-20-2001 23:55:30.901 - Command Echo 02-20-2001 23:55:30.901 - Recv: <cr><lf>OK<cr><lf> 02-20-2001 23:55:30.901 - Interpreted response: OK 02-20-2001 23:55:30.911 - Send: AT&F&A0&B1&C1&D2E0Q0V1S0=0<cr> 02-20-2001 23:55:30.921 - Recv: AT&F&A0&B1&C1&D2E0Q0V1S0=0<cr> 02-20-2001 23:55:30.921 - Command Echo 02-20-2001 23:55:30.921 - Recv: <cr><lf>OK<cr><lf> 02-20-2001 23:55:30.921 - Interpreted response: OK 02-20-2001 23:55:30.941 - Send: AT+ILRR=1;+MR=1;+ER=1;+DR=1<cr> 02-20-2001 23:55:30.951 - Recv: <cr><lf>OK<cr><lf> 02-20-2001 23:55:30.951 - Interpreted response: OK 02-20-2001 23:55:30.961 - Send: ATS7=60S19=0L2M1+ES=3,0,2;+DS=3,0;<cr> 02-20-2001 23:55:30.971 - Recv: <cr><lf>OK<cr><lf> 02-20-2001 23:55:30.971 - Interpreted response: OK 02-20-2001 23:55:30.981 - TSP(0000): Making call 02-20-2001 23:55:30.981 - Send: AT+IFC=2,2;B0X4<cr> 02-20-2001 23:55:30.981 - Recv: <cr><lf>OK<cr><lf> 02-20-2001 23:55:30.981 - Interpreted response: OK 02-20-2001 23:55:30.981 - Waiting for a call. 02-20-2001 23:55:30.991 - Send: ATS0=0<cr> 02-20-2001 23:55:31.021 - Recv: <cr><lf>OK<cr><lf> 02-20-2001 23:55:31.021 - Interpreted response: OK 02-20-2001 23:55:31.021 - 115200,8,N,1, ctsfl=1, rtsctl=2 02-20-2001 23:55:31.021 - Initializing modem. 02-20-2001 23:55:31.031 - Send: AT<cr> 02-20-2001 23:55:31.031 - Recv: <cr><lf>OK<cr><lf> 02-20-2001 23:55:31.031 - Interpreted response: OK 02-20-2001 23:55:31.061 - Send: AT&F&A0&B1&C1&D2E0Q0V1S0=0<cr> 02-20-2001 23:55:31.071 - Recv: <cr><lf>OK<cr><lf> 02-20-2001 23:55:31.071 - Interpreted response: OK 02-20-2001 23:55:31.081 - Send: AT+ILRR=1;+MR=1;+ER=1;+DR=1<cr> 02-20-2001 23:55:31.131 - Recv: <cr><lf>OK<cr><lf> 02-20-2001 23:55:31.131 - Interpreted response: OK 02-20-2001 23:55:31.141 - Send: ATS7=60S19=0L2M1+ES=3,0,2;+DS=3,0;<cr> 02-20-2001 23:55:31.151 - Recv: <cr><lf>OK<cr><lf> 02-20-2001 23:55:31.151 - Interpreted response: OK 02-20-2001 23:55:31.161 - Send: AT+IFC=2,2;B0X4<cr> 02-20-2001 23:55:31.161 - Recv: <cr><lf>OK<cr><lf> 02-20-2001 23:55:31.161 - Interpreted response: OK 02-20-2001 23:55:31.161 - Dialing. 02-20-2001 23:55:31.161 - TSP(0000): LINEEVENT: LINECALLSTATE_DIALING 02-20-2001 23:55:31.161 - TSP(0000): LINEEVENT: LINECALLSTATE_PROCEEDING 02-20-2001 23:55:31.171 - Send: ATDT####,###########<cr> 02-20-2001 23:56:03.527 - Recv: <cr><lf>+MCR: V90<cr><lf> 02-20-2001 23:56:03.527 - Interpreted response: Informative 02-20-2001 23:56:03.527 - Recv: <cr><lf>+MRR: 28800<cr><lf> 02-20-2001 23:56:03.527 - Interpreted response: Informative 02-20-2001 23:56:03.527 - Recv: <cr><lf>+ER: MNP<cr><lf><cr><lf>+DR: MNP5<cr><lf><cr><lf> 02-20-2001 23:56:03.527 - An unknown response was received while attemping to connect, but CD was high so completeing successfully 02-20-2001 23:56:03.527 - Connection established at 28800bps. 02-20-2001 23:56:03.527 - Error-control off or unknown. 02-20-2001 23:56:03.527 - Data compression off or unknown. 02-20-2001 23:56:03.527 - TSP(0000): LINEEVENT: LINECALLSTATE_CONNECTED 02-20-2001 23:56:33.531 - Read: Total: 0, Per/Sec: 0, Written: Total: 0, Per/Sec: 0 02-20-2001 23:58:21.736 - CD dropped--Remote modem hung up. ModemStatus=00000038 02-20-2001 23:58:21.736 - TSP(0000): LINEEVENT: LINECALLSTATE_DISCONNECTED(0x1) 02-20-2001 23:58:21.736 - TSP(0000): Dropping call 02-20-2001 23:58:21.736 - Hanging up the modem. 02-20-2001 23:58:22.367 - Recv: <cr><lf>NO CARRIER<cr><lf> 02-20-2001 23:58:22.367 - Interpreted response: No Carrier 02-20-2001 23:58:22.377 - Send: ATH<cr> 02-20-2001 23:58:22.708 - Recv: <cr><lf>OK<cr><lf> 02-20-2001 23:58:22.708 - Interpreted response: OK 02-20-2001 23:58:22.718 - Send: at#ud<cr> 02-20-2001 23:58:22.728 - Recv: <cr><lf>DIAG 02-20-2001 23:58:22.728 - Interpreted response: Diagnostic Info 02-20-2001 23:58:22.728 - Recv: <2A4D3263 0=10><cr><lf> 02-20-2001 23:58:22.728 - Recv: <cr><lf>DIAG 02-20-2001 23:58:22.728 - Interpreted response: Diagnostic Info 02-20-2001 23:58:22.728 - Recv: <2A4D3263 1=7 2=0 3=0><cr><lf> 02-20-2001 23:58:22.728 - Recv: <cr><lf>DIAG 02-20-2001 23:58:22.728 - Interpreted response: Diagnostic Info 02-20-2001 23:58:22.728 - Recv: <2A4D3263 4="E0C1651390478D"><cr><lf> 02-20-2001 23:58:22.728 - Recv: <cr><lf>DIAG 02-20-2001 23:58:22.728 - Interpreted response: Diagnostic Info 02-20-2001 23:58:22.728 - Recv: <2A4D3263 5=><cr><lf> 02-20-2001 23:58:22.728 - Recv: <cr><lf>DIAG 02-20-2001 23:58:22.728 - Interpreted response: Diagnostic Info 02-20-2001 23:58:22.728 - Recv: <2A4D3263 10=14><cr><lf> 02-20-2001 23:58:22.728 - Recv: <cr><lf>DIAG 02-20-2001 23:58:22.728 - Interpreted response: Diagnostic Info 02-20-2001 23:58:22.728 - Recv: <2A4D3263 11=F><cr><lf> 02-20-2001 23:58:22.728 - Recv: <cr><lf>DIAG 02-20-2001 23:58:22.728 - Interpreted response: Diagnostic Info 02-20-2001 23:58:22.728 - Recv: <2A4D3263 12=3202><cr><lf> 02-20-2001 23:58:22.728 - Recv: <cr><lf>DIAG 02-20-2001 23:58:22.728 - Interpreted response: Diagnostic Info 02-20-2001 23:58:22.728 - Recv: <2A4D3263 13=0><cr><lf> 02-20-2001 23:58:22.728 - Recv: <cr><lf>DIAG 02-20-2001 23:58:22.728 - Interpreted response: Diagnostic Info 02-20-2001 23:58:22.728 - Recv: <2A4D3263 14=E><cr><lf> 02-20-2001 23:58:22.728 - Recv: <cr><lf>DIAG 02-20-2001 23:58:22.728 - Interpreted response: Diagnostic Info 02-20-2001 23:58:22.728 - Recv: <2A4D3263 15=0><cr><lf> 02-20-2001 23:58:22.728 - Recv: <cr><lf>DIAG 02-20-2001 23:58:22.728 - Interpreted response: Diagnostic Info 02-20-2001 23:58:22.728 - Recv: <2A4D3263 16=E><cr><lf> 02-20-2001 23:58:22.728 - Recv: <cr><lf>DIAG 02-20-2001 23:58:22.728 - Interpreted response: Diagnostic Info 02-20-2001 23:58:22.728 - Recv: <2A4D3263 17=E><cr><lf> 02-20-2001 23:58:22.728 - Recv: <cr><lf>DIAG 02-20-2001 23:58:22.728 - Interpreted response: Diagnostic Info 02-20-2001 23:58:22.728 - Recv: <2A4D3263 20=C 21=E><cr><lf> 02-20-2001 23:58:22.788 - Recv: <cr><lf>DIAG 02-20-2001 23:58:22.788 - Interpreted response: Diagnostic Info 02-20-2001 23:58:22.788 - Recv: <2A4D3263 22=C80><cr><lf> 02-20-2001 23:58:22.788 - Recv: <cr><lf>DIAG 02-20-2001 23:58:22.788 - Interpreted response: Diagnostic Info 02-20-2001 23:58:22.788 - Recv: <2A4D3263 23=1F40><cr><lf> 02-20-2001 23:58:22.848 - Recv: <cr><lf>DIAG 02-20-2001 23:58:22.848 - Interpreted response: Diagnostic Info 02-20-2001 23:58:22.848 - Recv: <2A4D3263 24=780><cr><lf> 02-20-2001 23:58:22.848 - Recv: <cr><lf>DIAG 02-20-2001 23:58:22.848 - Interpreted response: Diagnostic Info 02-20-2001 23:58:22.848 - Recv: <2A4D3263 25=780><cr><lf> 02-20-2001 23:58:22.848 - Recv: <cr><lf>DIAG 02-20-2001 23:58:22.848 - Interpreted response: Diagnostic Info 02-20-2001 23:58:22.848 - Recv: <2A4D3263 26=7080 27=C5EA><cr><lf> 02-20-2001 23:58:22.848 - Recv: <cr><lf>DIAG 02-20-2001 23:58:22.848 - Interpreted response: Diagnostic Info 02-20-2001 23:58:22.848 - Recv: <2A4D3263 30=0><cr><lf> 02-20-2001 23:58:22.848 - Recv: <cr><lf>DIAG 02-20-2001 23:58:22.848 - Interpreted response: Diagnostic Info 02-20-2001 23:58:22.848 - Recv: <2A4D3263 31=0><cr><lf> 02-20-2001 23:58:22.848 - Recv: <cr><lf>DIAG 02-20-2001 23:58:22.848 - Interpreted response: Diagnostic Info 02-20-2001 23:58:22.848 - Recv: <2A4D3263 32=0 33=0><cr><lf> 02-20-2001 23:58:22.848 - Recv: <cr><lf>DIAG 02-20-2001 23:58:22.848 - Interpreted response: Diagnostic Info 02-20-2001 23:58:22.848 - Recv: <2A4D3263 34=7080 35=C5EA><cr><lf> 02-20-2001 23:58:22.848 - Recv: <cr><lf>DIAG 02-20-2001 23:58:22.858 - Interpreted response: Diagnostic Info 02-20-2001 23:58:22.858 - Recv: <2A4D3263 40=2><cr><lf> 02-20-2001 23:58:22.858 - Recv: <cr><lf>DIAG 02-20-2001 23:58:22.858 - Interpreted response: Diagnostic Info 02-20-2001 23:58:22.858 - Recv: <2A4D3263 41=80 42=0 43=0 44=80><cr><lf> 02-20-2001 23:58:22.858 - Recv: <cr><lf>DIAG 02-20-2001 23:58:22.858 - Interpreted response: Diagnostic Info 02-20-2001 23:58:22.858 - Recv: <2A4D3263 50=2 51=2><cr><lf> 02-20-2001 23:58:22.858 - Recv: <cr><lf>DIAG 02-20-2001 23:58:22.858 - Interpreted response: Diagnostic Info 02-20-2001 23:58:22.858 - Recv: <2A4D3263 52=509 53=38B 54=0 55=0><cr><lf> 02-20-2001 23:58:22.858 - Recv: <cr><lf>DIAG 02-20-2001 23:58:22.858 - Interpreted response: Diagnostic Info 02-20-2001 23:58:22.858 - Recv: <2A4D3263 56=49 57=3E 58=0 59=0><cr><lf> 02-20-2001 23:58:22.858 - Recv: <cr><lf>DIAG 02-20-2001 23:58:22.858 - Interpreted response: Diagnostic Info 02-20-2001 23:58:22.858 - Recv: <2A4D3263 60=51><cr><lf> 02-20-2001 23:58:22.858 - Recv: <cr><lf>DIAG 02-20-2001 23:58:22.858 - Interpreted response: Diagnostic Info 02-20-2001 23:58:22.858 - Recv: <2A4D3263 FF=3COM-USROBOTICS><cr><lf> 02-20-2001 23:58:22.858 - Recv: <cr><lf>OK<cr><lf> 02-20-2001 23:58:22.858 - Interpreted response: OK 02-20-2001 23:58:22.858 - Diagnostics 02-20-2001 23:58:22.858 - Modem Diagnostics: 02-20-2001 23:58:22.858 - Version 1.0 02-20-2001 23:58:22.858 - Call Setup Result: Data Answering signal detected 02-20-2001 23:58:22.858 - Multi-media mode: Data Only 02-20-2001 23:58:22.858 - DTE-DCE interface mode: Async data 02-20-2001 23:58:22.858 - V.8 CM octet string: "E0C1651390478D" 02-20-2001 23:58:22.858 - Received signal power level (in -dBm): 20 02-20-2001 23:58:22.858 - Transmit signal power level (in -dBm): 15 02-20-2001 23:58:22.858 - Estimated noise level (in -dBm): 12802 02-20-2001 23:58:22.858 - Normalized Mean Squared error: 0 02-20-2001 23:58:22.858 - Near echo loss: 14 dB 02-20-2001 23:58:22.858 - Far echo loss: 0 dB 02-20-2001 23:58:22.858 - Far echo delay: 14 ms 02-20-2001 23:58:22.858 - Round Trip delay: 14 ms 02-20-2001 23:58:22.928 - Transmit Carrier Negotiation Result: V.34 02-20-2001 23:58:22.928 - Receive Carrier Negotiation Result: V.pcm (asymmetric) 02-20-2001 23:58:22.928 - Transmit Carrier symbol rate: 3200 02-20-2001 23:58:22.928 - Receive Carrier symbol rate: 8000 02-20-2001 23:58:22.928 - Transmit Carrier frequency: 1920 02-20-2001 23:58:22.928 - Receive Carrier frequency: 1920 02-20-2001 23:58:22.928 - Initial transmit carrier data rate: 28800 02-20-2001 23:58:22.928 - Initial receive carrier data rate: 50666 02-20-2001 23:58:22.928 - Temporary carrier loss event count: 0 02-20-2001 23:58:22.928 - Carrier Rate re-negotiation event count: 0 02-20-2001 23:58:22.928 - Carrier Retrains requested: 0 02-20-2001 23:58:22.928 - Carrier Retrain requests granted: 0 02-20-2001 23:58:22.928 - Final transmit carrier rate: 28800 02-20-2001 23:58:22.928 - Final receive carrier rate: 50666 02-20-2001 23:58:22.928 - Protocol Negotiation Result: V.42 Alterative protocol (MNP) 02-20-2001 23:58:22.928 - Error control frame size: 128 02-20-2001 23:58:22.928 - Error control link timeouts: 0 02-20-2001 23:58:22.928 - Error control link NAKs: 0 02-20-2001 23:58:22.928 - Compression Negotiation Result: MNP5 02-20-2001 23:58:22.928 - Transmit flow control: V.24 ckt 106/133 02-20-2001 23:58:22.928 - Receive flow control: V.24 ckt 106/133 02-20-2001 23:58:22.928 - Transmit characters sent from DTE: 1289 02-20-2001 23:58:22.928 - Received characters sent to DTE: 907 02-20-2001 23:58:22.928 - Transmit characters lost (data overrun errors from DTE): 0 02-20-2001 23:58:22.928 - Received characters lost (data overrun errors to DTE): 0 02-20-2001 23:58:22.928 - Transmit Frame count: 73 02-20-2001 23:58:22.928 - Received Frame count: 62 02-20-2001 23:58:22.928 - Transmit Frame error count: 0 02-20-2001 23:58:22.928 - Received Frame error count: 0 02-20-2001 23:58:22.928 - Termination Cause: DTE Hangup Command 02-20-2001 23:58:22.928 - 115200,8,N,1, ctsfl=1, rtsctl=2 02-20-2001 23:58:22.938 - Initializing modem. 02-20-2001 23:58:22.948 - Send: AT<cr> 02-20-2001 23:58:22.958 - Recv: <cr><lf>OK<cr><lf> 02-20-2001 23:58:22.958 - Interpreted response: OK 02-20-2001 23:58:22.968 - Send: AT&F&A0&B1&C1&D2E0Q0V1S0=0<cr> 02-20-2001 23:58:22.978 - Recv: <cr><lf>OK<cr><lf> 02-20-2001 23:58:22.978 - Interpreted response: OK 02-20-2001 23:58:22.988 - Send: AT+ILRR=1;+MR=1;+ER=1;+DR=1<cr> 02-20-2001 23:58:22.998 - Recv: <cr><lf>OK<cr><lf> 02-20-2001 23:58:22.998 - Interpreted response: OK 02-20-2001 23:58:23.008 - Send: ATS7=60S19=0L2M1+ES=3,0,2;+DS=3,0;<cr> 02-20-2001 23:58:23.008 - Recv: <cr><lf>OK<cr><lf> 02-20-2001 23:58:23.008 - Interpreted response: OK 02-20-2001 23:58:23.018 - Send: AT+IFC=2,2;B0X4<cr> 02-20-2001 23:58:23.028 - Recv: <cr><lf>OK<cr><lf> 02-20-2001 23:58:23.028 - Interpreted response: OK 02-20-2001 23:58:23.028 - Waiting for a call. 02-20-2001 23:58:23.038 - Send: ATS0=0<cr> 02-20-2001 23:58:23.038 - Recv: <cr><lf>OK<cr><lf> 02-20-2001 23:58:23.038 - Interpreted response: OK 02-20-2001 23:58:23.038 - TSP(0000): LINEEVENT: LINECALLSTATE_IDLE 02-20-2001 23:58:23.048 - TSP(0000): Closing Call 02-20-2001 23:58:23.058 - Session Statistics: 02-20-2001 23:58:23.058 - Reads : 0 bytes 02-20-2001 23:58:23.058 - Writes: 0 bytes

Thanks for the suggestions everyone. I am going to try Ekstreme's tips - I have noticed that when connecting to the ISP through the COM port in hyperterminal, after successfully logging on, the screen fills up with a repeating pattern of ASCII characters. Inside this mess of junk is the expression MULTI-LINK, which leads me to think that it might have something to do with that setting. I disabled the "negotiate multi-link" tickbox, but didn't touch the "Enable LCP extensions" box. If this sorts out the problem I'll be so happy as I am just about at the point of returning the modem. Re - the port settings. As clutch said, the modem sets itself to COM3 but the OS installs only COM1 - do I have to set the modem manually to COM1 or should I just accept that COM3 and COM1 are the same thing?

Believe me there was no setup wizard. The CD interface was useless, as I said, no mention of drivers anywhere. I think it detects your OS and installs the appropriate drivers but there is no echoing of this so you are left in the dark as to what the hell's going on. The driver on the CD is the most recent - it matches the one I downloaded fromt he 3Com website. I will look at MS Client when I can next face trying to resolve this problem!!

Thanks for the suggestion but it's a Dell dimension PC and the motherboard is flashed to the most recent BIOS. There are no other indications of ACPI problems with the rest of the system. Unfortunately I don't have access to another PC that I can start installing new hardware on. I could understand if the modem wasn't recognised at all, or if it wasn't dialling out, but to have it dial successfully and just sit without sending or receiving is too much......

Does no-one have any suggestions regarding my modem query I posted recently? I can't believe that all you techno-gurus are stumped by my misbehaving modem....this forum has always been my first point of call for technical issues in the past - don't let me down now!!!

What CD-RW device would members recommend for use in Win2k. I see that plextor have just released a 16x/10x/40x model- that sounds tempting to me.... Also I get the feel that Nero is the preferred software under Win2k due to stability, however there appear to be some issues judging by the posts on the applications area of this site. Comment anyone?