Jump to content
Compatible Support Forums

Phalanx-Imawano

Members
  • Content count

    139
  • Joined

  • Last visited

    Never

Everything posted by Phalanx-Imawano

  1. Phalanx-Imawano

    Internet connection sharing: WinXP sharing with Win2k

    Quote: Your problem, which you say is now resolved, is interesting because I'm ALSO trying to set up a small network, consisting of just two machines, each running Win2K, and I'm blowed if I can get Internet Connection Sharing to work. No matter what form of IP allocation I try to use, the client PC just can't find the server when I try to dial up from it. My IP addresses check out okay. Did you find a crucial setting that did the trick? The LAN itself definitely works because the host machine successfully gives out the IP address across it, and also shared printing works. Any clues would be welcomed. In my case it turns out I changed the LAN card on the WinXP machine, but I did not remove the old drivers first. So what happened was ICS was still for some reason implementing sharing on the old LAN card and not the new one. Thus I had to run the Network Setup Wizard again. For the Win2k client to see the internet (this is assuming Static IP allocation, which I prefer), what's important are these (I read them from practicallynetworked.com http://www.practicallynetworked.com/sharing/ics/ics_win2k_client.htm ): 1. The IP address of the client must be within the range of 192.168.0.2 to 192.168.0.254, with subnet mask 255.255.255.0 (Class C) 2. The IP address of the LAN interface of the computer sharing its internet connection (which of course will be 192.168.0.1) should be entered as the Default Gateway and Preferred DNS Server on the LAN card properties of the client PC. 3. The Autodetect proxy server setting must be left unchecked on the client PC's browser settings. Good luck!
  2. Just learned something about WinXP and ATAPI DVD-ROM drives - it's very strict with DMA support for them. Whereas Win95/98/ME will try as much as it can to enable DMA support if you activate it in the CDROM device properties, WinXP will check the bios bootup configuration and comply with it (i.e. if the bios detects the DVD-ROM drive as supporting only PIO mode, WinXP will configure it as such even if Ultra DMA mode is allowed in that drive's device properties; Win95/98/ME will try as much as it can to support DMA mode if you activate it regardless of bios settings). I've had this instance. My PC used to be a PentiumIII 1GHz with ECS P6VXAT motherboard and Creative 8x DVD-ROM drive. At first the DVD-ROM drive would be detected by the bios and be configured in DMA Mode 2, and is automatically configured likewise in WinXP. Sometime later a problem seemed to develop on my mobo, and the DVD-ROM would only go to PIO mode. To my chargin WinXP followed suit, and the result was that DVD movie software playback got skippy and choppy (I read that Software DVD playback requires DMA support on the DVD-ROM drive). Sometime later I upgraded my system to a Pentium4 2GHz with ASUS P4S133 motherboard, while at first keeping the DVD-ROM drive - the drive would still be configured on PIO mode by the bios, and WinXP agreed! I decided on an experiment - I had a 2nd PC with an ASUS 8x DVD-ROM drive (that PC received the old PIII 1GHz CPU and ECS mobo). I swapped the ASUS and Creative drives between the two PCs. On bootup of the WinXP system which now had the ASUS drive, the ASUS drive was configured by the bios to DMA Mode 2 (to my surprise), and fortunately WinXP did the same. To my even bigger surprise when the PIII system (which had Windows ME) started up with the Creative drive, that one configured the Creative drive to PIO mode (at bios level), but WinME let me activate DMA support, which worked well (huh???). To test if it did work with DMA support, I popped in a DVD title and played it with my DVD software - no skipping (hmm...). I wonder what gives here. Or is WinXP doing the right thing being "compliant" to the hardware setup while WinME is "cheating" and will eventually cause problems?
  3. Phalanx-Imawano

    GeForce2 MX200

    Yeah. To hell with the MX200. Heck even a GeForce2 Pro (now badged GeForce2 Titanium) will be just about as value priced nowadays, if you can find one. Or a MX400 w/ 64MB VRAM if you're really tight on cash. But if you can afford it go for the GF4 Ti4200.
  4. Phalanx-Imawano

    WinXP very picky with DMA support for IDE DVD-ROM drives

    Update: recall that PC that had WinME in it (the PC where the bios configures the DVD-ROM to PIO mode)? Well, after complaints from its users about instability (my mom and dad) I changed the OS to Win2k. Surprise surprise, just like the Win9x guys Win2k isn't so fussy as WinXP about DMA support on the DVD-ROM (i.e. Win2k will get it to run on DMA mode if the IDE properites is set to "DMA if available" even if the bios configured it to PIO mode).
  5. Phalanx-Imawano

    Internet connection sharing: WinXP sharing with Win2k

    Never mind. Got it to work after re-running the Network Setup Wizard on the XP machine.
  6. Phalanx-Imawano

    Cannot send a fax under XP?

    Now here's a real bugger. I've tried the included Fax utility of Windows XP to see if I could send a fax with my modem (Creative Labs Modem Blaster PCI 56k), something I did seamlessly with Windows 98, WinME, and Win2k, with the help of Microsoft Mail/Outlook. Now WinXP has another niggle. While I was able to setup the Fax program and get it to recognize my modem, if I actually try to send a fax (already created the fax document and specified the fax number to send to), this happens: first the status window appears, then the modem goes off-hook (so I can hear the dial tone), then suddenly it goes on-hook (hangs up) after less than one second, and the status windows says "no answer detected", without even dialling (I didn't hear the tone dialling thing happen). All the other functions of the modem (dial-up connection to the internet or to a private network, and incoming connection) all work fine (and besides I have Windows XP drivers for my modem already). My modem is supposed to support all types of fax standards (it's written on the box). Any other XP users here able to utilize the fax functions of their modems (though I rarely send faxes from my home PC since email is more convinient anyway, so it's not that critical)?
  7. Phalanx-Imawano

    WinXP not detecting Ethernet Adapters?

    Just recently upgraded to Windows XP Home after about a year of using WinME. My system is generally up and running okay, except that I can't install LAN Cards! I've been using a CNET Pro120c 10/100 ethernet on my system (when it had WinME and even Win2k) without problems, but WinXP has a strange error when I try installing it, as well as a newer LAN card I purchased (forgot the brand, but it claims to be WinXP compatible as it has WinXP drivers in the accompanying diskette, and it gets detected as a Realtek LAN Card). WinXP tries to detect the card, attempts to install drivers, then this message appears at the end of the wizard (where it has the "Finish" button): "Windows could not properly detect the device. Data is incorrect." Any idea what's going on? System specs below if it would help (everything listed is working fine under WinXP). Intel Pentium III 1GHz ECS P6VXAT motherboard (Socket 370, VIA chipset) Apacer 512MB PC133 SDRAM (256x2) Leadtek Winfast GeForce3 Ti200 video card (w/ 28.32 reference drivers) Creative Soundblaster Live! Value Creative Modem Blaster PCI 56k internal modem 1 Maxtor 20GB, 1 Maxtor 40GB, 1 Seagate 30GB hard disks Creative 8x DVD-ROM drive Microsoft Sidewinder 3D Pro Joystick Logitech Wingman Force Feedback Wheel (via USB) Interact Axispad gamepad (via USB, using default WinXP drivers) Logitech Freedom Cordless Keyboard and Mouse
  8. Phalanx-Imawano

    WinXP not detecting Ethernet Adapters?

    Yes the box of the NIC had the WinXP logo on it, plus the older Microsoft Windows Logos having compatibility claims with Win2k, WinNT 4.0, WinME, Win98, and Win95. And the driver diskette had a folder and files for a WinXP driver, and when I told the New Device Wizard to use that driver, the Wizard didn't warn me that the drivers weren't digitally signed by Microsoft.
  9. Phalanx-Imawano

    post your system specs- XP ony computers plz

    Monitor: Likom 17" SVGA CPU: Intel PentiumIII 1GHz Motherboard: ECS P6VXAT (VIA Chipset, ATA-100) Memory: Apacer 512MB SDRAM (256MBx2) Video Card: Leadtek Winfast GeForce3 Ti200 Sound Card: Creative Labs SoundBlaster Live! Value Modem: Creative Labs Modem Blaster PCI 56k LAN Card: Edimax 10/100Mbps LAN Card (detected as Realtek) Hard disks: 1 Maxtor 20GB (System), 1 Maxtor 40GB (Games and Applications), 1 Seagate 30GB (Documents, downloads, extra stuff, etc) DVD-ROM drive: Creative Labs 8x DVD-ROM drive Floppy drive: Panasonic 3.5" Floppy drive Keyboard: Logitech Cordless Freedom Keyboard Mouse: Logitech Cordless Wheelmouse (bundled with the keyboard so it uses the same receiver) Joystick: Microsoft Sidewinder 3D Pro Gamepad: Interact Axispad USB Steering Wheel: Logitech Wingman Formula Force USB ATX Power Supply: 250W OS: Windows XP Home Edition OEM
  10. Phalanx-Imawano

    WinXP not detecting Ethernet Adapters?

    Ok, someone from the Microsoft Newsgroups was kind enough to point out this piece of info: http://www.winoscentral.com/article.php?sid=3497 It seems there's something really weird with the section of the Registry that handles the PCI devices - that section is set to Read Only, EVEN TO THE ADMINISTRATORS' GROUP! Because of that, any device you want to install and has to write to that section of the Registry gets denied access, resulting in that error message. So I changed the permission of that part of the Registry by granting Full Control of it to the ADMINISTRATORS and SYSTEM groups (and including all subkeys and children, but not inheriting from parent), and I got my LAN card to work. Anyway thanks for trying to help.
  11. Phalanx-Imawano

    60 Hz bug with nvidia drivers: does somebody have a solution

    Try this program. Worked for me http://www.pagehosting.co.uk/rl/
  12. Phalanx-Imawano

    WinXP not detecting Ethernet Adapters?

    Well, looks like I'm really stumped. First I can't alter the resource settings within WinXP, because the checkbox of "Use Automatic Settings" is greyed. Next, even moving the PCI boards around, or even taking out another PCI board (tried taking out the internal modem), didn't have any effect. And lastly, in the device manager the entry for the LAN card is "Other Devices->Ethernet Adapter" with the yellow question mark, so the device driver is not installed at all. Anyway here's a picture of that wizard containing the text, and my mistake, the message is "Data is Invalid". Looks like my PC won't go into a LAN for the time being.
  13. Phalanx-Imawano

    WinXP not detecting Ethernet Adapters?

    Blade]ZFA[, you just reminded me of something. When my PC had WinME, some of my installed peripherals were sharing resources. Most notable were my Sound Card and Internal Modem (both using IRQ11) and the Video Card and LAN Card (both using IRQ10). Right now with WinXP, the Sound Card and Modem are again sharing IRQ11 without problems. Is it possible that WinXP is disallowing anything to share an IRQ with the Video Card for the sake of performance (at startup after the POST sequence, the list of installed devices and their IRQ's are listed, and again the video card and lan card are sharing IRQ10)? If that's the case is there a way to force the LAN card to use another IRQ at the BIOS level or something, in case I can't do that within WinXP (back in Win98 I even had the sound card, internal modem, and LAN card sharing IRQ5!)?
  14. Phalanx-Imawano

    WinXP not detecting Ethernet Adapters?

    Already tried the drivers that came with the NIC. Same results.
×