zen69x

You can not control either computer via RDC because Win2k Pro does not support remote desktop (Terminal Services). Win2k Server supports 2 remote logins (In remote administration mode, more in Application server mode). WinXP Pro (Home does not) supports 1 active session, either console or remote. and Win 2003 Server supports multiple connections as did Win2k Server albeit in a slightly different manner. As far as the being prompted for a password, it is indeed because you will have to have matching accounts (usernames and passwords) on both machines. (Unless of course you have a domain setup ) Clear as mud now?

Yeah, 2k uses NTFS 5 and XP uses NTFS 5.1 though I am not aware of any compatibility issues and I'm not totally sure what is different between the two.

Yes, I have the WIA service started. That is how I can use the "wizard". Unfortunately, the wizard interface leave something to be desired. I am still unable to use the TWAIN interface though.

Here is a link that should provide a bit more info: http://www.cisco.com/univercd/cc/td/doc/product/aggr/vpn5000/5000sw/conce60x/5000cfg/ipaddr.htm I got the numbers correct at least. Not that it seems to matter much these days, but Class A is 1.0.0.0 to 127.255.255.255 (10.x.x.x falls here) Class B is 128.0.0.0 to 191.255.255.255 (172.16.x.x - 172.31.x.x falls here) Class C is 192.0.0.0 to 222.255.255.255 (192.168.x.x falls here) So my classes were correct. I goofed, good call, APIPA does work for Win98 and above, wish I saved the link to that. and an address like 192.168.0.0 where the host bits are all 0s identifies the network, while something like 192.168.0.255, where the host bits are all 1s is a broadcast address for that network. Of course this will all be pointless whe IPv6 comes out and DNS will rule because God help you with trying to remember an IPv6 address.

Ok, well, here goes from what I can remember. 127.0.0.1 - loopback address (Although the whole 127.0.0.0 - 127.255.255.255 range is really unusable) 10.0.0.0 - 10.255.255.255 - Class A non-routable 172.16.0.0 - 172.31.255.255 - Class B non-routable 192.168.0.0 - 192.168.255.255 - Class C non-routable 169.254.0.0 - 169.254.255.255 - Automatic Private IP Addressing (APIPA) Class B, and it's a Windows thing. You will be assigned an address in this range on Win2k and above DHCP clients that can't locate a DHCP server. BTW, yes I gave the whole range and yes I know that the first and last addresses in the range are generally not usable.

If it'll recognize one but not the other, I would try installing the one it won't recognize on another PC perhaps running another OS. I know you said it did work, but perhaps it went bad? Give it a shot on another PC and see if it works.

amir You have mail

Just kinda curious how this turns out. What version of OS on the client side? Would the level of encrytion as referenced by IE be of any value here?

I have the very same controllers, two of them even and XP didn't even flinch when installed them. It recognizes both quite happily. I have it connected to an SB Live value no less. I would suggest that you try installing them one at a time just to be sure that something didn't happen to one of them. If they both work, then connect them in the reverse order and see if they will work that way. Also, check the back of the controller and see if the switch is in one player, two player, or grip mode. Mine currently are working in grip mode. Hope this helps.

amir... send me your e-mail address and I will send you a copy of the drivers. They work in 2k or XP. I have noted a few problems though as they are not officially supported. Under Win2k, On shutdown, restart, hibernate or standby, if you have not stopped the quickcam then you will be greeted w/ a BSOD... again, can be worked around by only enabling/plugging in the camera when you want to use it. Under XP, On trying to resume from hibernate you will not be able to do so unless you stopped/removed the Quickcam prior to hibernating. I'm not sure about standby, but shutdown and restart don't care if the camera is active or not. Also, what version of quickcam software are you using? I think only version 4.x will recognize the camera. If you want a copy of that you may have to search around... I have it, but it's like 9MB.

