| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 30207 | 2003-02-13 04:12:00 | flyvideo 3000 | teachernsw (3160) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 120809 | 2003-02-13 04:12:00 | Lifeview flyvideo 3000 refuses to cooperate.Loading 20.51 setup has not helped.Neither has anyone in Taiwan. We always get a message that the HDTVPCI exe has created errors. 20.51 finishes instal indicating all is well.Followed by a message that instal is incomplete.... We have tried every option. HELP. | teachernsw (3160) | ||
| 120810 | 2003-02-13 04:25:00 | Check here (www.vidomi.com) for a possible solution. Could you please also post details of your system when you post, especially your operating system, eg. Win98/2000/XP, Linux, Mac, etc. |
antmannz (28) | ||
| 120811 | 2003-02-13 04:27:00 | Also check here (www.lifeview.com), in particular Q4 and follow the instructions there if you haven't already. | antmannz (28) | ||
| 120812 | 2003-02-13 07:27:00 | Thankyou antmannz.We run 2000pro,gforce2,.. I uninstalled all 3 components of Lifeview and rebooted. Startup detected device and new H/Wizard sought to instal driver. This is where the fun starts. The cd came with version 20.40 and when loaded results in an error message failing to complete. 20.51 is in a zip file on the desktop. Where do I go from here ?I have used the zip instal wizard and 20.51 loads. The message is instal complete.Then another message it is not. I could wait a year and nothing happens. If I load the cd at this time it proceeds without an error message. I end up with the three lifeview icons.The main icon opens the controller and all but the tv link work. That button and the other two shortcut icons always result in "cannot find device" when closed, a second message reads HDTVPCI exe errors... error log being created. Where that is I have no idea ! ps. I am a mac convert. my box has: mainboard vc 19- celeron2g the gforcethingee. genius audio 5.1. 256ddr ? |
teachernsw (3160) | ||
| 120813 | 2003-02-13 07:37:00 | More on the flyvideo. I found the device manager and there is a multimedia controller apart from the sound tv tuner root. The former indicates the device is not configured(code1) using the reinstall wizard returnes me to my earlier disasters? |
teachernsw (3160) | ||
| 120814 | 2003-02-13 21:14:00 | There could be a scratch on the CD preventing the proper installation of driver files. Unzip your 20.51 zip file into a folder, say, c:\flyvid. Uninstall any references to FlyVideo software in Control Panel -> Add/Remove Programs. Delete all references to the card in Device Manager. Reboot; if/when Windows detects the card point the driver installation to the c:\flyvid folder rather than the CD. This way you get a (hopefully) clean install of the 20.51 driver files. |
antmannz (28) | ||
| 120815 | 2003-02-14 04:27:00 | Windows detected the card and I took the option to direct the search for a driver to file c:/flyvid Wizard displayed a small icon of hard drive with c:/windows/inf/oem6.inf I tried Next and this results in "error occured during installation" All reference to flyvideo had been stripped, there being no card reference in the device manager nor in the add/remove control panel area.I did reboot before attempting the 20.51 load. The cd was not used and was not in the drive. Did I mess up the extraction. when I type c:/flyvid the slash is / not the other way. ? |
teachernsw (3160) | ||
| 120816 | 2003-02-14 06:10:00 | Yes, the slash should be the other way, but I don't think that is the problem. You specified the path c:\windows\inf\oem6.inf - I take it Windows picked this itself. :( Take another look at your Device Manager. Does the card now show as Lifeview/FlyVideo 3000 ?? or something else (maybe Unknown Device??). If it's unknown device you could try updating the driver from here, otherwise it'll require deleting the device again. I'm not 100% sure with Win2K, but you need to specify to Windows where to pick up the drivers from. You may need to rename that oem6.inf file to oem6.old to allow you to try again. Upon redetection, there should (hopefully) be an option to Specify a Location - ensure this is the only option selected and place the c:\flyvideo path in the text box beside this option. Good luck :) |
antmannz (28) | ||
| 120817 | 2003-02-14 07:50:00 | Maybe I only know enough to mess things up.I appreciate your patience. I found "legacy video capture devices" inthe sound video game are(WDM video for windows capture driver -win32) if that helps. Trying to follow advice, I fixed the slash error,ran upgrade device driver wizard within the device manager area and this time it did not skip to theoem6.inf but found C:\flyvid\cap7134 inf. This proceeded but failed with the same error message when the files were flying! I thought maybe with all the Lifeview uninstalled,the loss of the x8.1 was the problem so used the cd with 20.40 to reinstall x8.1 (some sort of windows software needed by the driver). After the reboots etc the upgrade wizard failed to locate c:\flyvid and went tothe oem6.inf again only to fail again with error message. I have found "cap 7134 lifeview flyvideo WDM video capture-kernel driver-stopped-ok" in the driver list in system tools, in system info, in software environment.........Is this a clue to my mess? |
teachernsw (3160) | ||
| 120818 | 2003-02-14 09:40:00 | Ummm ..... got a bit beyond my meagre amount of knowledge I'm afraid. Hopefully someone else will be able to offer some advice. | antmannz (28) | ||
| 1 | |||||