How to record via IEEE 1394 (Firewire) to Windows XP - Page 189

Typical Fox let's try the Hall CH.

Ok I’ve been testing every output on my DCX3200-STB HD, first one was hooking up the composite to my LG RC897T for DVD records. I found out last night when I go to FX HD and certain channels the screen goes green it could be a copyright thing in my 897T unit if the cable co has that ch flagged. Some analog channels also do this but if I change channels the picture comes back. The next thing I did was hook up my reverse transcoder to the DCX to my monitor via component. Went to FX HD and no picture loss using component outs on the DCX. So now I’m thinking it’s more on the 897T’s side as to why the screen goes green via composite in, to HDMI out to monitor. I didn’t test a straight to TV connection because it’s just not important to me atm.

This box also suffers from the PC firewire reboots if I restart the PC and leave the box on. But so far I’ve been able to record the channels I want and the 897T does a good enough job for the digital non HD stations. It really is a shame TWC flag so many stations through firewire it really is the simplest solution for the PC Oh how I miss my Adelphia days…

Wait a minute! DCX3400?!?

I thought it was a DCX3200...

Oh crap I meant, DCX3200 I'll edit my prvious post.

Aw nuts, I was hoping you had both a DCX-3200 and a DCX-3400 and had been successful at using both to record HD channels via FireWire ( the few that TWC allows you to).

Oh well, maybe someday.

I use to own a sa8300HD and that worked great for capturing video using firewire but now I have moved to Verizon FIOS and have not been able to capture any video. I have a QIP7100-P2 and edited the firewire.inf file to include the 4 lines needed to install the drivers correctly. It seems the drivers install fine under win7 according to the device manager. However when using the capdvhs program it just gives me an error message when trying to record any video. Been searching google and I've yet to find any thread or message about if the motorola qip7100-p2 has been successful for capturing video via firewire.

So guess my question is has anyone been able to capture video with the qip7100-p2 and if so what program is used to capture the video and any changes I might have to add/edit to my firewire.inf config?


thanks

Are you using the Windows 7 Legacy FireWire driver? You can't capture from a cable box without first switching the regular Windows 7 FireWire driver to the Legacy FireWire driver.

Install my version 3 FireWire .MSI package. It will automatically install the Legacy FireWire driver.


What is the error message?


I haven't heard of anybody doing it (or even trying).

If you could do me a favor and let me know what the Plug-and-Play ID's are for the Motorola QIP7100-P2, I can add it to the driver package so that it auto-installs with my .MSI. You just need to check in the Device Manager, as discussed in this post.

As I recall, I believe the new 1-port FIOS boxes are cousins of the 1-port DCX boxes. Same/similar internals... and firmware problems with firewire.

Neither has a working firewire interface, to the best of my knowledge.

Alright guys maybe you can help me out. I'm using a Motorola DCH6416 DVR, I download everything, including the extra set of drivers in the second link. When I get into device manager and try to install the tuner driver, I locate the folder that has the correct drivers and it tells me that the driver isn't there. My model is listed on the website with the second set of drivers as supported by.

Is there something critical I'm missing? Am I supposed to do something with the INF file first?

EDIT: I'm running Windows Vista 64 bit, going through this thread... there seems to be problems with 64 bit operating systems. Is that still going on now and why the drivers cannot be found?

Give up. 64-bit ain't gonna happen. The drivers can't be found because they do not exist.
I'd recommend reinstalling your OS, using 32-bit Windows instead. 64-bit Windows only real advantage is access to larger amounts of memory. Most things actually run a little bit slower on 64-bit Windows vs. 32-bit; I really look at 64-bit Windows as a negative for a HTPC. Everything I do, including h.264 video transcoding, uses well less than 768 MB of memory, so the ability to access larger-than-~3GB-of-memory means sh1t-all to me.