No, ATA66 to ATA133 in and of itself will not be noticible.. since RPM is the same, the only things that could effect performance are... density... how many GB per platter, firmware (effects caching algorithms), or amount of cache.. which except for newer WD drives is most likely 2MB. Also, as previously mentioned by Dosfreak, most drives top out 40MB/s sustained transfer. The 8MB cache versions of Western Digital's newer drives top out at like 49MB/s. The only speedup you would see is in the cache which could reach the burst rate, however, you'll still top out ~100MB/s or so even then due to PCI bus bandwidth being shared w/ other devices + overhead. Also, I would add that even in a RAID0 setup, even ATA66 is sufficient as each *channel* would have 66MB/s bandwidth and since IDE only can access 1 device on the channel at a time, you can't currently exceed the bandwidth of ATA66... sustained anyhow.

ok, maybe you didn't read my post all the way though... I said, no you won't be maxing out the card. Your bottleneck is the PCI bus. First, you are not maxing out any ATA100 RAID 0 array. the most SUSTAINED transfer rate on *any* IDE drive right now is slightly less than 44MB/s. Yes, that SUSTAINED rate will be about double, 88MB/s but you are only using ~1/2 of the total pipe available... 100MB/s per channel = 200MB/s, which you CAN'T use anyway due to PCI bus constraints. ...BTW, I don't much care about burst rates on the drives cuz you aren't going to be retrieving all that much data from a hard drives 2MB cache to really see a difference. Secondly as I said and Brian Frank reinterated, since you have 2 drives on one channel and 1 on another, you can only have 2 drives active in the RAID array at any given moment due to IDE ONLY being able to communicate with 1 device on a channel at any given time... so it will only offer max the same bandwidth as a 2 drive array, maybe less due to the overhead in switching devices on the channel w/ two drives. Finally, again as previously stated, the bandwidth on the PCI bus is shared... you start out w/ 133MB/s theoretically, and that is shared amongst the IDE controller, NIC, sound card, USB, and any other PCI devices you have. Think that most realistically you may expect is 100MB/s. So I don't care if you have a U320 SCSI controller even, you STILL have to go through the PCI bus for anything meaningful to happen and that is where you are bottlenecked.

If you know someone who has a copy of beta 2, not RC2, of WinXP, I think you can... need taskmgr.exe and another file... I think called php..something.dll. (Running the taskmgr.exe on win2k should tell you the file you need.) These you can place on Win2k. Beta 2 was before they started adding in all that themeing (sp?) crap.

first, there are no IDE drives capable of 50MB/s sustained transfer. The WD w/ 8MB cache is close, but not quite there yet. anyhow...look at it this way... each channel is limited to a maximum rate of it's supported protocol... i.e. ATA33=33MB/s 66=66 etc... all minus a few MB/s due to overhead. You will set them up so that each has it's own channel due to IDE having only 1 device active per channel at any given time. So, no the controller won't be maxed out. The problem you will see however is that all IDE interfaces connect to the PCI bus. And more than likely you will have a 32bit 33Mhz PCI bus... the bandwidth limit on the bus is 133MB/s. Of course this bandwidth is shared also w/ any other PCI devices in your system... sound card, NIC, etc. This is mainly why ATA133 is a real waste of time, except to support HDD >137GB. However, if you have 64bit 33Mhz or 66Mhz PCI bus, then you have nothing to worry about... if your IDE controller card is rated to work on that type of PCI bus. I would venture to guess though that if you have a motherboard w/ a 64bit PCI bus... you're probably running SCSI hard drives though.

1st, check out, as Greggy suggested if you are indeed running in PIO mode. Start device manager -> ata/IDE controllers -> primary (or secondary) IDE controller, double click here and choose the advanced settings tab. See if the current transfer mode is showing PIO or Ultra DMA... or something to that effect. If it's PIO mode, then that is most definitely your problem. As such it is not a "situation" and therefore I don't know how he means "fixed". Unless he is saying you will now have to download the entire thing even the files you do not, nor will ever need. Namely updates to Windows 2000 server editions. As for UDMA66 or UDMA100, doesn't really matter, you will personally experience NO difference between the two. Benchmarks may show some difference, but not what you are seeing now. The difference between thses two interfaces is negligible with current IDE drives. If it is set to PIO mode... change it to DMA if available... if it's already set to that, I may have a reg hack you can try... post back and let us know. As for the network install for SP2 as mentioned by packman... What I think he was trying to say is that the "network" version is the full service pack as provided by Microsoft. It contains *all* the updates, whether you need them or not. You can get a more tailored to your system service pack if you go through Windows Update, i.e. it only downloads fixes in the service pack applicable to your machine. As such it is not a "situation" and therefore I don't know how he means "fixed". Unless he is saying you will now have to download the entire thing even the files you do not, nor will ever need. Namely updates to Windows 2000 server editions.

