Pci Ven 109e Dev 036e Rev 11 Full Version
L have had this problem for a while, and do not seem to be able to solve it. Fraps works fine on new games, works fine on TR1, TR4 and TR5, but if l attempt to record with fraps while playing Tomb Raider 2 or 3 the frame rate drops to 1, which is basically useless. L tried playing in 800x600 l have tried changing the affinity on both fraps and the game exe, tried changing the record key to quite a few things, nothing has helped. L would really like to be able to record video footage from my favourite game TR2. Any help solving the mystery would be appreciated.Also l do not seem to be able to play the FMV from TR3, l have a suspicion that would be normal though is there no way to see them in the game.-Diagnostic tool developed for-Version: 2.44Author: SimulationSelect All (Ctrl A) then Copy (Ctrl C) and paste (Ctrl V) the text in Notepad into a reply on the forum.Operating System.
I'm from Italy and I bought my visionplus dtv dvb-t PCI card some months ago, set it up and had it running perfectly.Now, some days ago, after trying some 3rd party programs like mytheatre, progdvb and similar I got the window message asking me to install drivers for my card. I did that manually and then when I started VisionPlus DTV I immediately get a message saying 'device or drivers not supported, please check'.I tried everything from uninstalling any software and hardware and reinstall everything, i even re-formatted 3 times and still i can't get my card to work.I try to install drivers from the cd setup but when installation is proceeding i don't see any windows notification telling me that the device drivers have been installed (and infact they aren't). If I try to install the card manually by telling windows the drivers directory, windows won't find them.I don't know what do to now, i'm desperate.As I said before, my card worked perfectly before.
I have to add that when I first installed it, my other pci cards were set in different slots than now and i don't remember their order (could be important?) and after some months I had to swap them for some reasons but my VisionDTV continued working.What happened? Is my card spoiled?Please help me.ByeSimonP.S: I have to specify my system configuration:Pentium2 400Mhz320Mb RAMRiva TNTADSL pci modemSound Blaster Live!VisionDtv PCI TerWindows XP Professional. Simon,Can you open the device properties again and select the 'Resources' tab and tell us if there are any conflicts listed in the textbox at the bottom please.The bda drivers can be found at and also in the Technical & Development Forum.Probably the best way to install them would be to right click on the twinhan drivers and click 'Uninstall'. Then right click on something else and select 'Scan for hardware changes'.
It should find the devices again and when the wizard comes up to install the drivers, do i manually and select the location of the extracted drivers. 'The operating system inherently relies on the IDs of devices. A change in any of the IDs of a device between boots or sleep/resume cycles can have devastating effects. A change in an SID when resuming from sleep would, at a minimum, trigger a Plug and Play event.
The operating system would detect the new device ID and install a new instance of the device; a best-case example would be that the same driver is loaded for this instance. However, if the device had a custom driver or exceptions had been applied, adverse effects would occur; a worst-case example would be if the SID of the primary video controller changed during a resume, causing a surprise removal of the device that has a driver loaded. A race condition would result between the loaded driver being unloaded and the new driver being loaded, which would cause the system to hang.Note: The INF file parsing code for Windows 95 (original and OEM Service Releases) will stop searching INF files once a match is found. If the DID&VID entry in an INF file is found before the DID&VID&SID&SVID entry is found, only the driver associated with the DID&VID entry will be loaded.' Can u please control your VisionPlus card subsystem ID by executing regedit and finding the key under:HKEYLOCALMACHINESYSTEMCurrentControlSetEnumPCIVEN109E.If my thought are correct there should be a way for restoring the original ids.
Or should i contact my reseller?Please help me, this is driving me crazy.Some help from expert users is very appreciated.Thanks a lotByeSimon. Thanks you very much DrP for your reply but i did change my card slot a hundred times and still i got this problem I even reformatted 4 times.
The weird thing is that the card worked perfectly before and the first time I did install it in a minute.The 109E id is correct, it's the subsystem id that is wrong. I tried changing it in the.inf file, the drivers are now found and installed correctly but visiondtv won't start saying 'card or driver not supported, please check'.I wanted to know if this is a visiondtv card problem (is it the card which declares a wrong id?) or a Windows problem (is it windows which detects a wrong id?) so that maybe i can send back the card to assistance.I wrote also to Twinhan support, hoping to hear some help soon.Thanks a lot.ByeSimon.
I would like to see the source code for this little utility before I run an unknown binary on my systemI knew people would have been afraid of doing that.Anyway that utility, that I found in, is a simple Bt8x8 EEPROM Dumper/Writer and does not harm anything unless you set some parameters after the command e2prom.If you just type 'e2prom' from the command line without any parameters, as I did in that image above, you'll see the dump of your card memory and nothing is modified.Please it's very important for me, anyone with my same card can help?ByeSimon. Hey bear, I have to thank you SOOOOOOOOO MUCH!!!!I did fix it, could install drivers and VisionDTV worked fine, I just tested it for some minutes and it seems ok even if I had some difficulties in receiving a channel that I could see before (but maybe this depends on the broadcaster).For everyone having this problem I suggest this solution.
I'm also sure that all those people having the TER card detected as SAT maybe could have a look at their EEPROM and find something mistaken.Anyway tomorrow I'll check if everything else is ok.Thank you VERY VERY MUCH bear, you saved meCan I offer you a drink?Finally a happy ending!ByeSimon. Maybe you should post which third party program you suspect caused the problem so that others maybe spared the same grief.I suppose it was that I tried by mistake believing it was suitable for my card.I also tried lots of other third party programs as ProgDVB, MyTheatre, DigitalWatch etc.I'm sure 100% that it wasn't ProgDVB fault. For the others, I don't know.I suggest to put this topic on the FAQ about VisionPlus problems.Another thing I suggest to people who have their card detected as SAT instead of TER is to use the EEPROM reader and compare the result to the one in this topic.ByeSimon.
Just wanted to add that I had a similar problem with my VisionPlus DVB-t, after playing around with Digital Watch 0.7, Show Shifter 3.01.2557, and installing the DirectX 9 SDK (Summer 2004) to use GraphEdit. I'm not sure which application or combination of apps caused the problem, but even after removing all these programs from my system I could not even perform the basic VisionDTV install. It would go through the first part of the install, and some 'New Hardware found' messages would pop up, then need to reboot.
After rebooting the install failed to resume where it left off, and no drivers or software were installed.I downloaded the e2prom program and compared it to Simon and bear's results. I noticed that the beginning of the memory was corrupt, though the end was fine. I applied the changes as follows, and having done this the installation proceeded properly after the reboot and I now have Vision DTV installed again. I hope this helps others in the same boat!Cheers,myk-E:e2prome2promBt8x8 EEPROM Dumper/Writer.© 2003 Illusion & Hope. Hello chapsI'm a UK DVB-T user and I have a jaded history of trying new drivers and having the card go nuts.
I never remember what I do to screw things up (not always trying new drivers, I've also tried out stuff like showshifter etc). I should be more methodical, but there you go.Anyway, I'm getting very similar symptoms - two days ago I finally stumped up the cash to get my terrestrial roof top aerial sorted out so I could get all the UK freeview channels (was only getting about half of them because he old aerial was ollllllld)So.the engineer stuck in a new high gain aerial cos I'm in a poor signal area, and I happily got my set top boxes to find all the lovely channels I'd been missing out on.Even bought some new shielded gold-plated co-ax for all the devices, plugged one in to the PC and fired her up. Well, I think it's a dead duck.Installed it into my other PC (Win2K Pro fully patched, similar but different model MSI mobo) - installed the v2.608 package as it's not an MCE machine.Fired up DTV and got the 'easy setup' box - which I remember now, there has never been any text in the popup alert on either machine, just Yes and No buttons.Clicking Yes always gave me nothing. So I click No, and it takes me to the channel list which is empty.
Pci Ven 109e Dev 036e Rev 11 Full Version Free
Close that and try scanning, and whaddaya know, it only offers the DVB-S scan, defaulting to Astra (0192 or something). Same as on the MCE box.Also notable was the fact my Terratec pro audio card failed to show up in device manager, and the drivers didn't load.So I popped the twinhan and the terratec out and cried. When I fired the machine back up with all the PCI cards out, closed it down again, breathed in, and stuck the terratec back in and fired it back up - and thankfully Win2K found my it again.I'm no hardware expert but my considered opinion is that someone has put some kind of voodo hex on my twinhan.The card itself seems physically in perfect condtion - nothing rattles when I bang it repeatedly against my head. I suppose I could try prising off the lid to see if anything has fallen off but I think I'm going to have to consign this to the round filing cabinet under my desk before I do something that could hospitalise myself.edit: oh, and yeah I've tested with known-to-be-working aerial leads. Tried the INF clearout, but none of the Twinhan BDAs I've got do the trick - always get the 'code 10' error when I install the capture portion.Bah, and grrrrr.