Posted on 24-12-2011
Filed Under (Computing) by Steve

Ok, so I think the title makes it blatantly obvious what this post is about but in case you were wondering, this is about my recent purchase of the above – a Compro E750 dual tuner pcie tv card, and how to resolve some of the problems associated with installing it to Windows 7 64 bit.

Its quite simple really, the production 64bit drivers – both those shipped in the box and those available online DON’T WORK so don’t install them; they shall produce an array of artefacts and sound issues; when I first installed, every channel was buggered – the trouble is, I knew it had to have been a problem with the card as I was upgrading from a Compro U80 usb tv tuner that was working fine.

My Spec:

Crucial 8GB (2 x 4GB) 1333MHz DDR3
Intel Core i5 2400 3.1GHz Sandybridge
Gigabyte mATX (can’t remember the motherboard spec and not at the unit) fully up to date bios
Windows 7 Home Premium 64bit with SP1

After spending time searching, I happened across this post at Compro’s site though the beta drivers mentioned were unavailable for download but I was able to get into the ftp site and download version 1.05.520 an action that may have cost it for the rest of you because attempts to re-enter the site has resulted in password security – I apologise.

Anyway to the point, I can reports that these drivers do work producing excellent quality sound and video feeds across all 111 channels (this includes radio); the following instructions can be used even if you have already installed the stock drivers:

  1. Goto Control Panel > System > Advanced System Settings > Hardware > Device Installation Settings and change / ensure that “No let me choose what to do” is set – this ensures that you can control where drivers come from and in this instance stops Windows from installing the stock drivers
  2. If you have already installed the drivers, then uninstall them by going to:
    Control Panel > System > Device Manager > Sound, Video and Game Controllers
    and choosing to both uninstall the device and to delete the drivers from the system; reboot
  3. On Windows boot-up, extract the attached driver installation package and run
  4. Everything should now work

Just a word of warning, these drivers have not been released for production as users are reporting mixed results; however, they are working for me.
Download Here  << Open link in Chrome or Firefox if not working with IE (not working with my ie8)

(0) Comments   
Posted on 12-06-2011
Filed Under (Computing, Just a Thought..., Random Musings) by Steve

It puzzles me

Why would a programmer want to lock his code?

From a compiling perspective it is more a matter of the programme could not be without first compiling which has the effect of locking the code as the end-user has no real means of opening the project but from a macro perspective; what could possibly be gained from preventing such access?

Granted, that by preventing access, a programmer can ensure that the programme may still run as intended without fear of accidental or malicious damage but this seems to be the only real reason for such an act.

In my experience however I believe in allowing full access code, doing so satisfies several goals:

  • Usually, should a user accidentally gain access to the editor window they either take a poke about mostly run away.
    But for those that stick around
  1. This is a golden opportunity for a key piece of knowledge sharing; maybe the user hasn’t encountered code before and being eager to learn [and providing you as the developer have left adequate notes (which I'm sure you shall)] they shall have the best possible chance of learning how to programme from you; how cool is that? Teaching by proxy!
  2. Perhaps the user has had some programming experience but your code is far more superior to their knowledge and sets out to perform a very complex task, one in which they may have attempted but could not succeed; by looking at your code, you shall have shown them the way without ever intending to (you may add another gold star to the teaching by proxy score-sheet).
  3. Maybe the end user is a seasoned developer and by looking at your code, they have identified areas for improvement; of course, it may only shave milliseconds off each sub but like pennies, they do add-up. Whilst you may not be available to see it, your code may one day turn-up on the net showing how the improvement was made.

For me, points 1 & 2 are the most important; I may not be the greatest developer, I still have far to go, but by allowing access to my code, I  believe I am providing something priceless – the gift of knowledge.

Though if you believe that I am wrong, please do enlighten me.

(0) Comments   
Posted on 28-09-2010
Filed Under (Computing) by Steve

Well here it is hopefully…

I have finally completed my guide to Microsoft Office 2003:

An End Users Guide to Microsoft Office 2003 (627)


An 80 page reference manual to most of the features of Excel, Outlook, PowerPoint & Word for basic & intermediate users; also includes interface improvements & a list of 60+ of the most used Excel functions.

This guide has been written with the basic & intermediate office / home user in mind and at 80 pages cover to cover, you would struggle to argue with this.

Oh, and  by the way, whilst I realised that there was this gaping hole in the market for a reference manual of this type (the quick user guide for under 100 pages type) and decided to write one just to share the love/knowledge whatever, this guide is completely 100% free, please feel free to distribute at will,

but, should you being feeling a little flush at the moment, contributions can be paypal’ed to

(0) Comments    Read More