Give up? No way, ill just get 32 bit. I need to get Windows 7 anyways. I'm decent with computers; my understanding is that a clean install of an OS is able to "downgrade" to 32bit, correct?

My comment about giving up was only about finding 64-bit drivers.

Yes, with Windows 7 you can use either 32-bit or 64-bit (both discs are included and the same product key works for both).

I have that STB on FiOS and a WinXP-based HTPC. Although the post you linked to said the method wouldn't work in XP, I tried it anyway and it returned strings that matched the firestb.inf entries for the QIP-6416 except for the model number (QIP-7100, no -P2). So I did a Replace All and installation went smoothly. CapDVHS was able to record some but not all channels, e.g. it recorded Comedy Central HD but not AMC HD. I assume that's a 5C copy protection issue. I haven't tried the channel changer yet.

Cool! If I'm reading this correctly, I should add the following to the .inf file:

AVC\\MOTOROLA&QIP-7100&TYP_5&ID_0.DeviceDesc="Motorola AV/C Tuner Device (QIP-7100)"
AVC\\MOTOROLA&QIP-7100&TYP_9&ID_0.DeviceDesc="Motorola AV/C Panel Device (QIP-7100)"

(and also the stuff that tells it which driver files to use)

Let me know if that seems right.

If you want to determine if a channel is 5c copy protected, perform the following steps (this works on the 6412/6416/3412/3416 and probably the DCX and QIP series, though I'm not 100% sure):

1. Tune your Motorola STB to the channel that you're interested in (AMC HD).

2. Using either your remote or the buttons on the Set Top Box, press Power and then immediately press the OK/Select button.
(The timing is a little tough, so I find it easiest to just keep quickly pressing the OK/Select button right after hitting the Power button).

3. If you timed it properly, you'll see the Diagnotics screen with a lot of choices. Use the down arrow and select "d06 CURRENT CHANNEL STATUS"

4. The CURRENT CHANNEL STATUS dialog will appear and near the bottom will be "CCI: " followed by a hex number. This is the 5c status.

If it says "CCI: 0x00" then it is flagged as Copy-Freely. You could use a PC or Mac to record it to a MPEG2 TS stream.

If it says "CCI: 0x01" then it is flagged as Copy-No-More. This means that it is a copy of a Copy-Once program and can not be further duplicated. You could make multiple copies of the original Copy-Once program, but none of those copies could be duplicated. And only authorized devices are allowed to make a copy of a Copy-Once program...PC's and Mac's can not...The only authorized devices I can think of would be a DVHS VCR or a Cable/Sat/FIOS STB...actually I take that back, a PC running Windows Media Center would be able to record a Copy-Once program; it would encrypt it in a .WTV file and not allow you to play it back on other devices or decrypt it/burn to Blu-ray/etc.

If it says "CCI: 0x02" then it is flagged as Copy-Once. As mentioned above, only authorized devices can record a Copy-Once program. No second generation copies can be made. You pretty much must have a DVHS VCR to archive anything flagged in this fashion. (If you don't require a bit-perfect archive, you could look into using a Hauppauge or Black Magic capture device)

If it says "CCI: 0x03" then it is flagged as Copy-Never. My understanding is that it's illegal to flag material with the Copy-Never flag unless it is Pay-Per-View/On-Demand.

Yes, that exactly matches the second pair of lines in my edited version. And just to nail it down, here are the data I found in Device Manager:

Motorola AV/C Tuner Device (QIP-7100) Hardware IDs
AVC\\MOTOROLA&QIP-7100&TYP_5&ID_0
AVC\\MOTOROLA&QIP-7100&TYP_5

Motorola AV/C Panel Device (QIP-7100) Hardware IDs
AVC\\MOTOROLA&QIP-7100&TYP_9&ID_0
AVC\\MOTOROLA&QIP-7100&TYP_9


Ahhhh! Thanks for that. Yes, it does work on the 7100, although you're right about the timing. It worked the first time I tried it but every time since I've had to try several times and when it finally works I don't know what I did differently.

As expected, Comedy Central's CCI was 0x00 and AMC's was 0x02.

Is documentation available for the diagnostic pages? Some things are obvious, some aren't, and some apparently don't mean what I would expect them to (all channels I tried are of type DIGITAL ENC including unencrypted ones I can get with a clear QAM tuner). Also, is there any way to change channels without exiting diagnostic mode?

One strange thing happened. Yesterday the AV/C drivers seemed to be installed correctly. When I booted the computer today they were gone as though they'd never been installed. CapDVHS couldn't find a tuner and Device Manager had no entries. I ran TSReader Lite with its Firewire module to see if I still had a working connection (I did) and when I was done the drivers were back in Device Manager and CapDVHS worked again. I immediately set a restore point, just in case.

I'm not aware of any way to change the channel without exiting the Diagnostics menu.

I haven't seen much documentation, but try Googling "Motorola STB Diagnostics"
There's a little bit of info on here.


Strange. I haven't seen anything like that. It may just have been a fluke.

Anyone ever contact Dekueku, the author of CapDVHS? I sent an email to the address in the readme, but sending emails to addresses in old readme files have had a pretty bad track record for me.

--Dale--

You can also check out section 4 of the user manual for the DCT5100 found here. It is not perfect but it helps to explain most things even if you don't have this model.

I think I've solved the problem with the disappearing AV/C Tuner and Panel entries. It happened again, but they came back when I reseated the cable at the HTPC end. Flaky connection, I guess, and apparently if there's no connection the entries disappear. The fluke is that the connection just happened to come back when I tried TSRL the first time. That didn't fix it the second time around.

Thanks for that info, I now can capture using capDVHS on my qip-7100-p2. Seems alot of channels are copy-once though but its better then nothing.

thanks again..

Turned out to be crappy encoding by my cable company sadly some channels they were re-encoding only to save less than a half a mbit/s from the size of the feed lol, might as well just pass it through but no of course not hah :/ Anyway they are using really bad encoding generating lots of errors. So there is nothing I can do about It.

Just in passing, I happened to boot to WinXP today, in order to transfer this week's commercial-free edited DVHS recording ("for posterity") of SYTYCD8 from DVHS to TS on my PC using CapDVHS. I had accidentally deleted my WTV recording produced by WMC on Win7, from which I normally extract just the performances (for authoring to BluRay, also "for posterity"). Fortunately, I also copy from DCH3416 DVR recording to DVHS tape (old habit), so I actually had a fallback method to re-create the TS file for input to VideoReDo and my PC editing.

Anyway, since I'm in WinXP right now, I thought I'd pass on the device information from Device Manager in WinXP for the JVC HM-DT100 DVHS VCR which shows up when I connect my VCR to the PC. I don't know if this is relevant to your Win7 32-bit driver packaging, but I'm making it available to you anyway just in case it's helpful.

Note that this is all under the control of the original basic "MEIDVHS.ZIP" DVHS-only driver, rather than the more robust STB firewire driver for talking to DVRs. Since my PC is not connected to my DVR, I chose to install the basic DVHS-only firewire driver that I'd had success with for many years using CapDVHS. When getting started a long time ago I struggled to get the STB-firewire driver working properly, so when I finally had a breakthrough using MEIDVHS I just never wanted to change anything throughout several subsequent WinXP installs.

Note that this driver package (circa 2001) was coded by Panasonic (i.e. Matsushita Electric), primarily in support of their PV-HD1000 1st-generation DVHS VCR. But it also supports other DVHS machines that existed back at that time.

[Manufacturer]
%JVC%=JVC
%Panasonic%=Panasonic
%Hitachi%=Hitachi
%TOSHIBA%=TOSHIBA

(1) Device Manager shows:



(2) The "capture device" shown by CapDVHS:



(3) The "hardware ids" shown in Device Manager for the AV/C Tape Device are:



(4) The "compatible ids" shown in Device Manager are:




Let me know if there's anything else you'd like that I haven't already provided.

Thanks! I'll have to play around with that. My understanding is that Windows 7 (even 64-bit) automatically recognizes DVHS units and installs the needed driver, so I'm not sure that there is any advantage to me putting that into the Cable STB driver package (the only thing I can think of is adding a more descriptive name for how it appears in Device Manager). Maybe it would be useful for people still using Windows XP which (I think) does not automatically install a driver for DVHS units.

In fact, b/c Windows 7 x64 has a DVHS driver, I was looking into trying to use it and get it to work for cable STB's, but it turns out that the driver is only for the tape transport (AV/C Tape Device), not for the AV/C Tuner Device, which is what cable STB's need.

I discovered this very thing myself last night.

After finally finishing with my WinXP/CapDVHS work I rebooted to Win7 (x64), not realizing I still had the firewire cable plugged in between the DT100 and PC. I was puzzled when I saw the "new hardware detected, drivers being installed" icon active in the System Tray, unsure as to what "new hardware" could possibly have been detected.

Well sure enough, it was for the AV/C Tape Device, the DT100 machine, but only for the DVHS tape deck device. And when the whole driver install process finally completed sure enough, as you predict, there was no driver installed for the AV/C Tuner (which apparently had also been part of the discovered DT100's hardware, it would appear, and for which drivers were searched for).

So there were three green checks and one red X. But I wondered if having a driver available for the tape drive hardware would essentially be comparable to my WinXP environment, where I have minimal tape-only MEIDVHS installed as the total driver package, and yet CapDHVS works fine.

Not expecting anything further to really work properly in the x64 environment, I casually ran CapDVHS.exe, and it actually opened with EXACTLY the same "Microsoft AV/C Tape Subunit Device (JVC HM-DT100 #1)" value presented in its "Capture device" area! That was pretty amazing.

But the REC and STOP buttons were grayed out, so I couldn't actually use it. I'm not sure if the problem was 64-bit mode, or the absence of the AV/C Tuner driver, but it obviously was not going to work. And closing the program produced some kind of a "runtime error" (which I've actually seen before, even in WinXP, when the driver install process was unsuccessful).


Anyway, I've now of course removed the firewire cable and all is back to normal in Win7 x64, with the DT100 now disappeared.

Interesting.

Yeah, I'm 99.44% sure that I've used CapDVHS in Windows 7 x64 to capture from one of my JVC 30K DVHS units. It may be that you must revert to using the Windows 7 "legacy" FireWire driver. And you may also need to run CapDVHS with administrator rights*. Also, if you have a copy of Arcsoft Showbiz or Arcsoft Total Media Extreme, you can use that to capture from your cable box (instead of using CapDVHS). Arcsoft Showbiz is bundled by OEM's in a lot of video capture hardware such as the Hauppauge HD-PVR and Hauppauge Colossus, devices that allow for HD captures from anything with component video output or unprotected HDMI video output. I own 3 copies of Arcsoft (two are OEM slimmed-down versions bundled with my Hauppauge HD-PVR and Colossus, and 1 that I purchased from Arcsoft because I wanted the full non-OEM version). Even the slimmed-down OEM version of Arcsoft Showbiz that came with my Hauppauge Colossus allows me to capture from my Motorola DCH-3416 cable box DVR. And, like CapDVHS, it captures everything lossless in the MPEG-2 TS container. *Note: this will only work on 32-bit Windows XP/Vista/7 (any you probably need to be using the "legacy" FireWire driver if you're on Windows 7). It requires that you install the cable STB FireWire driver, otherwise Arcsoft wouldn't recognize your AV/C Tuner capture device.


A few months ago I was playing around to see if I could capture from my Motorola DCH3416 by routing it through a DVHS VCR and then from the DVHS VCR to my Windows 7 x64 computer. That's how I learned the hard way that MS only coded the driver for the tape transport, not the tuner.

My thinking was that, since MS had a driver that allows Windows 7 to talk to my DVHS VCR, all I need to do is run the cable box FireWire signal through it. But the only thing Microsoft allows their driver to do is read whatever the DVHS unit is playing through its tape transport; it doesn't route any FireWire signals originating from elsewhere. So for all intents and purposes it's worthless to me, as I am completely unwilling to record everything to DVHS first and later offload via CapDVHS...that's just too much effort compared to my current setup with Windows 7 x86.

Anyways, I'll try to play around with using Windows 7 x64 to capture from my JVC 30k DVHS unit, hopefully sometime this evening or tomorrow evening.

*Important note: It's been my experience that once you receive a CapDVHS error message, you often must reboot your cable box to fully correct the situation. It seems that sometimes when the FireWire gets pissed off it sort of locks up and will remain unuseable until the cable box is rebooted (which obviously sucks because then you must wait for 1-3 days until your guide is fully repopulated).

I don't see how that could be. I thought the whole essence of this thread was that 64-bit firewire drivers didn't exist which would enable firewire recording using CapDVHS. I thought you HAD to be using 32-bit Windows (either XP or 7).

Also, the REC and STOP buttons on CapDVHS were grayed out for me. So obviously something is missing that is making it unhappy.



What driver would that be? And is it usable on 64-bit Win7? I thought nothing like this existed. I thought you could only run with 32-bit WinXP or Win7?

Anyway, the Win7 accidental situation was just that... an accident. I have no problem with booting to WinXP for the very occasional situation where I want to make a PC clip from some copy-freely content on DVHS (which had to have been offloaded in the first place from my DCH3416, which I virtually never use anymore since I have my Ceton-based HTPC).

Instead, my current workflow is simply to record that copy-freely program (to WTV) on my Ceton-based HTPC using Win7 WMC in the first place, and then edit it using VideoReDo. Most recent example of that was near the end of the "Glee" season, to extract the amazing Lea Michele rendition of Barbra Streisand's "My Man". Just had to have that retained for posterity in its original HD/5.1 form.

Yesterday's issue with the SYTYCD8 episode from [DCH3416 to] DVHS to PC was a "should not occur" situation, because of my accidental deletion of the recorded WTV episode from my HTPC before having an opportunity to work on it with VideoReDo.

Yeah, you gotta love VideoReDo! And I'm really glad they made some recent improvements to their handling of WTV files!


There are no 64-bit FireWire drivers for the "AV/C Tuner Device", but there are 64-bit drivers (from Microsoft and built into Windows Vista and 7) for the "AV/C Tape Device". To record the playback from a DVHS unit, all you need is the "AV/C Tape Device" drivers. But to record from a cable box you'd need the "AV/C Tuner Device" drivers, which don't exist for 64-bit Windows.



I haven't seen this behavior, but there could be several reasons for it. To simplify things, perhaps you should go into the Control Panel and turn off User Account Control. You'll also probably need to switch to the legacy FireWire driver (see below for info and links).


The legacy FireWire driver is a Microsoft driver which is included with Windows 7 (both the 32-bit and 64-bit releases). You just need to go into the Device Manager and have it switch from the default FireWire driver to the legacy FireWire driver.

The steps can be found on the IEEE1394 trade association's website:
http://www.1394ta.org/consumers/FAQ....gacyDriverWin7
(look for the "How do I use a legacy 1394 driver with Windows7?" section.

The steps are:
1. Right-click on My Computer
2. Select Properties
3. Select Device Manager
4. Select 1394 Host Controller
5. Select Reinstall driver
6. Select Show me drivers on my system
7. Choose legacy 1394 driver

I've made a document with screenshots that walks through the steps and also gives a bit more information about FireWire and a little bit of info about using CapDVHS:
Click here for the PDF format
or
Click here for the XPS format (I recommend this, as Windows 7 can view XPS files automatically without any need to install Adobe Reader).

I see. Haven't been reading all of the posts in this thread, so it's my own lack of knowledge about this driver.

But following the few simple instructions to update driver software, sure enough the "legacy driver" is available for selection. The one which had previously been installed was "Texas Instruments 1394 OHCI Compliant Host Controller". I've now changed it to the "legacy" driver you alluded to.

When I plugged in the firewire cable to the DT100, the name of the installed device in Device Manager has now changed from yesterday. It's now called "JVC HM-DT100 AV/C Tape Recorder/Player" whereas with the original driver it was shown as "AV/C Tape Device" in Device Manager.



Interestingly, the "Capture Device" shown in CapDVHS exactly matches this new name in Device Manager using the "legacy" driver, whereas they didn't match yesterday with the original driver.

Unfortunately, it does not seem to make any difference. The REC and STOP buttons on CapDVHS are still grayed-out.




Now perhaps there's something else at play here, which is responsible for the failure of CapDVHS to get started properly and enable the REC and STOP buttons.

When I start the program, I get an error message:



Don't know what this is or means (although I believe the text should read "SampleGrabber is not registered"), but perhaps it's the "giant clue" that must be resolved for me in my x64 environment. Have you actually been able to capture from your JVC 30K machine using CapDVHS on an x64 version of Win7?


P.S. - I run with UAC off, and my user is the Administrator. So I don't think that's a factor.

Yeah, I'm thinking that's just more evidence that the FireWire firmware on DVHS units and cable boxes require the legacy FireWire driver in order to properly communicate with the computer.



Crap...the SampleGrabber error, I'm well familiar with that message from horsing around with getting Windows Server 2008 (x86) to work with CapDVHS and my .MSI FireWire package. Now I'm starting to wonder if it was Vista x64 instead of Windows 7 x64 that I used to capture from my DVHS unit.

Microsoft omitted qedit.dll from Windows Server 2008, which causes the same error message on that OS. I found that I had to copy qedit.dll from Windows Vista or earlier (and also add some registry so that Windows knows how to use SampleGrabber) in order for CapDVHS to function on Windows Server 2008. I also found that copying qedit.dll from Windows 7 did not work; it had to be from an older version of Windows (I successfully tested with qedit.dll from Windows XP and Windows Vista).

I speculate that Microsoft removed qedit.dll from Windows Server 2008 for reasons of security (and probably also because a server OS doesn't have much business performing the kinds of functions that qedit.dll provides). And they likely made some rather extensive changes to qedit.dll for Windows 7, perhaps omitting the SampleGrabber altogether.

I documented the qedit.dll info in a .RTF file that installs if you run my .MSI FireWire package on Windows Server 2008 (x86). Here's what it says:
----------------------------------------------------------------------
Info About a Problem with CapDVHS on Windows Server 2008
C:\\Windows\\System32\\qedit.dll is not included with Windows Server 2008. This file is required by CapDVHS. In order to use CapDVHS, you must copy qedit.dll from a 32-bit copy of Windows XP, 2003, or Vista (but NOT from Windows 7, as it is not compatible). If you insert a Windows XP CD, the following command line can be used to extract the qedit.dll file to your System32 folder:

extrac32.exe "Full path to\\qedit.dl_" "%SystemRoot%\\System32\\qedit.dll"

So, if your CD\\DVD\\BD drive is E:\\, you could use this command line to copy qedit.dll:

extrac32.exe "E:\\I386\\QEDIT.DL_" "%SystemRoot%\\System32\\qedit.dll"

(The extrac32.exe file comes with Windows Server 2008 and is used to extract the qedit.dll file from the QEDIT.DL_ file, which is compressed.)
*Note: I have tested this using qedit.dll from Windows XP with SP3 and Windows Vista (no service pack, but all critical and important patches applied). I have not tested this using qedit.dll from Windows Server 2003, but I would truly be shocked if it didn't work. I have also tested it with qedit.dll from Windows 7 (no service pack, but all critical and important patches applied) and it DOES NOT WORK. Apparently there are differences with Windows 7's qedit.dll that render it incompatible. I suspect that I could do some research and create another .reg file that would get it to work, but I'm not going to. Sorry. Use XP's or Vista's. (and, just to be clear, Windows 7 has no problem running CapDVHS; it's just that you can't transplant it's qedit.dll over to Windows Server 2008 and get CapDVHS to work).
In addition to copying qedit.dll, you must register qedit.dll by running the Qedit_Registration.reg file located in the CapDVHS folder.
More information can be found here:

http://groups.google.com/group/micro...44d2111e?pli=1

If you read the thread (and other similar threads), it seems that Microsoft made the decision to remove qedit.dll because they felt there was too much crap in there that was insecure and/or depricated. I speculate that Microsoft made a lot of changes to qedit.dll for Windows 7 in order to shore up security. It's likely that I would need to run some analysis tools and build a different .reg file in order to get Windows 7's copy of qedit.dll to satisfy CapDVHS on Windows Server 2008.

----------------------------------------------------------------------

I also include a .REG file that contains the registry needed to get things working on Windows Server 2008:
----------------------------------------------------------------------
Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\\CLSID\\{C1F400A0-3F08-11D3-9F0B-006008039E37}]
@="Sample Grabber"

[HKEY_CLASSES_ROOT\\CLSID\\{C1F400A0-3F08-11D3-9F0B-006008039E37}\\InprocServer32]
@="C:\\\\Windows\\\\System32\\\\qedit.dll"
"ThreadingModel"="Both"

[HKEY_CLASSES_ROOT\\CLSID\\{083863F1-70DE-11D0-BD40-00A0C911CE86}\\Instance\\{C1F400A0-3F08-11D3-9F0B-006008039E37}]
"FriendlyName"="SampleGrabber"
"FilterData"=hex:02,00,00,00,00,00,20,00,02,00,00,00,00,00,00,00,30,70,6 9,3*3,\\ 00,00,00,00,00,00,00,00,01,00,00,00,00,00,00,00,00,00,00,00, 30,74,79,33,00,*\\ 00,00,00,60,00,00,00,60,00,00,00,31,70,69,33,08,00,00,00,00, 00,00,00,01,00,*\\ 00,00,00,00,00,00,00,00,00,00,30,74,79,33,00,00,00,00,60,00, 00,00,60,00,00,*\\ 00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00
"CLSID"="{C1F400A0-3F08-11D3-9F0B-006008039E37}"

----------------------------------------------------------------------

I sort of doubt that it'll work for Windows 7...I'm thinking that it may be necessary to downgrade qedit.dll to the version from Windows Vista (if Windows 7 will allow that...qedit may be a protected file under the jurisdiction of Windows Resource Protection, and defeating that may be a bit of a trick).



I thought so, but I'm starting to think it was Vista x64 instead. I'll have to test it, but it'll have to wait a day or two.

Well, I'm a bit reticent about simply copying qedit.dll from my existing 32-bit WinXP \\Windows\\System32 folder and putting it into \\Windows\\System32 on 64-bit Win7. In fact, there is already one there, as well as a slightly smaller one in \\Windows\\SysWOW64.



I see no such Qedit_Registration.reg file in the unzipped CAPDVHS distribution zip file. Where is this file supposed to be found??

Again, I'm not much inclined to tamper with this basic functionality in Win7. Surely it doesn't seem right to replace the existing version in 64-bit Win7 with an old 32-bit version from WinXP. And what about the SysWOW64 copy... leave that one as is? Isn't that a significant mismatch?? Surely this isn't right.

Seems like highly unrecommended tampering, in my opinion, and likely to result in doom and failure.