Darth_vader
Member
- Joined
- Apr 5, 2013
- Messages
- 327
First off, does anybody know of an Ext-IO DLL that's actually compatible with Win2K and HD-SDR?
I've just shot almost three extremely maddening hours trying to get what is apparently my RTL2832U/E4000 (considering I actually paid for a R820T, and that's what it's marked as on the chassis) going on that box to absolutely no avail. I have tried using Zadig and both the usual Spench USRP package (http://wiki.spench.net/wiki/USRP_Interfaces) that I seem to see referred to in just about every tutorial I've come across, and the "other" Ext-IO from https://github.com/josemariaaraujo/ExtIO_RTL that somebody had referred to in an earlier thread. The Ext-IO option is always grayed out in the HD-SDR options flyout with an error message saying it can't be loaded. It also gives me error messages on startup depending on which Ext-IO plugin I have selected; the Spench one gives me a reference to an invalid instruction in my WS2_32.DLL file (component of Window$ that I can't do much about) and the josemariaaraujo file gives me an error message relating to the procedure entry point EncodePointer not being found in my KERNEL32.DLL file.
And what's the deal with this "WinUSB" thing and where do I download it from? Zadig just tries to stick me with the libusb-win32 or libusbk options which, from nearly all accounts I've read, don't work.
I'm reluctant to start using SDR Sharp (not like it actually works--I've tried) since that'd mean I'd have yet another interface to learn, just to add to the already-incurred madness. I now have a splitting headache from all this and am about to just give up and ship the thing back to Nooelec.
And lest you should want to run it by me that I should downgrade my box to XP, bear in mind that, in all likelihood, it will never happen: the digital restriction management incorporated in XP makes it practically worthless for what I use it for, and the "product activation" crap Micro$pend have put in helps to increase its uselessness, since that machine is not (and never will be) connected to any network. Unless somebody wouldn't mind telling me where I can download a patch to disable or (preferrably) bypass that needless little bug, since I do have an OEM XP installer disc somebody gave me some time ago...
I've just shot almost three extremely maddening hours trying to get what is apparently my RTL2832U/E4000 (considering I actually paid for a R820T, and that's what it's marked as on the chassis) going on that box to absolutely no avail. I have tried using Zadig and both the usual Spench USRP package (http://wiki.spench.net/wiki/USRP_Interfaces) that I seem to see referred to in just about every tutorial I've come across, and the "other" Ext-IO from https://github.com/josemariaaraujo/ExtIO_RTL that somebody had referred to in an earlier thread. The Ext-IO option is always grayed out in the HD-SDR options flyout with an error message saying it can't be loaded. It also gives me error messages on startup depending on which Ext-IO plugin I have selected; the Spench one gives me a reference to an invalid instruction in my WS2_32.DLL file (component of Window$ that I can't do much about) and the josemariaaraujo file gives me an error message relating to the procedure entry point EncodePointer not being found in my KERNEL32.DLL file.
And what's the deal with this "WinUSB" thing and where do I download it from? Zadig just tries to stick me with the libusb-win32 or libusbk options which, from nearly all accounts I've read, don't work.
I'm reluctant to start using SDR Sharp (not like it actually works--I've tried) since that'd mean I'd have yet another interface to learn, just to add to the already-incurred madness. I now have a splitting headache from all this and am about to just give up and ship the thing back to Nooelec.
And lest you should want to run it by me that I should downgrade my box to XP, bear in mind that, in all likelihood, it will never happen: the digital restriction management incorporated in XP makes it practically worthless for what I use it for, and the "product activation" crap Micro$pend have put in helps to increase its uselessness, since that machine is not (and never will be) connected to any network. Unless somebody wouldn't mind telling me where I can download a patch to disable or (preferrably) bypass that needless little bug, since I do have an OEM XP installer disc somebody gave me some time ago...
Last edited: