Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

  • Country

    United States

About JimmyW

JimmyW's Achievements



  1. I'm running XP 64 SP2 on a Tyan 2895 board. I can't install a USB 2.0 hub to any on-board USB 2.0 port. XP finds new hardware and the wizard opens, but going through the install drivers routine finds no drivers and the hub will not install. Normally, a hub should simply be recognized and installed automatically. I've tried a couple of different hubs with the same results. All other USB devices work okay.
  2. I still need to do the dump, but I found that the same freeze up occurs if I plug in a portable drive through a 1394b card. So, it's not only USB. There is no problem on the XP32 side of the machine, so I don't think it's hardware. I have no problem with USB dongles/keyboard/mouse. It seems to come down to an issue where XP64 won't handle a mass storage device.
  3. Thanks very much. I'd like to give that a try and would be happy to send the dump file to you. Now, my page file is on another physical drive, but I can change that. I have 8GB physical RAM in the box, although XP is seeing less. Before I begin, is that going to be an issue?
  4. Since installing Service Pack 2 on my XP 64 system, I can't attach USB hard drives. The USB removal tool recognizes the device and then hangs. The drive is not recognized in Windows Explorer, and I cannot open Device Manager. I also can't stop the device or close the removal window. None of my applications will open, although their processes may start. Removing the USB device does nothing to resolve the issue. I have, however, been able to use a USB thumb drive, which is recognized as a mass storage device. The only way out is a forced power down. Any ideas? Thanks!
  5. I have a system with one disk with one primary partition, C:, and an extended partition that conatins D:. It's set to dual boot. C: is XP64, and D: is XP32. I want to go to single boot with XP64 on its existing C:, after which I will resize C: to consume the entire drive.. The startup files, e.g., boot.ini, ntldr, etc., reside on C:\. What is the best way to proceed? Can I just delete D: and enlarge C: to consume the free space where D: existed? I imagine that I may have to edit the boot.ini, but what about other files? I run Partition Manager, so I have the means to create/remove/resize partitions. Scenario 2: I have another system with one disk with one primary partition, C: and an extended partition that conatins D: It's set to dual boot. D: is XP64, and C: is XP32. I want to go to single boot with XP64 on its existing D: In this case, the startup files, e.g., boot.ini, ntldr, etc., also reside on C:\, but I want to remove that partition and leave existing XP64, D:, as the boot partition. How should I proceed here? Thanks!
  6. On two identical machines, I typically cannot restart Windows from the XP64 partition. Windows closes normally, and the machine goes to the point at which it should start the POST. The monitor goes to sleep mode, and the keyboard and mouse are dead. There it remains. I then kill the power and can restart okay. If I shut down from 64, the machine shuts down okay. I can restart fine from the XP32 partition. I'm using a Tyan 2895 with current BIOS, two dual core Opterons, 8GB RAM, MSI video card. The 32/64 system is on an Ultra SCSI HD on the MB controller.
  7. Thanks, very much! You're exactly correct. I had set up a dual monitor system, but had shut off #2.
  8. On the XP64 side of my system, when I open certain applications, like Word 2003, they immediately minmize to the task bar. Clicking on the minimized application button does nothing. Right-clicking and choosing Maximize does nothing. I tried setting the applications' properties to open maximized, but that doesn't work, either. Thanks.
  9. Thanks very much! Got 'em and they work fine.
  10. I'm using an MSI 6600-TD128E card on 64, which installed its own drivers. Is there some support in 64 for configuring a dual monitor setup, as is there with the MSI drivers on the 32-bit side? I see that MSI offers a beta driver and wondered whether anyone tried it yet. It's dated 7/05. I'm running two dual core Oprtons on a Tyan 2895. Thanks.
  11. Does anyone have a link, if there is one, to where I can download the full MSIE 6.x installation package from MS? Thanks.
  12. Thanks very much for your patience and help. "Multi-homed" is not a term that I've heard for multiple adapters, despite my advanced years and at least modest talent. Sorry. I will admit to being foolish in not observing that VMnet8 had already grabbed the default gateway as its IP address. I skipped right by that, as there were no VMs running, and I didn't stop to think that the virtual adapter would have grabbed the gateway's address as its IP. For one, it shouldn't have the same IP for the adapter and gateway. As I mentioned, this came about suddenly, after VMware has been in substantial use. After reinstalling VMware, all is well, as its adapters assumed IPs elsewhere in the 192.168 range. Perhaps what happened is that, when I ran a VM with NAT or changed the IP within the VM to use DHCP, it assumed my gateway's IP as its own, and I neglected to reset the address. When I run a VM with networking, it's generally bridged to the host's physical adapter. As you observed, TCP/IP is not my strong point, but I do know enough to (usually) get by. For the times when I don't, I'm grateful to folks like you who can point out the obvious. Thanks again.
  13. Well, I just unistalled VMware, and I can get out. You might have seen this in the files I attached with my last post, but, after the uninstall, this is the ipconfig frm the particular NIC: Connection-specific DNS Suffix . : domain.actdsltmp IP Address. . . . . . . . . . . . : Subnet Mask . . . . . . . . . . . : IP Address. . . . . . . . . . . . : fe80::2e0:81ff:fe54:c788%4 Default Gateway . . . . . . . . . : What's the second IP address that's two-byte hex strngs? It's not my or the gateway's IP. Thanks!
  14. Thanks. I'm not sure what you mean by "multi-homed." I attached files with outputs from the commands. NETWORK 2 is the one with the issue, but the issue will exist with either NIC. Perhaps there's a conflict with VMware. ip.txt rt.txt

  • Create New...