[H]ard-Turtle

I dood that already..lol I tried it...no go. Oh and as a follow up... One type is USBUHCI.sys, which VIA uses, the other is USBOHCI.sys...which almost everone else uses. I'm not sure if I led you here yet or not..but try http://www.usbman.com

I had occasional lock ups under win2k...but XP just won't function...I agree...I'm almost certain it is a driver problem...I just chose not to wait until they figure it out as I can't write drivers myself.

Is your Front Side Bus overclocked at all?

Hey...yep..you have amd chipset alright... AMD® 751 (Irongate) North Bridge AMD® 756 (Viper) South Bridge is what I found on your board. From what I understand there are two types of host controllers: One is a Universal Host Controller (system file of UHCI or something like that) the other I've forgotten what it's called but it's what most of the other board manufacturers use. I can't spend hours trying to determine which you have for sure though. I love problems and love fixing them even more...but I could not get my USB stable under XP. I have the UHCI type from VIA...try to research and see which type yours is then make a decision to go from there. New PCI USB card or wait for XP driver support from Gigabyte.

XP detects and installs, native driver support, however, the cam comes on, displays video for about 2~3 seconds, then locks up. VIA USB problem? Any ideas?

This afternoon I was able to troubleshoot it to the VIA USB Host controller..not the cam. I've always known that via usb was a finicky thing... XP has native drivers for the cam. I purchased a $20 USB PCI card and all is well...works like a charm. Sad I had to buy something to make it work...but with no driver support for at least a few weeks..I didn't want to wait.

Yup...you and I have both just run into our first VIA USB problem it seems. Usually it only crops up on seriously overclocked FSB...but with XP the via controller just sucks. My solution for the time-being was to go down to the store, purchase a $20 PCI USB card and away she went...when/if via ever gets it straightened out I'll pull the card or use it in an old box.

This afternoon I was able to troubleshoot it to the VIA USB Host controller..not the cam. I've always known that via usb was a finicky thing... XP has native drivers for the cam. I purchased a $20 USB PCI card and all is well...works like a charm. Sad I had to buy something to make it work...but with no driver support for at least a few weeks..I didn't want to wait.

Just wanted to mention that Linksys 802.11b (Wi-Fi) network cards work fine with no issues in XP Professional 2600. Either PCMCIA card or w/ PCI adapter. Driver causes standard warning that it hasn't been tested. No issues.

Water cooling w/ Pelt is my next project now that the network and XP all play well. I've got an AOpen full tower case begging for all the watercooling hardware to go into. 12"X5" radiator w/ (4) 80mm fans...resevoir...dual power supplies...100+Watt pelt..etc. Takes dough though...so one piece at a time..hehe I'm an AMD fan how about you?

Hey...1-5MB/sec???? That would be fine for gaming considering my ADSL is only 784/128. But...you'll love this....try 11Mbps? I ran SiSoft Sandra's Network benchmark and it pegged out at 10.9Mbps...so I'd say it's working correctly! The setup is based on WiFi or 802.11b whichever you prefer to call it. Again...the only downside in my house is Range...I HAD to centralize the access point. I couldn't get through all the darn walls. I actually tried placing one computer in the garage...no luck...about 30 feet short. NEED MORE POWER!!! Unfortunately I'm not a programmer so a lot of what you said was Greek to me..I'm a hardware nut only at this point in time. But, I did get the UPC reader part...I've got a friend that just converted his warehouse to a setup using wireless readers. Oops, I forgot to tell you about gaming...yes, I play CS..no problem whatsoever. I've had 3 players at the same time...all wireless...not an issue.

Also having a problem with QuickCam Home. However, I can start the cam, won't shut down locks the video after 2 seconds.

I completely agree with you on Tesla...what a mind. I use a linksys Wireless Gateway/Router in the kitchen attached to the DSL modem. (1) computer in my Son's room, (2) in the office, (1) in my bedroom, and last but not least a laptop wherever I walk around. I have gone through several movements and gyrations as I couldn't afford all the wireless cards all at once...approx. $150 for the PCMCIA and PCI adapter set. So I've just done one a month and now everything is wireless. There is a 4 port switch on the Gateway...Really a flexible unit. Range could be better and an occasional loss of connectivity...but it doesn't require user interfernce..just comes back online in a few seconds.

Very Cool...I have a hate/love relationships: I hate it when things go wrong..but I love finding the answer and seeing it fixed!!! Glad you got it.

http://www.asusboards.com/forums/showthread.php?s=&threadid=8723 Here is the other board and post and solution for my A7V133....maybe it will help afterall. When I determined the bios for the Promise chip was hosed, no "normal" bios flash worked. I'm going to guess that when you flash if the data is the same it doesn't "re-flash" it...if you notice some of the blocks using aflash go unchanged...Maybe I wasn't flashing the promise. When I used the bios mentioned in that thread I KNOW it flashed the promise as there are visible changes. I'm typing from the A7V133 RAID w/ XP right this second...hehe

