 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Windows Forum / Windows Vista / Administration / August 2006Ok Jimmy B! (Or any other takers) How 'bout a Hard/software proble
To wit: In the Device Mgr. There is a yellow ? over a PCI i/o hardware device. Tracing it down, I have a PCI card for IEEE1394 installed in the machine. Window XP shows the card operating w/o any need of external drivers (I believe we call this native drivers?) However in Vista beta2, I get the Yellow ? with a PCI i/o device and Vista wants drivers. Device Mgr shows the TI 1394 Controller that is ON the card installed, so why is it wanting a PCI driver? I don't have any firewire devices to test the card with, as I installed the card in the machine when I built it, expecting to get a DV camera later on, and I was made to understand that the best transfer from a DV is with firewire. Any thoughts? Sorry, hardware issues aren't my cup of tea. I do find it fascinating that it found the hardware devices on the card itself... I didn't think it could do that without a driver for the host device. You could try doing a driver update, selecting from disk, and putting in a windows xp disk to see if it will pick up the driver from there. Also check windows update. - JB Vista Support FAQ http://www.jimmah.com/vista/ This is commonly known as a "Firewire" port. When I first plugged my HP printer into an XP box, XP recognized it by model number and installed it correctly, without me having to insert the included CD-ROM. This is not native support, merely a demonstration of HP having provided Microsoft with the drivers for this particular printer and Microsoft including these drivers in either the initial offering of XP or in one of the service packs or updates. All hardware drivers are produced by the manufacturer of the hardware. Certainly, over time, Windows XP has become very inclusive of many common hardware device drivers. Since the requirements for Vista, and especially for Vista x64 (all drivers must be digitally signed) have changed significantly, it may well be that many hardware vendors have yet to provide Microsoft with appropriate drivers for all of their hardware. As you can imagine, this is a daunting task, as the number of different pieces of hardware can be numbered in the hundreds of thousands. In your particular situation I would contact the maker of the computer, the maker of the motherboard and the maker of the port, in that order. I also would file a bug report with Microsoft regarding this issue so that they may contact the hardware manufacturer for an appropriate driver, if they so choose. > To wit: In the Device Mgr. There is a yellow ? over a PCI i/o hardware > device. Tracing it down, I have a PCI card for IEEE1394 installed in the [quoted text clipped - 10 lines] > a > DV is with firewire. Any thoughts? Well for one "I" am the computer maker-so that lets me out :) No seriously what I am trying to do is to understand the yellow? in the device mgr. It shows a PCI device as not having a driver. By noting the TI 1394 recognition, I am/was assuming that the card is being recognized by the system properly as there never was a disk with the card. Windows was always supposed to load it. Therefore I was trying to run down the PCI card causing the driver problem. The only PCI cards I have in the unit is a 56k Modem, firewire card, and a Creative sound card. The Creative sound card was one of the original problems, however I loaded the drivers for it and it went away. The modem shows up as ok in device mgr. Something you said, however triggered a thought. How does a device that connects by USB show up? For instance, I have a HP laserjet 3015 hooked up with USB2. The unit is an AIW for fax, copy, scan and print. Vista loads the 3015 for a PCL printer, BUT the scan and Fax software is rejected by Vista. Would the Modem in the unit be showing up as PCI? > This is commonly known as a "Firewire" port. > [quoted text clipped - 34 lines] > > a > > DV is with firewire. Any thoughts? Vista may be pulling the name of the device and filling in the blank when reporting it, as opposed to actually understanding what the device is. I passed Biology this way; memorized everything, filled in all the blanks, understood very little of what I was reading or writing. I'll reiterate that MSFT gets the device drivers for hardware from the manufacturers of the hardware and there is no such thing as "native" support for a hardware device in Windows. There are some pieces parts that are ubiquitous and it "seems" as though the driver is an integral part of the code, but that is the case of the manufacturer being on the ball and is usually a video card or a motherboard, where there are very few manufactures and not a wide range of products. I have exactly the opposite issue as you: I received the notification one day that "Unknown device has been installed successfully." Now, there is no change to the functionality of my system, I still have no sound and no modem and Device Manager still shows the yellow "bangs" next to those two items. I have no idea what Vista thinks it installed, no idea how to find out and really, with RC1 right around the corner, no real desire to track it down. Borrow a friend's firewire device, plug it in and see if it works. Try your modem and see if it works. Check with the motherboard manufacturer for a "Vista" update. File a bug report with Microsoft. > Well for one "I" am the computer maker-so that lets me out :) No > seriously [quoted text clipped - 73 lines] >> > a >> > DV is with firewire. Any thoughts? Yeah I agree. There IS no such thing as "native" support. > Vista may be pulling the name of the device and filling in the blank when > reporting it, as opposed to actually understanding what the device is. [quoted text clipped - 9 lines] > I have no idea what Vista thinks it installed, no idea how to find out and > really, with RC1 right around the corner, no real desire to track it down. Well what I was hoping as a beta testor, was that I could get a good idea of what's REALLY changed under the hood, seeing that they dropped the WinFS from the OS. Thought maybe I could get some of the "bugs" worked out before RC-1 Hit. Apparently they changed HOW certain functions worked, or the XP software for such things as my HP all in one would still load. Oh and BTW the drivers for my ole soundblaster was loaded off of the original cd. what kinda sound card you got? > Well what I was hoping as a beta testor, was that I could get a good idea > of what's REALLY changed under the hood, seeing that they dropped the [quoted text clipped - 7 lines] > what > kinda sound card you got? Yes, MSFT did change the way many things function. I very much like having the search bar on the Start menu, for instance, and having control over what gets indexed. My modem/soundcard is an onboard Conexant AC'97 in a Gateway. Have you been to their website? Anti-customer is the best I can give them. Gateway is no help, either. If you are a Technical Beta Tester, report the bug to MS and if enough people do so, perhaps MS will get the mfr to cough up the effort required for drivers that will work properly with Vista. This sometimes works, I can tell you from personal experience over many Betas. Otherwise, when Vista ships you may have to replace some HW with Vista-compatible HW. BTDT too.  SignatureRegards, Len Segal, MCP Microsoft - MVP -------------- My reply address is intentionally wrong to reduce SPAM Email. NOTE: We do not respond to unsolicited Email support questions, please post questions in newsgroup. > Yeah I agree. There IS no such thing as "native" support. > [quoted text clipped - 29 lines] > what > kinda sound card you got? |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.