Search options (Page 2 of 8)

Sometimes the written word can get misunderstood on these forums.  I wasn't cynical at all.  I literally was thankful that you pointed out the specific file for me.  Most of the time I get stuff like "it doesn't work".  Like that's supposed to be helpful to me.  By pointing out the file you saved me the time, effort, and aggravation of having to pinpoint the problem myself.  Anyway, I've made the same mistake myself several times where I've taken what someone wrote entirely wrong.  When there's no tone of voice or body language to observe it can be tough to tell if someone is being considerate or being a jerk.

The problem with Widcomm based bluetooth adapters is the licensing mechanism that they use.  It's a different install set for just about every vendor (and each chipset per vendor).  I know that there are "generic" Widcomm stacks out there, but the ones that are actually Widcomm code are more than likely not legal to distribute.

I started a Dell Bluetooth DP a while back to cover the various models that we use at my main job.  You would think that since they are all Widcomm that there would be a tremendous amount of statistical redundancy allowing for some crazy 7-Zip compression.  But sadly, this is not the case.  Having just four separate Dell models in one DP yields a .7z file close to 150MB.  Then of course is the trouble to make exception installers for all of these things <sigh>.

It would seem from what I have read here that adapters using the Toshiba stack seem to all work with the same install set (or am I missing something here?).  Unfortunately I think that so far as Widcomm goes, we're pretty much screwed.  You can quite easily make a DP consisting of the various .inf, .sys, and .cat files, but to get the full boat install would require a great deal more.

I like that this uses sqlite.  That is the direction that I eventually wanted to go in.  I haven't tried this out yet, but still wanted to say good job for implementing a database method.

Well it may end up being necessary to break driver signing, which of course would necessitate the end user enable the option to ignore driver signing.  It does not look as though there will be a perfect solution.

Looking at the .inf file myself, it would appear to be for both Vista and pre-Vista operating systems.  I would imagine that I could break the driver signing by cutting out all of the Vista specific code.

I use MRTG which is Perl based and it's incredible.  Plus I like that Perl is cross platform.

Unfortunately for me I will be supporting Windows until I retire.  And it will be XP for the next six years if I have anything to say about it.

Already there

I've been using Kubuntu as my primary OS on my desktop (still XP on my laptop) for over a year now.  I dare anybody to do that and still contend that Windows is anything but a piece of crap.

The more that I am getting into this the more I am beginning to think that I may need to port the code over to another environment.  VBscript offers good but not great support for regex.  There seem to be some missing functionality in the area of conditional processing and negative lookaround.

Updated

Just added a seperate script for collecting monitor HWIDs.  Also it appears as though monitor hwids are just like some other very short hwids.  It isn't optimal but this may wind up being a solution for now.  Or I may just have to perform two regex operations for everything in one script.

20081021 - v1.2.0
* Now picking up more HWIDs - and unfortunately a couple that it shouldn't  Getting closer.

I don't know everything about HWIDs, but in my testing with this script I've noticed a couple things that may or may not be worth looking into.  First of all, if you important the resulting .csv file into a spreadsheet program, sort the date by column C primarily and column B secondarily.  The HADAUDIO entries will be near the top and immediately I notice duplicate HWIDs between different vendors and within the same vendor but in different driver sets.  Again, I'm not too expert on this so I don't know if there are acceptable circumstances when duplicates are to be expected.

Yea, I'm still working my way through regular expressions.  I know it's possible to construct one that will catch everything, it's just that I'm pretty new with them.

You should just have to double click on the file itself.  It only requires that you have WSH on your system which you should unless it was removed by nLite.