Ok, normally I would agree w/ the delete and re-add account, but he already stated that he created a new account in safe mode and it too suffered the same problem. Not really sure if this is your problem, but when you are in safe mode, go to start -> run type in gpedit.msc and <enter> When the group policies MMC comes up, go to computer configuration -> Windows settings -> local policies -> User rights assignment -> look for Deny logon locally and see if administrators or any groups/users are listed there for some reason. If there is something listed there, I'm not totally sure how you get in under safe mode, but that is another matter, you will need to remove whatever is in that list and then right click on security policies and click reload. Then reboot the machine and try logging in again.

I have no dynamic disks on my PC. Running Windows 2000 SP2, but have done this even before service packs were released w/ no problem

When changing video cards in a 9x environment, I have always first changed the driver from whatever it was to standard VGA driver, shutdown, physically removed the old card and installed the new, booted up and then changed the driver from standard VGA to the new driver and reboot one more time.

Quote: Well, you can pick up a 60GB drive and answer both your space issues and your drive path issues with dynamic disks. Simply mount the new drive to a folder on your existing one, and you are set. You can have several drives all mounted to your system drive You don't need dynamic disks for mounting a volume in a folder, I have basic drives and am doing this as we speak w/ my c:\program files folder. The only limitation that I am aware of is that the folder in which you are mounting the drive in *must* reside on an NTFS partition. Dynamic disks are better suited for server type environments. In a windows 2000 or xp professional setup, the only options you have are simple volume, spanned volume, or striped volume. Keep in mind that only Windows 2000 and XP can use dynamic disks. Simple volume - The building blocks of a dynamic disk setup, a simple volume is most comparable to a partition. It offers you the ability to tack another simple volume onto it and make a larger volume, in this process it becomes a spanned volume. I don't know about ever removing the added volume though without reformatting. Spanned volume - Spanned volumes are as explained above, created when you lump 2 or more simple volumes together to create one logical volume. NOTE: You can NOT create a spanned volume using a partition that was upgraded to a simple volume, i.e. boot and system partitions. Striped volume - RAID-0. No redundancy here, just increased STR. This will also slightly slow down your seek times as you are seeking 2 separate physical drives here. This will give you performance roughly equal to a RAID-0 setup on a Promise or comparable IDE RAID card. If the RAID card has a dedicated chip on it though, or if you use more than 2 drives, go w/ an add-on board. Only limitation is that you can't create a RAID-0 boot partition. You can also check out this MS KB article for more info... link

try enabling the parallel port to use it's interrupt via device manager, and maybe try setting enable legacy plug and play mode and see if it'll work then.

Shouldn't be any difference at all, unless there is some program setup to run when the admin account logs in that isn't when the power user account logs in... I would probably check out what's going on there first. Anywho... hold down the shift key when you right click the shortcut... there will be a run as option.

ok, can't seem to find that MS KB article... I imagine that you are having a inaccessible_boot_device BSOD? Firstly, sysprep isn't meant to be able to change HDD controllers, and my guess is this is exactly what is being done. Also, you can use regedt32 and use the load hive command to load the registry hive on another NT/2K/XP, but I would advise 2k, box.

When a program crashes and says it's going to create an error log, it's Dr. Watson that will do this. So you should check out what kgeissler said before. Unless of course, you have some other program registered to do your debugging?

you can try the Umax European site. I have a Umax 600S and the European site has newer software that works far better w/ Win2k than the software available at the North American site... why this is, I have no idea. Link: http://www.umax.de/support/drivers.htm

You may want to check out this KB article from MS just to be on the safe side. http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q197667