I also had several BSODs while doing the A7V133 install...turned out the bios for the promise chip was corrupt. After flashing with a bios w/RAID bios I had no additional problems. I doubt seriously you have the same problem...so click that link and follow along...hehe I'm in the middle of an install on an Abit KT7-RAID, how easy...the built in RAID drivers for that board are sooooooo nice.

There is a small disagreement going but it doesn't apply to you at all. This gentleman has a scsi adapter and an actual PCI promise controller....I have done an install on a7v133 and it was a pain but I detailed it near the end of this post: http://www.ntcompatible.com/vb/showthread.php?s=&threadid=16965 To prepare for the install make sure you are not overclocked, don't have your RAM at improper settings...etc. I found the install/setup to be VERY sensitive to these things. If you need anything else..feel free.

Just wanted to mention that Linksys 802.11b (Wi-Fi) network cards work fine with no issues in XP Professional 2600. Either PCMCIA card or w/ PCI adapter. Driver causes standard warning that it hasn't been tested. No issues.

Good Morning BladeRunner, Lets go back a little and we can think about this some more...K? I'm sorry for getting snippy before. You said in your last post that you booted from a DOS disk and saw your old w2k folders (verifying the disks are partitioned and formatted) Was that boot disk a Win98 startup disk? And can I assume that the drives were setup on the RAID controller in your normal config? If all that is correct, there should be no reason why it didn't start the install of XP. I've now done my second install of XP on another computer similar to your setup. ASUS A7V with a PCI Promise RAID controller in RAID 0. I dealt solely with win98 full startup disk, I did add smartdsk.exe to it because the install goes soooooo much faster, not one with "system files only". I booted using win98 disk w/o CD-ROM. Fdisk, partitioned the RAID drive, restarted. Booted using win98 disk w/o CD-ROM. Formatted C:, restarted. Booted using win98 disk w/CD-ROM finally!!, ran smartdsk.exe twice (don't ask me why...just works this way...you can see that disk cache is enabled). Went to CD directory \I386 ran winnt.exe Text in lower right corner of setup screen for 20 seconds or so...Loooong pause with no text...Activity on the drive though. Same setup screen, yellow "status" bar and text indicating installation files are being copied to drive. At the end of this the message "MS-DOS portion of setup is complete, if you have a floppy disk in your drive please remove it and press any key to continue" or something like that was displayed. Did as I was told..lol Upon restart I immediately got a screen I recognize and love, black screen text at top left corner "Setup is inspecting your hardware configuration" Blue screen text at lower left corner "Press F6 to install additional...blah, blah..forget what it says" And aaawwwwwwaaaaayyyy she went. Now, I didn't go through all that because I think you are stupid, on the contrary...just wanted to relay exactly how it went so maybe you could try it and see where the whole process breaks down for you, then possibly we can go from there. Cool? Let me know if you decide to try it and what happens OK?

OK..so in a way...you just confirmed what I said...w2k was a flawless install WITH the boot floppies...but without, feel free to try my suggestion rather than wait for someone to produce floppies..no?

In my case the native XP firewall is not enabled. It appears to be just a problem of the Zonealarm software starting before the True Vector service is started. All of us should know that you can delay the za.exe just a little and all functions well. True vector, which is VSMON.exe and a few other associated services are just not loading fast enough as a user started service...it needs to come up with the other SYSTEM services. Like I stated in the previous post, vsmon.exe and the others were listed as SYSTEM services in Win2k, but are not in XP. If anyone knows how to change the designation I would be hugely appreciative.

The request to "Press F6 to install SCSI" doesn't come until after, quite a bit after actually the initial transfer of setup files drives, which is done in DOS. DOS obviously needs to see the disks by having them partitioned and formatted. I would love for someone to tell me how to get it done without having to do that first but so far no one can. You are correct..boot from CD won't work. When you run winnt.exe from DOS all of the setup and installation files transfer to the hard drives, you'll have text in the lower right corner of the screen of each file, then after quite a pause a status bar will be displayed, transferring more files. When this is complete the OS will tell you the MS-DOS portion is complete, remove and disks...blah, blah, blah. Press a key to restart...Just after restart it should boot from the RAID, Inspect Hardware, and ask you to press F6...from then on you should have smooth sailing....If those disks are partitioned and formatted before hand from the Win98 boot disk. I've done it several times both the right way and the wrong way...lol

OK...first thing..I'm not a dick head or anything but seriously...why all 3 os'?

Silly question but are the drives you want to install on partitioned and formatted? If they are not..that is the problem. You can fdisk and format them with FAT32 and then convert later in the install or not if you so decide. If they are not partitioned and formatted XP won't ever see them.

Hey guys...maybe we can help each other out. The true vector service on an XP machine is listed as a "User" instead of SYSTEM. This seems to be the problem. On a 2000 machine it installs as a SYSTEM service. There is a method to my madness too...when installing MotherBoard Monitor you have to specify you are using XP so that programs service is installed as SYSTEM as well. It gives the choice of Win9x/2000=Software(?) or XP=SYSTEM. So..now that we have a good possible answer...how do you change it to become a system service?